The open way to run
a community onchain
The Netizen Stack is the open source framework for digital citizenship: verified members, secret ballots, and tallies nobody has to take on faith.
One stack, every community.
Three modular layers: who belongs, what the community decides, and who can see the votes. Each layer is useful on its own. Together they replace the platform a community would otherwise rent, with infrastructure it owns.
Developed in the open, built on research from the Ethereum community, and already proven in production: a 750-year-old German town runs its citizen participation on this stack today.
Election-grade guarantees
Sovereignty and control
Attestation thresholds, voting windows, quorums and keyholders are parameters your community governs, not settings a vendor controls.
Secret ballots
Votes are encrypted on the voter's device and receipt-free. Nobody can prove how anyone voted, which makes coercion and vote buying pointless.
Tallies that cannot lie
Results are accepted onchain only with a zero-knowledge proof of correct counting. A wrong count is not disputed, it is impossible to submit.
No single operator
The decryption key is federated 3-of-5 across community keyholders. Between tallies it does not exist anywhere. Nothing to steal, subpoena, or leak.
Free for citizens
Account abstraction sponsors every transaction. Members vote with one tap, no wallet ceremony, no gas, no seed phrase.
Battle-tested infrastructure
Not a science project: deployed on Base mainnet, operated through real elections, with the runbooks and the production bugs published.
Designed for trust
Three layers, one stack
Citizenship
One verified human, one soulbound credential. Social attestation instead of document upload: nothing collected, nothing to leak.
Voice
MACI secret ballots with Groth16-proven tallies, wrapped in one-tap gasless UX a non-technical member actually completes.
Trust
The 3-of-5 key federation. Opening the ballot box takes three citizens acting in public; alone, everyone holds nothing.
Built in the open, bugs included.
The contracts, the apps, the coordinator, the key ceremony runbooks, and the ten production bugs we hit on the way are all public. The next community should not have to rediscover any of it.
By communities, for communities.
The Röbel case study
The full production story: architecture, workflows, numbers, and the day the system refused to lie. Read it ›
Runbooks and ceremonies
Operational documentation for deployments, key ceremonies, and tally sessions, as run in production. On GitHub ›
Field notes
Deep technical writing on the coordinator federation, the strategy, and what we learn town by town. Read the notes ›
Bring your community onchain.
Start with the open source stack, or let us run the pilot with you: deployment, ceremonies, and the words your members will understand.