Summary: Vocdoni is best understood not as a voting app, but as a full governance backend that bundles a purpose-built blockchain, gateway/indexer nodes, multiple voter-eligibility systems, IPFS-published election metadata, and optional anonymous voting into one election stack. The reusable mechanism is its separation of concerns: Vochain settles process state, gateways expose API and compute off-state results, different census origins define who counts as a voter, and client-side or gateway-side proof machinery determines whether voting is pseudonymous or anonymous. That makes Vocdoni a useful comparison class for Snapshot-style offchain governance, onchain governor systems, and election tooling where the real control surface is not just who votes, but who defines eligibility, who runs gateways, who admits validators, and who publishes results.
What it does:
Runs a dedicated governance backend around Vochain, a Byzantine-fault-tolerant blockchain used to register elections and votes
Exposes HTTP APIs through gateway nodes that also index chain data, compute results, and serve census proofs to clients
Supports several census origins, including weighted Merkle trees, indexed Merkle trees for zk voting, credential-service-provider flows, and token-holder censuses via Census3
Lets organizers create elections with configurable lifecycle, dynamic or immutable census rules, anonymous or pseudonymous voting, encrypted or public results, and overwrite / pause / interruption settings
Uses Ethereum-style accounts and delegates so organizations can create and manage elections with familiar wallet tooling
Publishes auxiliary election data such as questions, descriptions, images, and censuses to IPFS rather than storing everything directly in chain state
Key claims:
The protocol docs frame Vocdoni as a decentralized backend rather than just a UI: Vochain provides data integrity and universal verifiability, gateways provide the API and indexing layer, and IPFS stores auxiliary election data. That layered design is the main reason it belongs in the corpus.
Vochain currently runs as a Proof-of-Authority network, while the docs say a Proof-of-Stake transition is planned. The current validator surface is therefore materially more permissioned than generic decentralization language might imply.
The vocdoni-node README makes that validator-control surface unusually explicit: miner / validator admission is selective, not currently compensated, and prospective operators are told to contact the team so their node can be upgraded to validator status. This is a meaningful governance choke point.
The docs say voters do not need the native VOC token to cast ballots, but management actions such as creating elections do require it. That separation matters because it lowers user participation friction while keeping organizer and process-creation power inside the native control plane.
Gateway nodes are not passive RPC relays. The protocol docs say gateways compute election results and provide census services because those outputs are not part of core state. That means practical trust and availability sit partly with gateway/indexer operators even when ballot validity is chain-anchored.
Vocdoni’s census system is one of its strongest analytical contributions. The docs separate weighted Merkle trees, indexed Merkle trees for zk circuits, credential-service-provider flows, and token-holder censuses. In other words, the protocol treats voter admission as modular infrastructure rather than a single voter list.
The election-mode and vote-mode options show how much governance logic gets parameterized before a vote starts: dynamic census, anonymous ballots, encrypted votes, interruptibility, and vote overrides all meaningfully change coercion resistance, electorate mutability, and organizer discretion.
Vocdoni is a strong comparison class for Snapshot, Hats, Guild, Prop House, and other governance tools because it packages voter eligibility, tally publication, and verifiability into a dedicated protocol stack rather than outsourcing those pieces to separate services.
Whitepaper: No single canonical Vocdoni whitepaper surfaced in this pass. The strongest primary materials reviewed were the official developer portal, protocol docs, node README, and SDK README; see ../whitepapers/vocdoni-primary-sources-2026-05-10.md.