Democratic Backlog Prioritization
Quadratic conviction voting with time-decay. Surface the ideas your community actually cares about — not just the loudest voices.
Proposals accumulate conviction score from community votes. The most supported ideas float to the top.
Each additional vote costs quadratically more credits. Balances intensity of preference with breadth of support.
From ranking through promotion to final pass/fail vote. Proposals advance automatically when thresholds are met.
Daily credit allowances, vote decay, and sybil resistance. One person, one identity, one voice.
Community members spend credits to upvote proposals. Conviction score accumulates with quadratic cost.
When a proposal crosses the promotion threshold (default 100), it automatically enters the final vote.
A time-limited binary vote (Yes / No / Abstain) decides the outcome. Simple majority wins.
Traditional voting (1 person = 1 vote) lets small, passionate groups dominate. Token-weighted voting lets whales decide everything. Neither reflects genuine community preference.
Quadratic voting makes strong preferences expensive. You can signal that you care a lot — but it costs quadratically more. This balances intensity of preference with breadth of support.
The cost of conviction grows quadratically.
Every verified member receives a daily credit allowance. No pay-to-play.
Votes decay linearly from day 30 to day 60. Stale support fades, keeping rankings fresh.
Passkey authentication via EncryptID. One person, one identity, one credit stream.
Proposals that hit the threshold automatically move to a final pass/fail vote. No admin bottleneck.
The libraries and tools that power rVote.
Rock-solid relational database for proposals, votes, credit balances, and governance history.
Continuous preference signaling with quadratic cost and time-decay. Open-source governance math.
Ultrafast web framework for the API layer. Lightweight, edge-ready, and built for speed.
How rVote keeps your information safe.
All content encrypted before it leaves your device. Not even the server can read it.
The server processes your requests without ever seeing your data in the clear.
Run on your own infrastructure. Your server, your rules, your data.