GLAM Mint StagingStaging
price_single_asset_vault
Prices a SingleAssetVault by its base asset balance.
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 | writable | GLAM state account that stores vault configuration, integration ACLs, delegate permissions, policies, assets, mint linkage, and pricing records. |
| glam_vault | read-only | Vault PDA associated with the GLAM state and used as the vault authority. |
| signer | signer, writable | Calling authority or fee payer. |
| base_asset_ata | read-only | Token account read or written by this instruction. |
| integration_authority | read-only | Program-derived authority used by the integration for downstream invocation. |
| glam_protocol | read-only | GLAM Protocol program account used for authorization or CPI. |
| event_authority | optional | Event authority or downstream event account. |
| event_program | optional | Event authority or downstream event account. |
No arguments
Policy & permissions
- Requires a Single-asset vault GLAM state.
- Caller: any signer; no pricing-caller ACL is checked.
- Supplied account, oracle, and protocol data are validated before the priced protocol record is written.
TypeScript SDK usage
const pricingIxs = await glamClient.price.priceVaultIxs();
const validateIx = await glamClient.price.validateAumIx();
// Submit all pricing instructions and validation together.Cross-instruction constraints
- All pricing instructions for this pricing operation must be included in the same Solana transaction. Splitting them across multiple transactions is not supported and will produce incorrect or rejected NAV calculations.