withdraw_strategy
Withdraw principal from a direct lender strategy.
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.
- Withdraw principal from a direct lender strategy. - Permission requirement: `WithdrawStrategy`. - Policy - `strategy` must be tracked in `StateAccount::external_positions`.
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 `WithdrawStrategy` as the delegate permission for this instruction.
- Additional policy conditions documented for this instruction: Policy; `strategy` must be tracked in `StateAccount::external_positions`.
Accounts
Uses the standard Big Seven account pattern, plus the instruction-specific accounts below.
| Account | Role | Description |
|---|---|---|
| bs_auth | signer | Fixed program or sysvar account required by this instruction. |
| strategy | writable | External strategy account used by the instruction. |
| market_information | read-only | Instruction-specific account supplied by the caller or SDK. |
| principal_mint | read-only | Token mint account used by the instruction. |
| lender_ta | writable | Instruction-specific account supplied by the caller or SDK. |
| strategy_ta | writable | External strategy account used by the instruction. |
| associated_token_program | read-only | Standard Solana program account required by the instruction. |
| event_authority | read-only | Instruction-specific account supplied by the caller or SDK. |
Arguments
| Argument | Type | Notes |
|---|---|---|
| amount | u64 | Principal amount to withdraw from the Loopscale strategy. |
| withdraw_all | bool | If true, withdraw the full available strategy balance instead of an exact amount. |
Policy & permissions
Enable the Loopscale integration program on the vault integration ACL before Loopscale position actions.
Delegate permission:
WithdrawStrategy.
Cross-instruction constraints
- The Loopscale strategy must be tracked in the vault's external positions when required by policy.