Prove it here.Publish nothing.

ZECBASE takes the Zcash shape — a note nobody can trace, a book that still adds up — and puts it on Base, proved in your own browser over BN254. No trusted setup. No proving key to fetch. Nothing you type leaves the tab.

SEC.000 — BEFORE ANYTHING ELSE

Do not read six sections
before you have seen one work.

Type a number. The page commits to it, proves it clears a public bar, verifies that proof, then tries to stretch it into a claim it cannot support and gets refused. A few hundred milliseconds, entirely on your machine.

Nothing has run yet. Nothing will be sent when it does.

ISEC.001 — THE RECORD

BASE REMEMBERSEVERY ADDRESSYOU HAVE EVERBEEN.

A public chain is an index, not a ledger. One transfer ties a wallet to a name, and every transfer before and after it comes with the name attached. Nothing on Base forgets, and nothing on Base asks first.

  • 01Every balance, readable by anyone, forever
  • 02Every counterparty, joinable across chains
  • 03Privacy is a proof problem, not a policy
IISEC.002 — THE NOTE

ONE NOTEOUT OF MANY,SPENT ONCE.

A note is a Pedersen commitment. Spending it publishes a proof that one commitment in the set opens to a secret you hold, plus a tag derived from that same secret. The set never says which note moved. The tag makes moving it twice impossible.

  • 01Commitment and nullifier, the Zcash shape
  • 02A ring over the whole set, not a mixer
  • 03Double spends are caught by arithmetic
$ZECBASE · CONTRACT ON ROBINHOOD CHAIN
Read it on the explorer →
IIISEC.003 — THE SEAL

A BOOK THATADDS UPWITHOUTOPENING.

A launch publishes one number: the supply. Every allocation behind it stays sealed, and the same page proves the sealed amounts sum to that supply and that not one of them is negative. Open a line later if you choose; the commitment already bound you to it.

  • 01Allocations hidden, total public and proven
  • 02Every line proven non-negative, bit by bit
  • 03Reveal is optional, and cannot be rewritten
OPEN

I know what is inside this commitment.

2 points, 2 scalars
RANGE

The hidden balance clears the threshold.

32 bit proofs
RING

One of these notes is mine, and here is its tag.

3 scalars per note
SEAL

The hidden lines add up to the published total.

1 proof, any book
IVSEC.004 — THE WINDOW

EVERY WINDOWOF BLOCKS,COMMITTED,LINKED.

Blocks tile into windows of 512. Each window commits to the state root it opens with and the one it closes on, then proves it opens exactly where the last window closed — without publishing either root. The lineage is auditable. The contents are not.

  • 01Real roots, read live from Base at both ends
  • 02Linkage proved as pure blinding, zero leakage
  • 03Strict sequence: no gaps, no re-cutting
VSEC.005 — THE CORE

ONE LIBRARY.NO TRUSTEDSETUP.NO SERVER.

Sigma protocols over BN254, made non-interactive with keccak. There is no ceremony to trust, no proving key to download, and no endpoint that sees your inputs. The same file runs the assertions in your tab and in the repository's test run.

  • 0127 assertions, run locally, on demand
  • 02Half of them prove that forgeries fail
  • 03Bundles are JSON anyone can re-verify
SEC.006 — THE TOKEN

$ZECBASE PAYS FOR THE PROVING.

The core is free and always will be: it runs on your machine. The token funds what cannot — the relayer that pays gas for people who should not be seen paying it, and the anchors that keep the lineage tiling forward, window after window.

ZECBASE is a proving library and a page that runs it. Proofs are generated and checked in your browser; no secret you type is transmitted anywhere. Nothing here is investment advice, and no contract is claimed to be deployed until its address is printed on the token page.