> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/apps-on-rome/bloom.md). # Bloom — RWA issuance Bloom issues and holds **permissioned real-world assets** on Rome. An asset is an ordinary Solidity contract, deployed once, whose rule for *who may hold it* lives inside the contract and is enforced on every transfer. The same asset is reachable from an EVM wallet and from a Solana wallet — one deployment, both wallet worlds, with no bridge and no second token. This documentation is written per audience, because the audiences do not overlap: an issuer never buys, a Solana holder never issues, and a builder needs the contract surface none of the others touch. ## The guides * [**Investing**](/apps-on-rome/bloom/investing.md) — for a buyer. Browse an asset, check eligibility, apply for the allowlist, buy, and hold — including the one thing that is genuinely different for a holder who signs with a Solana wallet. * [**Getting funds to Rome**](/apps-on-rome/bloom/funding.md) — the cash-in before the buy. Bridge USDC or ETH in from Sepolia, then wrap the bridged gas into the wUSDC every sale is priced in. * [**Issuing**](/apps-on-rome/bloom/issuing.md) — for an issuer. The console, the creation wizard, the per-asset console sign-in gate, and each of the six administration tabs. * [**Building on Bloom**](/apps-on-rome/bloom/building.md) — for a developer. A ten-step method to take a Solidity asset onto Rome as a permissioned token, open it to both wallet worlds, and plug in your own KYC — with the real contract surface and code. The screenshots throughout are not mock-ups. Two evidence pages trace them to real transactions on chain: * [**Evidence — an issuer**](/apps-on-rome/bloom/evidence.md) — the demo asset issued and administered: the piecewise deploy, the sale, the batch allowlist, the roles. * [**Evidence — an investor**](/apps-on-rome/bloom/evidence-investor.md) — the same asset bought twice, once from an EVM wallet and once from a Solana wallet, with no bridge. ## What "permissioned" means here > The rule travels with the asset. Who may hold it is enforced by the asset contract itself, on every transfer — not by this website, not by a bridge, and not by a sequencer filter. The chain holds one fact per address: a single yes-or-no. No documents and no personal data ever touch this app or the chain. The compliance model in full lives in [COMPLIANCE.md](/apps-on-rome/bloom/compliance.md); the two-lane (EVM and Solana) mechanics your holders use are in [LANES.md](/apps-on-rome/bloom/lanes.md). These guides link to them rather than restating them. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rome.builders/apps-on-rome/bloom.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.