Cross-operator settlement, reconciled in the open. A Go gateway authenticates every transfer; a Rust engine replays its log, matches the operator files, and proves recovery after a kill-9. Simulated MVola, Orange and Airtel traffic.
Every request at the edge, typed as it lands. 0 shown
Each column closes with its own count and sum, like a sub-ledger.
Each operator row joined to the transfer that created it. Figures below come from the live report; the double rule means agreed.
| Settled exact | – |
|---|---|
| Settled within fee tolerance | – |
| Missing: transfer with no row | – |
| Orphan: row with no transfer | – |
| Mismatch: amounts disagree | – |
| Corrupt rows skipped | – |
| Decided rows | – |
No settlement processed yet.
Missing rows open the transfer that produced them.
One recorded run, with the hardware it came from. The RUSTGO bar stays unclaimed until a run supports it.
Loading…
—
Nothing open.
Gateway counters idle.
Recovery claims without evidence are marketing. The partition drill holds the engine's offsets exactly like a network outage; releasing replays the backlog. The kill-9 drill is scripted and fails on one differing byte.
Stop the engine process (kill -9 / Stop-Process -Force), start it again with the same environment, then compare the settlement report before and after. scripts/recovery.ps1 runs it and fails if one byte differs.