You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow v2 delegated accounts larger than one 10,240-byte runtime growth step to be undelegated safely.
Why
The v2 Undelegate temporarily copies account bytes into a DLP-owned buffer before changing ownership. Creating that full buffer in one instruction fails for larger accounts.
This must not be solved with a generic instruction that can resize arbitrary DLP-owned PDAs.
Scope
Add a narrowly scoped way to create and grow the canonical undelegation buffer over multiple instructions.
Limit every growth operation to the runtime-permitted increment.
Validate the delegated account, DelegationState, buffer PDA, target length, and authorized payer before every growth step.
Let the final Undelegate instruction require the exact buffer size, copy the current account bytes, and perform the same zero-and-assign handoff as the normal-size path.
Return temporary buffer rent to the account that funded it.
Provide a builder that returns the required preparation instructions for a target account size.
Allow preparation instructions and final undelegation to be placed in one transaction when transaction limits permit.
Keep the instruction specific to undelegation buffers; do not expose arbitrary DLP account resizing.
Activity
[-]Support large-account undelegation in the primary protocol[/-][+]Support large-account undelegation in v2[/+]