This site is satire. Data may be incomplete, links may break, scores are opinions. Verify at Congress.gov before citing us in your dissertation.

Leg day: Fri → Fri (19d) Recess

ABSURDITY INDEX OF THE UNITED STATES

EWP POC — Step 3 of 3

Oversight Dashboard

Verified

0

Crypto-Conflict

0

Spoiled

0

BB Leaves

0

Ledger Events

0

Controls

Trustee Shares (POC)

Select at least t shares to simulate threshold decryption at tally time.

Note: in production, trustee shares are held by independent people/organizations and are never stored together in one place.

Latest BB STH

Every time a ballot is added, the bulletin board publishes a new Signed Tree Head — a cryptographic snapshot of all ballots received so far. If anyone deletes or alters a ballot later, the snapshot won't match, making tampering detectable.

STH snapshots are recorded on the state node's distributed ledger as bb_sth_published events. In a real election, they would also be published to a public append-only log — independent monitors, media, and political parties could all download and compare tree heads to detect any inconsistency.

Loading...

Published Tally (POC)

Click Publish POC Tally above to decrypt all ballots and count the results.

In this POC, each ballot is encrypted with a fresh per-ballot key and that key is wrapped to an election public key whose secret is split across trustees (t-of-n). Publishing the tally reconstructs the election secret from trustee shares and decrypts locally. In a real election, trustees would decrypt during a public ceremony and publish decryption proofs.

Not published.

Fraud Flag Review Queue (POC)

cases only

This queue simulates the reviewer workflow from the VoteChain PRD: triage, investigation, escalation, and resolution. Every reviewer action is recorded as an immutable ledger event on the distributed oversight node.

Note: this is a demo. In a production system, reviewer actions would be role-gated, dual-controlled where required, and signed with reviewer credentials.

Flag Type Status Updated Case Nullifier Assigned Action

VoteChain Ledger Events

newest first

Every significant action — publishing the manifest, casting a ballot, issuing a tree head, publishing the tally, or flagging fraud — is recorded as a signed, immutable event on the VoteChain ledger. This is the public audit trail.

Ledger events are recorded on 3 distributed Cloudflare Workers nodes (federal, state, oversight) with Durable Object append-only storage. In a real election, VoteChain would span many more independent nodes — election authorities, civil society organizations, and international observers — so that no single party could rewrite history without detection.

Type Recorded Tx Payload

Bulletin Board Leaves

newest first

Each encrypted ballot gets its own "leaf" on the bulletin board — an append-only list that anyone can inspect. You can see the encrypted ballot hashes here, but not the votes themselves. The leaf hash is the identifier voters use to verify their ballot is included.

In this POC, BB leaves are stored locally in your browser. Each ballot cast is also anchored on the distributed ledger via an ewp_ballot_cast event. In a real election, the bulletin board would be a publicly accessible, append-only server — anyone could download the full list of leaves and independently verify the Merkle tree, ensuring no ballot was added, removed, or modified after acceptance.

Leaf Hash Received Ballot Hash