GLAMIDL Reference

emergency_access_update

Bypasses timelock for emergency access changes such as disabling a delegate, integration, or state.

Handler narrative

  1. Load the GLAM state or program account required by the instruction and verify the signer.
  2. Update the access-control record in the state account after checking owner authority and timelock or emergency rules.
  3. Bypasses the timelock for emergency updates on access control rules. Allowed operations: - removing an integration program - removing a delegate - enabling/disabling glam state

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.
  • The update must be limited to emergency access actions: removing an integration, removing a delegate, or enabling or disabling the GLAM state.

Accounts

AccountRoleDescription
glam_statewritableState account owned by the GLAM Protocol program; it records vault configuration, policies, and pricing records.
glam_signersigner, writableCalling authority. It must be the owner or a delegate with the explicit permission required by this instruction.

Arguments

ArgumentTypeNotes
argsEmergencyAccessUpdateArgsInstruction parameter object; field details are listed below. Fields: disabled_integrations: vec<pubkey>; disabled_delegates: vec<pubkey>; state_enabled: option<bool>

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.