Handle Failed Deposits¶

Purpose¶

Diagnose failed deposit transactions without weakening admission, custody, or readiness checks.

Required Authority¶

Read-only triage needs no role. Intent mutation requires allowlistAdmin. Governance or readiness remediation may require governor, controller owner, factory owner, or guardian roles depending on root cause.

Procedure¶

1. Decode revert selector.
2. Identify layer: format, amount, intent, custody, readiness, policy assertion, or deposit root.
3. Recompute intent hash with actual caller and current allowlistEpoch.
4. Check allowedDeposits and consumedIntents.
5. Verify vault address embedded in withdrawal credentials is factory-registered.
6. Query controller depositReadiness.
7. Re-run governor policy assertions.
8. Recompute deposit-data root.
9. Decide retry, intent replacement, readiness remediation, or incident escalation.

Abort Conditions¶

Do not retry if policy assertion fails, beacon authority drifted, readiness is unsafe, credentials point to an unknown vault, or a suspicious governance event is active.

Evidence To Archive¶

Failed tx, revert data, intent tuple, readiness output, policy assertion output, chosen remediation, and successful retry evidence if any.

Operational Procedure¶

Purpose¶

Use this runbook to triage a reverted deposit without confusing admission failures with custody/readiness failures.

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: read-only triage;allowlistAdminonly for intent repair. 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¶

• p.
• u.
• b.
• k.
• e.
• y.
• ,.
• .
• w.
• i.
• t.
• h.
• d.
• r.
• a.
• w.
• a.
• l.
• .
• c.
• r.
• e.
• d.
• e.
• n.
• t.
• i.
• a.
• l.
• s.
• ,.
• .
• a.
• m.
• o.
• u.
• n.
• t.
• ,.
• .
• c.
• a.
• l.
• l.
• e.
• r.
• ,.
• .
• e.
• p.
• o.
• c.
• h.
• ,.
• .
• r.
• e.
• v.
• e.
• r.
• t.
• .
• r.
• e.
• a.
• s.
• o.
• n.
• ,.
• .
• v.
• a.
• u.
• l.
• t.
• .
• a.
• d.
• d.
• r.
• e.
• s.
• s.

Step-By-Step Procedure¶

1. classify revert layer.
2. recompute intent hash.
3. read vault/factory/controller readiness.
4. fix only the failed layer.
5. retry only after independent review.

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¶

• DepositIntentAllowedFor.
• DepositIntentConsumedFor.
• DepositEvent.

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.