### Proposal Summary

- **Purpose**: Cancel the upgrade of Polkadot Runtime to v9320.
- **Reason**: A new code check in the scheduler pallet prevents the `set_code` function from working correctly.
- **Code Change**: The check ensures that scheduled calls do not exceed the block's weight limit.
- **Issue**: The `set_code` function is annotated to use the maximum block weight, causing it to fail the check.
- **Solution**: A new proposal will be submitted to fix this issue.
- **Proposal Hash**: `0x88998cf7535c1f22d62849be8464fdc38fe46c0a46dc943ec56c91ef6592ec65`
- **Process**: The proposal needs approval from the Council and then a community vote.

proposalHash

votingPeriod

delay

Cancel the upgrade of Polkadot Runtime to v9320

- Proposal hash: `0x98b3a8aa425c1e1ca5cd96d1b8f3491233b0745575e648a8c5497e83cec76f16`
- Aim: Increase the limit of nomination pools from 64 to 128 in Polkadot.
- Initial limit: Set at 64 to prevent risks during launch.
- Current status: Everything is working as expected.
- Next steps: If the Council approves, the community will vote in the referenda queue.
- Decision: Final decision will be made by the community.

Increasing Max Number of Nomination Pools

- The proposal aims to avoid a situation where no one can change or set nominations due to the high number of nominators.
- It targets to outstrip Referendum 86, which is currently up for community vote and sets higher nomination minimum bond limits.
- The new motion suggests shorter voting and enactment periods compared to Referendum 86.
- If approved and fast-tracked, this proposal would make Referendum 86 redundant.
- Along with updating staking configurations, this proposal would cancel Referendum 86.
- The importance of higher nomination minimum bond limits is discussed in an initial post.
- The proposal is crucial as the number of nominators is close to reaching 50,000.

Redefining Slightly Nomination Minimum Bond Limits and Removing Max Number of Nominators (replacing Referendum 86)

### Summary

- A proposal to upgrade Polkadot's runtime to v9320 was submitted but will fail due to a code change in the scheduler pallet.
- The scheduler now checks if a scheduled call exceeds the block's remaining weight, which causes the `set_code` call to always fail.
- An external motion (306) has been opened to cancel this proposal.
- A new proposal with the correct call will be submitted soon.
- The proposal includes various updates and fixes, such as removing contracts RPCs, adapting to weightv2, and improving documentation visibility.
- The proposal hash is `0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162`.
- After Council approval, the community will vote on the proposal in the referenda queue.

[PLEASE REJECT] Runtime v9320 Upgrade On Polkadot

### Summary of Snowbridge Proposal

- **Snowbridge Development**: Proposal to fund Snowfork team for 28 months to develop a trustless, permissionless bridge between Polkadot/Kusama and Ethereum.
- **Bridge Hub**: The bridge will launch on the Bridge Hub, a common-good parachain being developed by Parity for Kusama and Polkadot.
- **Funding Request**: The proposal seeks funding for 16 months retroactively and 12 months in the future.
- **Goal**: To launch Snowbridge as a common-good bridge on both Polkadot and Kusama.
- **Additional Details**: The full proposal includes a long-term roadmap, governance plans, and economic incentives.
- **Voting**: Both Kusama and Polkadot networks are voting on the project.
- **Approval Process**: If approved by the Council, the proposal will go to the community for a vote in the referenda queue.
- **Proposal Hash**: 0xcb7a0584b5d85d6065d2e492d476aa1c1b92b9a0e492aa668b33036671500ddb

Treasury Proposal: Snowbridge Funding Proposal

- The v9320 release of parachains is updated to match the v9320 runtime of the Relay Chain.
- Changes to Assets and Uniques are small.
- "Anonymous" proxy is now called "Pure" proxy.
- There are also some small bug fixes.
- Two examples of actions are "Authorize Upgrade" and "Send from Polkadot."
- A proposal with a hash is submitted for community voting.
- The Polkadot Council will first approve it, then the community will vote.
- Make sure to review and vote on the proposal.

