A Solidity contract compliance-gated asset. EVM wallets can already hold it — that was never the question. The hard part is Solana. Bloom: deploy that one issuance on Rome, and both EVM and Solana wallets buy and hold it — one contract, one allowlist, no mirrored token.

What's real vs what's yours: The on-chain enforcement — refusal, admission, the gate agreeing — is real, and re-runs on demand with a live purchase each time. The eligibility decision stays yours: in production the issuer runs KYC in-house. Bloom is a testnet reference.

If you're bringing a protocol to Rome, the oracle question is already answered. The Oracle Gateway exposes Solana's Pyth and Switchboard accounts through the interface your Solidity already uses — Chainlink's latestRoundData(). No relay, no new oracle network, no code changes.

Need a feed that isn't listed? Three paths. Published on Solana: clone a direct adapter against that price account. Want the cached path: clone a cached adapter and crank refresh() yourself. Nobody publishes it: CachedFeedAdapter wraps any source you run.

Building with an AI agent this weekend? Rome is agent-ready: one CLI for terminal agents, one MCP server for the rest — grounded facts from the live registry, zero hallucinated addresses, repos with AGENTS.md your agent reads to onboard itself. How 👇

Rome runs the EVM natively inside the Solana runtime. One application, EVM users and Solana users — and your agent already knows how to build it. Docs: docs.rome.builders