zkVerify prototype · testnet
ProofRoute
Prototype for proving that a delivery was picked up and dropped off without exposing the customer’s address or GPS trail, using zero-knowledge circuits, zkVerify and a USDC escrow contract on a test network.
The problem
Proving a delivery happened usually means keeping the customer’s address and GPS trail. Zero-knowledge proofs can show it happened without revealing them.
What it does
- Four apps: a worker PWA, a merchant console, a bilingual marketing site and the API.
- Two real Circom circuits, one for pickup and one for drop-off, with witness generation and a geofence check.
- Relay code that uses snarkjs and zkverifyjs to submit proofs.
- Solidity contracts for a USDC job escrow and a proof registry, with a mock USDC for tests.
- Passkey (WebAuthn) sign-in scaffolding.
How it is built
- Fastify 5 API, Next.js 16 apps, Postgres 16 and Redis 7; Hardhat 3 and viem for contracts.
- Docker Compose, PM2 deploy scripts and a staging runbook.
- Targets the Base Sepolia and zkVerify test networks.
Honest notes
- A prototype. By default the zkVerify relay is a stub and circuit artifacts are placeholders; the project’s own audit rates verification as partial.
- Its release notes say go for testnet, hold for production.
Engineering depth
Counts taken from the repository itself, not performance claims.
- ~35
- API routes
- 2
- zero-knowledge circuits
- 3
- Solidity contracts
- 106
- commits, March to June 2026