Handle Failed Claims¶

Purpose¶

Resolve failed reward or settlement-claim attempts while preserving caps, beneficiary routing, and risk controls.

Procedure¶

1. Decode the failed call and revert reason.
2. Identify claim type: running reward, executor-assisted claim, settlement reward, principal claim, or remainder drain.
3. Read current claim state, pending claim, caps, executor grant, reserve health, and risk freshness.
4. Check whether a risk update, receipt, exit, or settlement transition cancelled the pending claim.
5. For executor failures, verify scope bits, expiry, daily cap, and global executor pause.
6. For beneficiary claims, confirm caller rights and claim-period cap.
7. Retry only after the state explains the failure.

Required Review¶

Any change to executor grants, reserve coverage, or trigger state needs independent operations review. Principal claims and remainder drains need treasury/governance review.

Abort Conditions¶

Abort if observation is stale, claim state is stop-loss/paused, reserve coverage is invalid, beneficiary differs from seat config, or pending claim was created under stale assumptions.

Evidence To Archive¶

Failed tx, pending claim state, cap reads, executor grant, claim-state derivation inputs, remediation tx, and post-claim ledger/balance reads.

Operational Procedure¶

Purpose¶

Use this runbook to triage failed reward, settlement, or principal claim attempts.

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; controller owner or beneficiary/executor depending on failure. 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.
• ,.
• .
• c.
• a.
• l.
• l.
• e.
• r.
• ,.
• .
• b.
• e.
• n.
• e.
• f.
• i.
• c.
• i.
• a.
• r.
• y.
• ,.
• .
• a.
• m.
• o.
• u.
• n.
• t.
• ,.
• .
• c.
• l.
• a.
• i.
• m.
• .
• m.
• o.
• d.
• e.
• ,.
• .
• p.
• e.
• n.
• d.
• i.
• n.
• g.
• .
• c.
• l.
• a.
• i.
• m.
• ,.
• .
• r.
• i.
• s.
• k.
• .
• o.
• b.
• s.
• e.
• r.
• v.
• a.
• t.
• i.
• o.
• n.
• ,.
• .
• r.
• e.
• c.
• e.
• i.
• p.
• t.
• .
• l.
• e.
• d.
• g.
• e.
• r.

Step-By-Step Procedure¶

1. classify claim-state blocker.
2. check executor grant and caps.
3. check pending delay.
4. check reward/principal bucket.
5. retry only if state and authority are correct.

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¶

• ClaimExecutorGrantSet.
• PendingClaimInitiated.
• SettlementRewardsClaimed.
• PrincipalClaimed.

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.