- There is a proposal to upgrade Polkadot to version 0.9.23.
- The new version has some changes, including updates on weights.
- You can find more details in the release notes.
- The Council needs to approve the proposal first.
- After approval, the community will vote on it.
- Everyone is encouraged to vote when they can.
- A special code, called a call hash, is used for the upgrade.

proposalHash

votingPeriod

delay

Polkadot Runtime Upgrade to v9230

Fix: Establish HRMP Channels for Statemint

- A proposal is being made to upgrade Polkadot to a new version called 0.9.22.
- Information about this upgrade, including changes and important links, is available online.
- After the Council approves the proposal, the community will get to vote on it.
- Everyone is encouraged to vote when they can.
- A special code called a call hash for this upgrade is provided.

Polkadot Runtime Upgrade to v9220

- The Web3 Foundation and other teams joined the World Economic Forum (WEF) 2022 to talk about blockchain technology.
- They wanted to help important leaders learn about Polkadot and its uses.
- The goal was to build relationships with business leaders and journalists who don't usually know about Polkadot.
- They aimed to show how Polkadot can help businesses and improve real-life situations, not just finance.
- The foundation also wanted the media to understand blockchain and its impact on our lives.
- They believe teaching today's leaders will help create positive changes for the future.

 Proposal: Polkadot at Davos during the World Economic Forum’s Annual Meeting 2022

- A new upgrade for Polkadot is proposed to change its version to 0.9.20.
- Important information about this upgrade can be found in the release notes.
- The upgrade includes improvements for faster parachain block times.
- There’s a special code (hash) for this proposal.
- If the Council approves, the community will get to vote on it.
- Everyone is encouraged to vote when they can!

Polkadot Runtime Upgrade to v9200

- Five parachains want to connect with Statemint.
- The parachains are numbered 2011, 2000, 2004, 2006, and 2012.
- Channels between them will have a maximum capacity of 1,000.
- A deposit of 100 billion is needed for sending and receiving messages.
- The proposal requires some DOT (a type of currency) from the Treasury to be sent to Statemint.
- There are specific rules for managing the channels and messages.
- The process involves sending messages back and forth between Statemint and the Relay Chain.

First Statemint HRMP Channels

Lower HRMP Channel Deposits to 10 DOT

