### Polkadot Runtime Upgrade Proposal

- **Version**: 0.9.20
- **Purpose**: To upgrade the Polkadot runtime.
- **Changes**: Includes improvements to parachain block times and other client-side enhancements.
- **Proposal Hash**: `0xf94667fb9411092c1c0b2f157021ff871d92c60becfe8cd467a16e6d6ccf4a92`
- **Process**: Needs approval from the Council, followed by community voting.
- **Enactment**: The upgrade will be enacted if the proposal passes.
- **Check Hash**: You can verify the proposal hash using srtool.
- **Vote**: Community members should vote when the proposal is up for approval.

Polkadot Runtime Upgrade to v9200

- Five parachains requested HRMP channels with Statemint.
- The motion accepts these requests and opens return channels.
- Parachains involved: 2011, 2000, 2004, 2006, and 2012.
- Channel config: maxCapacity is 1,000 and maxTotalSize is 102,400.
- HRMP config: hrmpSenderDeposit and hrmpRecipientDeposit are both 100,000,000,000.
- The proposal involves sending DOT from the Treasury to Statemint for channel setup.
- The final call hash is `0x6306b068f6a71eb1db5abd9609a0ffbbe7c441c9144ecf8a49e7c2bc19f7f6e9`.

First Statemint HRMP Channels

Lower HRMP Channel Deposits to 10 DOT

- This proposal is for upgrading both the Polkadot Relay Chain and Statemint.
- The Relay Chain will be upgraded to version 0.9.19, which includes new features like child bounties and slot swapping for parachains.
- Statemint will be upgraded to version 900, allowing DOT transfers between Polkadot and Statemint, and enabling NFT operations.
- Both upgrades need to be voted on by the community and approved by the Council.
- The Statemint upgrade also prepares for future XCM V3 updates.
- Users can check the proposal details and vote when the time comes.

Polkadot Relay Chain v9190 and Statemint v900 Upgrades

### Phala Network Parachain Issue

