Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 141 of 179

Conviction Voting

A governance method where support accumulates the longer you hold a position, funding proposals continuously as conviction builds — designed for ongoing treasury allocation without snapshot-vote gaming.

Beginner
8 min readUpdated July 2026Block Clarity Hub Editorial Team

Support That Builds Over Time

Conviction voting is a governance mechanism where your support for a proposal grows stronger the longer you keep backing it, rather than being a single yes/no snapshot. You stake your voting power on proposals you favour, and 'conviction' accumulates over time the longer your support stays in place. When a proposal's accumulated conviction crosses a threshold (which is higher for proposals requesting more funds), it passes and is funded. There is no fixed voting day — proposals pass continuously whenever enough sustained support builds up behind them.

Why Continuous, Time-Weighted Voting

It was designed to fix problems with traditional snapshot voting, where a proposal is decided by whoever shows up (or whales who swing in) at a single moment. By rewarding sustained conviction, it favours proposals with durable, genuine support over ones that win a momentary popularity spike or a last-minute whale vote. It also lets a community allocate an ongoing treasury smoothly — proposals flow through as support matures — rather than through disruptive all-or-nothing voting events. It is used by DAOs (notably in the Aragon/1Hive ecosystem) for continuous funding decisions.

  • Conviction (support strength) accumulates the longer you back a proposal
  • A proposal passes when its conviction crosses a threshold (higher for larger asks)
  • There is no single voting day — proposals pass continuously as support matures
  • Designed to reward durable support and enable smooth ongoing treasury allocation

Key Takeaways

  • Support strengthens over time rather than being a one-moment snapshot
  • Proposals pass when sustained conviction crosses a funding-scaled threshold
  • It suits continuous treasury funding and resists momentary vote swings

Related Content

Permit2 & Signature Approvals

How Permit2 and EIP-2612 replace clunky, dangerous unlimited token approvals with signed, time-boxed permissions — improving UX and safety, and where the new signature surface can still be abused.

Account Abstraction: Paymasters & Bundlers

A deep dive into the ERC-4337 machinery beyond the wallet: how bundlers relay user operations, how paymasters sponsor or tokenise gas, and the economics and trust of gasless transactions.

Decentralized AI Training & Inference

How crypto networks try to coordinate distributed AI compute, training, and inference — Bittensor, Akash, Ritual and others — the token incentives involved, and the hard technical limits.

Quadratic Funding

How quadratic funding uses a matching pool and a square-root formula to fund public goods by breadth of support rather than size of wallet — the math, why it fights plutocracy, and how sybils break it.

Futarchy: Governance by Prediction Markets

A governance model that decides policy using prediction markets — 'vote on values, bet on beliefs' — its elegant logic, the real experiments running it, and why it is powerful but perilous.

Retroactive Public Goods Funding

The 'reward impact after it happens' model — RetroPGF — that funds public goods based on proven results rather than promised plans, why it fixes prediction risk, and the hard problem of judging impact.

Shared Sequencing & Based Rollups

Who decides the order of transactions on a rollup — and why decentralising that role matters. Shared sequencers, based rollups, and preconfirmations, explained without hype.

ZK Coprocessors

How smart contracts can trustlessly use heavy computation and historical chain data they could never afford to process on-chain — by verifying a zero-knowledge proof instead of redoing the work.

References & further reading