Invoice addresses that cost nothing until they are paid.
Every invoice gets its own NEAR address, and issuing it needs no transaction.
zeroinit.vercel.app · NEAR testnet only · mock token only · MIT
Try it · Claims · How it works · Verify · Limits · AI use
ZeroInit gives every invoice its own NEAR address, computed from the invoice terms, so issuing an invoice sends nothing to the chain.
The payer's one transaction creates the account, pays the merchant and sets the tax aside (92/8 in the demo); nobody holds a key to that account.
Why it is new. Designs that give each item (an invoice, an NFT, a job) its own NEAR account create that account first: one transaction and one storage deposit per item, paid before anyone has paid anything.
ZeroInit derives the address from the terms with NEAR's deterministic account ids (protocol 88), so issuing costs 0 transactions; the account comes into existence only when someone pays.
- Live site: https://zeroinit.vercel.app
- The one-transaction payment on testnet:
GFzvAw8t… (invoice INV-1111-V33-A, contract v3.3: state init + pay, 0.92 to the merchant, 0.08 to the tax vault)
- For AI agents: an MCP server with
issue_invoice, invoice_status and verify_invoice (read-only, never signs). No clone needed: claude mcp add zeroinit -- npx -y -p @erhantrk/zeroinit zeroinit-mcp
Tracks: Open Innovation (primary) · Real-World Money. Testnet only, mock token only, not audited.
The local dashboard (npm run zi -- serve), Chrome, 2026-11-13 UTC, contract v3.3. The first NEAR invoice was paid in one transaction, the second by a plain transfer and a sweep, the third was issued and never paid, so its account does not exist; the tUSDC invoice was paid from the page, with its registration on the token in the same transaction as the payment. Each address shows its check code.
Try it in 2 minutes
Fastest, with no clone (Node 22 or newer, package @erhantrk/zeroinit 0.2.0 or newer, which ships the v3.3 recordings):
npx -y @erhantrk/zeroinit verify INV-1111-V33-A # read-only live check over testnet RPC: every line PASS, ends INFO status=PAID
npx -y @erhantrk/zeroinit replay fixtures/v33/demo-run.json # the recorded live run, replayed offline: 62 PASS lines, exit 0
From a clone, the full check. No keys and no .env needed. Node 22; npm ci needs the npm registry once, everything after that is offline except the last line.
npm ci --include=dev
npm test # 255 tests, all pass
npm run zi -- replay fixtures/v33/demo-run.json # a recorded live testnet run, replayed offline: 62 PASS lines, exit 0
bash scripts/judge-offline.sh # the whole offline check; last line: JUDGE-OFFLINE: ALL PASS
npm run zi -- verify INV-1111-V33-A # one read-only live check over testnet RPC: every line PASS, ends PASS no-access-keys / INFO status=PAID
The replay prints, among 62 PASS lines, PASS pay-tx-success INV-1111-V33-A GFzvAw8t… [], PASS split-merchant INV-1111-V33-A 0.92 and PASS split-vault INV-1111-V33-A 0.08.
Every step, with its full expected output, is in docs/VERIFY.md.
Headline numbers
| |
|---|
| 0 | transactions to issue an invoice |
| 1 | transaction to create the invoice account, pay and split the money |
| 0 | access keys on an invoice account (zi verify prints PASS no-access-keys) |
| 0.0075647 NEAR | measured cost of that one transaction to the payer (gas plus NEAR's 0.007 NEAR account-creation charge) |
| 255 + 104 | offline JavaScript tests (npm test) + Rust unit tests on the contract (npm run contract:test) |
| 1 | reproducible build: the deployed code CrwuvfSL… is what cargo near build reproducible-wasm produces at commit 7727a1c; CI rebuilds it from the on-chain metadata on every push, and it is verified on SourceScan (docs/REPRODUCE.md) |
This is the beginning of the README. Read the rest at the original. Read the full README ↗
