Protocol Wars & Forks5 min read

Decred Politeia: After the Vote, Who Sends the Money?

Politeia gave Decred stakeholders a say over project spending in 2018. Actual payment still needed a manager’s signature. The later decentralized treasury shows how approving work differs from controlling the transaction that pays for it.

Decred Politeia: After the Vote, Who Sends the Money?

3-Minute Fast Briefing

  • The ParadoxPoliteia launched on October 15, 2018, as an off-chain system for proposals and stakeholder voting. Its launch post explicitly acknowledged that a manager still had to sign treasury payments.
  • The Turning PointProposal voting used eligible staking tickets, with a 20% participation quorum and 60% approval threshold. A funded proposal created a budget to claim against as work progressed.
  • The LegacyDCP0006 later required on-chain approval for spending from a new treasury account. Human work and administration remained, and a 2021 spending-limit bug showed that payout rules also needed scrutiny.

Chronological Timeline

October 15, 2018Politeia goes live

Stakeholders gain a formal proposal process; the launch announcement distinguishes voting power from payment-signing control.

2021 · block 552,448A new treasury account

DCP0006 becomes active, requiring stakeholder approval for expenditures from the new account.

June 25, 2021A payout delay is disclosed

A spending-limit bug blocks normal payments from the new treasury; the project says contractors will continue to be paid from the legacy wallet.

The Signature Left at the End

On October 15, 2018, Jake Yocom-Piatt announced that Decred’s proposal system, Politeia, was entering production. The launch transferred an important part of the project’s financial decision-making to stakeholders. In the same post, he identified a limit: releasing treasury funds still required his signature as a manager of the development organization. He retained a possible veto if a payment endangered the project or created legal jeopardy.[1]

This was an unusually concrete description of a governance transition. A community could decide which work deserved funding while a conventional organization still controlled the transaction that paid for it. Politeia, an off-chain proposal and voting platform, changed how decisions were reached. It did not instantly replace the human signer at the end of the process.[1][6]

A Budget Is Permission to Do Work

The system gave proposals a public path through submission, discussion, revision and voting. A spending proposal established a budget that could be drawn down as progress was demonstrated. Approval was therefore connected to a program of work, not necessarily to an immediate transfer of the entire requested sum. The distinction matters whenever a project pays contributors over time.[2]

Voting was tied to live staking tickets, obtained by temporarily locking DCR, rather than to the number of website accounts. The documented proposal rules require 20% of eligible tickets to cast a yes or no vote and at least 60% of the votes cast to support approval. Votes require wallet signatures. These are the proposal rules; they should not be substituted for the separate rules governing every on-chain vote.[2]

Moderation with a Receipt

Politeia also retained administrators. Submitted proposals were reviewed, spam or invalid material could be censored, and an administrator started voting after the author authorized it. The design did not pretend that a proposal website could operate without moderation. It tried to make the exercise of that authority visible.[2]

The documentation describes censorship tokens: cryptographic receipts that let a submitter demonstrate what was submitted and challenge its suppression. This makes the claim narrower and more useful than an assertion that nothing can ever be removed. A receipt can establish a record of submission; it does not force other participants to endorse the proposal or turn an unpopular idea into a funded project.[2]

Moving the Spending Decision On-Chain

The next change concerned the treasury itself. DCP0006 specified a new treasury account whose funds could be spent only with stakeholder agreement. Authorized Politeia key operators still constructed and signed a treasury-spend transaction. Voting wallets then expressed stakeholder preferences through on-chain votes. The spending transaction became valid only after sufficient approval under the treasury rules.[3]

The specification records activation at block 552,448 in 2021. This moved an important condition for spending into consensus: an operator’s signature alone could not release funds from the new account. It did not make proposals write themselves, verify a contractor’s work automatically, or remove the operators who assembled payment transactions. Each of those jobs remained distinct from approving the spend.[3]

When the Guardrail Stopped Payments

The machinery soon exposed another boundary. On June 25, 2021, Decred disclosed that an overly restrictive expenditure check was preventing normal payments from the new treasury. A small test payment had become the basis for a spending limit that was too low. The project reported no funds at risk from this issue and said contractor payments would continue through the legacy treasury wallet while the new system was repaired.[4]

DCP0007 proposed changing the expenditure policy back to the income-based approach approved in the original proposal. Its recorded activation at block 657,280 confirms that the correction later passed through consensus governance; it was not merely an administrator changing a website setting. The specification now also notes that a subsequent proposal, DCP0013, superseded it. This episode describes a historical repair, not a permanent account of today’s spending formula.[5]

What a Treasury Vote Can Decide

A vote can settle whether a defined budget has stakeholder support. It cannot establish by itself that the work is good, that an invoice is accurate or that a voter has understood every trade-off. The launch post explicitly warned about poor spending decisions and resisted treating Politeia as a tool for micromanaging contributors. Funding a team and directing every task are different responsibilities.[1][2]

Decred’s experiment is revealing because it exposes the steps often hidden inside the word governance. People propose work, ticket holders weigh it, contributors deliver it, and a payment still needs preparation and authorization. Politeia made the decision process more explicit; the treasury changes constrained how money could leave. Following both histories lets a reader ask a precise question about any community fund: where does the vote end, and what still has to happen before someone is paid?[1][2][3]

Connected Lore & Universe

Connected Stories in this Universe

Explore the chain reaction of historical breakthroughs, blunders, and legends.

Sources & References

  1. [1]Source 1: Politeia launch: stakeholder control and the remaining manager signatureDecred Blog · 2018-10-15Accessed 2026-09-14
  2. [2]Source 2: Politeia overview: budgets, ticket votes and transparent censorshipDecred DocumentationAccessed 2026-09-14
  3. [3]Source 3: DCP0006: decentralized treasury process and activationDecred Change ProposalsAccessed 2026-09-14
  4. [4]Source 4: June 2021 disclosure of the treasury expenditure-policy bugDecred Blog · 2021-06-25Accessed 2026-09-14
  5. [5]Source 5: DCP0007: expenditure-policy correction and activation historyDecred Change ProposalsAccessed 2026-09-14
  6. [6]Source 6: Decred project history: Politeia and contractor invoicingDecred DocumentationAccessed 2026-09-14
← Back to all storiesExplore all coins →