candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

whitelisted_caller

Rejected

Duplicate of #354 - please ignore

Executed

WHO: Kusama and Polkadot communities
WHAT: Initializing the Kusama side of the Polkadot<>Kusama bridge by calling `forceXcmVersion` and `bridgePolkadotGrandpa::initialize()`
PRICE/TIMEFRAME/RESOURCES: Not specified.

Initialize Polkadot GRANDPA light-client running on Kusama BridgeHub

WHO: Kusama System Parachains 
WHAT: Update `safeXcmVersion` to value 3 
PRICE/TIMEFRAME/RESOURCES: Not specified

Set `safeXcmVersion` to 3 for AssetHub, BridgeHub and Encointer

- Rococo discovered a slowdown in block import times when a parachain processed around 5,000 orders in one block.
- The issue was reported on GitHub.
- To fix this temporarily, the maximum number of orders was reduced from 10,000 to 500.
- This change was made using `configuration.setOnDemandMaxQueueSize`.
- The OnDemandQueue stores orders waiting to be assigned to a core.
- The new limit of 500 orders is a safe temporary measure.
- A permanent solution will be developed later.

WHO: The proposal does not mention any specific organization or individual.

WHAT: Adjusting the configuration through `configuration.setOnDemandMaxQueueSize` to limit the total number of orders temporarily to 500 due to slow block import times caused by a batch call for approximately 5,000 orders in a single block.

PRICE/TIMEFRAME/RESOURCES: No information provided.

Setting setOnDemandQueueMaxSize to 500

Set BEEFY genesis (thus starting BEEFY consensus on Kusama)

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.

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

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.

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 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.

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.

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.

[1] Origin: WhitelistedCaller