LLegate
Cleanverse Build: Trusted Assets · Track 02 · Monad testnet

Compliance runs before the payment exists.

Legate is a cross-border payment rail where identity and asset provenance are preconditions to settlement, not paperwork filed afterwards. Every payment clears Cleanverse's real on-chain validator for both parties before any value moves — and again before it settles, so a revocation reaches money already in flight. Humans use this app; AI agents use the same contracts.

Start the walkthrough →No wallet? Verify a payment instead

Four steps, about three minutes. The last one needs no wallet at all.

Three enforcement layers, each owned by whoever is accountable for it

1
Who is this?
owned by Cleanverse
Both parties must clear the real on-chain validator. Legate keeps no identity list of its own.
2
How much, how often?
owned by Legate
Per-transaction and rolling daily corridor caps — the time-based limits a static rule cannot express.
3
Whatever the licence demands
owned by The operator
Operators register their own policy on-chain. Legate ships smurfing detection to prove the extension point is real.

The walkthrough

1
SendCompliance runs before the payment exists — three layers, on-chain, both parties.
2
ClaimThe recipient settles. If nobody ever does, the sender takes their money back.
3
AgentAn AI agent spends under caps held in contract storage, not in a prompt.
4
VerifyAnyone can audit any payment. No wallet required — this is the judge's entry point.

Nothing here is staged. Every refusal you see is a real contract revert, decoded from its actual revert data. Every A-Pass lookup is a live call to Cleanverse's sandbox. Where something could not be made real, it says so on screen rather than pretending.

Reading the code instead? bash demo/run-demo.sh runs all four scenes against real contracts in about forty seconds — no wallet, no credentials, no testnet funds.