FEEPASS For judges · BCH BLAZE 2026 · Mainnet Track · BUIDL 51513

Send dollars.
No spendable BCH.

FeePass lets a wallet that holds PUSD but no spendable BCH send PUSD on Bitcoin Cash mainnet: a covenant pool lane pays the miner fee, and the sender pays exactly 0.01 PUSD back in the same transaction. Spendable means non-token BCH: a token coin always keeps its few hundred sats of dust.

Reading the pool from mainnet…

Try it: about 60 seconds

  1. Open feepass.edycu.dev on a laptop and press Connect wallet. Scan the QR with a WizardConnect wallet and approve (the wallet gate targets Selene and Paytaca; neither is verified yet, see Honest limits). The app is mainnet only.
  2. No PUSD? Press Get 0.25 starter PUSD: one claim per address, 12 per UTC day, from the faucet shown live above. No BCH is needed for it.
  3. Send 0.10 PUSD. The recipient is prefilled (it returns to the faucet). Press Send and approve one signature in your wallet: it signs only your own coin.
  4. Read the ticket: what you sent, the 0.01 PUSD you paid, the lane that paid the miner fee, your spendable BCH before and after (read from the chain), and an explorer link.

Already hold PUSD? Skip step 2. No wallet handy? Open the first mainnet send and read in0 (the sender's PUSD coin), in1 (the lane) and out2 (the lane back with +0.01 PUSD).

Receipts on chain

WhatProofDetail
First mainnet send d59f120b…f8b7 0.10 PUSD sent; the lane paid the 580-sat miner fee; exactly 0.01 PUSD went back to the pool; sender spendable BCH 0 → 0; 572 bytes. Signed by a headless test key through the app's own builder and VM check (not a named wallet); its coin came from the operator's prep tx 7c0b37c3…7f55. Record: evidence/mainnet-send.json
Pool lane funded 9d80b411…7dee One lane of 100,000 sats + the 0.01 PUSD seed at the covenant. 20 lanes is the design target. All operator txs: evidence/mainnet-txs.csv
Same send on chipnet 78be2edf…f848c Earlier run on Bitcoin Cash's public test network with a test token in place of PUSD.
The covenant FeePassPool.cash Eight rules (R1–R8): fixed 2-in/3-out shape, the lane comes back with exactly +0.01 PUSD, a lane loses at most 2,000 sats per send, at most 675 sats of dust top-up.
Tests CI/CD 189 unit + covenant VM tests, 32 Playwright E2E (16 × desktop + mobile), Lighthouse CI, CodeQL, gitleaks over full history, on every push.

Reproduce

# the app, reading Bitcoin Cash mainnet
git clone https://github.com/edycutjong/feepass && cd feepass && npm ci && npm run dev
# the covenant, builder and flow, offline on the BCH VM (no keys)
npm test
# operator only: one real sponsored send on mainnet (needs the operator's funded key files and a written cap)
npx tsx scripts/mainnet-send.ts --network mainnet --authorized-cap <bch>

Honest limits

  1. One funded lane today (target 20). Two sends in the same moment: the second is asked to re-sign on another lane or retry.
  2. No named wallet verified yet. FeePass asks the wallet to sign input 0 only, with sighash 0x61 (SIGHASH_ALL|FORKID|UTXOS); that is protocol-tested through the real relay with a headless wallet. Whether a given wallet accepts it is exactly what /gate.html records.
  3. The starter faucet is small: 0.25 PUSD per address, 12 claims per UTC day, while its balance lasts. If it says "out for now", use PUSD you already hold.
  4. The covenant does not pick the recipient. Your own signature (sighash 0x61) binds the outputs, as far as your wallet shows them.
  5. Not "zero BCH". A token coin always carries a few hundred sats of dust; the claim is no spendable BCH.

Links