STP.vote: Revolutionizing Democratic Elections with Separation of Three Powers(Participants)

Introduction

Electronic voting holds the potential to make democratic elections more efficient, transparent, and accessible. Yet existing systems — from paper-based methods to digital platforms such as Voatz and Estonia's i-Voting — share a fundamental structural weakness: the entity that runs the system also has the ability to observe or alter its results. This is not primarily a technology problem. It is an institutional design problem.

This article presents STP.vote (Separation of Three Powers Electronic Voting), an electronic voting architecture invented by Bob Li and granted Australian Patent No. 2022201573. STP.vote resolves the institutional design problem through a three-layer separation of Registration, Transmission, and Computation, combined with a five-node information isolation mechanism that makes it structurally impossible for any single party — or any combination of two parties — to simultaneously know both who a voter is and how they voted.

 

The Four Guarantees

STP.vote is designed to simultaneously satisfy four properties that no existing electronic voting system achieves together:

●        Absolute computational fairness: All candidates receive identical, real-time vote data via the same API. Any party can independently compute results and cross-verify with others — the final count is not determined by any single authority.

●        Absolute voter privacy: No node in the system holds enough information to link a voter's identity to their voting choice. Breaching one or even two nodes reveals nothing.

●        Universal end-to-end verifiability: Every voter receives two independent verification tokens (Token1 and Token2) after voting. They can enter these on any candidate's computation server to confirm their ballot was accurately recorded — without revealing their identity. No cryptographic expertise is required.

●        Perfect resistance to insider fraud and external cyberattack: Linking voter identity to voting choice requires simultaneously breaching three separately operated institutions. In a national deployment, registration servers alone number in the tens of thousands, operated across different political jurisdictions — making coordinated attack structurally impossible.

 

System Architecture

STP.vote separates the election process into three independent layers, each operated by a different institution with no shared data access:

1. Registration Layer — Municipal Government Registration Server

●        Verifies voter identity (name, date of birth, address, email).

●        Stores all personal data exclusively on municipal government servers — never transmitted to the voting system.

●        Obtains an anonymous identifier (V898) from STP.vote via API. The Registration Server does not know the voter's V898; it receives only the Voting Pass to forward to the voter.

●        All voter personal data remains permanently within the municipal government's jurisdiction.

2. Transmission Layer — STP.vote Server + Two Relay Nodes

