GLAM Mint StagingStaging
validate_aum
Validates vault AUM after pricing instructions populate priced protocol records.
Applies toVaultTokenized VaultSingle-Asset Vault
Required conditions
- Mint actions must satisfy the linked GLAM state, Token-2022 mint configuration, mint policy, and any request queue or escrow state involved in the flow.
- All pricing instructions for the same pricing operation must be in one Solana transaction; splitting them across multiple transactions is unsupported and can produce stale, inconsistent, or rejected NAV calculations.
- Oracle, token-account, position, and pricing-record accounts must all refer to the same vault state and base asset so the AUM calculation is internally consistent.
Accounts
| Account | Role | Description |
|---|---|---|
| glam_state | read-only | GLAM state account that stores vault configuration, integration ACLs, delegate permissions, policies, assets, mint linkage, and pricing records. |
| signer | signer, writable | Calling authority or fee payer. |
| event_authority | optional | Event authority or downstream event account. |
| event_program | optional | Event authority or downstream event account. |
No arguments
Policy & permissions
- Any signer can call. AUM is computed from
glam_stateand emitted as anAumRecordevent; no pricing-caller ACL is checked and no per-protocol valuation records are written.
TypeScript SDK usage
const pricingIxs = await glamClient.price.priceVaultIxs();
const validateIx = await glamClient.price.validateAumIx();Cross-instruction constraints
- Run after all required pricing instructions, and include validation in the same transaction when the operation depends on an atomic NAV calculation.