BombayLocal

Show a valid train pass. Reveal nothing else.

A passenger's phone proves "I hold a valid pass" with a zero-knowledge proof. The ticket checker's phone verifies it offline in about 50 ms and learns one thing: this pass is valid right now. Try both phones below: real Ethereum, Arkiv and proofs; only the payment is simulated.

Passenger · BombayLocal Pass

Buy a pass

Your pass lives on this phone and works without signal.

Simulated payment — no money is charged

The pass secret exists only in this tab's memory. The Android app keeps it in the phone's Keystore.

Ticket checker · BombayLocal Scan
Syncing…

Drag this phone onto the pass code

Synced once from Ethereum and Arkiv. Every check then runs offline in this browser.

What the scanner learned

Nothing yet. Scan a pass.

Requests the page made during the check (fetch/XHR)
—
Check time
—
Name, phone number, pass ID
never sent

Behind the scenes

  • Real Ethereum Sepolia and Arkiv data. The only simulated part is the payment.

How it works

  1. Buy. Your phone makes a secret and sends only its one-way hash. The issuer adds it to the list of valid passes.
  2. Publish. The issuer posts one 32-byte fingerprint of the whole list (a Merkle root) on Ethereum, and the list itself on Arkiv.
  3. Prove. Your phone rebuilds the list from Arkiv, checks it against Ethereum, and makes a zero-knowledge proof: "my pass is in this list and valid today". The code changes every 10 minutes.
  4. Check offline. The checker's phone verifies the proof and the issuer's signature with no internet. Showing the same code twice turns Amber, then Red.

Limits we state up front: duplicates are caught per scanner; the trusted setup is demo-grade; the authority is a single key (a multisig in production); payment is simulated. Details in the README.