Skip to content
Star5

Testnet runs

A separate lab repository runs scenarios on Base Sepolia with the published @hashspan/* packages. Each run checks, in the same process, the spans hashspan recorded, and writes one line to a run ledger, also when it fails. This page shows that ledger: every run, its outcome and the transactions it sent.

  • treasury: the example agent with a scripted model. It pays 0.00001 ETH to itself and tries a withdrawal that the vault rejects. It passes when each tool span has a send 84532 and a confirm 84532 span under it, in one trace, with the receipt data and the decoded revert reason. It checks that these attributes are there and well formed; it does not compare them with the receipts.
  • sealed-fees: sends nothing. It watches up to 50 transactions of other accounts with watch() and compares each confirm span with the sealed receipts of its block: status, blockchain.tx.l1_fee and blockchain.tx.fee must be the sealed receipt’s, never a flashblocks preconfirmation’s. Spans recorded without fees, the documented fallback, may be up to 20%; fewer than 10 compared transactions is reported as an error (an idle chain or a failing RPC), not as a finding.
  • paths: a send in background confirmation mode without a wait, a transaction confirmed with watch(), and three calls that revert with Error(string), Panic(0x11) and a custom error. It passes when each gets a confirm span with the receipt data, the three revert reasons are decoded, the watched transaction has no send span, and traceTransport() records eth_sendRawTransaction under each send span.
  • call-batches: two EIP-5792 batches through viem’s fallback to plain transactions. It passes when each batch has a send span with its id and two calls, the first ends success and the second partially_reverted, and each of the three plain transactions has a confirm span with fees.

A run that fails its setup (wrong chain, too little balance) or its span check is listed as failed. The hashspan version on each run is the @hashspan/viem version its scenario pinned when it ran.

16 runs of 4 scenarios on 2 days: 15 passed, 1 failed. Copied from the lab's run ledger on 2026-10-03 15:35 UTC.

  1. passcall-batches · hashspan 0.9.0

    No transactions in the ledger line.

  2. passpaths · hashspan 0.9.0
  3. passsealed-fees · hashspan 0.9.0

    50 of 50 watched transactions compared with sealed receipts; 0 recorded without fees.

  4. passtreasury · hashspan 0.9.0
  5. passcall-batches · hashspan 0.9.0

    No transactions in the ledger line.

  6. passpaths · hashspan 0.9.0
  7. passsealed-fees · hashspan 0.9.0

    50 of 50 watched transactions compared with sealed receipts; 0 recorded without fees.

  8. passtreasury · hashspan 0.9.0
  9. passpaths · hashspan 0.8.2
  10. passsealed-fees · hashspan 0.8.2

    50 of 50 watched transactions compared with sealed receipts; 0 recorded without fees.

  11. passtreasury · hashspan 0.8.2
  12. passtreasury · hashspan 0.8.2
  13. passtreasury · hashspan 0.8.2
  14. passtreasury · hashspan 0.8.2
  15. failtreasury · hashspan 0.8.0
  16. passtreasury · hashspan 0.7.0

More setups, run once and checked by hand, are on Tested setups.