Evidence before claims.

Everything on this page is reproducible from the public repository. If a claim has no evidence behind it, it is listed as not yet done.

Relayer fuzz cases

1.0M

False accepts

False rejects

Accounting failures

WHAT WAS TESTED

The ledger.

Each row is something that actually ran against this deployment or its logic — not a projected number.

Chain id, mailbox bytecode, router / mailbox binding on all four chainsPASS

Remote router enrollment — all twelve directionsPASS

ISM binding and trusted relayer identity per chainPASS

Locked collateral equals summed synthetic supply179 = 179

Relayer message fuzz — forged sender, recipient, origin, destination, malformed bodies0 / 0

Accounting pressure — random route traffic across all twelve paths0 failures

Router-scoped relay — non-Trestle mailbox messages rejectedPASS

External third-party auditnot yet

REPRODUCE

Run it yourself.

npm install
npm test                        # on-chain wiring + accounting + relayer scope
npm run test:pressure:quick     # 10k relayer fuzz + 10k accounting, seconds
npm run test:pressure:relayer   # 1,000,000-case relayer fuzz
npm run test:pressure:accounting   # 1,000,000-case accounting pressure
node frontend/logic_test.js     # bridge routing logic, no browser

The pressure harnesses are deterministic: they seed a PRNG, so a reported failure can be replayed with the same --seed value.