Skip to main content
All transactions below are on Stellar testnet. Generated by scripts/setup-testnet.mjs and appended to by scripts/demo-loop.mjs.

​
The four accounts

Public keys only — secrets never leave the operator’s .env. These make fee sponsorship verifiable in two clicks: open any payment row below on stellar.expert and the transaction’s source / fee account is the FEEPAYER, while the payer appears only inside the Soroban authorization entry / transfer event. The FEEPAYER key is also published live by the facilitator at stellarsight.xyz/health as feePayer.

​
The transactions

135 rows: 5 setup + 3 cleanup + 127 settled x402 payments. Dates are each transaction’s ledger created_at (UTC) as reported by Horizon. Every payment here was generated by this repository — there is no third-party traffic yet, and the rows say which script produced each one. Rows prefixed load: came from npm run evidence:batch, a serial script paying our own seller: they are breadth of settlement, never evidence of demand. The full label map is docs/status/provenance.json, and EVIDENCE.md aggregates it. Rows marked via hosted stack settled end to end through the public deployment at stellarsight.xyz: discovery, the 402 challenge, payment verification, settlement and durable cataloging all ran on the hosted facilitator, not on localhost. Rows marked conformance were produced by npm run verify:conformance, which drives an unmodified @x402/fetch client — wrapFetchWithPayment, no STELLARSIGHT code on the path — through the whole 402 → sign → settle → 200 loop against apps/seller.