This referendum is part of the Kusama Bounty Cleanup initiative, which aims to clean up stale proposals, close inactive bounties and return unused funds to the Treasury.

It closes bounties #19, #27, #33 and #38. What is left on their accounts, about 8,972.70 KSM in total, returns to the Treasury, and each curator's deposit is returned.

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 four bounties have had no new work for months, and their remaining funds sit idle on their accounts:

• #19: no payment since 5 Mar 2026; 3,791.66 KSM are left.
• #27: no child bounty was ever created since its funding in March 2024. The full 5,102 KSM are unused.
• #33: no new work since 2 Jul 2025 (its last award, from June 2025, was paid out in October 2026); 58.18 KSM are left.
• #38: no activity since 28 Jul 2025 (milestones 1 to 3 paid, milestone 4 never paid); 20.86 KSM are left.

Closing them returns these funds to the Treasury, where they can be allocated again. Any remaining work can still be funded through a new proposal.

Decisions

Effect on the treasury

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

The bounties today

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

#19 Infrastructure Builders Program

#27 POLKADOT <> KUSAMA BRIDGE SECURITY BOUNTY

#33 KSM RFP #2 - RFP Launcher Dapp

#38 KSM RFP #4 - BigTipper

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,977 (14 Oct 2026, 04:54 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, 4 of 4 calls applied.

Effects: 4 × Balances.Unreserved, 4 × Balances.Transfer, 4 × Bounties.BountyCanceled.

13 bookkeeping events left out (4 zero-amount releases, 4 emptied accounts and 5 batch markers); the dry run in "Verify it yourself" lists them all.

Not covered: the vote itself, and what may change before enactment: the curator opening a child bounty or awarding the bounty; anyone removing the curator of #33, whose update deadline has passed (the closure should still return the funds, but the curator's deposit is then slashed; not dry-run in that state); anyone removing the curator of #38, whose update deadline has passed (the closure should still return the funds, but the curator's deposit is then slashed; not dry-run in that state). 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 0x2804105f074c5f076c5f07845f0798. It should read Utility.force_batch(calls: [Bounties.close_bounty(bounty_id: 19), Bounties.close_bounty(bounty_id: 27), Bounties.close_bounty(bounty_id: 33), Bounties.close_bo….
2. Check the state. In Developer → Chain state, query bounties.bounties(19), bounties.bounties(27), bounties.bounties(33), bounties.bounties(38): 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