GLAM MintProduction
mint_tokens
Mints GLAM share tokens under authorized mint-management flow.
Handler narrative
- Load the GLAM state or program account required by the instruction and verify the signer.
- Apply mint lifecycle, token-account, ACL, or policy changes after verifying the required authority.
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.
- 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.
Accounts
| Account | Role | Description |
|---|---|---|
| glam_state | writable | State account owned by the GLAM Protocol program; it records vault configuration, policies, and pricing records. |
| glam_signer | signer, writable | Calling authority. It must be the owner or a delegate with the explicit permission required by this instruction. |
| glam_mint | writable | Token-2022 mint associated with the GLAM mint or tokenized vault. |
| mint_to | writable | Token mint account used by the instruction. |
| recipient | writable | Instruction-specific account supplied by the caller or SDK. |
| policy_account | writable, optional | Policy account used by GLAM Policies for transfer-hook lockup checks. |
| system_program | read-only | Standard Solana program account required by the instruction. |
| token_2022_program | read-only | Standard Solana program account required by the instruction. |
| policies_program | read-only | GLAM Policies program account used for Token-2022 transfer-hook behavior. |
Arguments
| Argument | Type | Notes |
|---|---|---|
| amount | u64 | Amount of GLAM share or mint tokens to issue, in the mint's smallest unit. |
Policy & permissions
- No external integration enablement is required beyond the program-level functionality involved in this instruction.
- Caller must be the owner or a delegate with the explicit protocol permission required by this instruction.
Cross-instruction constraints
- No additional cross-instruction constraint is documented beyond account initialization, authority checks, and policy validation.