- This proposal is about upgrading Polkadot and Statemint.
- The Relay Chain will have a new version called 0.9.19, which includes helpful updates like child bounties and crowdloan migration.
- Users are encouraged to vote on the proposal after it is approved by the Council.
- Statemint will launch its version 900, which allows moving DOT (Polkadot's currency) easily between the Relay Chain and Statemint.
- With Statemint v900, users can also open channels and manage NFTs without any problems.

Polkadot Relay Chain v9190 and Statemint v900 Upgrades

- Phala parachain is currently stuck or "bricked."
- The team wants to fix this by asking for help with a special call to change its code.
- Phala Network became a parachain recently.
- They found a mistake in their setup that prevents upgrades.
- Both sudo and democracy are turned off, making it hard to add new features.
- Without help, the parachain will stay stuck forever.
- More details about the issue and their plans are available in a discussion link.

Unbrick Phala Network Parachain (at team's request)

Statemint Upgrade v800

- The proposal is to upgrade Polkadot to version 0.9.18.
- Important changes include logging in two parachains, and adding new types for contracts.
- The upgrade will allow for the use of a special function called set_code.
- A specific call hash is mentioned for the upgrade.
- The Council will vote on the proposal, and then the community can vote as well.
- Everyone should remember to vote when it's their turn!

Runtime Upgrade v9180 - Polkadot Network

- The Composable Finance team had a problem on the Picasso chain in Kusama.
- There was a mistake in the weight calculations for something called "pallet-democracy."
- This mistake could cause the chain to stop working after a certain time.
- A public file for using the software can be found online.
- There is a design related to preimages shared with a picture.
- A preimage hash was also provided, which is a special type of code.
- The original message about this problem can be found in a post online.

Help Composable Finance Unbrick Their Chain

- A proposal suggested by Kian from the Staking team aims to change nomination limits in Polkadot.
- The goal is to increase the maximum number of nomination intentions from 22,500 to 50,000.
- It also suggests lowering the stake needed to submit a nomination intention to 10 DOT.
- This change is possible because of new features released in Polkadot's runtime 9170.
- The proposal should be acted upon before the number of nominators reaches 22,500 to avoid issues.
- There should be no negative impact on current stakers with this proposal.

Polkadot Proposal: Lowering Nomination Intention Limits

Extend Current LP7 Crowdloans

- A proposal is made for a batch call that upgrades Polkadot and Statemint together.
- The Polkadot upgrade will change its runtime to version 9170, improving block time issues and other features.
- The Statemint upgrade will change its runtime to version 700, adding new tools for NFT creation and fixing previous problems.
- The proposal includes important call hashes for both upgrades.
- Developers need to be aware of changes related to transferring assets between networks.
- The upgrades will allow more flexibility with assets in the Polkadot network.
- Community voting will be necessary for the proposal to be enacted.

Polkadot Runtime Upgrade to v9170 and Statemint Runtime Upgrade to v700

- A new proposal wants to temporarily increase the limit for nominations to 160 DOTs.
- This change helps keep the Polkadot nomination system active.
- The previous proposal had a mistake: it used the wrong unit of measurement.
- Instead of DOTs, the proposal should have used PLANKs, which are smaller units.
- The right amount for the bond is actually 1,600,000,000,000 PLANKs.
- All other values in the proposal stay the same, except for the minimum nominator bond. 
- There are specific codes called call data and call hash related to this proposal.

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

- A proposal is made to raise the DOT nomination limit from 120 to 160.
- This change is temporary until a bigger upgrade (0.9.16) is done on Polkadot.
- The upgrade will allow nominations to change based on demand, instead of having a fixed limit.
- There were some problems with the upgrade after it was tested on Kusama, so it hasn't been proposed for Polkadot yet.
- More people are allowed to nominate, reaching a total of 22,500.
- This temporary increase will help keep the nomination system active while waiting for the main upgrade.
- The proposal keeps all other values the same, except for the minimum nomination amount.

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

- A proposal is made to upgrade Polkadot's system to a new version called v9151.
- This upgrade fixes some issues, including one about council voters and their deposits.
- People can check the details and changes about the upgrade online.
- There is a special code called a hash that identifies the proposal.
- It is important for everyone to vote on this upgrade soon.
- The upgrade is needed to get ready for the next improvements in the system.

Polkadot Runtime Upgrade to v9151

- A proposal is being voted on to upgrade Polkadot to version v9150.
- This upgrade includes fixes for some issues in the system.
- The proposal has a special code called a hash for reference.
- Voting is important and should happen soon to get ready for future updates.
- There is an update suggesting to vote “Nay” on Referendum 49 because of potential problems.
- Some people might see errors in Kusama nodes because of the upgrade.
- An additional upgrade may be needed to fix these issues later.

Runtime v9150 on Polkadot Network

- Shell updated Statemint and started block production with collators.
- There was a problem because two types of keys were used: sr25519 and ed25519.
- Aura needed sr25519 keys but was using ed25519 keys from the start.
- A temporary fix was made to use ed25519 keys in Aura for Statemint.
- This change will help validators check the signatures on blocks.
- After resolving the issue, a further upgrade will switch back to sr25519 keys.
- A special call hash was created for this update.

Fix Statemint - Aura Key Scheme

- This is about a vote called a referendum related to Polkadot.
- The previous referendum didn’t pass because Polkadot needed a default setting for messages.
- This setting helps keep Polkadot safe by making sure messages are sent with a safe version first.
- Since Polkadot is using a new feature called cross-chain interaction, they had not set a version before.
- The new proposal includes the same two calls from the last vote plus a new call to set a safe version to "2".

Upgrade Shell to Statemint (with XCM Fix)

- There are two important actions planned for upgrading a system called Statemint.
- The first action will set certain storage settings to prepare for the upgrade.
- This includes important items like setting the first Aura collators and updating a safety feature.
- The second action will authorize the actual upgrade to Statemint.
- These actions need to be carefully scheduled to ensure they happen in the right order.
- The proposal involves sending messages from a main network called Polkadot to Statemint.
- Each action is given a lot of importance to make sure they are completed properly.
- After the upgrade is authorized, it will take about an hour for the changes to take effect.

Upgrade Shell to Statemint

- A new update called Polkadot Runtime v9140 is being proposed.
- It will disable xcm teleports and reserve transfers.
- This change is needed to upgrade Shell to Statemint.
- You can find more information in the release notes online.
- There's a special code called a proposal hash for this update.
- It's important to vote on this proposal when you can.

Runtime v9140 on Polkadot Network

- A proposal to upgrade Polkadot Runtime to version v9122 is open for voting.
- This upgrade will help with the first auctions and crowdloans on the Polkadot Network.
- You can find more details in the release notes online.
- The proposal has a special code called a hash: 0x0f598b97de6adfb2c5edffb7e8e5aed6408d29382a9de372ed229391a20c4a86.
- This change is only about the runtime, so node operators don’t need to update anything.
- No new installation files have been created for this release.
- Everyone is encouraged to cast their vote when they can!

Democracy External Proposals