This is a proposal for four parachains to open HRMP channels with Statemint. Each channel opening consists of:

- A `forceTansfer` of 20 DOT from the Treasury to Statemint sovereign account.
- A `forceOpenhrmpchannel` from Statemint (1,000) to `ParaID`.
- A `forceOpenhrmpChannel` from `ParaID` to Statemint (1,000).

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

Litentry: 2,013
Composable: 2,019
Polkadex: 2,040
Zeitgeist: 2.092

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.

This proposal aims upgrade the Polkadot network to runtime [v9420](https://github.com/paritytech/polkadot/releases/tag/v0.9.42): the specific details on this upgrade please check the release notes. This runtime contains the changes from v9370 to v9420. Please note there are 4 runtime migrations for the Relay Chain in this release (details below). In addition to the migrations mentioned above, all the migrations included in runtimes since v9380 have been included in this release, allowing to jump over a few runtimes. 

- Call Hash: `0x0352127d49a9cb7794251a4caeb9c6b729444f1f40a9ebd2284dfbc168319363`
- Preimage is submitted.

### Relay Chain

Among other things, this proposal includes the inclusion of OpenGov on Polkadot. Note that, in order for OpenGov to be fully operational, [the proposal upgrading collectives parachain](https://polkadot.polkassembly.io/motion/403) needs to be approved and enacted (this is ongoing). If this happens, Fellowship will be created in the Collectives parachain. The Technical Fellowship is an integral part of OpenGov model.

#### Relay Chain Changes

- [S] ✅ audited [#12951](https://github.com/paritytech/substrate/pull/12951) Low - Deprecate Currency; introduce holds and freezing into fungible traits

- [S] ✅ trivial [#13287](https://github.com/paritytech/substrate/pull/13287) Low - Metadata v15: expose api to fetch metadata for version

- [P] ✅ trivial [#6897](https://github.com/paritytech/polkadot/pull/6897) Low - Update weights

- [P] ✅ audited [#6701](https://github.com/paritytech/polkadot/pull/6701) Low - Introduce opengov into polkadot

- [P] ⏳ pending non-critical audit [#5974](https://github.com/paritytech/polkadot/pull/5974) Low - Kusama: enable dispute slashes

- [S] ✅ trivial [#13558](https://github.com/paritytech/substrate/pull/13558) Low - Getcallindex trait

- [P] ✅ trivial [#6928](https://github.com/paritytech/polkadot/pull/6928) Low - Vstam1/xcm admin origin

- [P] ✅ trivial [#6937](https://github.com/paritytech/polkadot/pull/6937) Low - Inherent disputes: remove per block initializer and disputes timeout event

- [S] ✅ audited [#12287](https://github.com/paritytech/substrate/pull/12287) Low - Emit event when changing total locked value in pallet-balances

- [S] ✅ trivial [#13704](https://github.com/paritytech/substrate/pull/13704) Low - Frame: fix the referenda confirming alarm

- [S] ✅ audited [#13715](https://github.com/paritytech/substrate/pull/13715) ‼️ HIGH - Reward pool migration fix

- [S] ✅ trivial [#13648](https://github.com/paritytech/substrate/pull/13648) Low - Contracts: add host function tracing

- [P] ✅ trivial [#6846](https://github.com/paritytech/polkadot/pull/6846) Low - Proxy for nomination pools

- [P] ✅ trivial [#6980](https://github.com/paritytech/polkadot/pull/6980) Low - Tighter bound on asset types teleported so that weight is cheaper

- [S] ✅ trivial [#13702](https://github.com/paritytech/substrate/pull/13702) Low - [contracts] overflowing bounded deletionqueue

- [S] ✅ trivial [#13610](https://github.com/paritytech/substrate/pull/13610) Low - Refactor: inconsistent balanceconversion fn

- [S] ✅ trivial [#13798](https://github.com/paritytech/substrate/pull/13798) Low - Uniform pallet warnings

- [S] ✅ trivial [#13722](https://github.com/paritytech/substrate/pull/13722) Low - Implement #[pallet::composite_enum]

- [S] ✅ trivial [#13699](https://github.com/paritytech/substrate/pull/13699) Low - Deprecate v1 weights

- [S] ✅ trivial [#13835](https://github.com/paritytech/substrate/pull/13835) Low - removepallet migration utility struct

- [S] ✅ trivial [#13302](https://github.com/paritytech/substrate/pull/13302) Low - Metadata v15: add runtime api metadata

- [S] ✅ trivial [#13851](https://github.com/paritytech/substrate/pull/13851) Low - Fix fungible and fungibles set_balance return value

- [S] ✅ trivial [#13724](https://github.com/paritytech/substrate/pull/13724) Low - Contracts: add sr25519_verify

- [P] ⏳ pending non-critical audit [#6934](https://github.com/paritytech/polkadot/pull/6934) Low - Enable changing executor params through governance

- [P] ✅ audited [#6843](https://github.com/paritytech/polkadot/pull/6843) Low - Xcm: properly set the pricing for the dmp router

- [S] [#13779](https://github.com/paritytech/substrate/pull/13779) Low - Add freeze/thaw events and tests

- [P] [#6662](https://github.com/paritytech/polkadot/pull/6662) Low - Xcm: remote account converter

- [S] ✅ trivial [#13827](https://github.com/paritytech/substrate/pull/13827) Low - Pallet-democracy: do not request the proposal when scheduling

- [S] ✅ audited [#13936](https://github.com/paritytech/substrate/pull/13936) ❗️ Medium - Removes reportsbykindindex

- [P] [#7114](https://github.com/paritytech/polkadot/pull/7114) ❗️ Medium - Offences migration v1: removes reportsbykindindex

- [S] ✅ trivial [#13988](https://github.com/paritytech/substrate/pull/13988) ❗️ Medium - Pallet collective: fix genesis member sort order

- [P] ⏳ pending non-critical audit [#7098](https://github.com/paritytech/polkadot/pull/7098) Low - Xcm: implement a blocking barrier

- [S] ⏳ pending non-critical audit [#13932](https://github.com/paritytech/substrate/pull/13932) Low - Frame: inherited call weight syntax

- [P] ✅ trivial [#7150](https://github.com/paritytech/polkadot/pull/7150) Low - Update weights

### System Parachain Runtimes

This Polkadot system parachain upgrade includes changes since v9370, which has several major updates. For one, it includes XCM v3.

On Statemint, this does not include NFT 2.0 or Foreign Assets as the Statemine release does, although with the audits completed these will be in an upcoming release. It does include the new runtime API to [query account balances](https://github.com/paritytech/cumulus/pull/2455), which will return all the fungible assets (under the Balances pallet and both instances of the Assets pallet) that an account owns in a single RPC call. This should be particularly useful for front end developers.

### External Motion

Please note this proposal is submitted as an external motion: meaning after/if Council approves, this submission will be up for vote in referenda queue for the community to have the final decision. It is a general expectation, given the size of the upgrade, for the community to vote on this for a complete launch period (28 days). 

Make sure to vote at your convenience!

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.

This proposal aims to upgrade Collectives system parachain to runtime [v9420](https://github.com/paritytech/cumulus/releases/tag/parachains-v9420): the specific details on this upgrade please check the release notes. This release contains the changes from v0.9.41 to v0.9.42. Please note there are 4 runtime migrations for relay chain on this release (details below), in addition to the migrations mentioned above, all the migrations included in runtimes since v9380 have been included in this release, allowing to jump over a few runtimes. Preimage is submitted:

`0x89902130dbc0b878d643e0367f5b9cc85c1b8ac80c4f6cceed9013491177da15`

This Polkadot system parachain upgrade includes changes since v9370, which has several major updates. For one, it includes XCM v3.

On Collectives specifically, this update includes the [Technical Fellowship](https://github.com/paritytech/cumulus/pull/2186). It corresponds to the launch of Open Gov on Polkadot, which is included in the Relay Chain runtime. The Fellowship will manage its membership and referenda voting on the Collectives chain, while sending its decisions (e.g. to whitelist a call for the `WhitelistedCaller` track) in an XCM message to the Relay Chain.

For specific PRs included on this release, please visit: [https://github.com/paritytech/cumulus/releases/tag/parachains-v9420](https://github.com/paritytech/cumulus/releases/tag/parachains-v9420). 

This proposal is submitted as an external motion: meaning if/after Council approves, the community will have the final decision via referenda queue. 

Make sure to review and vote at your convenience!

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.

Acala Foundation have registered para id 3336 and won a parachain slot auction by bidding with the intention to use the new lease to renew Acala para lease.

However, due to [bug in Polkadot](https://github.com/paritytech/polkadot/issues/7202), parachain 3336 can never produce valid block and therefore unable to perform lease swap action.

This proposal aims to perform lease swap between 2000 (Acala) and 3336 (parachain bid by Acala Foundation).

---

## Technical Details

In order to participate parachain auction, we need to register a parathread, which requires a genesis state and geensis wasm. However, it is time consuming to prepare those as the provided template project is not suitable for production usage and therefore we used a dummy wasm during registration.

Once we won the auction, we have created a new valid parachain wasm and use [`register.schedule_code_upgrade`](https://polkadot.subscan.io/extrinsic/15425400-2) and[ `register.set_current_head`](https://polkadot.subscan.io/extrinsic/15425407-2) to update the genesis wasm and genesis state for para 3336.

The state and wasm is correctly updated. However, there is an unexpected side effect. Due to bug [polkadot#7202](https://github.com/paritytech/polkadot/issues/7202), this set the upgrade go ahead signal. 

When the parachain is onboarded, the collator for para 3336 starts try to produce block but it failed with error:

`[Parachain] panicked at 'No new validation function found in storage, GoAhead signal is not expected', /home/build/.cargo/git/checkouts/cumulus-59522f43471fa161/a3d6cd4/pallets/parachain-system/src/lib.rs:396:21`

This is because parachain received the upgrade go ahead signal and expecting it is during the runtime upgrade process, which is not the case. This caused the inherent to panic.

It is not possible to rescue the parachain from this state without intervene from relaychain and therefore we proposed this propsoal.

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.

After the submission of [referendum 112](https://polkadot.subsquare.io/democracy/referendum/112), seeking to increase the validator active set to 500, the community discussed the possibility and the need of Polkadot increasing the validators set. 

Feedback from the proposals indicates two points:

- There's interest with increasing the number of validators of the active set **but with increments**;

- There needs to be some analysis on the effects of the increase to ensure there's no security concerns.

The results indicate that participating members would like to increase the active set to 400 with increments of 5 per era. They believe that this increase would not compromise the security of the chain and allow for natural (opportunistic) leveling as the set increases. Core developers have also agreed on similar increases by value: 

“With increasing to 500, the amount of DOT needed to acquire a validator will sharply reduce from 1.7 mDOT now, to just around 370 kDOT. We think this is overall unavoidable, but we would personally suggest first increasing to 400 and re-evaluate”

This proposal aims to increase the active set of validators by 5 per era, for 20 eras. The call also executes a one-time increase by 3 to reach 400 validators by the end of the 20 eras. Note that this initiative is submitted on behalf of a coalition of 1kvP validators.

- Preimage Hash: `0xbacad43f5467717cb1edfba6317524dc1d24fe3246afbe6a8cea7ed5fae1ba5f`
- Call data: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-rpc.dwellir.com#/extrinsics/decode/0x1a0408070a0c010401000000014038000014000000fe070a14)

Please note this proposal is submitted as an external motion: meaning if/after Council approves, the community will vote in referenda queue for the final decision. 

Make sure to review and vote!

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.

**Proposal**
###
A proposal by the Polkadot Council, and later to be voted by the community for the final decision, to fix the issue with the enactment of the recently executed [referendum #113](https://polkadot.polkassembly.io/referendum/113), submitted by Watr.
###
**Context**
###
[Referendum #113](https://polkadot.polkassembly.io/referendum/113) was enacted, and after the execution of the two extrinsics from the preimage, the runtime was correct, and the header was correct, but the header got overwritten. The header was overwritten via [inherent transaction](https://docs.substrate.io/learn/transaction-types/#inherent-transactions) from the collator. This transaction was supposed to be rejected. Still, it was not rejected due to a Substrate bug: [https://github.com/paritytech/substrate/issues/9210](https://github.com/paritytech/substrate/issues/9210)
The issue now needs to be fixed by re-executing one of two extrinsics from the previously executed referendum to set the correct header of the parachain.
###
**Impact**
###
The network runtime is in the correct state after the execution of the previous proposal to reset the parachain. Still, due to the incorrect head, the parachain cannot produce blocks.
###
**Remedy**
###
The execution of one of the extrinsic to set the Watr’s parachain (2,058) head from the previously executed governance proposal will fix the issue.
###
**Proof of Authencity**
###
`We confirm the intention to reset the head of the Watr parachain (id: 2058) to 0x0000000000000000000000000000000000000000000000000000000000000000001a3a2baafaa9623dbeab06759b78f4bce878d0fbfeef992a546bce6670131e6103170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400 to resolve the issue caused by a bug in the enactment of referendum 113`
###
Signature

`0x9618272c953c90b67973d2525bead280ea74f71d0104b267767b9312f7785f28ec683f269d565d6faf4927faa4262730b4939e71fea292be50be7e5b1f9bb987`
###	
Below is the preimage:

- Hash: `0xac9ff5733f194470235d78f67d56e656a0d8ee8a908dda7782d22ed2dfb9f9eb`

- Extrinsic: `paras.forceSetCurrentHead`(2058, [newHead](https://github.com/Watr-Protocol/seedling/blob/main/watr-head-data))

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.

As three more parachains have requested an HRMP channel opening with Statemint, this proposal aims to accept and open return channels - the following batch call aim to be executed on this proposal for each of the parachains:

1. A `forceTansfer` of 20 DOT from the Treasury to Statemint sovereign account.
2. A `forceOpenhrmpchannel` from Statemint (1,000) to [ParaID].
3. A `forceOpenhrmpChannel` from [ParaID] to Statemint (1,000).

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

- BitGreen: ParaID 2,048
- SubSocial: ParaID 2,101
- Manta Network: ParaID 2,104

Encoded Call:

`0x1a040c1a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000000080000e8030000009001003c0700080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000035080000e8030000009001003c0735080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000038080000e8030000009001003c0738080000e8030000e803000000900100`

Proposal Hash: 

`0xaed18f873e30ac5f2e80c5323fcca4c654c7a6eb2ffd0dc1755028ba87eb6352`


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.

This is a proposal to add a Bridge Hub (BH) parachain to Polkadot. All technical details can be found in the [Bridge Hub Genesis release](https://github.com/paritytech/cumulus/releases/tag/parachains-bridge-hub-polkadot-v9382). The runtime is taken from the v9382 parachains release.

The BH will be the gateway between Polkadot and other networks, like Kusama and Ethereum. For now, the BH only contains some basic logic, and none of the bridge-specific pallets. Those will get added in future runtime upgrades; the goal of this proposal is to get approval from Polkadot stakeholders and launch a "shell" such that bridge teams can focus on releasing their bridge logic, not launching a parachain.

The BH will primarily act as a message routing system within the network and between others. For example, parachains can configure their XCMP routing to interpret `parents: 2` (indicating, "go to another consensus system") as something to send to the BH to handle. Likewise, the BH can handle incoming messages and route them to the correct parachain within Polkadot.

Once operational, a Polkadot<>Kusama bridge will allow more interaction between the networks. For example, from the Polkadot Collectives parachains, the Technical Fellowship can serve both Polkadot and Kusama; or the Kusama network (as a unit body) could join the Polkadot Alliance.

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.

Contextual Information from the team, below:

**Proposal**

A proposal requested by the Watr team to reset the blockchain back to seedling. Contextual information can be found below.

**Context**

We tried to reset a technical genesis (pre-commercial deployment of runtime) of Watr. The current parachain model doesn't allow privileged operations such as a reset without either tokens in the sudo account, on-chain governance accounts or relay chain governance. However the tokens generated in this genesis block are locked and unusable. So we are unable to perform the reset and progress to commercial deployment. As such the network is locked and unusable without intervention from relay chain governance.

**Impact**

The network is locked and cannot be used or reset without intervention from relay chain governance. Whilst Devnet is active, the reset will be purely a technical rollback since our Parachain has not gone live to user transactions or funds yet. There is no risk to other applications, other Parachains or the relay chain.

**Remedy**

We have explored all other solutions and after discussion and advice from Parity experts, have created this proposal to reset the Parachain to seedling state so we can progress to commercial deployment of the Watr Parachain.

**Proof of Authenticity**

We submit the following proof of authenticity, signed by the registrar of the Watr Parachain (id: 2058) `13DgtSygjb8UeF41B5H25khiczEw2sHXeuWUgzVWrFjfwcUH`,

- Text: This proposal has been submitted to Polkadot governance by the Watr Team with pre-image hash `0x2929e149de9d487466fed4093f721f68cfcdce1600e8d44e4b5b5c725efebcc3`. We confirm our intention to update the genesis state to `0x0000000000000000000000000000000000000000000000000000000000000000001a3a2baafaa9623dbeab06759b78f4bce878d0fbfeef992a546bce6670131e6103170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400` and the runtime to (Blake2-256) `0x900f07dfc7cfa4567f2f8ee94fb18793c79d46f233331913516c82a8ea379095`

- Signature: `0xa096627fbd5cd2ec0ad77fc7687e7201aedc5d793bede53df7dd7dc74d45a12d6d30a88bd4cde6fc72456524577c80f6bf2fd62099ca7065b445a564a9631387`

**Preimage**

Below is the preimage:

- Hash: `0x2929e149de9d487466fed4093f721f68cfcdce1600e8d44e4b5b5c725efebcc3`

- Extrinsic: 

utility.batchAll(

paras.forceSetCurrentCode(2058, [newCode](https://github.com/Watr-Protocol/seedling/blob/main/watr_runtime.compact.compressed.wasm)),

paras.forceSetCurrentHead(2058, [newHead](https://github.com/Watr-Protocol/seedling/blob/main/watr-head-data))

)

**Make sure to vote at your convenience! Please note this proposal is submitted as an external motion: meaning if/after Council votes, the proposal will pass to referenda queue for the community to make the final decision.**

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.

This proposal aims to change the configuration of three operations on: Fast-unstake pallet, Staking pallet, Nomination pools pallet, particularly:

1. Increasing the minimum number of tokens to create a nomination pool **from 200 DOT to 500 DOT**.

2. Increasing the bond size required to become a direct nominator from **100 DOT to 250 DOT**.

3. **Enabling fast unstake** on Polkadot: this has been well tested in Kusama, and is ready to go 🚀. Read about fast unstake [here](https://forum.polkadot.network/t/path-to-fast-unstake-in-polkadot-kusama/1539) or [here](https://twitter.com/Polkadot/status/1625550205960523780).

4. Increasing the number of validator candidates **from 1200 to 1500** in anticipation of an increase in the active set of validators

5. **Increasing the number of pools to 256**: given the successful launch of Pools so far on Polkadot, and the network having almost the full list of 128 pools, I propose doubling the maximum count again to 256.

The previous discussion on this proposal can be found [here](https://polkadot.polkassembly.io/post/1650). 

- Call data: `0x1a000c28020100000007160100a89c13460200000000000000000000000001dc0500000000270b0001005039278c040000000000000000000001000100000000`

- Call hash: `0x4d779af12cec076f6dfe5b6087746b501592222bbcee70ff6ec51825eb389dde`

Preimage can be checked [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a000c28020100000007160100a89c13460200000000000000000000000001dc0500000000270b0001005039278c040000000000000000000001000100000000).

Please nots this is submitted as an external motion: meaning if/after Council approves, the proposal will need to be up for vote by the community in referenda queue for the final decision. 

Make sure to vote at your convenience!

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.

A proposal requested by the Manta team to register a new genesis wasm. Contextual information below:

**What Happened**

Our parathread was registered on the Polkadot relaychain, obtained a parachain slot and was upgraded to a parachain. However, we encountered a minor setback when the genesis collators failed to produce blocks on the new chain. It turns out that the registration process contained incompatible genesis WASM and state files, which caused our parachain to be stuck at genesis.

**Impact / why fast-track?**

After the acquisition of a parachain slot, Manta Network’s core development team has begun a sequence for launching the network. Not having this parachain producing blocks would prevent and delay that launch. The extrinsics called in our proposal affect just our 2104 parachain and it has not completed genesis, so there are no XCMP channels to worry about either, the relaychain should be unaffected by this.

**Remedy** 

After thorough investigation and collaboration with the Parity development team, we've identified a solution to the issue. With assistance from Polkadot governance, we can correct the incompatible parachain state & WASM files that were originally registered. This correction will not have any impact or loss of state since the chain has never produced any blocks. We believe that this is the most efficient and effective solution to get our parachain up and running.

**Council Proposal**

We humbly request that the technical committee fast-track the proposal to register the correct genesis state and code on Polkadot. This will allow our collators to begin producing blocks.

We have submitted the Preimage for the below proposal:

hash: `0x2d1b0d07d86ebe11297eb5a732d5d56e2b118eb1e8e55b0bdc801c5d313371c9`

in extrinsic [https://polkadot.subscan.io/extrinsic/14362712-2](https://polkadot.subscan.io/extrinsic/14362712-2) from the same account as was used to originally register the paraID/parathread in [https://polkadot.subscan.io/extrinsic/13905786-2](https://polkadot.subscan.io/extrinsic/13905786-2).

**Extrinsics called:**

`batchAll()`

`    - registrar::setCurrentHead(2104, corrected.state)`

`    - paras::forceSetCurrentCode(2104, corrected.wasm)`

New WASM file can be found [HERE](https://github.com/Manta-Network/Manta/actions/runs/4234987640).

registrar.paras(2104) => manager: 15ynbcMgPf7HbQErRz66RDLMuBVdcWVuURhR4SLPiqa6B8jx

Gist by the CEO of Manta Network Shumo Chu: [https://gist.github.com/stechu/9c97c7766951d377accd8835e5da79fb](https://gist.github.com/stechu/9c97c7766951d377accd8835e5da79fb)

Message Text:

"This shall serve to testify that the following Polkadot governance referendum has been initiated and is endorsed by the Manta Network team  - Referendum number: TBD - Proposal hash: 0x2d1b0d07d86ebe11297eb5a732d5d56e2b118eb1e8e55b0bdc801c5d313371c9 - Polkassembly discussion: https://polkadot.polkassembly.io/motion/362"

signature from the account that registered paraID 2104: `0x2478a5e64e8c7915e12ca048a2dfb5d04ff97f188fc1f7948bd77c19446fd421af3555a96ebbb1720b7ac1c548877ff8fc9ad12dcbf095f0aef9d8f54b444087`

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.

This proposal aims to schedule the set of parachain auctions on Polkadot in 2023 (LP12-LP15) to ensure that all auctions are properly scheduled throughout the year and the community can continue including new parachains and allowing those already up and running to renew their slots in 2023.

This proposal suggests two actions in LP12 and LP13 each, followed by seven auctions per LP14 and LP15, in a total of 18 auctions until the end of the year. Full details of the schedule can be found in the calendar [here](https://docs.google.com/spreadsheets/d/1audL4P9LhCIFuX9AXB5K7cQEvn4JgukBmcA_vxwYfTY/edit#gid=218733256).


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.

This proposal aims upgrade Polkadot to runtime [v9370](https://github.com/paritytech/polkadot/releases/tag/v0.9.37): the specific details on this upgrade please check the release notes. 

- System.setCode using Utility.withWeight: `0x56ee5c8542848bfa5c8f5be09ebf74857984031841b50679f2d5009ecfb41f6e`

- Call data can be found [HERE](https://i.ibb.co/wCRwt3j/Screenshot-2023-02-22-at-11-48-59.png).


**Runtime**

- [S] ✅ trivial [#12721](https://github.com/paritytech/substrate/pull/12721) Low - frame_support::storage: add storagestreamiter

- [S] ✅ audited [#12307](https://github.com/paritytech/substrate/pull/12307) Low - Add callbackhandle to pallet-assets

- [S] ✅ audited [#12883](https://github.com/paritytech/substrate/pull/12883) Low - Contracts: improve contract address derivation

- [S] ✅ trivial [#12963](https://github.com/paritytech/substrate/pull/12963) Low - Fix fast-unstake for accounts with slashing

- [S] [#12765](https://github.com/paritytech/substrate/pull/12765) Low - Nfts 2.0

- [S] ✅ trivial [#13010](https://github.com/paritytech/substrate/pull/13010) Low - Ignore empty authority changes

- [S] ⏳ pending non-critical audit [#12967](https://github.com/paritytech/substrate/pull/12967) Low - Add ensure-ops family methods

- [P] ✅ trivial [#6465](https://github.com/paritytech/polkadot/pull/6465) Low - Deploy scheduler agenda cleanup migration

- [S] ✅ trivial [#13045](https://github.com/paritytech/substrate/pull/13045) Low - Selectable on-runtime-upgrade checks

- [S] ✅ trivial [#13043](https://github.com/paritytech/substrate/pull/13043) Low - Remove copy from ensure* traits

- [P] ✅ trivial [#6498](https://github.com/paritytech/polkadot/pull/6498) Low - Co #13045: selectable on-runtime-upgrade checks

- [P] ✅ trivial [#6546](https://github.com/paritytech/polkadot/pull/6546) Low - Update weights (0.9.37)

Please note this proposal is submitted as an external motion: meaning if/after Council approves the motion, the community will have the final say in referenda queue.  

Make sure to vote at your convenience!

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.

Five more parachains have requested an HRMP channel opening with Statemint. This motion accepts them all and opens return channels - the following calls aim to be executed on this proposal for each of the parachains:

- A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
- A force_open_hrmp_channel from [ParaID] to Statemint (1,000).
- A force_open_hrmp_channel from Statemint (1,000_ to [ParaID].

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

- HydraDX -> 2,034 - [https://polkadot.subsquare.io/post/7](https://polkadot.subsquare.io/post/7)  
- Ajuna -> 2,051 - [https://polkadot.subsquare.io/post/10](https://polkadot.subsquare.io/post/10)
-  Kapex -> 2,007 - [https://polkadot.subsquare.io/post/11](https://polkadot.subsquare.io/post/11)
- Pendulum -> 2,094 [https://polkadot.subsquare.io/post/12](https://polkadot.subsquare.io/post/12) 
- Litentry -> 2,013

Encoded call can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a04141a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000f2070000e8030000009001003c07f2070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000003080000e8030000009001003c0703080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000d7070000e8030000009001003c07d7070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e80300002e080000e8030000009001003c072e080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000dd070000e8030000009001003c07dd070000e8030000e803000000900100). 

Encoded call data: `0x1a04141a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000f2070000e8030000009001003c07f2070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000003080000e8030000009001003c0703080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000d7070000e8030000009001003c07d7070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e80300002e080000e8030000009001003c072e080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000dd070000e8030000009001003c07dd070000e8030000e803000000900100`

Proposal hash: `0xe91253279d2f83810f4275cb3f100046fac5ced92a9f0b8a06518d2e78e32141`

Since this call requires Root origin, Council will vote first on this external motion and the community will make the final decision in referenda queue. Make sure to review and vote at your convenience!

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.

The parachains [v9370 release](https://github.com/paritytech/cumulus/releases/tag/parachains-v9370) contains updates that correspond to the v9370 runtimes of the respective Relay Chain. The main update in this release is addition of OpenGov origins to Statemine. See the release notes for more details.

[Statemint Authorize Upgrade](0x01029985e134020e8a1e2e211afcd5ac9ec6a2fd21dfb5e1c39b3b670f4415e90406)

[Collectives Authorize Upgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/extrinsics/decode/0x0102dcc6cda49b51efbe0fd184b974074d1258ca9f15b9fccfedc35b7dee6e1ab9e9) 

[Send from Polkadot](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a0008630001000100a10f0204060202286bee8801029985e134020e8a1e2e211afcd5ac9ec6a2fd21dfb5e1c39b3b670f4415e90406630001000100a50f0204060202286bee880102dcc6cda49b51efbe0fd184b974074d1258ca9f15b9fccfedc35b7dee6e1ab9e9) 

Proposal Hash: 0x75df893fe3cd4e5960179865bef1291225df793082a46e721a786b3ce463471a


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.

Based on the conversations the Zeitgeist team had with TC in the last days, and taking into account the same issue appeared for the team on Kusama and the fix was approved by the community (see [HERE](https://kusama.polkassembly.io/referendum/251)), this proposal is now submitted as external motion for consideration of the Council, before making it to referenda queue for the final decision. 

You can find the contextual information on this proposal by the Zeitgeist team [HERE](https://hackmd.io/PXotv7zMTSOphZFg4f99iQ) or below:

### What Happened

The runtime that is now deployed on Polkadot was prepared before the ParaId was obtained. During local testing rococo-local was used as the relay chain. The parachain was onboarded using another ParaId than the one within the runtime and the parachain was capable of producing blocks and functioning as expected. Assuming that everything is fine, the same runtime was used to bid in the parachain auction using a different ParaId than the one noted in the prepared runtime. As it turns out, the parachain is uncapable of producing blocks on Polkadot due to a ParaId mismatch.

About the same time Zeitgeist also bid for a slot on Kusama to execute a slot lease swap. The testing procedure was the same and also resulted in success, however the chain was also uncapable of producing blocks. If those two events were temporaly further apart, the human error would only have happened once. Unfortunately we are forced into the highly aggrevating situation to ask the governance body twice to fix our Parachain, once for Kusama (proposal) and once for Polkadot.

### Remedy

To fix the bricked chain, the chainspec used for Zeitgeist’s parachain on Polkadot must use 2092 within ParachainInfo::ParaId. To inform Polkadot about the new state root that results from the updated chainspec, paras.forceSetCurrentHead(2092, genesisHead) has to be invoked by the Root origin, whereas genesisHead is set to the resulting genesis state head that is derived from the new chainspec.

We also want to supply a new runtime. It is much more recent (polkadot-v0.9.29 instead of polkadot-v0.9.19).

### Council Proposal

We are aware of the recent discussion around the technical council circumventing due process on governance here: [https://forum.polkadot.network/t/how-to-recover-a-parachain/673/23](https://forum.polkadot.network/t/how-to-recover-a-parachain/673/23) and withdrawing from fixing broken parachains. However there is currently not a best practice solution other then avoiding mistakes.

Our humble request to the Technical Committee is to fast-rack this proposal, this is purely a technical hotfix to get the chain started the first time. 

### Proof of Authenticity

To proof that this request is authentic, the manager of ParaId 2092 does provide a signed statement of approval.

Manager (`registrar.paras(2092)`): `15Q7heNtPy5vaZ79c3eUt7M42Ao3okf7PKKdRDULBz3Z4UyF`

Statement: [1675099734007] I hereby approve the deployment of the genesis state `0x000000000000000000000000000000000000000000000000000000000000000000c2e17f26b505c2be4dcefd0ebfd3abe4536fcc86ded7329af33ddd0a9496db9a03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400` and the genesis wasm with the blake2-256 hash `0xa4fe96b65d8f78a7f92d1b7eb917ca501518b6910bee573565d16a911fb91a14` for ParaId 2092 on Polkadot

Signature: `0x6a87523b11d4dd17411c3d9ebed91175dafed6b570014b164074b54b3b2c2b147574a9a5e3f2a25dfcd15340617c4df0730302f51016d5264257e7e8b0c39880`

### 

**PLEASE NOTE THIS PROPOSAL IS SUBMITTED AS AN EXTERNAL MOTION: MEANING IF/AFTER COUNCIL APPROVAL, THE COMMUNITY WILL HAVE THE FINAL DECISION ON THE PROPOSAL IN REFERENDA QUEUE. ALSO NOTE [REFERENDUM 103](https://polkadot.polkassembly.io/referendum/103), SUBMITTED BY THE ZEITGEIST TEAM, AIMS TO EXECUTE THE SAME PROPOSAL: HOWEVER THE TEAM HAS PUBLICLY DISCUSSED 56 DAYS FOR ENACTMENT IS A LONG TIME TO WAIT FOR A FIX. IF THIS PROPOSAL PASSES, THEN REFERENDUM 103 WILL NEED TO BE CANCELED OR DOWNVOTED.**

### 

Make sure to review and vote at you convenience!

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.

**NOTE**: Due to an issue with the length of the call when submitting an external motion 333 on Polkadot.js Apps (already fixed by this [PR](https://github.com/polkadot-js/apps/pull/8899))the previous motion won't execute successfully. Motion 333 is replaced by this one.


This proposal aims upgrade Polkadot to [v9360](https://github.com/paritytech/polkadot/releases/tag/v0.9.36): the specific details on this upgrade please check the release notes. 

System.setCode hash: `0x5f48aacbbd94a881a3ce5a496e1d852f21cffe33d1f7592023f2140254683d20`

Hash wrapped on Utility > withWeight call: `0x1daf74e45c1db64e50a5fa01b20ec2e8101e589bed278841b2946d4c4d258f78`

![](https://i.ibb.co/10xqxjy/Screenshot-2023-01-27-at-10-40-07.png)

**Runtime**

- [S] ✅ trivial [#12889](https://github.com/paritytech/substrate/pull/12889) Low - Staking: store last min-active-bond on-chain

- [S] ✅ audited [#12582](https://github.com/paritytech/substrate/pull/12582) Low - Automatic withdraw_unbonded upon unbond

- [S] ✅ trivial [#12894](https://github.com/paritytech/substrate/pull/12894) Low - Warn on missing pallet::call_index

**Misc**

- [S] ✅ trivial [#12875](https://github.com/paritytech/substrate/pull/12875) Low - Use log_target in consensus related crates

- [S] ✅ trivial [#12889](https://github.com/paritytech/substrate/pull/12889) Low - Staking: store last min-active-bond on-chain

- [S] ⏳ pending non-critical audit [#12537](https://github.com/paritytech/substrate/pull/12537) Low - Try-runtime revamp and facelift

- [S] ✅ audited [#12582](https://github.com/paritytech/substrate/pull/12582) Low - Automatic withdraw_unbonded upon unbond

- [P] ✅ trivial [#6440](https://github.com/paritytech/polkadot/pull/6440) ‼️ HIGH - Fix wrong rate limit + add a few logs.

- [S] ✅ trivial [#12894](https://github.com/paritytech/substrate/pull/12894) Low - Warn on missing pallet::call_index

- [P] ✅ trivial [#6450](https://github.com/paritytech/polkadot/pull/6450) Low - Update weights (0.9.36)


Please note this proposal is submitted as an external motion: meaning if/after the Polkadot Council approves, the proposal will be up for vote by the community in democracy module for the final decision.

Make sure to vote at your convenience!

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.

This motion aims to approve the [Wasm Smart Contracts Bounty - bounty 19(https://polkadot.polkassembly.io/bounty/19).

Proposed by coalition of teams to encourage and promote the adoption and development of WebAssembly smart contracts on Polkadot parachains, the goal is to create audited Ink!/Ask! smart contract showcases, an incubation program, and a React Hooks library called “UseInk”.  Please note that due to the value requested the proposal has been submitted as an external motion. Meaning, that after/in case of Council approval, the proposal will be up for community vote via Referendum for the final decision. For information on budget, roadmap and scope of work of the bounty, please visit the bounty's contextual information: [https://polkadot.polkassembly.io/bounty/19](https://polkadot.polkassembly.io/bounty/19). 

Please note the preimage for this proposal is submitted already, however, since the proposal is wrapped on an external motion call to be voted first by the council, the preimage is not noted on Polkadot.js Apps (this is an application issue). If the proposal passes to external queue, then the preimage will pair automatically. 

Proposal hash: `0xad5bd919076c71a6acba8ffafe12dfaf8ef83e40d69a56ee1ae1d5ffaa9f429e`

![](https://i.ibb.co/QQtPkQN/Screenshot-2023-01-23-at-11-17-39.png)


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.

This proposal aims to enable pre-checking for runtime upgrade on parachains: With pre-checking enabled a parachain is only allowed to upgrade their runtime **after validators have tried compiling it and they agree it is good**, as opposed to just accepting it blindly and then fail when the parachain tries to produce blocks with the new runtime. This is just generally a good idea, exists for a while already and has been successfully tested on Versi, Rococo and Westend. It is also required for rolling out slashing as it helps reducing the risk of unjustified slashes.

Parachains need to support the `go_ahead_signal,` but that should be a non issue as this has been introduced over a year ago.

 - Call to be enacted: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.dotters.network%2Fpolkadot#/extrinsics/decode/0x332901).

Preimage is submitted. Make sure to review and vote at your convenience!

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.

The parachains [v9360 release](https://github.com/paritytech/cumulus/releases/tag/parachains-v9360) contains updates that correspond to the v9360 runtimes of the respective Relay Chain. For Statemint, this contains updates to the Assets pallet that breaks transaction version; wallets should update accordingly. For the Collectives Parachain, this merges the Founder/Fellow roles into one “Fellow” role, removes veto power, and allows Fellows to step down to Ally. See the release notes for more details.

[Statemint Authorize Upgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x010239127c43fb7051d78dd91eb724b087607cb09bc046824b0d52e0a48981943e68)

[Collectives Authorize Upgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/extrinsics/decode/0x0102de7616501046da7138c35e0b4699bf403a09523533f30e0e5180dbb5fb8fec4d) 

[Send from Polkadot](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a0008630001000100a10f0204060202286bee88010239127c43fb7051d78dd91eb724b087607cb09bc046824b0d52e0a48981943e68630001000100a50f0204060202286bee880102de7616501046da7138c35e0b4699bf403a09523533f30e0e5180dbb5fb8fec4d) 

Proposal Hash: `0xa730cdb8c4b933b9e9ced277e63e79f0f52c0159f78bf60037f6ba312324051f`


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.

Contextual information from the Bitgreen team, below:

For a detailed description please refer to this: [https://hackmd.io/@t9B1coeOQ1GlARb2EZRx3g/Hy0mnACdo](https://hackmd.io/@t9B1coeOQ1GlARb2EZRx3g/Hy0mnACdo)

The bitgreen parachain was upgraded from a shell runtime to our latest runtime code at block 191202.

The upgrade executed without issues and the parachain continued to produce blocks. The upgraded parachain runtime introduced a couple of new pallets, the pallet-parachain-staking among them. This new pallet was responsible to assign new validators to session pallet and by extension the aura pallet. After the runtime upgrade, when a new session was triggered, it set the new authorities to an empty set since the pallet-parachain-staking was not set with any initial values.

We have explored all other solutions and after discussion and advice from Parity devs have created this proposal. Our humble request to the TC is to fastrack this proposal, this is purely a technical rollback since our chain has no user transactions or funds yet. We would like to distribute token rewards as soon as possible. Similar parachain resetshave been fastracked by the TC in the past and we request that our proposal be fastracked aswell.

Proposal hash: `0xfc0c33d0c0ae08d940fddadb11e239710da69b8660eaae7f77ea102a331e4ebe`

Preimage is submitted. 



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.

This proposal aims upgrade Polkadot to [v9340](https://github.com/paritytech/polkadot/releases/tag/v0.9.34): the specific details on this upgrade please check the release notes. 

- This is a runtime-only release. 
- No node client is released, also this Polkadot runtime replaces runtime v9320 and v9330.

Proposal hash: `0xace5dccb8eecfab754154a27c370a513d79d4fcda40f5837be1c0f129cdf4726`

Please note this proposal is submitted as an external motion: meaning if/after the Polkadot Council approves, the proposal will be up for vote by the community in democracy module. 

Make sure to vote at your convenience!

### IMPORTANT NOTE ON THIS UPGRADE:

Assuming Referendum 96 passes, Polkadot will upgrade to runtime v9340 on Saturday 14 Jan. This will have several effects: **please read below!**

First, any outstanding multisig calls (ones where one signatory has signed, but not the threshold) will not be able to execute. Please either finish your multisig calls before this upgrade, or wait until after it is completed. [https://github.com/paritytech/substrate/pull/12072](https://github.com/paritytech/substrate/pull/12072).

All preimages and the dispatch queue will be cleared. Any Referenda already passed but not enacted will thus not execute. If the Referendum is ongoing, the preimage can be re-uploaded after the upgrade. [https://github.com/paritytech/substrate/pull/11649](https://github.com/paritytech/substrate/pull/11649).

Runtime Release v9340 for Polkadot

This is a motion to upgrade Statemint to v9330. The release notes can be found in the [Cumulus release page](https://github.com/paritytech/cumulus/releases/tag/parachains-v9330). Like the Statemine upgrade, this adds the new asset destruction interface. It also brings in the ability to pay XCM fees using sufficient assets ([PR 1910](https://github.com/paritytech/cumulus/pull/1910)).

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.

This proposal aims to cancel the upgrade of Polkadot Runtime to v9320, due to a change on FRAME code explained below:

As the dev team works on transforming all FRAME pallets and code to work properly with WeightsV2, they have added the following check to the scheduler pallet: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107)

This piece of code should ensure that we don't execute a scheduled call that would use more weight than we have left for the block. For most calls this isn't any problem as they should be fit easily into a block. However, for `set_code` the dev team currently has annotated it with using the max block weight: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 ](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 )

So, when trying to execute `set_code` with the scheduler it will always fail this check. There will be already some consumed weight when trying to dispatch the call and `some_weight + max_block_weight` will always be bigger than `max_block_weight`. A new proposal will be submitted with the correct call soon.


 - Proposal hash: `0x88998cf7535c1f22d62849be8464fdc38fe46c0a46dc943ec56c91ef6592ec65`

 - Preimage is submitted. 

- Note this motion is an external one: meaning if/after Council approves, the community will vote on this proposal with the final decision.

Tech. Comm. Proposals