XRPL Testnet demo · no real value

Proof you can inspect

Every claim has a boundary: recorded Testnet transactions, local measurements, or simulated fixtures. None of these is a mainnet release.

1,000 purchases, each re-read from a public node

Every purchase went through the product’s escrow service, and an independent script that imports none of the product code re-fetched both transactions of all 1,000 from a public node. All 1,000 matched on amount, destination, lock and key. Median 20.3 s end to end. Run npm run proof:testnet-verify to repeat it. These are scripted repeats of one team-authored note from fresh accounts. Read the run.

The protocol model, a million crash schedules and 34 attacks

A model checker explored 210,480 bounded protocol states with no violation and caught all seven deliberately seeded bugs. One million simulated crash and retry schedules ran against the real purchase code with no violation, and 34 attacks on the local stack found no breach. Read the report and what it does not cover.

Refunds without the writer

An opt-in holdback puts a fifth of the price in a second escrow, created with the first in one atomic Batch. Buyer policy releases it when the promise checks pass, or takes it back after a deadline when they fail, with no writer cooperation. Of 17 real purchases, 11 were released and 6 refunded, and all were verified. The key-release payment stays paid. Read the evidence.

Real content you can check

The free tier is 12,104 passages from the XRPL and x402 documentation, each cited by its real page URL. Paid ledger-analytics reports are signed “as of validated ledger N”; open that ledger in an explorer and repeat the query. Read the content evidence.

Verify a recorded run without asking a question

Open the judges’ corner, choose Home → Verify, then “Run the checks”. The featured 12 Nov run is one hosted run where the browser check shows all five gates held: 24 passed, 0 failed, 2 not checked; public Testnet 6/6. It uses recorded receipts and public-node reads, without a question. Identity and origin skips remain. Read passed and not-checked groups separately. Missing transactions are pending; an unreachable node is unavailable, never a pass.

Check the key yourself

Open a payment’s key check: your browser fetches validated successful EscrowCreate and EscrowFinish transactions and recomputes sha256(key) against the lock. A match proves this escrow’s key reveal, not quality or identity. It needs a reachable public node.

Follow the money

Open the Testnet ledger to re-check the recorded transaction hashes against public servers. On mobile, each record keeps its explorer link and validation result together.

Verify exported receipts outside the app

Install the verifier, export receipts from the app, then run python -m researchagent verify answer.json --ledger. Verification checks receipts and cited content; it does not establish the truth of every source sentence.

Measured progress, including misses

Read the measurements and misses we kept. Each snapshot states its source and cutoff.

Why the token is TEST-SGD

Our escrow demonstration uses a labelled Testnet stand-in token. Check the official RLUSD issuer’s escrow permission live.