●        STP.vote Transmission Server: Generates the anonymous identifier V898, the Voting Pass (a one-time QR code credential linked to V898 — not to the voter's name or date of birth), Token1, and Token2. Transmits encrypted vote data to all Computation Servers via secure one-way broadcast. Does not know voters' real identities or contact details.

●        Independent Anonymisation Server: Operates on a "forward only, no storage" principle. Receives Token1 from STP.vote and forwards it through the Registration Server to the voter, then immediately discards it. This breaks the direct path between STP.vote and the voter's contact details.

●        Parliament Email Server: Also operates on a "forward only, no storage" principle. Receives the Voting Pass and Token2 from STP.vote and delivers them to the voter's email address, then immediately discards them. STP.vote never learns the voter's email address.

3. Computation Layer — Independent Calculation Servers

●        Each candidate, media outlet, and independent institution operates its own Computation Server.

●        All servers receive identical, real-time voting data via API broadcast from STP.vote.

●        Each server independently tallies the results; discrepancies between servers are immediately visible to the public.

●        V898 cross-verification: Computation Servers can query the Voting Server using V898 to confirm that a ballot record is genuine — without learning the voter's real identity.

●        Physical backup: every vote generates a paper ballot printed at the polling station and deposited in a physical ballot box.

 

Five-Node Information Isolation

The following table shows the information boundaries of each node. No single party — and no combination of two parties — can ever simultaneously know "who this person voted for." Linking a voter's identity to their voting choice requires simultaneously breaching three separately operated institutions: the Registration Server (identity), the Independent Anonymisation Server (V386↔V123 mapping), and the STP.vote Transmission Server (V123↔V898 mapping).

 

Information Type	Registration Server (Municipal Gov't)	Independent Anonymisation Server	STP.vote Transmission Server	Parliament Email Server	Computation Server (Candidates)
Knows voter's real identity	✅ Yes	❌ No	❌ No	❌ No	❌ No
Knows voting choice	❌ No	❌ No	⚡ Handles during transmission; does not retain	❌ No	✅ Yes (anonymous)
Knows Token1 / Token2	❌ No	⚡ Forward only, no storage	✅ Yes	⚡ Forward only, no storage	✅ Yes
Can link identity to voting choice	❌ Cannot	❌ Cannot	❌ Cannot	❌ Cannot	❌ Cannot

 

 

Voting Process

(1) Registration Stage

●        The voter registers on the municipal government website, providing name, date of birth, address, and email.

●        The municipal government server calls the STP.vote API to register a voting slot and receives the Voting Pass.

●        The Voting Pass QR code is linked to the anonymous identifier V898 — not to the voter's name or date of birth. The voter's personal data never leaves the municipal government server.

●        The voter receives the Voting Pass via the Parliament Email Server and receives Token1 via the Independent Anonymisation Server → Registration Server. Neither relay server retains any data.

(2) In-Person Voting Stage

●        On Election Day, the voter brings their Voting Pass to the polling station.

●        Scan the QR code → verification passed → enter the federal voting page → select choices → click "VOTE".

●        Voting data is simultaneously: transmitted in real time to all Computation Servers via API; printed as a paper ballot for the voter to sign; and emailed to the voter as a record.

●        The signed paper ballot is deposited in the physical ballot box at the station.

●        Indelible ink is applied at exit to prevent double voting.

(3) Mail-In / Remote Voting

●        Available to military personnel, overseas voters, persons with disabilities, and other eligible groups.

●        Apply via the municipal government website; the Voting Pass is delivered by email upon identity verification.

●        Complete voting online; print and sign the ballot; mail the signed ballot to the local polling station as a physical backup.

(4) Dual Token Verification

●        Token1 (e.g., "gefehw"): generated by STP.vote, relayed via the Independent Anonymisation Server → Registration Server → voter. The relay server does not retain it.

●        Token2 (e.g., "hjtghf"): generated by STP.vote, relayed via the Parliament Email Server → voter. The relay server does not retain it.

●        Both tokens are stored only on the STP.vote Transmission Server and the Computation Servers of all candidates.

●        Any voter can enter both Token1 and Token2 on any candidate's Computation Server to confirm their ballot was accurately recorded. Because the tokens carry no identity information, verification exposes nothing personal.

●        The Voting Pass and voting link are single-use only, preventing duplicate voting.

 

Why STP.vote Is a Genuine Breakthrough

🔹 1. The End of the Vote-Counting "Black Box"

In every existing voting system — paper-based or digital — the vote-counting process is opaque. Even where audits are permitted, the public must ultimately trust that the count was performed correctly. STP.vote eliminates this requirement entirely: because all candidates receive identical raw vote data via the same API, any party can run the count independently and verify that every result matches. The outcome is mathematically reproducible and publicly transparent — no central authority's word is required.

🔹 2. Voters Can Confirm Where Their Vote Went

In traditional systems, once a ballot is cast, the voter has no way to confirm it was counted correctly. STP.vote gives every voter two anonymous verification tokens. Using these tokens on any candidate's server, voters can verify — without revealing their identity — exactly which candidate their vote was recorded for. This is end-to-end verifiability accessible to the general public, not just to cryptographers.

🔹 3. Structural Impossibility of Insider Fraud

Because voter identity and voting choice are held by completely separate institutions with no operational overlap, no insider — even a system administrator — can link a voter's name to their ballot without simultaneously compromising three independently operated nodes. The security guarantee is institutional, not merely technical.

 

Comparative Analysis

The table below compares STP.vote against mainstream voting approaches across the dimensions that matter most for secure, fair, and transparent elections:

 

Key Dimension	Mainstream Systems	STP.vote
Cyberattack Protection	Firewalls and centralised security; single point of failure	Five-node isolation; distributed hidden servers; one-way broadcast — no single node holds enough information to reconstruct voter identity ✅
Vote Verifiability	Few systems verifiable; cryptographic expertise required (e.g., Helios)	Any voter can enter Token1 and Token2 on any candidate's server to confirm their ballot — no cryptography knowledge needed ✅
Insider Fraud Resistance	Operator with system access can alter or observe votes	Three separate institutions must simultaneously collude — structurally impossible ✅
Architecture Design	Centralised or semi-centralised; operator is trusted by default	Registration, Transmission, and Computation fully separated; no operator can see both identity and voting choice ✅
Public Transparency	Results published by a central authority; public must trust the operator	All candidates receive identical data via API and can independently compute results — mutual verification eliminates single-authority trust ✅
Practicality	Academically sophisticated; difficult to explain or independently verify without specialist knowledge	Designed for general public understanding; verifiable by any voter without cryptographic expertise ✅

 

 

Conclusion

STP.vote addresses the deepest structural flaw in modern elections: the concentration of information in a single system operator who must be trusted but cannot be independently verified. Through the tri-power separation of Registration, Transmission, and Computation, combined with five-node information isolation and dual-token end-to-end verifiability, STP.vote makes it structurally impossible — not merely technically difficult — for any party to commit undetected election fraud.

Without fair elections, there can be no true democracy. STP.vote provides a practical, publicly verifiable path to elections that are simultaneously secure, fair, transparent, and accessible to all voters — without requiring any knowledge of advanced cryptography.

 

This research was independently conducted by inventor Bob Li

Australian Patent No. 2022201573

Contact Information:

Email: bobli@stp.vote

Phone/WhatsApp: +61 420 355 918

X: https://x.com/STPvoteOfficial

Official Websites (under construction): STP.vote | STPvote.org | STPvote.com

Monday, November 9th, 2020