Statemint Runtime Upgrade to v9320

### Summary of Polkadot Staking Changes

1. **Nomination Pools**: Polkadot is introducing nomination pools to simplify staking for DOT holders.
2. **Current System**: Nominators currently need at least 10 DOTs and compete within a limit of 50,000 to be in the top 22,500 for staking rewards.
3. **Active vs. Waiting**: Nominators are either active (in the top 22,500) or waiting.
4. **Goal**: Encourage waiting nominators to join pools and prevent new waiting nominators.
5. **Proposed Change**: Increase the minimum nomination limit to 100 DOTs to discourage waiting nominators.
6. **Buffer**: Keeping a buffer of waiting nominators is beneficial for economic security.
7. **Immediate Action**: Reject nominations with less than 50 DOTs, directing them to join pools.
8. **Original Discussion**: For more details, see the [original post](https://polkadot.polkassembly.io/post/1224).

Proposal: Slightly higher nomination limits

### Polkadot Runtime Upgrade Proposal

- **Proposal**: Upgrade Polkadot's runtime to version v9300.
- **Previous Issue**: Motion 286 replaced Motion 285 due to queue limitations.
- **Audits**: Several low-priority audits and trivial changes are pending or completed.
- **Proposal Hash**: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`
- **Process**: Requires Council vote followed by community referendum.
- **Verification**: Use SRTool to verify the proposal hash.
- **Vote**: Community members should vote at their convenience.

Runtime v9300 Upgrade On Polkadot

- **Motion 286** is a proposal up for vote on Polkadot.
- It aims to remove limits on the number of members in nomination pools.
- This change is needed to fulfill the goals of **Referendum 78**.
- The previous proposal had a mistake, so pools are still unusable.
- Voting is important to fix this issue.
- The community should vote soon to move this to the referenda queue.
- This will help make nomination pools functional on Polkadot.

Removing members' limit for the community to join nomination pools

### Polkadot Runtime Upgrade Proposal

- **Proposal**: Upgrade Polkadot's runtime to version v9300.
- **Audits**: Several changes are pending non-critical audits.
- **Changes**: 
  - Improvements in transaction payment, staking, and storage.
  - Additions to validator ranking and fast-unstake features.
- **Proposal Hash**: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`.
- **Process**: Requires Council vote followed by community referendum.
- **Verification**: Use SRTool to verify the proposal hash.
- **Action**: Community members should vote on the proposal in the referenda queue.

**Fix for Referendum 74**

- Fixes a failed execution of Referendum 74.
- Uses a batch of Transact instructions instead of a single batch call.
- Adds a sixth pair with ParaId 2030 (Bifrost).
- Includes a force_transfer of 22 DOT: 20 for the new parachain and 2 for XCM fees.
- Requests fast tracking if it passes the Council.
- The original 5 channel requests remain unchanged.
- The fix should work on the current version of Polkadot.

Statemint HRMP Channel Establishment

### Summary of the Proposal for Common Good Parachain

- **Purpose**: Add a new "common good" parachain to Polkadot focused on collectives.
- **First Collective**: Likely the Polkadot Alliance, but will support other collectives serving the Polkadot network.
- **Kusama Involvement**: No Kusama counterpart planned; Kusama may join collectives like the Polkadot Alliance.
- **Technical Fellowship**: A group of technical experts contributing to Polkadot, with members deploying code on Kusama first.
- **Proposal Steps**:
  1. Register the parachain with a four-year lease.
  2. Runtime upgrade to the Relay Chain to recognize the parachain.
- **Referenda**: Series of votes on Polkadot for approval by stakeholders.
- **Call Details**: Finalized when Parity publishes the Collectives genesis release and the Technical Committee sets a timeframe.
- **Call Hash**: `0x9ef867bcaaee9750487738c6e6537eb52a3047c7bb2f06eb30dc05073dae90d5`

Polkadot Collectives Common Good Parachain Proposal

### Tether's USDT on Polkadot

- **USDT Registration**: Tether registered USDT on Polkadot's Statemint with asset ID `1984`.
- **Governance Request**: Tether is asking Polkadot governance to make USDT sufficient for paying transaction fees and account creation without needing DOT.
- **Statemint Assets**: On Statemint, assets can be Sufficient or Non-Sufficient. Sufficient assets can create accounts without needing DOT.
- **Proposal Benefits**: This proposal would make it easier for users to hold USDT on Polkadot, boosting the ecosystem and increasing transactions, especially in DeFi.
- **Call on Statemint**: The encoded call and call hash are provided for the proposal.
- **Call on Relay Chain**: The call hash and call data for the relay chain are also provided.

Proposal for USDT Token Sufficiency on Statemint

### Proposal Summary

- **Objective**: Upgrade Polkadot and Statemint runtimes to versions v9291 and v9290 respectively.
- **Polkadot Upgrades**:
  - Fixes various issues and includes improvements like making chain extension state types public and resetting approved accounts after transfers.
  - Proposal hash: `0x8fe3a4b4214f090c01c1da47882c41eb08e0544d379c7e1959dcdc4810e12c50`
- **Statemint Upgrades**:
  - Updates XCM weight calculations and prepares for the first Collectives parachain.
  - Proposal hash: `0x076ee423671cc95bd1eb19675009154d4e6b817554d755e6627c6138094a924b`
- **Community Involvement**: The proposal requires approval from the Council and a community vote.
- **Batch Call**: Combines both runtime upgrade proposals into a single batch call.
  - Batch call hash: `0xbc2cb73740d701dac3fa5f31b7b23e552d6160ccd40d95746e91c131c699523d`

Runtime Upgrade v9291 on Polkadot + v9290 on Statemint

- Polkadot is introducing nomination pools for staking DOT tokens.
- Users can join a pool with as little as 1 DOT.
- Creating a pool requires an initial stake of 200 DOTs.
- There is a limit of 64 pools and 16,000 members across all pools.
- These limits can be increased if needed.
- The proposal aims to be voted on by the community.
- The configuration details can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x270a0100e40b540200000000000000000000000100204aa9d101000000000000000000000140000000010040000000).

