Collaborative Decision Deposits Are Live on Kusama: Crowdfunding the 666.67 KSM Barrier

I have watched a good governance proposal die for a boring reason: nobody could front the entire decision deposit. On Kusama, a Wish for Change needs 666.67 KSM before it can go to a vote, and governance takes that deposit from one account. Support is not the bottleneck; liquidity concentration is. So when the birdbrain team announced a live contract that lets many accounts share the deposit, I wanted to know whether this is a clever hack or a real fix.

Key Metrics at a Glance

How the Contract Works

Each pool is fixed to one referendum and its exact deposit. It has no owner, no admin key, and no upgrade path. Contributors pay from their own accounts, and the payment that fills the pool tries to place the deposit in the same transaction. If placement fails, the money stays in the pool and anyone can retry. Contributors can withdraw while the pool is open and before placement. After the referendum ends, anyone can reclaim the deposit and send payouts to contributors as separate calls. Approved, rejected, cancelled, and timed-out referenda allow a refund; killed referenda do not. Network fees are additional.

The Live Numbers

The Kusama pool for #676 opened with a target of 666.66666666 KSM and a 5 KSM minimum. By November 1 it held 380 KSM from three addresses; by November 2 it held 435 KSM, leaving 231.67 KSM before the November 3 deadline. Contributors included a 25 KSM test-then-contribute and a 10 KSM top-up. On Paseo, the byte-for-byte rehearsal (#147) needs 20,000 PAS with a 500 PAS minimum, and a separate 1 PAS proof pool (#145) was expected to end around November 6.

What the Code Review Found

Community review moved fast, which is exactly what an unaudited contract needs. Zealynx flagged three real issues: (1) reclaim() calls weighMessage(refundMessage()) as an ordinary call before the low-level refund, so if weighing ever fails after a runtime upgrade, reclaim reverts even with the KSM already back in the contract, and with no admin there is no other path to the refund state; (2) KSM sent directly to the contract mapped account via a plain balances transfer never enters pool accounting and is stranded; (3) an address that withdraws and pays again is listed twice, so contributorCount() overcounts, harmless for payouts but misleading on the page. Birdbrain acknowledged the duplicate-entry issue and fixed the page; the contract itself is immutable by design.

Comparing Governance Deposit Models

A Deposit Accessibility Score

Define Deposit Accessibility as potential contributors divided by single-account deposit size, adjusted for refund safety. Kusama default scores terribly: one account versus 666.67 KSM. The pooled model raises the numerator into the hundreds at the cost of smart-contract risk. The score makes the trade-off explicit: crowdfunding democratizes participation but adds a code layer that must be audited.

Risks Before You Contribute

• No independent audit -- the team deployed before review to beat the timeout; treat funds as at-risk until audited.
• Killed referenda lose the deposit -- a bug or a kill means contributions may not be refundable.
• reclaim() revert risk -- the weighMessage path could strand refunds after a runtime change; the public-network refund is still unproved.
• Stranded transfers -- KSM sent directly to the contract account outside contribute() is never repaid.
• Deadline pressure -- funding closes November 3, 12:00 UTC, ahead of #676 estimated timeout.

TL;DR

• What: A live Kusama contract lets many accounts crowdfund the 666.67 KSM Wish for Change deposit for referendum #676.
• Status: Pool at 435 of 666.67 KSM (~65%) as of November 2; funding closes November 3, 12:00 UTC.
• Caveat: Experimental and unaudited, with no admin or upgrade path; killed referenda lose deposits.
• Watch: independent code review, the Paseo #147 rehearsal outcome, and whether this spreads to Polkadot.

Sources

• Polkadot Forum: Collaborative decision deposits live on Kusama
• birdbrain collaborative deposit tool
• Polkadot Fellows RFCs (crowdsourced deposits)
• Polkadot Wiki: Governance

Gemma Nguyen is Content Lead & Journalist at TotesTek. She writes about cryptocurrency, Web3, DeFi, and the Polkadot ecosystem, blending personal experience with evidence-based analysis.