02 / Live demo · Watch the boundary hold
Don’t take our word for it.
Run the protocol.
One button starts a server-owned Arc testnet story. Follow the money from routine payroll to the recovery receipt.
Constructed attack facts.
Everything labeled.
REPAYD CONTROL PLANE
A payment meets its boundary.
THE LOOP
Let agents act.
Keep risk in bounds.
Four routine payments. One frozen hold. One mined policy revert. One controlled miss. One recovery that closes the loop.
Nothing starts until you press Run demo.
- Elapsed · real time
- —
- Started · local time
- Not started
- Latest confirmed receipt
- No receipt yet
- Server heartbeat
- Awaiting heartbeat
- 01Preflight
- 02Deploy
- 03Payroll
- 04Contain
- 05Block
- 06Recover
- 07Provenance
- 08Verify
Allowlisted payments completed.
Unknown destination paused.
Contract violation reverted.
Covered loss paid back.
The persistent record
What happened, in order.
The journal is waiting.
Press Run demo. The server keeps the run if you navigate away.
How to read this demonstration +
WHAT THE CHAIN PROVES
Balances, confirmed receipts, reverted calls, blocks, and token transfers are read from Arc testnet. Open a journal item for its explorer link.
WHAT IS CONSTRUCTED
Attack history, clock facts, watcher reasoning, and owner-origin judgment are local demo inputs. They are marked as local, not presented as TEE attestations.
Next