> For the complete documentation index, see [llms.txt](https://docs.eiva.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eiva.money/the-vault.md). # The vault Deposits are held in a Safe multisig. Its address is published on the Transparency page and in the app and never changes, so you can check the balance on-chain at any time without going through us. Signers: \[number of signers needed to move funds, and who they are: Alpha] What moves: USDC leaves the vault only to fund a verified, approved invoice, to stake idle USDC, or to pay withdrawals, redemptions and interest. Invoice funding is converted to sterling on the way out and paid to the creative; when the invoice settles, the funded amount is converted back and returned to the vault. Every movement is tagged in the ledger. Idle USDC: money waiting for approved invoices is staked in \[idle venue: Alpha] rather than left idle. What it earns is vault income and follows the same order as invoice fees. See [Where the yield goes](/where-the-yield-goes.md). Networks and assets: USDC and USDT. \[Whether USDT deposits are held as USDT or converted to USDC, and what the note pays in: Alpha] The vaults are available on Ethereum, Solana, Robinhood Chain, Avalanche and BNB Smart Chain. \[Networks live at launch: Alpha] Deposits of anything else, or on any other network, aren't accepted and can't be recovered by the app, so check before you send. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eiva.money/the-vault.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.