GLAM ProtocolProduction
update_mint_params_by_mint_authority
Internal GLAM Mint authority path for mint-parameter updates that are not owner-timelocked.
Handler narrative
- Load the GLAM state or program account required by the instruction and verify the signer.
- Apply the requested state, policy, pricing, or system action after enforcing owner/delegate checks.
- For glam mint program's use only, timelock is not enforced
Required conditions
- The submitted accounts must match the declared account list, signer requirements, writable requirements, fixed program addresses, and account relationships shown below.
- The GLAM state account is the source of truth for owner, enabled integrations, delegate permissions, policies, assets, borrowable assets, timelock settings, mint linkage, and pricing records.
- Owner-level actions must be signed by the state owner unless the instruction is explicitly an integration callback, mint-authority callback, delegate action, or emergency access update.
- Configuration changes must pass owner or authorized-manager checks and, when the state or mint timelock is active, must follow the propose/apply timing model instead of taking effect immediately.
Accounts
| Account | Role | Description |
|---|---|---|
| glam_state | writable | State account owned by the GLAM Protocol program; it records vault configuration, policies, and pricing records. |
| glam_mint | read-only | Token-2022 mint associated with the GLAM mint or tokenized vault. |
| glam_mint_authority | signer | Token mint account used by the instruction. |
Arguments
| Argument | Type | Notes |
|---|---|---|
| params | vec<EngineField> | List of mint engine fields updated through the mint-authority path. Fields: name: EngineFieldName; value: EngineFieldValue |
Policy & permissions
- No external integration enablement is required beyond the program-level functionality involved in this instruction.
- Only the owner is expected. Delegates do not receive this capability by being added; it must be granted explicitly if supported.
Cross-instruction constraints
- No additional cross-instruction constraint is documented beyond account initialization, authority checks, and policy validation.