Undelegate Transaction

The Undelegate transaction withdraws principal from a pool position. It burns the corresponding principal shares, converts them back to ANM at the pool’s loss-adjusted price, and parks the released principal in a per-validator pending-unbond entry that matures after the full unbond interval. Any accrued reward on the position is settled and paid to the delegator at the same time. See Unbonding for the user-facing flow.

The Payload Type for Undelegate is 10.

Payload Structure

• Delegator address owns the position and is the transaction signer; it is also the beneficiary of the released principal.
• Validator address is the pool to withdraw principal from.
• Amount is the principal to undelegate. 0 means a full exit (the whole position). A value greater than 0 is a partial exit and must leave at least the minimum delegation (100 ANM) in the position.

Behaviour

• The released principal is parked in a pending-unbond entry releasing at the current height plus the unbond interval (a 21-day window). It can then be retrieved with a Withdraw transaction, which pays the rightful delegator.
• Parked principal stays slashable for the full waiting period, so unbonding cannot be used to dodge a penalty.
• Accrued rewards are settled immediately — only principal waits out the interval.
• An operator cannot undelegate its self-bond below the operator minimum while other delegators remain.
• As with Delegate, an Undelegate against a pool whose validator is currently in the committee (or joining at the next height) is accepted and escrowed: the request is recorded immediately and the shares are burned, stake reduced, and principal parked in the slashable pending-unbond entry only once the validator rotates out of the committee. (The request is committed right away — this is not a deferred mempool tx.)