recSOL Metadata: The Boring Stuff That Matters

Every Solana project needs metadata. Token addresses. Program IDs. RPC endpoints. Mint authorities. The configuration that everything else depends on.

Scatter it across repos and you get inconsistency. Hardcode it and you get maintenance nightmares. recSOL centralizes it.

What Lives Here

The RECTOR ecosystem spans multiple projects — MEV tools, token infrastructure, deployed programs. Each needs to reference the same addresses, the same configurations, the same constants.

recSOL is the single source of truth:

• Token metadata (symbol, decimals, mint address)
• Program IDs for deployed contracts
• RPC endpoint configurations
• Network-specific settings (devnet, mainnet)

Why Bother

Metadata repositories arent exciting. But theyre essential. When you need to update an RPC endpoint, you update one file. When you deploy a new program version, the ID lives in one place. When someone forks a project, they know exactly what to change.

The alternative is grep across ten repos hoping you found everything. Been there. Never again.

Contents: Token metadata, Program IDs, RPC configs, Network settings

Ecosystem: RECTOR LABS Solana projects

Link: GitHub