Polkadot Nomination Pools Initial Configuration

- **Gossamer** is a Polkadot host written in Go, designed to build and run nodes for blockchain protocols compatible with the Polkadot ecosystem.
- The proposal seeks funding for further development of Gossamer over a 12-month period.
- The project has already received initial support from the Web3 Foundation Grants Program.
- The main goal is to enhance client diversity within the Polkadot ecosystem.
- The proposal includes a budget, milestones, and a detailed roadmap.
- It is currently up for vote by the Polkadot Council and, if approved, will be voted on by the community.
- Links to the original Treasury post and discussion are provided for more information.

External Motion: #168 Gossamer Ongoing Development Grant

### Polkadot Runtime Upgrade Proposal

- **Purpose**: Upgrade Polkadot's runtime to version 0.9.28 to fix a security vulnerability.
- **Issue**: Previous release allowed fake data to be added to blocks.
- **Fixes**: 
  - Security vulnerabilities.
  - Improvements to storage, contracts, and transaction payments.
- **Included Changes**:
  - New storage layer.
  - Event addition in asset-tx-payment.
  - Auto-incremental collection ID.
  - Fixes in contract function IDs and decoding depth.
  - Updates to nomination pools and weights.
- **Vulnerability Impact**: Potentially affects block authoring.
- **Process**: Proposal needs approval from the Council and community vote.
- **How to Vote**: Community members should vote for the final decision.
- **Details**: Full release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.28).

Runtime v9281 Upgrade On Polkadot

### Polkadot Runtime Upgrade v9280

