Status Manager usable by contract #10389
Comments
mergify bot
added a commit
that referenced
this issue
Nov 12, 2024
closes: #10389 ## Description - `StatusManager` with `OBSERVED`, `ADVANCED` states tracked in local `MapStore` - `StatusManager` state updates via `Settler` and `Advancer` - `CctpTxEvidence` type, typeGuard, and fixtures ### Security Considerations See FastUSDC thread model ### Scaling Considerations - includes a `seenTxs` SetStore that will keep track of every tx observed by fusdc contract to assert uniqueness ### Documentation Considerations Includes state diagram in exos/README.md and the usual jsdoc ### Testing Considerations Includes unit tests of exos with a mocked LCA. ### Upgrade Considerations None, unreleased
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Fast USDC needs to keep track of the status of transaction in flight.
Description of the Design
A StatusManager exo that has a map store in its state.
The store is keyed by a composite tuple (MintedAmount, EUD) and the value is an array of matching transactions.
Each transaction has a state and the exo validates state transitions.
Tentative: a separate facet for the Advancer and Settler for POLA.
No vstorage output yet.
Security Considerations
Scaling Considerations
Test Plan
Exo test of transition validation
Contract test is separate: #10388
Upgrade Considerations
The text was updated successfully, but these errors were encountered: