candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

whitelisted_caller

Executed

Following the new Fellowship release, this upgrades the Kusama system to v1.1.2. Requires whitelist by https://kusama.polkassembly.io/member-referenda/58

Kusama Runtime Upgrade v1.1.2

- This vote removes old, broken keys from storage.  
- 19 keys were from a 2019 upgrade that went wrong.  
- 381 more keys were inactive and couldn't be read.  
- No active validators were affected.  
- The removal was checked by code to be safe.  
- The Fellowship group approved this change.  
- The person who suggested this is verified.

This referendum cleans up all undecodable keys from storage.

The first 19 keys removed are undecodable Locks, which were not migrated correctly during a runtime upgrade in 2019. See [this issue](https://github.com/polkadot-fellows/runtimes/issues/104) and [this PR](https://github.com/polkadot-fellows/runtimes/pull/122) for more info.

The remaining 381 keys removed are undecodable, inactive SessionKeys also likely created due to a bad runtime upgrade. See [this comment](https://github.com/polkadot-fellows/runtimes/issues/140#issuecomment-1898081577), [this issue](https://github.com/paritytech/polkadot-sdk/issues/1149), and [this other issue](https://github.com/polkadot-fellows/runtimes/issues/151) for more info.

This call was programatically created and verified for safety checking that

1.  There are no longer any undecodable keys on Kusama
2.  Only Locks from the faulty 2019 runtime upgrade are removed
3.  No session keys removed are from the active validator set

using the code at [this commit](https://github.com/polkadot-fellows/runtimes/compare/main…liamaharon:runtimes:liam-kusama-undecodable-keys-check-safe-removal).

Whitelisted by Fellowship in [this referenda](https://kusama.subsquare.io/fellowship/referenda/57).

---

The identity for [this account](https://www.subscan.io/account/DDdfRGvKc9i2BTnqe5T2yBYuY88DxVmCjs66pLiy77TskWo) is verified on Polkadot - `liamaharon` Fellowship rank I.

WHO: Polkadot-Fellows

WHAT: Remove undecodable keys from Kusama storage, including 19 undecodable Locks and 381 inactive SessionKeys.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Clean up undecodable Locks and SessionKeys

Upgrade Kusama Asset Hub to Patch Release v1.1.1

- This referendum is about lowering the minimum balance needed for assets on Kusama's Asset Hub.
- When you pay fees with certain assets, the system still calculates the fee in KSM and converts it.
- If the minimum KSM balance is reduced by 10 times, fees in other assets will increase by 10 times.
- The proposal lowers the minimum balance for assets like USDT, RMRK, and DOT by 10 times.
- It also updates the metadata for bridged DOT, which had an issue before.
- The change will happen at block 21,570,500, just before the Asset Hub updates.

The proposal aims to reduce the minimum balance requirement for all sufficient assets by a factor of 10, preserving the ratio, and update metadata for bridged DOT. The enactment block is set just before the Asset Hub upgrades to the lower ED. No information provided on price/timeframe/resources.

Update Sufficient Asset Minimum Balances

Runtime Upgrade v1,001,000

### Summary of Kusama Relay Chain XCM Issue

- **Issue**: Kusama relay chain adds `SetTopic` instruction to XCM programs, which XCM v2 doesn't support.
- **Problem**: Relay chain sends XCM messages in v2 format, causing errors when destinations use v3.
- **Impact**: Mismatched XCM versions lead to failed transactions between relay chain and parachains.
- **Solution**: Set `safeXcmVersion` to v3 on the relay chain.
- **Outcome**: Relay chain will send XCMs in v3 format by default.
- **Long-term**: Defaulting to v3 is a strategic move for future compatibility.

WHO: The proposal does not mention a specific organization or individual.
WHAT: Set the Kusama relay chain's `safeXcmVersion` to v3 to avoid XCM version mismatch issues.
PRICE/TIMEFRAME/RESOURCES: The proposal does not mention any specific cost or timeframe for implementation.

Setting the relay chain's safeXcmVersion to v3

This is a ReferendumV2 post. It can only be edited by the proposer of the post .

Influx new builders and teams into the Polkadot ecosystem and boost the development of user-centric apps, dApps, and innovative toolings through Easybuild, a three-tiered retroactive reward system. The program aims to attract and integrate new builder teams by providing clear milestones, integrated support and mentorship, and funding. The program is cohort-based and consists of six-month modules that have a "building lag." The target is to attract 10-15 teams every month for 6 months to present their MVPs and initiate prototype development, propel 20 teams total from prototype creation to public beta testing, and onboard at least 6 teams in total, moving from beta testing to ecosystem integration.

Approved

[Whitelisted Caller] Referendum #297: Upgrade Kusama v1,000,000

- Kusama and Polkadot use groups of 5 validators to check parachain blocks.  
- A new idea suggests reducing the group size to 3.  
- Right now, 2 out of 5 validators must approve a block.  
- With 3 validators, only 2 approvals would still be needed.  
- This keeps the system fair and avoids conflicts.  
- Smaller groups help spread the work more evenly.  
- If some validators are slow, blocks might be skipped slightly more often.  
- But since groups change every minute, this shouldn’t be a big problem.

The backing group size on Kusama (and Polkadot) has been set to 5 (configuration->activeConfig->maxValidatorsPerCore). This proposal is aiming at reducing the group size to 3. Currently, when a parachain produces a block, it requires 2 out of 5 backing validators to verify and sign it in order to back it and move forward. With 2-of-3, we'd guarantee that backing quorum is a group supermajority, so there're not two competing 2/5 backed candidates. And one extra validator is allowed to be slow. Smaller backing groups should also contribute to distributing the load of approval-checking more evenly. There's a small risk, however, that with slow/unresponsive validators, parachain slots might be skipped more often with 2/3 instead of 2/5. This should not be an issue in practice since validator groups rotate every minute.

WHO: The proposal does not specify a particular organization or individual.

WHAT: The proposal aims to reduce the backing group size on Kusama and Polkadot from 5 to 3.

PRICE/TIMEFRAME/RESOURCES: The proposal does not mention any specific price, timeframe, or resources required for implementation.

Set backing group size to 3

- Encointer released a bugfix update (version 1.5.1).  
- Fixed a counting bug for sufficients.  
- Fixed a cycle gathering assignment bug.  
- Updated to Polkadot v1.0.0.  
- Allowed the Encointer council to set faucet reserves.  
- Users are encouraged to upgrade quickly.  
- Steps for upgrading involve submitting referendum calls.  
- Some calls have already been executed.

Encointer has a new bugfix release for its runtime

  
[release 1.5.1](https://github.com/encointer/encointer-parachain/releases/tag/1.5.1), runtime spec version 16

-   fix sufficients counting bug:
    
    [PR pallets#345](https://github.com/encointer/pallets/pull/345)
    
-   fix cycle gathering assignment bug: 
    
    [PR pallets#346](https://github.com/encointer/pallets/pull/346)
    
-   update to polkadot-v1.0.0 dependencies [PR #194](https://github.com/encointer/encointer-parachain/pull/194)
    
-   allow Encointer council to set faucet reserve amount [PR #197](https://github.com/encointer/encointer-parachain/pull/197)
    

We would welcome swift upgrade because these bugs can lead to undesirable situations for members of Encointer communities, even if these bugs are not likely to occur in standard usage patterns.

**Generating the calls for this referendum**

1.  Encointer parachain: authorizeUpgrade _0x010268b2b7197585341346ebb1851d85532ed31192d63f4f2059a0a2514cc186485300_
2.  relaychain: xcmPallet.send _0x630001000100a50f0204060202286bee8c010268b2b7197585341346ebb1851d85532ed31192d63f4f2059a0a2514cc186485300_
3.  call hash _0x1402ad75d10184d754f727fa72d7f7deb7d6012365641341bacba9dd6098ac05_

_./target/release/opengov-cli submit-referendum --proposal 0x630001000100a50f0204060202286bee8c010268b2b7197585341346ebb1851d85532ed31192d63f4f2059a0a2514cc186485300 --network "kusama" --track "whitelistedcaller" --after "10" --no-batch_

Submit the preimage for the Fellowship referendum: [encoded call](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000882c001402ad75d10184d754f727fa72d7f7deb7d6012365641341bacba9dd6098ac05)

-   [executed](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/explorer/query/0xa9d2f1e1b32efda221ae8175ea8217769ee04f9afc43a7de1e943b3e2dc512c4)

Open a Fellowship referendum to whitelist the call: [encoded call](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x17002b0f02e274c9326f75528c9a638beddfabc049fd5ac33d67eae6c828b27cac5e1f0e2722000000010a000000)

-   [https://kusama.polkassembly.io/member-referenda/49](../member-referenda/49)

Submit the preimage for the public referendum: [encoded call](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000d82c03630001000100a50f0204060202286bee8c010268b2b7197585341346ebb1851d85532ed31192d63f4f2059a0a2514cc186485300)

-   [executed](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/explorer/query/0xb7bf3c32284f020ce31dac7e7d958421d5529fcb1d0e69161521d9bfd2895c5f)

Open a public referendum to dispatch the call: [encoded call](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x15002b0d022ba82999d966123c37ce48bd2c47559b27cd8a56f8cb2569ae18dfb75d34155d36000000010a000000)

-   [executed](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/explorer/query/0x693e5a9bd6fdb1800b30233c5d3a4b3aa4c903e3ed2d017cb6448fb2e502a1c1)

Encointer has released a bugfix for its runtime, including fixes for counting and assignment bugs. They urge swift upgrade to avoid undesirable situations. The proposal outlines the steps to authorize and dispatch the upgrade, with no specified price or timeframe.

Encointer runtime upgrade to v16

- Kusama parachains stopped working because of a block dispute.  
- The chain froze to stop new parachain blocks.  
- A fix called "force_unfreeze" is needed to restart block inclusion.  
- There are links to check the voting details.  
- People are voting to approve the fix.  
- The problem happened because a finalized block couldn't be changed.  
- The chain is currently rejecting new parachain candidates.  
- Voting is happening in both Fellowship and public groups.

This morning CEST Kusama parachains stopped including blocks. The cause was a dispute in a finalized block that stopped the inclusion of new blocks from parachains.

After the chain issued a revert, it "freezes" the current chain to not include any new parachain candidates. As the block was already finalized, we could not revert to and continued producing on this chain. So, the chain currently is rejecting any new parachain candidates. force\_unfreeze reverts the freeze. This proposal aims to fix this, for chains to continue with block inclusion.

Info on all submissions below:

-   Preimage for the Fellowship referendum: [https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000882c0090e492d7fc2315e0ad47eb060fe96b2c428260eb15ede5519d1476a962d0a0fc](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000882c0090e492d7fc2315e0ad47eb060fe96b2c428260eb15ede5519d1476a962d0a0fc)
    
-   Fellowship referendum to whitelist the call: [https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x17002b0f022cd47cef425d196e70628486dd854a8ce1a41f5d211d26790908f83b64196d4022000000010a000000](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x17002b0f022cd47cef425d196e70628486dd854a8ce1a41f5d211d26790908f83b64196d4022000000010a000000)
    
-   Preimage for the public referendum: 
    
    [https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2c033e00](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2c033e00)
    
-   Public referendum to dispatch the call: [https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x15002b0d02d9c7afcffeb2bc4639716f13d6d5e5bc1e1ca12846cb5931fe0596a195b193d804000000010a000000](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x15002b0d02d9c7afcffeb2bc4639716f13d6d5e5bc1e1ca12846cb5931fe0596a195b193d804000000010a000000)
    

Please note that Fellowship is already voting on [a proposal](../member-referenda/48) that whitelists this hash. Make sure to review, and vote at your convenience!

The proposal aims to fix the issue of Kusama parachains not including blocks due to a dispute in a finalized block. The proposal includes several submissions with preimages and referendums. The Fellowship is already voting on a proposal that whitelists the hash. No information on the price, timeframe, or resources is provided.

Fixing Inclusion Issues On Parachains Side

[Whitelisted Caller] Referendum #260

- This proposal registers the asset `{ parents: 2, interior: GlobalConsensus(Polkadot) }` on the Kusama Asset Hub.
- It adds metadata for the asset: name "Polkadot" and symbol "DOT".
- The minimum balance for DOT is set at 0.01 DOT.
- The "owner" of the asset is the account ID conversion of the path to the Polkadot Relay Chain.
- This registration is part of setting up a Polkadot <> Kusama bridge.
- Future assets sent over the bridge won't need governance motions.
- A similar referendum will be held to register KSM on Polkadot.

WHO: Governance of Polkadot

WHAT: Register asset `{ parents: 2, interior: GlobalConsensus(Polkadot) }` on Kusama Asset Hub with metadata (name: "Polkadot", symbol: "DOT") for a minimum balance of 0.01 DOT.

PRICE/TIMEFRAME/RESOURCES: Not specified.

[Whitelisted Caller] Referendum #258: Register DOT on Asset Hub

- Encointer has a new update called runtime v15.  
- It adds a faucet to help with testing.  
- It includes reputation checks for identity.  
- Built using Polkadot version 0.9.42.  
- Changes from older versions are listed in a link.  
- A special code is needed to upgrade.  
- More details are in a linked post.

Encointer has a new runtime upgrade ready with new features:

Release 1.5.0 for runtime v15: [https://github.com/encointer/encointer-parachain/releases/tag/1.5.0](https://github.com/encointer/encointer-parachain/releases/tag/1.5.0)

-   add faucet functionality
-   add reputation commitments for personhood oracle
-   this runtime is built on polkadot-v0.9.42
-   Changes since v12: [https://github.com/encointer/encointer-parachain/compare/1.3.2…1.5.0](https://github.com/encointer/encointer-parachain/compare/1.3.2…1.5.0)

proposed call: authorizeUpgrade call on Encointer:

`0x0102dfcb7cf28fa3d9af8810d0aec33d2b8e1d5a7164cc7b33d1cab7e7282bd73689`

for whitelisting referendum, see: 

[https://kusama.polkassembly.io/post/2597](2597)

WHO: Encointer

WHAT: Release 1.5.0 for runtime v15 with new features including faucet functionality and reputation commitments for personhood oracle.

PRICE/TIMEFRAME/RESOURCES: Not specified. 

Note: Encointer has proposed a call for authorizeUpgrade call on Encointer.

Encointer runtime upgrade to v15 (whitelisted)

- PVF execution has a memory limit of 128MB, the same as Cumulus.
- Parachain validators need more memory than collators to load state proofs.
- A proposal suggests increasing the memory limit to 512MB for PVF execution.
- A code snippet shows how to set the new memory limit.
- Links are provided to submit and open referendums for the change.
- The change requires approval through a public referendum.

WHO: The proposal is made by an unknown individual or group.

WHAT: The proposal suggests increasing the memory limit for PVF execution to 512MB.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Increase MaxMemoryPages to 512MB

[Whitelisted Caller] Referendum #232: Update Parachain Validation No Show Slots

[Whitelisted Caller] Referendum #231: Open HRMP Channel Between Asset Hub and Bridge Hub

- This referendum removes limits on Kusama pools.
- It allows pools to grow without any restrictions.
- Changes include:
  - No limit on the number of pools (was 256).
  - No limit on total members (was 65,536).
  - No limit on members per pool (was 1,024).
- Currently, there are 141 pools and 915 members.

WHO: Kusama network

WHAT: Remove pool limits on Kusama, allowing nomination pools to grow without bounds.

PRICE/TIMEFRAME/RESOURCES: Not specified.

[TAKE TWO] Next revision of increasing nomination pool limits & commission

- This proposal is about removing limits on Kusama's nomination pools.
- It allows pools to grow without any restrictions.
- Changes include:
  - No limit on the number of pools (was 256).
  - No limit on total pool members (was 65,536).
  - No limit on members per pool (was 1,024).
- The proposal is not set up correctly and won't pass.

TimedOut

This proposal removes pool limits on Kusama, allowing nomination pools to grow without bounds. WHO: Kusama network. WHAT: Remove pool limits. PRICE: Not specified. TIMEFRAME: Not specified. RESOURCES: Not specified.

Next revision of increasing nomination pool limits & commission

[Whitelisted Caller] Referendum #221: Upgrade Kusama to v9430

[Whitelisted Caller] Referendum #219: Increase Parachain Validators to 300

Update `relayVrfModuloSamples` in Parachain Config

- The proposal is about upgrading the Kusama relay chain and system parachains to runtime v9420.
- It includes changes from v0.9.41 to v0.9.42, with 4 runtime migrations for the relay chain.
- New features include the NFT 2.0 pallet on Statemine and a new instance of the Assets pallet called ForeignAssets.
- A new runtime API allows querying account balances for all fungible assets in one call.
- The proposal is submitted on the Whitelisted Caller track, meaning it needs approval from the Fellowship.
- If approved, the upgrade will happen at block #18,062,739.
- Users are encouraged to vote on the proposal.

The proposal aims to upgrade Kusama relay chain and Kusama System Parachains to runtime v9420, including several changes and migrations. The proposal is submitted on Whitelisted Caller track, and if approved, enactment will happen in block #18,062,739.

Runtime Upgrade v9420 on Kusama and v9420 on System Parachains

Increase Parachain Validators to 250

A proposal has been made to change the default XCM version on the Kusama Network from version 1 to version 2. XCM v1 has been removed from the network, and it is now considered unsafe. The proposal includes a call data and screenshots to support the change. It is submitted on the Whitelisted Caller track, along with a Fellowship proposal to whitelist the hash for successful execution. There are also preimages and referendums for both the public and Whitelisted Caller tracks. People are encouraged to review and vote on the proposal.

The proposal aims to update the XCM version from 1 to 2 on the Kusama Network. The proposal is submitted on the Whitelisted Caller track and requires a Fellowship referendum to whitelist the hash for successful execution. The public referendum will dispatch the call. No price, timeframe, or resources mentioned.

[1] Origin: WhitelistedCaller