Handle Validator Exit¶

Purpose¶

Request and track validator exit through the controller and withdrawal vault.

Procedure¶

1. Confirm vault and pubkey binding.
2. Read current exit-request fee with currentExitRequestFeeWei or obtain approved manual fee.
3. Confirm controller policy allows exit preparation.
4. Call requestValidatorExitDynamic or requestValidatorExitWithManualFee with sufficient fee.
5. Verify ExitRequested from controller/vault path and exitSubmitted on vault.
6. Monitor consensus for exit acceptance.
7. Once accepted, call recordExitAccepted.
8. Track final exit withdrawal receipt and settlement path.

Abort Conditions¶

Abort if pubkey hash mismatches, fee source is untrusted, fallback route is invalid, exit was already submitted, or a pending claim state is unexplained.

Evidence To Archive¶

Pubkey/vault binding, fee quote, request tx, ExitRequested, consensus acceptance proof, recordExitAccepted, and settlement follow-up.

Operational Procedure¶

Purpose¶

Use this runbook to request or monitor validator exit while preserving claim and settlement accounting.

When To Use¶

Use it for production, staging, or rehearsal actions that affect live authority, validator custody, economic accounting, claims, or incident response. Do not use it as a substitute for source review; deployed-state evidence remains Evidence required unless captured for the exact chain and address set.

Required Authority¶

Required authority: controller policy path, operator automation, or governance depending on trigger. Read-only preparation can be performed by an operator or auditor, but transaction submission must come from the documented production holder in the permission matrix.

Preconditions¶

• The current source manifest and generated inventory are up to date.
• The acting Safe or owner has been verified against the current permission matrix.
• No unresolved incident is active for the same contract, validator, role, or operation.
• The reviewer can identify which layer is affected: Upgrade governance, Deposit permissioning, Custody/readiness, or Economic/claim safety.

Inputs Required¶

• v.
• a.
• u.
• l.
• t.
• ,.
• .
• p.
• u.
• b.
• k.
• e.
• y.
• ,.
• .
• f.
• e.
• e.
• .
• s.
• o.
• u.
• r.
• c.
• e.
• ,.
• .
• e.
• x.
• i.
• t.
• .
• r.
• o.
• u.
• t.
• e.
• ,.
• .
• r.
• i.
• s.
• k.
• .
• s.
• t.
• a.
• t.
• e.
• ,.
• .
• t.
• r.
• i.
• g.
• g.
• e.
• r.
• .
• s.
• t.
• a.
• t.
• e.

Step-By-Step Procedure¶

1. verify exit is allowed by policy.
2. estimate fee or approve manual fee.
3. call dynamic or manual exit request path.
4. monitor accepted exit evidence.
5. prepare settlement once funds and receipts are final.

Independent Review Requirement¶

A second reviewer must check the decoded calldata, expected state transition, affected role or validator, and expected events before submission. For emergency use, capture the reviewer identity and incident ticket before or immediately after the transaction.

Abort Conditions¶

• Source manifest hash drift or unexpected implementation metadata.
• Caller or Safe does not match the permission matrix.
• Revert reason points at a different layer than the runbook is trying to change.
• Any required input is missing or only inferred.
• A guardian, canceller, or incident commander has frozen the action window.

On-Chain Pre-Checks¶

Read current role/owner/admin state, operation status, target code hash where applicable, validator/vault mapping where applicable, and the latest readiness or claim state that the action depends on. Record block number and RPC endpoint.

On-Chain Post-Checks¶

Confirm the intended state changed, no adjacent authority changed unexpectedly, and no pending operation or stale intent was left active. Re-read the affected contract rather than relying only on transaction success.

Events Or Logs To Monitor¶

• ExitRequested.
• ExitAcceptedRecorded.
• SettlementProposed.

Evidence To Archive¶

Archive calldata, transaction hash, decoded event logs, pre/post reads, reviewer approval, incident or change ticket, and any source-manifest or release-artifact references used to justify the action.

Escalation Path¶

Escalate to governance signers for authority or upgrade anomalies, to controller/risk owners for economic or claim anomalies, to admission operators for intent mistakes, and to security incident response for unexpected code, role, or event drift.