Batch of HRMP Channels with Statemint

- The proposal is to upgrade the Polkadot network to a new version called runtime v9420.
- This upgrade includes changes from earlier versions and has four migrations for the Relay Chain.
- A big part of this upgrade is adding something called OpenGov to Polkadot.
- For OpenGov to work, another proposal about collectives needs to be approved first.
- There are many improvements in the Relay Chain, such as new features and fixing some issues.
- This upgrade also helps developers by making it easier to see account balances.
- The proposal needs to be approved by the Council before the community can vote on it, which will take 28 days.

Runtime Upgrade v9420 on Polkadot Network

- The proposal is to upgrade the Collectives system to a new version called v9420.
- This upgrade includes important changes and improvements since version v9370.
- It introduces XCM v3 and the Technical Fellowship for managing votes and membership.
- The Fellowship will work with the Relay Chain to make decisions using messages.
- There are four runtime migrations for the relay chain included in this upgrade.
- The community will get to vote on this proposal after the Council approves it.
- For more details, you can check the linked release notes.

Runtime Upgrade for Collectives Parachain To v9420

- The Acala Foundation wanted to renew their parachain lease with a new parachain called 3336.
- They won the auction for this new parachain, but a bug in Polkadot stopped it from working properly.
- The plan is to swap the lease between Acala’s old parachain (2000) and the new one (3336).
- Creating the new parachain required special coding, which was difficult and took time.
- After winning the auction, they updated the new parachain's code, but a signal from the bug caused problems.
- The new parachain tried to work but failed, leading to an error because it wasn't set up correctly.
- Now, they need help from the relaychain to fix this issue.

Lease swap for Acala

- A proposal called referendum 112 wants to increase the number of validators in Polkadot to 500.
- The community discussed this and thought it was a good idea, but suggested increasing the number of validators slowly.
- They proposed increasing to 400 validators first, by adding 5 every era.
- Core developers agree and see that increasing the number to 500 will lower the amount of DOT needed for each validator.
- They plan to first increase the count by 3 to reach 400 after 20 eras.
- This proposal is submitted by a group of validators and will need community votes after the Council approves it.

1kvP Validators Initiative: Increase Validators Active Set to 400

