Origin able to dispatch a whitelisted call.

whitelisted_caller

### Summary of Polkadot Upgrade

- **Upgrade Focus**: Affects Relay Chain and Asset Hub.
- **Identity Pallet**: Locked until migration to People Chain.
- **Wallets/UIs**: Identity info will be unusable for 2-3 weeks.
- **Release Notes**: Available on GitHub.
- **Enactment Date**: Scheduled for July 8.
- **UI Actions**: Prepare to fetch Identity info from People Chain after launch.
- **Expected Downtime**: 2-3 weeks.

Executed

WHO: Polkadot-fellows

WHAT: Partial upgrade of Relay Chain and Asset Hub, locking Identity pallet for migration to People Chain. 

PRICE/TIMEFRAME/RESOURCES: Total expected downtime is 2-3 weeks. Enactment is set for 8 July. No information on price or resources.

[Whitelisted Caller] Upgrade Polkadot: v1.2.6

Upgrade Polkadot v1.2.5

[Whitelisted Caller] Upgrade Polkadot v1.2.4

- A proposal is moving 5 million DOT to the Treasury's account.
- This move is from Relay to Asset Hub and has been tested before.
- It allows new ways to spend money called staged payouts.
- The proposal sets asset rates the same as another Polkadot proposal.
- The rates weren't moved before because the rules changed while a vote was happening.
- The proposal needs approval from a group called the Fellowship.

WHO: The proposal does not specify who is making the proposal.

WHAT: The proposal suggests moving 5 million DOT to Asset Hub into the Treasury's account and setting asset rates the same as Polkadot 645 under XCM v4.

PRICE/TIMEFRAME/RESOURCES: The proposal does not mention any specific price, timeframe, or resources required. It requires whitelisting from the Fellowship.

Move Part of Treasury to Asset Hub

- A proposal was voted on but failed due to a mistake.
- It is being proposed again to fix the problem.
- The proposal is about the Polkadot Bridge Hub, which has a bug.
- The bug causes problems when changes happen in validators.
- This upgrade will help fix the bug and prevent future problems.
- There is another related proposal to whitelist this upgrade.

WHO: Polkadot Bridge Hub

WHAT: Upgrade `pallet_bridge_grandpa` to fix a bug causing traffic to be stuck between Kusama and Polkadot.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Polkadot Bridge Hub 1.2.2 upgrade: Unstuck bridge with Kusama

- LAOS Network won Auction #68 with a self-funded bid, so the petition is no longer needed.
- LAOS started a Crowdloan for parachain Auction #68 on April 20, 2024.
- The Crowdloan had almost 100 participants and received 92,477 DOT from 321 contributors.
- A problem occurred: Auction #68 didn’t recognize the Crowdloan contributions.
- The issue can be fixed by changing the **first_period** from **16** to **17**.
- If not fixed, contributions won’t count for Auctions #68 to #73, and funds will be returned.
- LAOS tested the fix on their Rococo testing network, and it worked.
- They apologized for the oversight and hope the fix is considered safe and neutral.

TimedOut

LAOS Network started a Crowdloan for parachain #3370 to compete in Auction #68, but contributions were not recognized. Proposal to fix by incrementing first_period from 16 to 17. Crowdloan already has 92,477 DOT from 321 participants. If fixed within a month, contributions will make it in time for the last 3 auctions.

Proposal Outdated - Do Not Vote: LAOS already won Auction 68 with SF Bid

- The `pallet_bridge_grandpa` at Polkadot Bridge Hub is in an inconsistent state due to a bug.
- The bug involves how the GRANDPA light-client handles validator set changes after slashing.
- This bug caused Kusama to Polkadot traffic to get stuck.
- An upgrade is being prepared to fix this issue.
- A Polkadot runtime upgrade (to 1.2.0) is already up for a vote.
- The fix will be applied after the runtime upgrade.
- The proposal to fix the bug is on the Whitelisted Caller track.
- A parallel submission is being voted on by the Fellowship to whitelist the proposal.

WHO: Polkadot Bridge Hub

WHAT: Fixing a bug in the Polkadot-GRANDPA-light-client running BH that causes traffic to be stuck between Kusama and Polkadot.

PRICE/TIMEFRAME/RESOURCES: Not specified.

### Summary of Polkadot Referendum

- **Purpose**: Enables async-backing on Polkadot, allowing parachains to produce blocks faster.
- **Runtime Upgrade**: Activated in Polkadot runtime version 1.2.0.
- **Block Production**: Parachains can choose to produce blocks every 6 seconds instead of 12 seconds.
- **Testing**: Async-backing has been tested on Rococo, Westend, and Kusama.
- **Dependencies**: Requires Polkadot runtime v1.2, which is part of another referendum.
- **Known Issues**: Validators need to upgrade to version 1.8 or higher for smooth operation.
- **Action Needed**: Un-upgraded validators should upgrade to avoid issues.

Polkadot proposes enabling async backing, allowing parachains to produce blocks at a faster rate. This will be enabled with the Polkadot runtime upgrade 1.2.0, and after the referendum, parachains can decide to produce blocks at a 6s rate. No critical issues are known, but validators need to upgrade to a version higher than v1.8. Whitelisted by the Subsquare fellowship, testing has been done on Rococo, Westend, and Kusama.

Enable async backing on polkadot

Initialize Snowbridge on BridgeHub and AssetHub

Upgrade Polkadot to Release v1.2.0

### Proposal Summary

- **Objective**: Increase the backing timeout for validators from 2 seconds to 2.5 seconds and the approval-voting timeout from 12 seconds to 15 seconds.
- **Reason**: This change aims to provide a smoother experience for async backing parachains by allowing them to fully utilize the 2 seconds of execution time per block.
- **Rationale**: Detailed in [GitHub issue #3565](https://github.com/paritytech/polkadot-sdk/issues/3565).
- **Implementation**: The changes are implemented in the call found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-kusama.luckyfriday.io#/extrinsics/decode/0x332e0c01002000000600c4090000000000000601983a000000000000).
- **Additional Change**: The `MaxMemoryPage` parameter is reset to its previous value as the call overrides all parameters of `ExecutorParams`.
- **Testing**: The proposal has been tested locally using zombienet and on the Rococo network.

WHO: The proposal is made by an anonymous entity.

WHAT: The proposal aims to increase the backing timeout on validators from 2s to 2.5s and approval-voting timeout from 12s to 15s.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Bump parachain validation timeouts

[Revision] Nomination Pool: Remove max pool and max member limits

Set BEEFY genesis (thus starting BEEFY consensus on Polkadot)

### Summary of Proposal

- The proposal sets a minimum fee of 0.025 DOT for each block order in the on-demand system.
- The goal is to prevent spam while allowing for cost-effective experimentation.
- If the fee is too high after the system starts, another proposal can be made to lower it.
- The proposal is part of the Whitelisted Caller track.
- The Fellowship is also voting on Referendum 89 to whitelist the hash.

WHO: The proposal is submitted on the Whitelisted Caller track.

WHAT: Establishes the minimum fee for a single block order via the on-demand system at 0.025 DOT.

PRICE/TIMEFRAME/RESOURCES: Not mentioned.

Setting onDemandBaseFee to 0.025 DOT

The P<>K bridge is a system that connects different blockchains and charges user fees. It pays rewards to people who help it work, called "relayer rewards." These rewards are a big part of the bridge's costs. To start, the bridge needs some money to begin working. They suggest giving 10100 DOT and 2030 KSM to the bridge's accounts. This money will help the bridge get started. As the bridge works, it will make enough money from user fees to pay for the rewards. Any extra money will go back to the treasury. You can find more details about the bridge's accounts and money here: https://github.com/polkadot-fellows/runtimes/issues/238. The bridge has already been approved by a group called https://collectives.subsquare.io/fellowship/referenda/88.

WHO: P<>K Bridge

WHAT: Proposes an initial funding of 10100 DOT and 2030 KSM to be split among system chain sovereign accounts for initial deployment. 

PRICE/TIMEFRAME/RESOURCES: The funding will be pre-funded by the treasury and will only be an initial seed. The bridge will cover operation costs from user fees paid on Asset Hub.

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

Polkadot Runtime Upgrade v1.1.3

Duplicate of #545 - please ignore

- The call helps connect Polkadot and Kusama through a bridge.
- It sets the rules for communication between different parts of Polkadot and Kusama using XCMv3.
- It connects Polkadot AH to Polkadot BH and both to Kusama.
- It starts the Kusama light-client on Polkadot Bridge Hub.
- It follows a list of approved actions from a website.

WHO: Polkadot

WHAT: Initialize the Polkadot side of the Polkadot<>Kusama bridge by calling `forceXcmVersion` on system parachains and `bridgePolkadotGrandpa::initialize()`

PRICE/TIMEFRAME/RESOURCES: Not specified.

Initialize Kusama GRANDPA light-client running on Polkadot BridgeHub

WHO: Polkadot System Parachains. 
WHAT: Updating the `safeXcmVersion` to value 3 to support new V3 destinations/connections by default. 
PRICE/TIMEFRAME/RESOURCES: Not specified. 
Note: Requires whitelisting by Polkadot community.

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

- The approach on Polkadot is like Kusama.
- They are changing a setting called `setOnDemandMaxQueueSize` to 500.
- This change is based on observations from a test called Rococo.
- During tests, handling too many orders at once slowed down the system.
- Limiting the number of orders is a temporary fix.
- They plan to look for a better solution later.

WHO: The proposal does not mention a specific organization or individual.
WHAT: Adjusting the `setOnDemandMaxQueueSize` to 500 on Polkadot to limit the total number of orders.
PRICE/TIMEFRAME/RESOURCES: No specific information provided.

Setting setOnDemandQueueMaxSize to 500

Polkadot recently updated to version 0.8.28. In this update, there was a change in the "apply" function. The second part of the function, called "CandidacyBond," was supposed to be 100 DOT, but it was changed to 1 DOT by mistake. This caused some accounts to only have 1 DOT unreserved instead of 100 DOT. To fix this, a proposal was made to use "Balances::force_unreserve" to correct the amounts for the two affected accounts. More information can be found in the linked issue.

WHO: Polkadot network

WHAT: Call a referenda to force unreserve incorrect amounts of DOT for two accounts

PRICE/TIMEFRAME/RESOURCES: Not specified.

Compensate for insufficient `phragmenElection.renounce` unreserve amount

Upgrade System to v1.1.2

- A problem was found in the Kusama system with version 1.1.0, so it's suggested to cancel a vote related to it.
- A new update for Polkadot Asset Hub with version 1.1.1 is being proposed to fix this issue.
- The new version will lower the minimum amount of DOT needed to 0.01.
- It includes changes from another referendum that needs to be rejected.
- The vote for the new upgrade will happen 24 hours after the 1.1.0 upgrade on February 13.
- There is a decision period of 28 days to make the vote.
- The new balances will take effect shortly after the Asset Hub upgrade.
- Timely submissions are important, but there shouldn't be any major issues.

Cancelled

WHO: Polkadot Asset Hub

WHAT: Update to patch release v1.1.1, reducing existential deposit to 0.01 DOT and updating minimum balances of sufficient assets to maintain their ratio with the DOT existential deposit.

PRICE/TIMEFRAME/RESOURCES: N/A (not specified)

Update Polkadot Asset Hub v1,001,001 and Sufficient Asset Minimum Balances

WHO: Not specified
WHAT: Clean up related storage entry due to removal of `SudoBalances` proxy type from the runtime
PRICE/TIMEFRAME/RESOURCES: Not specified

Clean up undecodable storage entry

- A proposal is suggested to change the deposit amount needed for using digital assets called Asset Hubs.
- It is recommended to reject this proposal and create a new one with improvements.
- The plan involves reducing the minimum balance required for certain assets like USDT and USDC by ten times.
- If the DOT deposit decreases, it will cause fees to be higher for those assets.
- There is also a plan to fix an issue with KSM assets that didn't work correctly before.

The proposal suggests reducing the minimum balance requirement for USDT, USDC, and KSM by a factor of 10 to reduce the existential deposit on Asset Hubs. This will increase fees in sufficient assets by a factor of 10. The proposal also includes updating metadata for bridged KSM.

Update Sufficient Asset Minimum Balances

root

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

medium_spender

big_spender

Referenda Whitelisted Caller

Origin for signaling that the network wishes for some change

Origin able to cancel slashes and manage minimum commission.

Origin for spending up to 10,000,000 DOT from the treasury as well as generally administering it.

Origin for managing the composition of the fellowship.

Origin able to spend around 250 DOT from the treasury at once.

Origin able to spend around 1,000 DOT from the treasury at once.

Origin able to spend around 10,000 DOT from the treasury at once.

Origin able to spend around 100,000 DOT from the treasury at once.

Origin able to spend up to 1,000,000 DOT from the treasury at once.

[1] Origin: WhitelistedCaller