KUDVO Request a demo

Blockchain-Backed Voting

Central control.
Independent integrity.

Kudvo is a next-generation voting platform for elections, resolutions, motions and surveys. The authorized organisation controls the voting event; blockchain protects the integrity evidence.

See how it works Explore voting events
No wallet required Anonymous ballots Central authority retained
The Kudvo model
Authority Creates and governs the voting event
→
Voting Server Validates, accepts and processes votes
→
Blockchain Proof Preserves tamper-evident integrity evidence
Not Bitcoin-style voting. No public wallets. No public vote ledger.

What Kudvo solves

From “trust our database” to “verify the integrity.”

Conventional online voting ultimately depends on the integrity of a centrally managed database. Kudvo keeps the practical advantages of a central application while creating an independent cryptographic record that exposes unauthorized changes.

01

Central administration remains mandatory

Only authorized administrators create the voting event, eligible voter list, questions, candidates or options, timing and result rules.

02

Blockchain is the evidence layer

Blockchain does not run the voting event. It receives cryptographic commitments proving what the platform recorded at each controlled stage.

03

Ballot secrecy is preserved

Identity and eligibility checks remain separated from the anonymous ballot record. The blockchain stores proofs, not readable voter choices.

One platform, many voting events

Voting is wider than elections.

Kudvo treats every decision process as a configurable Voting Event.

Election Voting

Positions, candidates, single or multiple selections, weighted rules, multiple seats and organization-specific election workflows.

Resolution / Motion Voting

Board, AGM, association and corporate resolutions with For / Against / Abstain, weighted entitlement, quorum and approval thresholds.

Survey Voting

Polls, preference ranking, feedback questions, member consultations and configurable response formats under the same secured event framework.

One event engine. Different voting rules, voter groups, authentication levels and audit requirements — all configured by the authorized administrator.

Architecture

Central voting system + blockchain proof layer

Kudvo is intentionally not a permissionless Web3 voting network. The voting authority remains responsible for governance and operational control.

Authority Layer

Voting Authority / Organisation

  • Create voting event
  • Define roles and administrators
  • Upload / approve eligible voters
  • Configure authentication rules
  • Create positions, candidates, motions or questions
  • Open, close and publish results
→
Operational Layer

Kudvo Central Server

  • Authenticate voter
  • Check eligibility and voting status
  • Load correct event and ballot
  • Validate business rules
  • Accept vote atomically
  • Generate results and reports
→
Integrity Layer

Blockchain Integrity Engine

  • Canonical event hashing
  • Sequential event chaining
  • Digital signing
  • Merkle batching / root creation
  • Blockchain anchoring
  • Independent verification
Principle: Centralized governance. Anonymous voting. Distributed, tamper-evident proof.

Blockchain implementation

What gets protected?

Kudvo can commit critical lifecycle events so later database changes become detectable.

01VOTING_EVENT_CREATEDEvent identity, authority, rules and initial configuration.
02CONFIGURATION_FROZENPositions, candidates, motions, questions and voting rules committed.
03VOTER_ROLL_COMMITTEDEligible voter population protected as a cryptographic commitment.
04VOTING_OPENEDOfficial start status and timing recorded.
05BALLOT_ACCEPTEDAnonymous ballot commitment and sequence evidence generated.
06VOTING_CLOSEDOfficial closure and final accepted ballot state committed.
07RESULT_COMMITTEDPublished result becomes independently verifiable against the committed history.
1Normal stateOperational database matches the blockchain-backed commitment.
→
2DBA changes dataA vote, count, configuration or result is altered directly in SQL.
→
3Integrity failureRecomputed proof no longer matches the anchored evidence.

Anonymity preserved

Verify integrity — not voter choice.

The identity domain and ballot domain must remain technically separated.

Kudvo should be able to prove:

“This valid voter was authorized and a valid anonymous ballot was accepted.”

Kudvo should not be able to prove:

“This specific person voted for Candidate X / Option Y.”

Identity & eligibility
Voter identity
Authentication
Eligibility check
One-time authorization token
Privacy boundary
Anonymous ballot
Ballot issued
Vote selected
Ballot committed
Blockchain proof

KUDVO

Voting events with central authority and blockchain-backed integrity.

For elections, resolutions, motions, surveys and other trusted decision processes.

Next step

Build the Kudvo pilot

Start with a production-capable institutional platform, prove the tamper-detection model, then expand toward high-assurance and future government deployments.

Contact Kudvo