- The Polkadot Council made a proposal to fix a problem from a recent decision (referendum #113).
- After the decision was made, there was a mistake because the header got overwritten by a bad transaction due to a bug.
- Because of this mistake, the parachain (a type of blockchain) couldn't produce new blocks.
- They want to fix this by redoing a part of the earlier decision to set the correct header for the parachain.
- The incorrect header needs to be reset to a specific value to solve the problem.
- The Council confirmed their intention to fix it and provided a signature as proof.
- This proposal will be voted on by the community before it can be put into action.

Fix incorrectly enacted referendum caused by a Substrate bug

- Three parachains want to connect with Statemint using HRMP channels.
- The proposal includes transferring 20 DOT from the Treasury to Statemint.
- It involves opening channels between Statemint and each parachain.
- The parachains are BitGreen (ParaID 2,048), SubSocial (ParaID 2,101), and Manta Network (ParaID 2,104).
- Each parachain is requesting this connection through their team.
- A specific encoded call and proposal hash are included for the proposal.

Three New HRMP Channels batch On Polkadot

- The proposal is to add a Bridge Hub (BH) to Polkadot, allowing communication with other networks like Kusama and Ethereum.
- The BH will be a gateway and help route messages between different networks and parachains.
- Currently, the BH has basic features, with more complex functions to be added later.
- The main goal is to get approval from Polkadot stakeholders to start the project.
- Once it's working, it will help Polkadot and Kusama work together better.
- This will allow groups from both networks to support each other more easily.

Polkadot Bridge Hub Genesis

- The Watr team wants to reset their blockchain to an earlier state called "seedling."
- They found that current rules don't allow this reset without special permissions or tokens.
- The blockchain is currently locked and can't be used until the relay chain helps.
- This reset won't affect other applications or networks since Watr hasn't started real transactions yet.
- The Watr team has tried other options and is now asking for permission to reset.
- They submitted proof that supports their request to reset the blockchain.
- Community voting will be needed to decide if the proposal will go ahead.

Reset Watr Parachain

- A proposal wants to change some rules about tokens in a system called Polkadot.
- The minimum number of tokens to start a nomination pool will go up from 200 DOT to 500 DOT.
- To be a direct nominator, the bond size will increase from 100 DOT to 250 DOT.
- Fast unstaking, which is already tested in Kusama, will be available in Polkadot.
- The number of validator candidates will rise from 1200 to 1500.
- The maximum number of nomination pools will increase from 128 to 256.
- This proposal will need Community voting after being approved by the Council.

Adjusting Nomination Configuration

- The Manta team has a new parachain on Polkadot, but they faced a problem because their blocks wouldn't produce.
- They found out the original code and data files used were not compatible.
- This issue prevented their network from launching and making transactions.
- Manta Network wants to fix this with help from Polkadot governance by changing the files.
- The solution won't cause any data loss since the parachain hasn’t made any blocks yet.
- They are asking for quick approval to start producing blocks and make their network work.
- The proposal has a special identification number for tracking.

Fix genesis registration for Manta Parachain

- The proposal is about scheduling parachain auctions on Polkadot in 2023.
- It aims to have these auctions happen throughout the year.
- There will be a total of 18 auctions planned from LP12 to LP15.
- Two auctions are planned for LP12 and LP13 each.
- Seven auctions are planned for both LP14 and LP15.
- The goal is to include new parachains and allow current ones to renew their slots. 
- More details can be found in a calendar linked in the proposal.

Polkadot Auction Schedule 2023

- A proposal to upgrade Polkadot to version v9370 has been made.
- The upgrade includes various changes for better performance and features.
- Some changes involve storage and contract management improvements.
- Users can check the specific details by visiting the release notes.
- The proposal will be reviewed by the Council, and if approved, the community can vote on it.
- Changes aim to make Polkadot easier and more efficient to use.
- The proposal encourages everyone to participate in the voting process.

Runtime Release v9370 for Polkadot

- Five parachains want to connect with Statemint.
- This action will allow proposals for money transfers and channel openings.
- Each parachain will have a specific identifier called ParaID.
- The parachains are HydraDX, Ajuna, Kapex, Pendulum, and Litentry.
- A total of 20 DOT will be transferred from the treasury.
- The Council will vote on this proposal before it goes to the community for a final decision.
- Everyone is encouraged to review and vote on the proposal.

A New Batch Of HRMP Channels: HydraDX, Kapex, Ajuna, Pendulum, Litentry

- The parachains v9370 release includes updates for the Relay Chain.
- The main change is the addition of OpenGov origins to Statemine.
- There are also upgrades for Statemint and Collectives.
- Links are provided to see more information and proposals related to these updates.
- The release has specific proposal hashes for tracking changes.

Upgrade System Parachains to v9370

- The Zeitgeist team made a proposal to fix a problem with their parachain on Polkadot.
- There was an issue with the ParaId number that made it hard for the parachain to work correctly.
- They had a similar problem on Kusama, and the community approved a fix there.
- The proposed fix involves updating the parachain's chainspec to use the correct ParaId and a newer runtime.
- The team asked the Technical Committee to quickly approve the fix to start the chain.
- A signed statement from the ParaId manager confirms the proposal's authenticity.
- If this proposal is approved, the community will have the final say through a referendum.

Unbrick Zeitgeist Parachain

- There was a problem with a previous motion in Polkadot, so it has been replaced by Motion 333.
- This new motion wants to upgrade Polkadot to a new version (v0.9.36).
- The proposal includes important details you can find in the release notes.
- Some updates in the upgrade are about improving how things work on the system, like handling bond amounts and log targets.
- This proposal needs approval from the Polkadot Council first.
- After that, the community will vote on it for the final decision.

Runtime Release v9360 for Polkadot (replacing motion 333 due to length issues)

- A proposal to support WebAssembly smart contracts on Polkadot parachains is being considered.
- It plans to create showcases for smart contracts that have been checked for safety.
- The proposal includes an incubation program and a library called "UseInk" for developers.
- The council needs to approve this proposal first.
- If approved, the community will vote on it.
- More details about the budget and work are available online.
- The proposal has a special code called a hash for identification.

Approval of Wasm Smart Contracts Bounty - bounty 19

- The proposal is about checking new software updates for parachains before they happen.
- This means validators will test the updates to make sure they work properly.
- If the updates are good, they can be added; if not, they won't be accepted.
- This process helps prevent mistakes when parachains try to create new blocks.
- It has been tested successfully on different platforms like Versi, Rococo, and Westend.
- Changes to prevent unfair punishments, called slashing, also need this method.
- Parachains have had the tool to support this for over a year.
- People are encouraged to review and vote on this proposal.

Setting pvfCheckingEnabled In The Configuration To TRUE

- The parachains v9360 release has important updates for its system.
- Statemint, a part of the release, has changes in the Assets section that affect how transactions work.
- Wallets need to be updated to match these changes.
- The Collectives Parachain now has a new role called "Fellow."
- The new "Fellow" role combines the old Founder and Fellow roles and takes away veto power.
- Fellows can also choose to step back to a role called Ally.
- More details can be found in the release notes.

Upgrade Polkadot System Parachains v9360

- The Bitgreen team upgraded their parachain code to a new version at block 191202.
- The upgrade went well, and the parachain continued working without any problems.
- A new feature called "pallet-parachain-staking" was added during the upgrade.
- This new feature helps assign new validators for the parachain's sessions.
- After the upgrade, there was an issue with setting initial values, leaving the authorities empty.
- The team talked with Parity developers and created a plan to fix this issue.
- They are asking for the proposal to be approved quickly so they can start distributing token rewards.
- Similar proposals have been approved quickly before, and they hope for the same support.

Unbrick Bitgreen Parachain

- A proposal is made to upgrade Polkadot to a new version called v9340.
- This upgrade is only about the software used and does not include a new client.
- The new version will replace older versions, v9320 and v9330.
- The Polkadot Council will decide if the proposal can be voted on by the community.
- If the council agrees, the vote will happen on January 14.
- Some important changes will happen after the upgrade, like stopping certain unfinished tasks.
- Any votes that have passed but not started will not go ahead until after the update.

Runtime Release v9340 for Polkadot

Upgrade Statemint to v9330

- The Polkadot Alliance was created by seven important projects to set rules and protect open-source development.
- The founding members are Acala, Astar, Interlay, Kilt, Moonbeam, Phala, and Subscan.
- The Alliance has two main ranks: "Fellow" and "Ally."
- Their goals include making rules, managing members, and keeping a list of bad actors.
- Membership shows a group's commitment to quality contributions within the Polkadot community.
- Members must follow rules like respecting each other's work and working together against scams.
- If members break the rules, they can be removed by a vote.

The Seeding of the Polkadot Alliance: Fighting for an open source culture and open collaboration that benefits the Polkadot ecosystem

- A proposal wants to stop the upgrade of Polkadot to version 9320.
- This is because of changes in the FRAME code that affect how schedules work.
- There is a new check in the code to prevent exceeding weight limits for blocks.
- Most functions will work fine, but the `set_code` function will not pass this check.
- This is due to `set_code` using the maximum block weight, which always fails the check.
- A new proposal will be made with the correct call soon.
- The Council must approve this motion before the community votes on it.

Tech. Comm. Proposals