Akamig
commented
10 months ago Out of invalidation, We have several event states when comes to recording transactions in two different views, internally, and externally.
Local Transaction States Through Lifecycle
- Requested (BridgeSe -> Bridge with memo)
- Processing (Handling Request, Not yet Staged)
- Staging (Bridge -> Memo Staged, Not yet confirmed)
- Confirmed (Success, Failure, Invalid)
Global (External) Transaction States
- Synced (Data Matching "1:1" Tx Staged successfully, Bridge -> memo)
- This must be idempotent, to prevent duplicated response processing (due to unintended nonce-race condition or whatever)
- Desynced (Diff occured between two)
- This doesn't mean bridge faulted, but it must be handled in certain timespan, in order to sustain eventual consistency.
- Also this can be, and recommended to be cross-checked with bridge instance. to validate each other's state records.
It's bit long to explain, but in short On bridge side for now, since urql internally utilizing wonka, we can feed-in customized stream into urql, while handling normal-lifecycle logic.
Uh, I need to workoff now, so will write more about this but will implement in Saturday.
It should record(store) processed transaction relations. (upstream tx <-> downstream tx)