GLAMIDL Reference

price_loopscale_loans

Prices Loopscale loan positions held by the vault and records their value for vault AUM.

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

AccountRoleDescription
glam_statewritableGLAM state account that stores vault configuration, integration ACLs, delegate permissions, policies, assets, mint linkage, and pricing records.
glam_vaultread-onlyVault PDA associated with the GLAM state and used as the vault authority.
signersigner, writableCalling authority or fee payer.
sol_usd_oracleread-onlyOracle or price account used for valuation or downstream validation.
base_asset_oracleread-onlyOracle or price account used for valuation or downstream validation.
integration_authorityread-onlyProgram-derived authority used by the integration for downstream invocation.
glam_configread-onlyGlobal GLAM configuration account for fee and asset/oracle metadata.
glam_protocolread-onlyGLAM Protocol program account used for authorization or CPI.
event_authorityoptionalEvent authority or downstream event account.
event_programoptionalEvent authority or downstream event account.

No arguments

Policy & permissions

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