> For the complete documentation index, see [llms.txt](https://docs.vault.ky/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vault.ky/getting-started/supported-ecosystems.md). # Supported ecosystems Vault supports campaigns for projects across seven blockchain ecosystems: * Solana * Ethereum * Base * BNB Chain * Monad * Robinhood Chain * HyperEVM ## Project identity is not custody This is the single most important distinction on this page. A campaign can display a token or project associated with any of the ecosystems above. That is **project identity only** — it describes what the campaign is for, and it is used for branding, token metadata, and market data on the campaign page. **Funding and escrow always remain on Solana.** Every Vault campaign is funded in SOL. Every escrow account is a Solana account. There is no bridge and no multichain custody. So a campaign supporting an Ethereum project still collects SOL, still holds it in a Solana escrow account, and still refunds in SOL if it fails. ## Why it works this way Keeping custody on a single chain keeps the trust model simple. There is one escrow implementation to audit, one set of state transitions to verify, and no bridge risk anywhere in the funding path. --- # 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.vault.ky/getting-started/supported-ecosystems.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.