Activity feed mapping
Confirmed event chronology, settlement outcomes, and independent current request actions.
Event-first history
Activity records confirmed events. A queued burn submission remains a "Burn requested" event after completion; it is not rewritten into current request state. Processing, cancellation, and claims have their own timestamps and transaction links.
| Event | User-facing meaning |
|---|---|
| Approval | Allowance granted or revoked |
| Bootstrap/mint | EVE minted for ETH |
| Immediate burn | EVE burned and ETH paid in the transaction |
| Queued burn | EVE escrowed; settlement still pending |
| Processed redemption within tolerance | EVE burned; ETH credited to claimable balance |
| Processed redemption outside tolerance | EVE returned; no ETH settlement |
| Cancellation | EVE returned before pricing or after expiry |
| Claim | Actual ETH payout, potentially combining multiple redemptions |
An unknown processing result is shown as unavailable and is never assumed to be a successful burn. A claim must not be assigned an invented per-request association.
Current actions
Current wallet/claimable balances and request eligibility are read from RPC. Claims and cancellations live in Portfolio's Available actions. Historical event cards do not offer them. Discovery of pending requests is independent of Activity pagination.
Last updated on