Reference
Program IDs
xVault's three Anchor programs, their source-declared addresses, and deployment status.
xVault is split into three Anchor programs on Solana. The IDs below are the addresses declared in source today; they are the planned xVault addresses for integration and documentation.
Pre-deployment
These program IDs are not yet documented as deployed and verified for a live target environment. Treat them as source-level IDs pending deployment. A formal deployment announcement will update this page with cluster + slot metadata.
Current program IDs
| Program | ID |
|---|---|
xvault_vault | A8gnNqXsVFon2h6wGwUWyBFMDY5nrjNJfc1FvW6k2LMm |
xvault_oracle | 2VsYpWPX86ZMF2BCWZ9X6EiKe33ooHGLP5yPE4r1UnSU |
xvault_rewards | 6T7wbptCbfmzrmdrLeSfKCXDxJMrqcrk1UxLRJBS7y8m |
Responsibilities
| Program | Owns |
|---|---|
xvault_vault | Vault state, deposits, withdrawals, rebalance bookkeeping, fee accrual, pause controls |
xvault_oracle | Keeper-pushed NAV snapshots with per-leg multiplier-aware entries |
xvault_rewards | $VLT staking, lockup tracking, epoch Merkle roots, claim proofs |
See Architecture for the full component map and data flow, and Reference → Instructions for the per-ix authority and effect table.
Notes for integrators
- Verify deployment status before wiring production clients. The canonical status lives in this page and the release notes.
- IDL + SDK artifacts are the canonical source for instruction layouts. Consume
packages/sdkrather than hand-rolling account parsing. - No mainnet assumption. Do not assume these IDs imply mainnet availability until the rollout is complete.
- Squads authority. All admin-authority ix require a Squads v4 multisig signer; integrating clients should expect multi-sig batching rather than single-wallet submission for those paths.