> 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/campaigns/creating-a-campaign.md). # Creating a campaign ## Submitting a request Campaigns start as a request. You tell Vault: * what you are raising for, and the campaign's stated purpose * your funding goal, in SOL * your deadline * the project or token the campaign supports **No wallet connection, account, or registration is required to submit a campaign request.** Contact details are optional. ## What happens next Vault reviews the request. If it proceeds, a campaign funding address is created automatically on Solana. At that moment the campaign's terms are locked: * the funding goal * the deadline * the fee rates that will apply * the funding policy **None of these can be changed after creation.** This is deliberate — contributors need to know that the rules they evaluated when contributing are the rules that will decide the outcome. ## Custom campaigns Not every campaign fits a standard template. Vault supports custom campaign requests for projects, organizations, and structures that need something different — a specific fulfillment arrangement, an identified beneficiary, or a non-standard deliverable. Submit a custom request through the application and describe what you need. ## What creators receive A successful campaign does not transfer the escrow balance to the creator as an unrestricted cash payout. Successful funding is used to fulfill the campaign's stated purpose. Where the campaign is service-backed, Vault purchases or arranges the associated service or deliverable. Where the campaign has a disclosed beneficiary or charitable structure, funds are directed according to the campaign's disclosed terms. --- # 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/campaigns/creating-a-campaign.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.