- Phala Network (ID: 2035) recently became a parachain.
- The team discovered a misconfiguration in the genesis runtime.
- Both sudo and democracy are disabled, preventing runtime upgrades.
- Without relaychain assistance, the parachain will be "bricked."
- The team proposed a `Paras.forceSetCurrentCode` call to fix this.
- Proposal hash: `0x7af427aa7665a073ca61b83c04791f185d9170ea2e49a8a7be323650cea8b75f`
- More details are available in the discussion link: [Polkassembly Post](https://polkadot.polkassembly.io/post/1005).

Unbrick Phala Network Parachain (at team's request)

Statemint Upgrade v800

### Polkadot Runtime Upgrade Proposal

- **Version**: 0.9.18
- **Purpose**: Upgrade Polkadot's runtime.
- **Key Changes**:
  - Allow two parachains to swap slots.
  - Restore `maxnominators` as a metadata constant.
  - Add proxy types for Kappa Sigma Mu.
  - Enable upgradable contracts using `set_code` function.
- **Proposal Hash**: `0xa9ad07f0ea8e95c15247ba05a2754405acbf4de6cea8fe0cfdb94196c6093670`
- **Process**: 
  - Council approval needed.
  - Community voting required.
  - Enactment after approval.
- **Check Proposal**: Use `srtool` to verify the proposal hash.
- **Action**: Vote when convenient if the proposal passes.

Runtime Upgrade v9180 - Polkadot Network

- **Composable Finance** faced a similar issue on Kusama as on Picasso chain.
- The problem was due to a stray `todo!` in weight calculations for pallet-democracy.
- This error would have caused the chain to stop working after a certain period.
- A public wasm file to fix the issue is available [here](https://github.com/ComposableFi/composable/releases/tag/v2.1.2).
- The preimage design is shown in the image linked in the original post.
- The preimage hash is `0xad2813b46b52fe8f38cb5af7da9c7f0f66416900070b949daa62cf92bbdc6fd7`.
- The preimage has already been submitted.

Help Composable Finance Unbrick Their Chain

- This proposal suggests changes to Polkadot's nomination limits.
- It aims to increase the number of possible nomination intentions from 22,500 to 50,000.
- The proposal also suggests lowering the stake required to submit a nomination intention from 10 DOT to 1 DOT.
- These changes are meant to prevent the "nominate" transaction from becoming unavailable.
- The proposal should be enacted before the number of nominators reaches 22,500.
- It is designed to relax limits without negatively affecting stakers.
- The proposal is explained by Kian from the Staking team.

Polkadot Proposal: Lowering Nomination Intention Limits

Extend Current LP7 Crowdloans

### Polkadot and Statemint Upgrade Summary

- **Polkadot Upgrade**: Polkadot will be upgraded to version **v9170**, addressing block time issues and enabling a new feature that removes the strict maximum count for nominators.
- **Statemint Upgrade**: Statemint will be upgraded to version **v700**, improving NFT class management and enabling full use of HRMP channels with other parachains.
- **Security Enhancements**: The upgrade includes fixes for issues found by independent auditors, preparing Statemint for asset and NFT creation.
- **Council Motion**: A council motion will authorize the upgrade, with a specific call hash and encoded call for the XCM (Cross-Consensus Message) process.
- **Community Vote**: The proposal will be voted on by the community after approval by the council.
- **Resources**: Detailed information about the upgrades, including release notes and runtime changes, can be found in the provided links.

Polkadot Runtime Upgrade to v9170 and Statemint Runtime Upgrade to v700

### Summary of the Proposal

- The proposal aims to temporarily increase the nomination limit to 160 DOTs, similar to [motion 157](https://polkadot.polkassembly.io/motion/157).
- This change allows the `chill_other` transaction to be used, helping to manage the number of nominators.
- The previous proposal had a major flaw: it used PLANKs instead of DOTs, the smallest unit of the DOT currency.
- The correct value for the minimum nominator bond should be `1600,000,000,000` PLANKs.
- The call data and hash for the correct proposal are provided.
- This change is necessary to keep the nomination ecosystem active while waiting for the next runtime upgrade.

Polkadot’s Update to 160 DOTs as minimum nomination limit: A follow-up proposal fixing a unit mistake

- Polkadot planned to remove the 120 DOTs nomination limit with the 0.9.16 upgrade.
- The 0.9.16 upgrade was delayed on Polkadot due to issues on Kusama.
- The number of nominators in Polkadot reached the 22,500 limit.
- A temporary increase to 160 DOTs is proposed to manage the nomination limit.
- This change allows the `chill_other` transaction to reduce the number of nominators.
- The proposal aims to keep the nomination ecosystem active while waiting for the 0.9.16 upgrade.
- The call hash and call data for the proposal are provided.
- The preimage for the proposal has been submitted.

Polkadot’s Update to 160 DOTs as minimum nomination limit: The Reason

### Polkadot Runtime Upgrade Proposal

- **Version**: v9151
- **Purpose**: Upgrade Polkadot's runtime
- **Changes**: Includes runtime cleanup and fixes, such as fixing locked deposits for council voters
- **Proposal Hash**: `0xc0d644131338cbf809cdb03afe0f7e1660b228e18011087858828ced4365d82e`
- **Verification**: Use `srtool` to check the proposal hash
- **Voting**: Vote at your convenience to upgrade as soon as possible
- **Next Steps**: Prepare for the next runtime upgrade

Polkadot Runtime Upgrade to v9151

### Polkadot Runtime Upgrade v9150

- **Proposal**: Vote on upgrading Polkadot Runtime to v9150.
- **Details**: Includes runtime cleanup and fixes, such as addressing locked deposits in council voters and Nicks pallet.
- **Hash**: `0x960d3ad3f42eb41ab2131e1561dd8cc20f87585e37d2d1b02525578204f11d4b`
- **Verification**: Use `srtool` to check the proposal hash.
- **Vote Recommendation**: Initially, vote to upgrade as soon as possible.
- **Update**: Advise voting `Nay` on Referendum 49 due to missing companion changes for Polkadot.
- **Kusama**: Likely to propose an additional runtime upgrade to revert the issue.
- **Mainnet**: Avoid risks until the issue is resolved.

Runtime v9150 on Polkadot Network

- Shell upgraded Statemint to use new keys, but there was a key type mismatch.
- Aura uses sr25519 keys, but Statemint's keys were ed25519.
- A temporary fix was made by creating a new runtime to allow ed25519 keys in Aura.
- This fix will let validators check collator signatures.
- Once blocks are produced, Aura will switch back to sr25519 keys.
- The call hash for this change is `0x0e21b5233c7591ee89eca0cae71cf9a9a4c45fe2393075ab33361a673f5d322d`.
- The preimage for this change is shown in the image link.

Fix Statemint - Aura Key Scheme

- This is a follow-up to Referendum 46, which failed due to no default XCM version set in Polkadot.
- A protection was added to prevent the Relay Chain from sending messages without a safe version, after a previous vulnerability.
- This is the first cross-chain interaction for Polkadot, so the version was not initialized.
- The new batch includes the same two calls as Referendum 46, plus an additional call to set the default XCM version to 2.
- The images show the details of the calls and the XCM version setting.

Upgrade Shell to Statemint (with XCM Fix)

### Summary of Scheduled Transactions

1. **Two Transactions**: Two transactions are scheduled to ensure `set_storage` happens before the upgrade authorization.
2. **Set Storage**: The first transaction sets storage keys in Shell for Statemint's "genesis".
   - Includes setting Aura collators and `SafeXcmVersion` to `2`.
3. **Authorize Upgrade**: The second transaction authorizes the upgrade to Statemint.
   - Once authorized, the runtime can be submitted for upgrade.
4. **Shell Constructions**: Both transactions are constructed on Shell and dispatched via XCM from the Relay Chain.
5. **Polkadot Proposal**: The proposal schedules these messages to dispatch from Polkadot to Shell, ensuring they are processed separately.
6. **Call Hash**: The call hash for the proposal is `0xa6830793b6a3473f66fbd7305a9e330dd2dd688df0e8fcbd0c9ff08d28040a34`.

Upgrade Shell to Statemint

### Polkadot Runtime Upgrade Proposal (v9140)

- **Proposal**: Upgrade Polkadot Runtime to version 9140.
- **Purpose**: Disable xcm teleports and reserve transfers.
- **Reason**: Prerequisite for upgrading Shell to Statemint on the network.
- **Proposal Hash**: `0x317c7862dc523bd083e4dd6545079bdc18058f561bada9e5e5646935b1cc04af`
- **Details**: Release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.14).
- **Verification**: Users can check the proposal hash using srtool.
- **Vote**: Please vote at your convenience.
- **Note**: This is a runtime-only release.

Runtime v9140 on Polkadot Network

### Polkadot Runtime Upgrade Proposal

- **Proposal**: Upgrade Polkadot Runtime to version 9122.
- **Purpose**: Supports the first auctions and crowdloans on the Polkadot Network.
- **Hash**: `0x0f598b97de6adfb2c5edffb7e8e5aed6408d29382a9de372ed229391a20c4a86`.
- **Verification**: Use srtool to check the proposal hash.
- **Release Type**: Runtime-only; no node upgrades required.
- **No Binaries**: No new binaries, packages, or Docker images created.
- **Voting**: Vote at your convenience.
- **Details**: Full release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.12-1).

Runtime v9122 on Polkadot Network

Proposal to Onboard Shell on Polkadot

### Proposal for First Parachain Auctions on Polkadot

- **Purpose**: To schedule the first parachain auctions and get Council approval for a 3-6 month auction schedule.
- **Readiness**: Parity engineering team believes the code for parachains, auctions, and crowdloans is ready for production.
- **First Batch**: 
  - 5 auctions starting on November 11, each lasting 7 days.
  - Auctions will begin every 7 days for lease periods 6-13.
- **Second Batch**: 
  - 6 auctions starting on December 23, each lasting 7 days.
  - Auctions will begin every 14 days for lease periods 7-14.
- **Timing**: Auctions will start around mid-day UTC on November 11.
- **Stability**: Proposes limiting Polkadot parachain slots to 75% of Kusama's to ensure stability.
- **Duration**: Initial schedule will last until early March, with potential updates based on network growth.

Proposal for First Parachain Auctions on Polkadot

- A proposal to upgrade the Polkadot network to version 9110 was submitted with a compact hash, but it was too large for the network.
- A new motion, **Motion 117**, is now up for vote with a compressed hash to fix this issue.
- The motion aims to upgrade the Polkadot Runtime to version 9110, with details available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.11).
- The correct hash for the proposal is `0x791e698f3690481e0eb16d35017cf3bb27ec095ec6f27dafd3a230b76dc42f86`.
- Users can verify the proposal hash using `srtool`.
- Voting is open for the Council to decide on the upgrade.

Runtime v9110 on Polkadot Network

### Polkadot Runtime Upgrade Proposal (v9110)

- **Proposal**: Upgrade Polkadot Runtime to version **v9110**.
- **Details**: Release notes, runtime changes, and proposal hash are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.11).
- **Hash**: `0xe874dd4219efa603acc0ab24a592d6f1b8553b7aedb196d1ef65fdd7fc3b8fe5`.
- **Verification**: Use `srtool` to check the proposal hash.
- **Importance**: Migrations and changes in v9100 require this upgrade; skipping is not possible.
- **Timing**: If fast-tracked, ensure it follows v9100 on the network and v9110 on Kusama.
- **Action**: Vote at your convenience.

### Polkadot Runtime Upgrade Proposal (v9100)

- **Proposal**: Upgrade Polkadot Runtime to version 9100.
- **Details**: Release notes and changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.10).
- **Proposal Hash**: `0x8160fd4a5aa5d58491cc8d4f0919780da25feb9ada92c2126b3f1d859800dd81`.
- **Verification**: Use `srtool` to check the proposal hash.
- **Runtime Version**: Uses a non-compressed version.
- **Timing**: Fast-track after Kusama's runtime upgrade.
- **Voting**: Vote at your convenience.

Tech. Comm. Proposals