Fuse v0.1.0 · early prototype

Fuse v0.1.0 · early prototype

Anonymous, rate-limited access to the protected parts of the web. A server stops asking "who is this?" and asks "has this client used up its budget?", enforced with zero-knowledge proofs so nobody learns who anybody is.

1. Back it once. Put down a deposit at a registry and get a credential. The registry never learns where you use it.
2. Spend a daily budget. Each credential gets 200 first-contact slots a day across the whole web. The first time you touch a site's login, upload, API or admin page costs one. Public pages are free.
3. Get a sticky local pseudonym. Same site, same pseudonym, so bans stick. Different sites can't link you.
4. Cheating confesses. Every slot is a point on a secret line. Use a slot twice and the two points reveal your key; the shared log publishes it and the credential burns.

Try it (Node 22): npm install && npm run demo, then open http://localhost:4700 for four scenarios: an honest agent, a mass scanner, a cheater, and a ban that sticks. A Chrome extension and an agent CLI (npx fuse) are included.

Real: Groth16 proofs (circom, 6,076 constraints, 389-byte token, ~0.2 s to prove), Poseidon Merkle membership, key recovery, slashing, revocation, an RFC 6962 log with Ed25519-signed tree heads, sticky per-pseudonym bans.

Simulated: deposits are play money, the trusted setup is a single-party development ceremony (not for production), and there is one registry and one log. See docs/design.md §9–10.

3-minute explainer: https://www.youtube.com/watch?v=QrJPH10kAC4

MIT licensed.