request_withdrawal
Request a Neutral bundle withdrawal for the GLAM vault.
Handler narrative
- Load the GLAM state or program account required by the instruction and verify the signer.
- Verify that the integration is enabled on the vault and that the caller has the required delegate permission or owner authority.
- Validate the instruction-specific policy, then invoke the external protocol with the vault authority where required.
- Request a Neutral bundle withdrawal for the GLAM vault. - Permission requirement:
RequestWithdrawal. - Policy:bundle_accountmust be present inNeutralPolicy::bundles_allowlist.
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.
- The vault account must be the PDA controlled by the core protocol program and derived conceptually from the state account; instructions use it as the vault authority for SOL, token accounts, and external positions.
- The vault integration ACL must enable this integration before the instruction is accepted; that enablement is defined on the GLAM state account.
- If the signer is not the owner, the delegate ACL on the GLAM state must contain the exact protocol permission required by this instruction; registering a delegate alone is insufficient.
- Instruction-specific destination accounts must satisfy the external protocol's own account model; GLAM validates the accounts it needs for authorization and policy enforcement, then passes the remaining protocol accounts through CPI.
- The instruction metadata names
RequestWithdrawalas the delegate permission for this instruction. - Additional policy conditions documented for this instruction: Policy:
bundle_accountmust be present inNeutralPolicy::bundles_allowlist.
Accounts
Uses the standard Big Seven account pattern, plus the instruction-specific accounts below.
| Account | Role | Description |
|---|---|---|
| user_bundle_account | writable | Instruction-specific account supplied by the caller or SDK. |
| bundle_account | writable | Instruction-specific account supplied by the caller or SDK. |
| oracle_data | writable | Pricing or oracle account used to calculate value for the instruction. |
| bundle_temp_data | writable | Token account read or written by the instruction. |
| rent | read-only | Fixed program or sysvar account required by this instruction. |
Arguments
| Argument | Type | Notes |
|---|---|---|
| shares_amount | u128 | Neutral bundle share amount requested for withdrawal. |
| min_estimated_value | u64 | Minimum estimated value the withdrawal must return for the request to be acceptable. |
Policy & permissions
- Enable the Neutral integration program on the vault integration ACL before Neutral bundle actions.
- Delegate permission:
RequestWithdrawal.
Cross-instruction constraints
- The Neutral bundle depositor account must be initialized and the bundle must remain allowlisted.