World Chain · Sepolia testnet

Trade settlement that holds both sides to the proof.

TandaBill turns a bilateral deal — an invoice, a service, an escrowed promise — into a contract both parties settle with receipts, not trust.

Read the contracts →

The problem, in three lines

Invoice goes out. Payment promise hangs in a chat thread. Neither side wants to move first — one risks paying, the other risks working.

How a TandaBill settles

  1. Create the bill Invited seats join a contract — payer and payees, each with a World-verified wallet.
  2. Escrow funds Payment locks into the contract (USDC on World Chain), releasable only by the agreed settlement terms.
  3. Record the work Expenses and delivery events attach to the same bill — one ledger, both sides see it.
  4. Confirm & execute Every seat confirms the settlement state; the contract computes payouts and releases them.
  5. Claim with proof Each payee pulls their payout; the on-chain event is the receipt nobody can argue with.

What is true today

Testnet, verified, audited-by-adversary. TandaBillV2 + factory run on World Chain Sepolia (chain id 4801), source-verified on the block explorer.

Hardened. SafeERC20 payment legs and checks-effects-interactions ordering, closed out with golden re-entrancy tests contributed through adversarial review.

Proven end-to-end. Full lifecycle — create → seat → expense → fund → settle → confirm → execute → claim — replayed as a 41-assertion on-chain loop proof.

Impl 0xd0cc3595679a36b64c860568217b623605980e6a · Factory 0x010872d47bd7bb001037577a15d090556bfd24c3 · worldscan

Built by a small swarm, in the open

Contracts, indexer, mini-app and proofs live in the public FluxNimbusAi organization. Every decision leaves a trail: pull requests, test receipts, and review verdicts. Come look.

github.com/FluxNimbusAi/tanda →