candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

whitelisted_caller

Executed

Upgrade Kusama: v1.2.6

This referendum upgrades Kusama to v1.2.5. See the Fellowship release notes for more details: https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.5

Upgrade Kusama: v1.2.5

- The referendum increases the number of parachain validators from 300 to 400.
- It also increases the maximum backing group size from 3 to 4.
- The total number of cores stays at 100, with 56 active and 44 inactive.
- Changing the backing group size helps improve parachain block times.
- It ensures all 100 backing groups receive rewards during a 1-hour session.
- Group rotations happen every 1 minute.
- More details can be found on the Polkadot forum.
- The referendum is whitelisted for further review.

WHO: Kusama community 
WHAT: Increase parachain validator set size from 300 to 400 and maximum backing group size from 3 to 4, while keeping the total number of cores at 100. 
PRICE/TIMEFRAME/RESOURCES: Not specified.

Increase max_validators to 400 and max_validators_per_core to 4

Update Kusama System v1.2.4

This proposal assigns a core to the People Chain directly on the relay effective immediately. As it stands the People Chain will only start making blocks in 12 days at its next assignment, as the previous assignment came before the core was ready on the relay chain.

Assign core for People Chain directly on relay

- This referendum helps make the network bigger by allowing up to 500 validators.
- It changes how validators vote to make the process faster and use less computer power.
- Validators will use a new way to vote and can approve multiple things at once with one signature.
- These changes help reduce the amount of data and work the network needs to do.
- The goal is to make the network handle more validators smoothly.
- The changes were made in late 2023.
- You can learn more about these updates on GitHub.

WHO: Polkadot network validators

WHAT: Enact two approval voting protocol improvements to scale up the number of parachain validators to 500. 

PRICE/TIMEFRAME/RESOURCES: Not specified.

Enable approval voting protocol improvements

Enable Identity Again on People Chain

Upgrade Kusama Relay Chain for People Launch

Register People Chain and upgrade Coretime Chain to v1.2.3

- Kusama needs an upgrade to fix issues with core sales and bridges.
- The upgrade will fix a problem where a message about leases didn't work because of a weight mismatch.
- The upgrade will also let parachains renew their cores if they had leases before core sales started.
- After the upgrade, core sales will restart 7 days later.
- There's a bug in the Kusama BridgeHub that can cause problems with validator set changes.
- This bug has already caused issues on the Polkadot BridgeHub, stopping traffic from Kusama to Polkadot.
- The upgrade will fix this bug on Kusama BridgeHub.
- The proposal is being voted on to make sure it can go through.

The proposal suggests upgrading Kusama to the latest release (1.2.2) to fix issues with core sales and bridges. The upgrade will include a fix to ensure every parachain can renew their core and reset the sales state. The upgrade will also fix a bug in the Polkadot-GRANDPA-light-client running on Kusama BridgeHub. The proposal is submitted on the Whitelisted Caller track, and a parallel submission is up for a vote on Fellowship to whitelist the proposal.

Kusama Runtime Upgrade to 1.2.2

Enable Coretime

### Kusama Async-Backing Referendum

- **Purpose**: Enable faster block production for parachains.
- **Current Status**: Async-backing logic is active but in sync mode, producing blocks every 12 seconds.
- **Proposed Change**: Parachains can choose to produce blocks every 6 seconds.
- **Testing**: Successfully tested on Rococo and Westend since late 2023.
- **Dependencies**: Requires the upcoming `v1.2` runtime release.
- **Known Issues**: Some validators need to upgrade to avoid backing issues.
- **Action Required**: Validators should ensure their network keys are persistent to avoid discovery issues.

The proposal enables async backing on Kusama, allowing parachains to produce blocks at a faster rate of 6s. This is not mandatory, and they can still run at 12s. No critical issues are known, and the proposal won't change anything regarding that. The referendum will be enacted after the upcoming v1.2 runtime release.

Enable async backing on kusama

Upgrade Kusama v1.2.0

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.

The P<>K bridge charges user fees on originating Asset Hub, but it pays relayer rewards from AssetHubs' sovereign accounts on sibling BridgeHub parachains. These relayer rewards are a large part of the bridge's "operating costs". For initial deployment, AssetHub's sovereign accounts on BridgeHubs should be pre-funded by treasury. An initial 10100 DOT and 2030 KSM is proposed to be split among the relevant system chain sovereign accounts to provide initial bootstrap runway to the bridge. This will only be an initial seed. As the bridge operates, it should cover operation costs (relayer fees) from the user fees paid on Asset Hub, and any unspent user fees ("bridge profits") are going to the treasury anyway, so in the longer term these funds are practically paid back (plus profits). Exact system chain addresses being funded and amounts for each can be found here: https://github.com/polkadot-fellows/runtimes/issues/238

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

The call in this referenda updates the `safeXcmVersion` of Kusama System Parachains to value 3.
Currently set version 2 is outdated and will be deprecated. Setting this to version 3 is required to support new V3 destinations/connections by default.
Note: Kusama Relay already has this set to 3 so that's why it's not included in the call.
Needs to be whitelisted by: <a href="https://kusama.subsquare.io/fellowship/referenda/61">https://kusama.subsquare.io/fellowship/referenda/61</a>

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

This sets BEEFY genesis to the next block after it executes, thus enabling BEEFY consensus on Kusama.
BEEFY consensus will then be used in the Kusama&lt;&gt;Ethereum Snowfork bridge.
Requires whitelist by <a href="../member-referenda/59" target="_blank" rel="noopener">https://kusama.polkassembly.io/member-referenda/59</a>

[1] Origin: WhitelistedCaller