candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

whitelisted_caller

Executed

Register Coretime Parachain

### Summary

- **Proposal**: Increase backing timeout from 2s to 2.5s and approval-voting timeout from 12s to 15s.
- **Rationale**: To ensure a smoother experience for async backing parachains.
- **Details**: Found in [GitHub issue #3565](https://github.com/paritytech/polkadot-sdk/issues/3565).
- **Call Details**: Available [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-kusama.luckyfriday.io#/extrinsics/decode/0x332e0c01002000000600c4090000000000000601983a000000000000).
- **Parameter Adjustment**: `MaxMemoryPage` param is reset to its previous value.
- **Testing**: Conducted locally with zombienet and on Rococo.

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

WHAT: Increase the backing timeout on validators from 2s to 2.5s and approval-voting timeout from 12s to 15s.

PRICE/TIMEFRAME/RESOURCES: No information provided.

Bump parachain validation timeouts

- A referendum is moving 25,000 KSM (about 10% of the Kusama Treasury) from the Relay Chain to Asset Hub.
- It sets the KSM asset rate to 1, meaning 1 KSM equals 1 KSM.
- This move requires special permission (root privilege).
- Once moved, the Treasury can operate normally on Asset Hub using Treasurer and XSpender tracks.
- Moving funds to Asset Hub enables new Treasury features, like staged spends.
- If successful, a similar proposal will be made for Polkadot.
- Polkadot could use more features like USDC/T spends and funding sub-treasuries.

WHO: Kusama Treasury

WHAT: Move 25k KSM from Relay Chain to Asset Hub, set asset rate of KSM to 1, enable new Treasury features

PRICE/TIMEFRAME/RESOURCES: Not specified.

Migrate 25k KSM to Asset Hub Treasury

### Summary of Async Backing Referendum

- **Purpose**: Enable async-backing on Kusama, allowing parachains to produce blocks at a faster rate.
- **Current Status**: Async backing is already enabled in sync mode since v1.1.0, with a 12-second block production rate.
- **Proposed Change**: Parachains can choose to produce blocks at a 6-second rate after the referendum.
- **Testing**: Async backing has been tested on Rococo and Westend since late 2023, with successful migration to 6-second block rates.
- **Dependencies**: The referendum should be enacted after the v1.2 runtime release, which includes critical fixes.
- **Known Issues**: Some validators need to upgrade to avoid backing issues, and network key persistence is crucial for proper functioning.
- **Action Required**: Validators should upgrade to a version higher than 1.8 and ensure network keys persist across restarts.

TimedOut

WHO: Kusama network

WHAT: Enabling async backing on Kusama, allowing parachains to produce blocks at 6s rate instead of 12s rate.

PRICE/TIMEFRAME/RESOURCES: No information provided.

[Please reject] Enable async backing on kusama

- The proposal sets the minimum fee for an on-demand order to 0.005 KSM per block.
- This fee aims to prevent spam while allowing for affordable experimentation.
- If the fee is too high after the system goes live, a new proposal can be made to lower it.
- The proposal is on the Whitelisted Caller track, requiring approval from the Fellowship.

WHO: The proposal is not clear about who is proposing the change.
WHAT: Set the minimum fee for an order for a single block via the on-demand system to be 0.005 KSM.
FOR WHAT PRICE/TIMEFRAME/RESOURCES: The proposal does not mention any specific price, timeframe, or resources.

Setting onDemandBaseFee to 0.005 KSM

- The P<>K bridge charges fees when users start transactions on Asset Hub.  
- It pays rewards to relayers from AssetHub's accounts on BridgeHub parachains.  
- These rewards are a big part of the bridge's costs.  
- At first, the treasury will fund these accounts with 10,100 DOT and 2,030 KSM.  
- This money helps the bridge start working.  
- Later, user fees will cover the costs.  
- Extra fees ("bridge profits") go back to the treasury.  
- More details on funding can be found in the link.

WHO: The P<>K bridge

WHAT: Proposes an initial seed of 10100 DOT and 2030 KSM to be split among relevant system chain sovereign accounts for initial bootstrap runway to the bridge.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Fund system chains sovereign accounts on Kusama BridgeHub for Polkadot<>Kusama bridge

Kusama Runtime Upgrade v1.1.3

Rejected

Duplicate of #354 - please ignore

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.

[1] Origin: WhitelistedCaller