> 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/smart-contracts/program-ids.md).

# Program addresses

Vault's programs and protocol accounts are deployed on Solana mainnet. Every address below can be inspected on any Solana explorer.

## Programs

| Program        | Address                     |
| -------------- | --------------------------- |
| `vault-core`   | `<VAULT_CORE_PROGRAM_ID>`   |
| `vault-escrow` | `<VAULT_ESCROW_PROGRAM_ID>` |

## Protocol accounts

| Account          | Address                      |
| ---------------- | ---------------------------- |
| Global config    | `<GLOBAL_CONFIG_ADDRESS>`    |
| SOL treasury     | `<TREASURY_SOL_ADDRESS>`     |
| Execution wallet | `<EXECUTION_WALLET_ADDRESS>` |

## Verifying a campaign

You do not need any of the addresses above to verify your own contribution. Every campaign page shows its escrow address, and you can look that address up on an explorer to confirm the balance directly.

The addresses on this page are for verifying the protocol itself: that the program a campaign runs under is the program Vault publishes.

## Upgrade authority

The programs are upgradeable. The upgrade authority is held by Vault.

This is stated plainly because it is a real trust consideration: an upgrade could change program behavior for campaigns created afterward. Terms fixed on an existing campaign account — goal, deadline, fee rates, caps — are stored per campaign and are not altered by later global configuration changes.


---

# 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/smart-contracts/program-ids.md?ask=<question>&goal=<endgoal>
```

`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.