This referendum is part of the Kusama Bounty Cleanup initiative, which aims to clear stale proposals and inactive bounties from Kusama's bounty system.

It rejects five stale bounty proposals: #34, #35, #36, #37 and #39. Their requested budgets were never approved or set aside; rejection removes them from the list.

The decisions are independent (Utility.force_batch): if a bounty changes state before enactment, only its decision fails and the others still apply.

Why

These five bounty proposals have been in the Proposed state for 13 to 18 months, and none can move forward:

• #34: its approval (with a curator) was put to a vote in referendum #517, which was rejected on 24 Apr 2025.
• #35, #36, #37: their approval was put to a vote in referendum #632, which was rejected on 10 Feb 2026. The same three topics have since been funded as multi-asset bounties MA-0, MA-1 and MA-2 (referenda #647–#649, approved on 19 May 2026), so these proposals are no longer needed (the link rests on matching titles; it is not recorded on chain).
• #39: no referendum has ever proposed to approve it.

None of them was ever funded, so rejecting them returns no budget. The only funds that move are the proposers' bonds (0.169667 KSM in total), which the Bounties pallet slashes to the Treasury on every rejection; this is how the pallet works, not a penalty chosen for these proposals. Rejecting them clears proposals that can no longer progress.

Decisions

Effect on the treasury

For scale: the treasury holds 910,833.26 KSM available at block #22,545,764 (14 Oct 2026, 04:45 UTC); this referendum adds 0.169667 KSM to it when enacted. It will have moved by enactment.

The bounties today

Read on Kusama Asset Hub at block #22,545,764 (14 Oct 2026, 04:45 UTC); history from our indexer, which re-reads the chain.

#34 KSM RFP#3 - Kusama.App

#35 Zero-Knowledge and Advanced Cryptography

#36 Proof-of-Personhood

#37 Art

#39 Bounty

Technical details

Testing

The exact proposal above was dry-run with DryRunApi.dry_run_call, origin Origins.Treasurer, against the state of live Kusama Asset Hub at block #22,545,764 (14 Oct 2026, 04:45 UTC) (statemine v2003002). Nothing was submitted. A dry run shows what the call would do on the state of that block; it does not guarantee the result at enactment.

Result: Ok, 5 of 5 calls applied.

Effects: 5 × Balances.Slashed, 5 × Balances.Deposit, 5 × Bounties.BountyRejected.

11 bookkeeping events left out (5 treasury deposit echoes and 6 batch markers); the dry run in "Verify it yourself" lists them all.

Not covered: the vote itself, and what may change before enactment: another referendum approving one of these proposals. The call is checked again when it runs: a decision whose bounty moved fails alone, the other decisions still apply (Utility.force_batch).

Verify it yourself

1. Decode the call. In Polkadot.js Apps → Extrinsics → Decode, paste the proposal bytes 0x2804145f07885f078c5f07905f07945f079c. It should read Utility.force_batch(calls: [Bounties.close_bounty(bounty_id: 34), Bounties.close_bounty(bounty_id: 35), Bounties.close_bounty(bounty_id: 36), Bounties.close_bo….
2. Check the state. In Developer → Chain state, query bounties.bounties(34), bounties.bounties(35), bounties.bounties(36), bounties.bounties(37), bounties.bounties(39): the state must match "Current state" above.
3. Run the dry run. In Developer → Runtime calls, call dryRunApi.dryRunCall with origin Origins → Treasurer, the call above and XCM version 5: the result should be Ok with the events listed in Testing.

References