Please Vote Nay

Update (please vote NAY): We’ve since confirmed with the runtime/dev team that the existing bounties pallet will not support the multi-asset / DOT-based KV flow we intended. The prior plan to extend the current bounties ran into breaking changes, so the approach is now a new multi_asset_bounties pallet.

As a result, bounties #35 #36 #37 are not going to be the correct on-chain mechanism for Kusama Vision going forward. We will therefore recreate the bounties under the new pallet once it is deployed on Kusama Asset Hub, and resubmit the appropriate OpenGov actions at that time.

The curator groups remain the same; this is purely a technical substrate/pallet migration issue.

Edited

We found out the old bounties system can't work with our new plan.
So we're making a new system for bounties instead.
The old bounties numbers 35, 36, and 37 won't be used.
We'll make new bounties when the new system is ready.
The people in charge of the bounties will stay the same.
This is just a tech update, not a change in who's involved.

Source

Update (please vote NAY): We’ve since confirmed with the runtime/dev team that the existing bounties pallet will not support the multi-asset / DOT-based KV flow we intended. The prior plan to extend the current bounties ran into breaking changes, so the approach is now a new multi_asset_bounties pallet.

As a result, bounties #35 #36 #37 are not going to be the correct on-chain mechanism for Kusama Vision going forward. We will therefore recreate the bounties under the new pallet once it is deployed on Kusama Asset Hub, and resubmit the appropriate OpenGov actions at that time.

The curator groups remain the same; this is purely a technical substrate/pallet migration issue.

Edited