Bridge Integration StagingStaging
price_managed_transfers
Prices managed inflight transfers and publishes aggregated amount.
Required conditions
- 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. |
| bridge_registry | read-only | Bridge route, session, registry, or managed-transfer account. |
| integration_authority | read-only | Program-derived authority used by the integration for downstream invocation. |
| glam_protocol_program | read-only | GLAM Protocol program account used for authorization or CPI. |
| glam_config | read-only | Global GLAM configuration account for fee and asset/oracle metadata. |
| base_asset_oracle | read-only | Oracle or price account used for valuation or downstream validation. |
No arguments
Policy & permissions
- No signer or pricing-caller ACL is enforced. Validated managed transfers from the bridge registry are priced via supplied oracles and published as a priced protocol through the integration authority.
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.
- Managed transfers must be validated before they are priceable.