THE TRANSACTION VANISHED. YOUR DELIVERY DIDN’T.
Rehearse the rollback.
Before it becomes an incident.
Walk a real development-chain fork, compare delivery policies, and expose what an application can no longer undo.
02 / NODE-REPORTED CANONICAL BRANCH
0 / 0Loading…
A delivery has lost its supporting chain evidence. The recorded delivery remains. Returning to an old branch does not clear the incident.
| Order / event | Depth | State | Action |
|---|
03 / SAME OBSERVATIONS, SIMPLE BASELINE
First-seen is not forever.
A comparison consumer credits each transaction/log once on first sight, without waiting or rolling back. It is a deliberately limited baseline, not an industry benchmark.
04 / REPLAYABLE INCIDENT HANDOFF
Keep the irreversible part visible.
A saved run includes the observations, waiting rule, cursor and simulated acknowledgments. Opening it replays those decisions; imported totals are never trusted.
This is a developer rehearsal, not a live payment gateway. Edited files are not authenticated evidence. Nothing is delivered, refunded or sent by this website.
Trace provenance and limits
The fixture is generated by compiling and deploying DemoOrders.sol, submitting transactions, mining, then reverting a local snapshot and producing a competing branch. The website replays that recording; it does not connect to Ethereum or simulate live consensus. Run npm run evm to generate a fresh trace locally.
Ganache is archived and used only as an isolated development fixture. Forkline does not verify headers cryptographically, prove RPC completeness, choose Ethereum’s canonical chain, or guarantee exactly-once delivery to external services. The core trusts its supplied observation graph. No external webhooks, wallets, custody or real tokens.