- **Upgrade Details**: The Polkadot network is getting an upgrade to version 9280.
- **Key Feature**: Adds nomination pools to the Polkadot runtime.
- **Governance**: After the upgrade, nomination pools need to be configured by the community.
- **Security**: Several changes have been audited for safety.
- **Bug Fixes**: Fixes include issues with storage layers, contract functions, and transaction payments.
- **Community Involvement**: The proposal needs to be voted on by the community.
- **How to Check**: You can use a tool called srtool to verify the proposal hash.
- **Vote**: Make sure to vote if you're part of the community!

Polkadot Runtime Upgrade to v0.9.28

### Summary of Motion Proposal

- **Purpose**: This motion corrects errors in previous motions (256 and 257) and opens HRMP channels between Statemint and five additional parachains.
- **Parachains Involved**: 2021, 2031, 2032, 2035, 2046.
- **Treasury and Statemint Addresses**: Provided for reference.
- **Process**: The proposal involves sending encoded call data from the Relay Chain to Statemint, which then executes the call.
- **Funding**: 100 DOT is taken from the Treasury to cover the cost of opening 10 channels plus fees.
- **Voting**: The proposal needs approval from the Council and then a community vote in the referenda queue.
- **Preimage**: The preimage for this proposal has already been submitted for community verification.

Second Batch Of Statemint HRMP Channels (replacing motions 256 and 257)

- The v9270 runtime is based on Polkadot/Kusama v9270.
- It allows buying and selling NFTs in the Uniques pallet on Statemint and Statemine.
- Statemine can now use sufficient assets to pay XCM fees.
- This feature will first run on Statemine before coming to Statemint.
- Statemint currently has no sufficient assets for XCM fees, so it won't affect interactions.

Upgrade Statemint to v9270

### Polkadot Runtime Upgrade Proposal

- **Version**: v9270
- **Details**: Upgrade the Polkadot Runtime.
- **Release Notes**: Available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.27).
- **Proposal Hash**: `0x55507b53f5c37e97e3faf9a9274dba0c5eace970aa5c653c179126f679ed496e`
- **Verification**: Use srtool to check the proposal hash.
- **Process**: Needs Council approval, then community vote.
- **Enactment**: After successful vote.
- **Action**: Vote when convenient.

Polkadot Runtime Upgrade to v9270

### Polkadot Runtime Upgrade Proposal

- **Version**: v9260
- **Release Notes**: Available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.26)
- **Changes**: 
  - Updates to referenda and conviction voting
  - Weight updates
  - Council can now send XCMs
- **Proposal Hash**: `0x282b1166e009892d0088efb1d7158b1c04f03394b9d9cff05e19eec76ecb4e7c`
- **Verification**: Use `srtool` to check the proposal hash
- **Process**: 
  - Needs Council approval
  - Community voting required
  - Enacted after approval
- **Vote**: Make sure to vote when the time comes!

Polkadot Runtime Upgrade to v9260

Increase maximum number of HRMP channels from 10 to 30

- Polkadot is voting on upgrading its runtime to version 0.9.25.
- The release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.25).
- You can check the proposal hash using `srtool`.
- The proposal needs approval from the Council and community.
- Proposal hash: `0x73a9fe9a8dcced92ad7eb36963f64d7b49a4f66a2c5e626a812e5b6cd0e56d42`.
- Make sure to vote when you can!

Runtime Upgrade 0.9.25

### v9230 Runtime Summary

- **Based on Polkadot/Kusama v9230**: Shares the same release as Polkadot and Kusama.
- **XCM and Core Substrate Changes**: Includes updates from v9190 to v9230.
- **Renaming in Uniques Pallet**: Changes `class`es and `instance`s to `collection`s and `item`s for better industry alignment.
- **Max Items Setting**: Allows NFT collection owners to set a maximum number of items.
- **Deposit Updates**: Increases the deposit for creating fungible and non-fungible asset classes to 10 DOT.

Democracy External Proposals