> 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/security/custody-and-escrow.md). # Custody and escrow ## Where your contribution goes When you contribute to a Vault campaign, your SOL goes into that campaign's own escrow account on Solana. It does **not** go to: * the campaign creator * a Vault company wallet * a pooled or commingled account shared across campaigns Each campaign has its own escrow. The address is public. ## Verifying it yourself The campaign funding address is shown on the campaign page. You can look it up on any Solana block explorer and confirm the escrow balance directly, without relying on anything Vault's interface tells you. This is the point of building on a public chain: you do not have to take Vault's word for where the money is. ## Who can move escrowed funds Escrowed funds can only move along the paths the protocol allows: * **To fulfillment**, when the campaign meets its success conditions. * **Back to contributors as refunds**, when the campaign fails or is canceled. There is no discretionary withdrawal path. Vault cannot move escrowed contributions outside these paths, and neither can the campaign creator. ## Fixed terms The goal, deadline, and fee rates are locked when the campaign is created. No party can change them afterward — not the creator, and not Vault. The refund fee cap is also fixed in SOL at creation, so it does not depend on a price feed at the time a refund is processed. ## Unsupported assets Vault campaigns are funded in SOL. Sending any other asset to a campaign funding address is not supported, and such transfers cannot be recovered. The escrow account's derivation, the contribution receipt that records your entitlement, and the rent rules that keep custody accounts alive are described in [Accounts and PDAs](/smart-contracts/accounts-and-pdas.md). --- # 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/security/custody-and-escrow.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.