Skip to content

Handling Slashing And Exit

Purpose

Move a validator from normal operations into fail-closed, exit, receipt, and settlement handling.

Slashing Procedure

  1. Verify slashing or ejection evidence from independent finalized sources.
  2. Stop affected claim/deposit actions.
  3. Submit risk update with slashing/ejection data.
  4. Confirm claim state is disabled or appropriately limited.
  5. Cancel or clear pending claims created under old assumptions.
  6. Prepare exit request if not already submitted.

Exit Procedure

  1. Verify pubkey and vault binding.
  2. Read dynamic exit fee or approve manual fee.
  3. Call the controller exit request path with sufficient fee.
  4. Confirm vault exitSubmitted and ExitRequested.
  5. Monitor consensus until exit accepted.
  6. Call recordExitAccepted.
  7. Record final exit withdrawal receipt.
  8. Propose and finalize settlement when evidence supports it.

Abort Conditions

Abort if pubkey hash mismatches, exit fee is untrusted, fallback route is invalid, evidence is unfinalized, or settlement inputs are incomplete.

Evidence To Archive

Consensus proof, risk update, exit request, acceptance proof, receipt posting, settlement events, vault balance, and communication record.