State And Ledger Definitions¶
Seat State (SeatConfig)¶
Important fields:
- beneficiary and principal destination
- claim delay and per-period caps
- trigger and exit flags
- settlement phase
- reserve settings
- expected credential type
- principal/effective target values
- cleared safe epoch
Observation State (RiskObservation)¶
Important fields:
- epoch and balances
- credential type and finalization status
- slashed/ejection flags
- derived risk state
- quarantine and same-epoch-conflict flags
Receipt Ledger (ReceiptLedger)¶
Key accounting buckets include:
userRewardBucketWeiprincipalRepairBufferWeirecoveryBufferWeireceiptHoldbackWeifinalExitWithdrawalWeiappliedReserveWeicoveredPrincipalWei- claimed counters and post-settlement drains
Dust Accounting (DustAccounting)¶
Tracks:
- covered principal gap
- reserve advance debt
- rolling advance usage and window
- persistent dust history
- total smoothing advanced and recouped
Settlement Snapshot (SettlementSnapshot)¶
Tracks proposal and finalization details:
- proposed and ready timestamps
- emergency mode flag
- final outcome and timing
- covered principal, deficit, reserve application, settlement excess
Running Claimable Breakdown View¶
Controller exposes runningClaimableBreakdown:
- verified reward claimable
- reserve-funded smoothing claimable
- total claimable
- recoup pending
- principal protection gap
Operational Detail¶
State and ledger names must be read as accounting boundaries: risk observations describe validator condition, receipt ledgers describe physical or classified inflows, dust accounting tracks shortfalls, and settlement snapshots close lifecycle buckets.
Required Checks¶
- Verify source manifest and generated inventory if the claim path changed.
- Read current risk observation, receipt ledger, reserve coverage, claim mode, pending claim, and gatekeeper caps.
- Confirm the caller is the beneficiary or an authorized executor for the required scope.
- Confirm no incident, stale oracle, slashing, exit, or settlement blocker changes the allowed path.
Failure Handling¶
A failed claim is not automatically a contract defect. Preserve revert data, current reads, and source evidence. Retry only after identifying whether the failure belongs to Upgrade governance, Deposit permissioning, Custody/readiness, or Economic/claim safety.