Invalid

Original Proposal: [HERE](https://polkadot.polkassembly.io/treasury/192).

The proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Polkadot/Kusama and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team (16 months retroactive, 12 months in future), with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal can be reviewed on [the post](https://polkadot.polkassembly.io/treasury/192) and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project. Please note that both networks are voting on the project: the Kusama proposal (up for vote by the community on OpenGov) can be found [here](https://kusama.polkassembly.io/referenda/1). 

If approved by Council, this proposal will be up for vote after by the community in referenda queue. @Councillors: please review and vote at your convenience!

Proposal hash: 0xcb7a0584b5d85d6065d2e492d476aa1c1b92b9a0e492aa668b33036671500ddb

1. The Snowfork team wants to create a bridge between Polkadot/Kusama and Ethereum.
2. The bridge will be fully trustless, permissionless and for general use.
3. The Snowbridge team is asking for funding for 28 months to cover all operations.
4. The goal is to launch the bridge on the Bridge Hub for both Polkadot and Kusama.
5. Both networks will vote on the project before it can be approved.

Treasury Proposal: Snowbridge Funding Proposal

canceling, will recreate on OpenGov

Hello everyone!
I'm an active Polkadot ecosystem user who believes in its future!

I am pleased that the system provides the ability to return funds that were mistakenly transferred.

2022-05-11 17:28:30 I accidentally [sent](https://polkadot.subscan.io/extrinsic/0xbbc0738087df6875137fd8aed2e533b243dc660a1b428b97e79174d37226fed6) 254.1591507553 DOT to the address 0x0000000000000000000000000000000000000000000000000000000000000000(null). In fact, from the extrinsic [event](https://polkadot.subscan.io/extrinsic/10261275-2?event=10261275-14), I observed that these DOT were sent to the 13YMK2eYoAvStnzReuxBjMrAvPXmmdsURwZvc62PrdXimbNy address, so I believe that community may help me and transfer back my DOT. **I admit that this is my mistake but I hope for community understanding.** Thank you in advance!

Extrinsic: https://polkadot.subscan.io/extrinsic/0xbbc0738087df6875137fd8aed2e533b243dc660a1b428b97e79174d37226fed6
Sent from: 13b9d23v1Hke7pcVk8G4gh3TBckDtrwFZUnqPkHezq4praEY
Sent to: 13YMK2eYoAvStnzReuxBjMrAvPXmmdsURwZvc62PrdXimbNy





<ins>UPD:</ins> I also observed that these 254.1591507553 DOT were crossed out to the Acala network https://polkadot.subscan.io/xcm_message/polkadot-89bc9819c0d0315bbc0889808e05fa0529e61dfd, and tokens are actually on the https://acala.subscan.io/account/zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3 Acala address(with only one my mistaken transfer). So probably, my proposal should be for the Acala network instead of Polkadot: to make a force XCM transfer(if it's possible) from Acala zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3 to my Polkadot address 13b9d23v1Hke7pcVk8G4gh3TBckDtrwFZUnqPkHezq4praEY. Or probably just to send DOT from zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3 inside the Acala network to my Acala address 23TkCwTwrCVugQf8oT4JThhheUBAShETStL9YaifdP1hfe2e (which is the same Substrate address as 13b9d23v1Hke7pcVk8G4gh3TBckDtrwFZUnqPkHezq4praEY).
I would appreciate any help!


<ins>UPD2:</ins> please delete/cancel/rollback this proposal, because:
1) I've created [a new one](https://acala.subsquare.io/democracy/proposal/22) more proper on the Acala network, because tokens are on the Acala network.
2) Token amount on this proposal is incorrect because have many ending zeros.

For a second-grade student:
- Someone accidentally sent their money to the wrong address on the Polkadot ecosystem.
- They are asking for help from the community to get their money back.
- They found out that their money was transferred to another network called Acala.
- They made a new proposal on the Acala network to get their money back.
- They asked to delete the old proposal because it had the wrong amount of money.

Cancellation: Return back DOT which were mistakenly sent to the 0x0000000000000000000000000000000000000000000000000000000000000000 address - public proposal #25

This is a democracy proposal to open a bi-directional HRMP channel between Statemint and [Composable](https://www.composable.finance/). Posted as a discussion [here](https://polkadot.subsquare.io/post/21). Composable's parachain ID is 2019 which is used in HRMP calls for channel opening.

This channel will be used to obtain native stablecoins in the Composable ecosystem.

The batch_all contains:

A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
A force_open_hrmp_channel from Composable to Statemint.
A force_open_hrmp_channel from Statemint to Composable.

- A proposal has been made for Statemint and Composable to open a channel to exchange stablecoins.
- Composable has a unique ID (2019) that will be used to make this exchange possible.
- The proposal includes a transfer of 20 DOT from the Treasury to Statemint's account.
- Both Statemint and Composable will open HRMP channels to facilitate the exchange.
- This exchange will allow for the use of stablecoins within the Composable ecosystem.

HRMP Channel Opening: Composable <> Statemint

## Polkadot EVM Smart platform
- The EVM smart contract parachain PSC developed by the ChainX team uses DOT as the original Gas fee. 
- PSC will be integrated into the Omnichain financial platform OmniBTC to help us achieve PolkaDot's mission of universal chain interconnection.

## For a detailed description please refer to this:
https://github.com/OmniBTC/PSC/issues/1

Launch PSC Parachain - public proposal #21

As all but one of the council [chose to abstain](https://polkadot.polkassembly.io/motion/373) from voting to pass this proposal to a community vote - I'm now submitting this through democracy for the community to decide whether this proposal should be voted on by the community.

Some of you might feel this proposal reaches outside of the normal scope the treasury - I would argue that, given this technology's stated aim to be decentralised and unstoppable, this is an existential question the community should decide.
 
I would ask people to read the proposal and consider the impact voting for it would have for both`Polkadot and the people affected by this disaster. 


**Proponent: Simon Hipkins (Key Pictures)
 Beneficiary: Ihtiyac haritası (NeedsMap.coop) 1haY6iHgLopw2WWmPhcdCy2jwzL2jthbNL515rUyJtnmhUt
 Date: 20.03.2023
 Requested DOT: 171333.51 (USD $1,081,000.00) Converted to DOT using the EMA7 rate on subscan on date of submission (20/03/2023)**

**Summary:**
 On February 6th, 2023, two earthquakes hit Pazarcik and Elbistan in Kahramanmaras, Turkey, leading to over 50,000 deaths and leaving 1.5 million people homeless. This was the deadliest earthquake worldwide since the 2010 Haiti earthquake. 

It is also proving to be one of the first major examples of blockchains and their tokens being used to directly offer humanitarian assistance. 
 So far over $12.5 million in donations have been made from blockchain protocols, treasuries, exchanges and donors.

**This proposal provides a tangible and transparent way for the Polkadot community to contribute to a long-term and a UNDP approved best practice project that will help people recover from this terrible disaster.**

Ihtiyacharitası (NeedsMap.coop) is one of Turkey's most reliable non-governmental organizations and has been at the forefront of search and rescue efforts in recent weeks. As UNDP co-lead for reconstruction efforts in the region they are now beginning to construct a series of villages built from repurposed shipping containers across the affected region. These villages will provide much needed housing, social and psychological care for those affected by the earthquake. They will also be a best practice model for other UN affiliated organizations and contractors building hundreds of such container villages across the region. 

 This proposal would allow the Polkadot community to build a neighbourhood in one of these villages. This neighbourhood would consist of around 100 containers (households) and house approximately 400 - 450 people over an area of 6900m2.

As it is usual for such temporary post-earthquake housing to be necessary for at least two years - this proposal also budgets to support the maintenance and social program for this neighbourhood for 24 months.

**In effect we will be using DOT to give a two-year lifeline to hundreds of people to rebuild their lives and helping to define a best practice model for post-disaster housing.**

Please read the full proposal and budget [here](https://docs.google.com/document/d/102KiQRMjDSemj8eSNCYJe8VSwOc_aMbqBU6mXbjJbms/edit?usp=sharing).

And you can [listen to an interview](https://drive.google.com/file/d/1M7oAbRKsvYmue2qJs7j_GFVOqWzXkZdx/view?usp=sharing) I made with [Esra Arslan](https://www.linkedin.com/in/esra-arslan-63088314/), co-founder of the beneficiary organisation NeedsMap and project lead for the container village in Hatay. During the interview I was able to ask her many of the questions raised over the last weeks.

And you can view images of the current construction work [here](https://drive.google.com/drive/folders/18JkK3xWBmTYEN5DSSEg0eabyP_gfS-i0?usp=sharing). 

> 
**Beneficiary Identity**

The DOT Account of the Beneficiary, ‘Ihtiyaç haritası’ (NeedsMap) has been approved by ‘MASAK’ (The Turkish Financial Regulator). As part of the Turkish government regulations, NeedsMap (along with all NGOs in Turkey) were mandated to set-up their wallet addresses on Turkish exchanges, Paribu and BTCTurk. The ‘Ihtiyaç haritası’ (NeedsMap) wallet address has been opened on the local Turkish crypto-exchange, Paribu. 

As the NeedsMap wallet address is on an exchange it is not possible for them to create an on-chain identity for the beneficiary account. In lieu of this on-chain identity, NeedsMap has publicly tweeted out the beneficiary address in the proposal - available to see here:

[https://twitter.com/ihtiyacharitasi/status/1632116990390288391?s=20](https://twitter.com/ihtiyacharitasi/status/1632116990390288391?s=20)

This DOT address - can be verified to be the same on Paribu - the Turkish exchange - webpage here:

[https://www.paribu.com/blog/en/news/about-our-disaster-support-plan-and-the-cryptocurrency-donation-system/](https://www.paribu.com/blog/en/news/about-our-disaster-support-plan-and-the-cryptocurrency-donation-system/)

If this proposal is successful, Paribu will hold NeedsMap’s DOT in account and convert it into Turkish Lira gradually so as not to affect the market value. 

In accordance with the Turkish Regulator’s requirements, for every request NeedsMap makes for funds from their account at Paribu - they must supply an invoice - e.g. for the purchase of 100 containers. All these invoices will be made available to the DOT community as part of the reporting process on the project (see milestones) to ensure full transparency that the DOT contributed is being used to pay for the project.

All of NeedsMap’s transactions regarding support they receive are audited on a daily basis by Mazars, an independent audit, tax and accounting company. In addition, every spend from their DOT beneficiary address will be invoiced for, and these invoices will be made available to the Polkadot community in 3 milestone reports over the duration of the project.

- In Turkey, two earthquakes hit Pazarcik and Elbistan on February 6th, 2023, causing over 50,000 deaths and leaving 1.5 million people homeless.
- A non-governmental organization called Ihtiyac haritası (NeedsMap.coop) is constructing a series of villages built from repurposed shipping containers across the affected region to provide much-needed housing, social and psychological care for those affected by the earthquake.
- This proposal aims to allow the Polkadot community to build a neighborhood in one of these villages, consisting of around 100 containers and housing approximately 400-450 people over an area of 6900m2.
- The proposal budgets to support the maintenance and social program for this neighborhood for 24 months, providing a two-year lifeline to hundreds of people to rebuild their lives and helping to define a best practice model for post-disaster housing.
- The DOT account of the beneficiary, NeedsMap, has been approved by the Turkish Financial Regulator, and if this proposal is successful, Paribu will hold NeedsMap's DOT in account and convert it into Turkish Lira gradually so as not to affect the market value.

Polkadot Spending Proposal: DOT Housing for those affected by the Turkish-Syria Earthquake

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

This proposal was enacted via

https://polkadot.polkassembly.io/referendum/113

This is no longer needed, please reject





[Please Reject] Superseded by referendum 113

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!

- Polkadot network is getting an upgrade to runtime v9420.
- OpenGov will be included in Polkadot, but it needs another proposal to be approved and enacted.
- There are many changes to the Relay Chain, including the deprecation of Currency and the introduction of holds and freezing into fungible traits.
- The upgrade includes changes since v9370, including XCM v3.
- This proposal is submitted as an external motion and will be up for a community vote for 28 days.

Runtime Upgrade v9420 on Polkadot Network

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.

Acala Foundation won an auction to use a new lease to renew Acala para lease, but due to a bug in Polkadot, the new lease cannot produce a valid block. They want to perform a lease swap between Acala and the new lease. 

To participate in the auction, they needed to register a parathread, which required a genesis state and wasm. They used a dummy wasm during registration and created a new valid parachain wasm once they won the auction. 

Updating the genesis state and wasm for the new lease caused an unexpected side effect due to the bug in Polkadot. The upgrade go ahead signal was set, causing the inherent to panic when the collator for the new lease tried to produce a block. 

The parachain cannot be rescued from this state without intervention from the relaychain. 

A proposal has been made to perform a lease swap between Acala and the new lease.

Lease swap for Acala

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!

- Polkadot community discussed increasing the number of validators in the active set.
- They want to increase the active set to 400 with increments of 5 per era.
- The proposal aims to execute a one-time increase by 3 to reach 400 validators by the end of 20 eras.
- Core developers agree with similar increases by value.
- The initiative is submitted on behalf of a coalition of 1kvP validators.

1kvP Validators Initiative: Increase Validators Active Set to 400

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!

1. The proposal is about upgrading the Collectives system parachain to a newer version called v9420.
2. The upgrade includes changes since v9370, which has several major updates, including XCM v3.
3. The Technical Fellowship is included in this update, which corresponds to the launch of Open Gov on Polkadot.
4. The Fellowship will manage its membership and referenda voting on the Collectives chain and send its decisions in an XCM message to the Relay Chain.
5. The proposal needs to be approved by the Council, and the community will have the final decision via referenda queue.

Runtime Upgrade for Collectives Parachain To v9420

# Context
Over the past few months, there have been numerous discussions surrounding treasury spending, particularly concerning the return on investment (ROI) and the value generated from these expenditures. We recognize that these metrics can sometimes be subjective. However, we have identified a specific treasury allocation that was granted, marked as lost, and subsequently re-awarded by the Polkadot Council. 

# Initial Treasury Request
For clarity, this discussion is not related to the content of the proposal or the team receiving DOT but is solely focused on the funds marked as ["lost”](https://polkadot.polkassembly.io/motion/152#d5254fb0-f5b5-48c3-a045-2c0e1b88da5a).

In February 2022, the Supercolony team requested 6,011 DOT ($128,000) to host an online event dedicated to Polkadot smart contracts called the "WASM Conference." You can find the Council Motion and treasury proposal [here](https://polkadot.polkassembly.io/motion/152).

It is worth noting that the majority of the Supercolony team are from Ukraine, and in March 2022, the Russian invasion of Ukraine took place. Understandably, the Supercolony team had to leave their home country.

This situation led to treasury proposal 96, which can be viewed [here](https://polkadot.subsquare.io/treasury/proposal/96). The team stated that they lost access to the funds while leaving Ukraine. They then established a new account identity and were awarded an additional 6,011 DOT to host the WASM Conference.

# Current Situation
An account containing approximately 6,000 DOT, awarded by the treasury and marked as "lost," now exists. You can see the account [here](https://polkadot.subscan.io/account/5HTb4Sr2kLAhhELhqGTsgvMb2xE1ByaSk4xbY8rwLF8XRuau?tab=transfer).

The Polkadot Council, and by extension our ecosystem's treasury, has paid twice for the same project (WASM Conference).

The team was re-awarded the necessary amount due to the political situation in Ukraine. The funds were allocated specifically for completing tasks outlined in their proposal and were granted twice.

ChaosDAO strongly believes that it is inappropriate to allow these DOTs to remain in this account as the team were reissued the original allocation of tokens subsequent to the first payment being lost.

Due to the factors above, we are proposing the following extrinsic be initiated:

* balances.ForceTransfer

This extrinsic will transfer 6,011 DOT from the lost Supercolony account to the Polkadot treasury.

We would like to remind the community that each referendum is unique and discrete in its scope, and every individual referendum should be evaluated on its own merits prior to voting. There should not be any precedent set by approving the aforementioned extrinsic. This should never be used as a basis for approving future uses of the balances.ForceTransfer extrinsic haphazardly. 

Ultimately, we believe that the fate of these lost funds should be decided upon by the DOT token holder DAO, as they belong to the treasury. Whether the outcome of the decision is AYE or NAY, we believe that it is of the utmost importance that this decision be decided by the collective token holders, and not retroactively by the council with no community input.

To reiterate, this discussion is not about the Supercolony team or any specific individual; it is solely focused on addressing accounts claimed to be "lost" that have received treasury rewards.



- There was a request for 6,011 DOT ($128,000) to host an online event called the "WASM Conference."
- The Supercolony team lost access to the funds while leaving Ukraine due to the Russian invasion of Ukraine.
- The team established a new account identity and was awarded an additional 6,011 DOT to host the WASM Conference.
- The Polkadot Council paid twice for the same project (WASM Conference).
- ChaosDAO is proposing to transfer 6,011 DOT from the lost Supercolony account to the Polkadot treasury.

Returning Supercolony lost funds back to the Treasury

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`


Here is a summary of the SubSquare post content:

- Three more parachains have requested an HRMP channel opening with Statemint.
- This proposal aims to accept and open return channels for each of the parachains.
- The proposal includes a `forceTransfer` of 20 DOT from the Treasury to Statemint sovereign account.
- The proposal also includes a `forceOpenhrmpchannel` from Statemint (1,000) to each ParaID.
- The ParaIDs for each parachain requesting the channels are BitGreen (ParaID 2,048), SubSocial (ParaID 2,101), and Manta Network (ParaID 2,104).
- The encoded call and proposal hash are also provided.

Three New HRMP Channels batch On Polkadot

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.

- A proposal has been made to add a Bridge Hub (BH) parachain to Polkadot.
- The BH will act as a gateway between Polkadot and other networks like Kusama and Ethereum.
- The BH will primarily act as a message routing system within the network and between others.
- 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.
- Once operational, a Polkadot<>Kusama bridge will allow more interaction between the networks.

Polkadot Bridge Hub Genesis

**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))

- Polkadot Council proposed a solution to fix an issue with a recently executed referendum.
- The issue was caused by a Substrate bug that allowed an incorrect transaction to overwrite the header of a parachain.
- The network runtime is correct, but the parachain cannot produce blocks due to the incorrect header.
- The proposed solution is to re-execute one of the extrinsics from the previous proposal to reset the parachain's head.
- The preimage containing the hash and extrinsic details is provided as proof of authenticity.

Fix incorrectly enacted referendum caused by a Substrate bug

To help make validating on Polkadot more accessible the following proposal aims to increase the maximum number of active validators per era from 297 to 500.

Currently validators require having at least ~1.663.500 DOT in nominations in order to have a chance at becoming an active validator. This has created a challenge for independent decentralized validators to get into the active set, even when getting support from the thousand validator programme. Increasing the maximum number of active validators per set should help make validating on Polkadot more open to individuals, and lower the nomination target barrier.

![](https://i.imgur.com/ymepSVw.png)
![](https://i.imgur.com/Kula6ci.png)

preimage hash: 0x8a9858782be312ee01e3c12adcbda468f8b8dc46a1e5f5cb029e0ce231ebd705
Encoded call: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x0709d107

- Polkadot is a platform where people can validate transactions.
- Currently, validators need a lot of DOT to become an active validator.
- This makes it hard for some people to become validators.
- A proposal has been made to increase the maximum number of active validators per era from 297 to 500.
- This should make it easier for more people to become validators.

Increase maximum active validator count to 500

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.**

- Watr team wants to reset their blockchain to seedling state.
- They cannot perform the reset because the tokens generated in the genesis block are locked and unusable.
- The network is currently locked and cannot be used without intervention from relay chain governance.
- The reset will not affect other applications or Parachains.
- The team has submitted a proposal to Polkadot governance with proof of authenticity and a pre-image.

Reset Watr Parachain

****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.

****Remedy****

After thorough investigation and collaboration with the Parity development team, we've identified an 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.

Extrinsics called in this proposal:
- batchAll()
    - paras::forceSetCurrentCode(2104, corrected.wasm)
    - registrar::setCurrentHead(2104, corrected.state)

- A team tried to register their parathread on Polkadot but faced a problem when the chain didn't produce blocks.
- The problem was caused by incompatible files during the registration process.
- The team worked with the Parity development team to find a solution.
- The solution involves correcting the incompatible files with the help of Polkadot governance.
- The correction will not cause any loss of state and will allow the parachain to start producing blocks.

Fix genesis registration for Manta Parachain

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!

1. The proposal suggests increasing the minimum number of tokens required to create a nomination pool from 200 DOT to 500 DOT.
2. It also suggests increasing the bond size required to become a direct nominator from 100 DOT to 250 DOT.
3. The proposal aims to enable fast unstake on Polkadot, which has been successfully tested in Kusama.
4. The number of validator candidates is proposed to be increased from 1200 to 1500 in anticipation of an increase in the active set of validators.
5. The maximum count of pools is proposed to be doubled from 128 to 256 due to the successful launch of Pools so far on Polkadot. 

Please note that this proposal needs to be approved by the Council and then voted on by the community before it can be implemented.

Adjusting Nomination Configuration

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)


- A motion has been proposed to approve the Wasm Smart Contracts Bounty.
- The goal is to encourage and promote the adoption and development of WebAssembly smart contracts on Polkadot parachains.
- The proposal includes creating audited Ink!/Ask! smart contract showcases, an incubation program, and a React Hooks library called “UseInk”.
- The proposal has been submitted as an external motion and will be up for community vote via Referendum for the final decision.
- For more information on the budget, roadmap, and scope of work of the bounty, please visit the bounty's contextual information.

Approval of Wasm Smart Contracts Bounty - bounty 19

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`

- Manta Network encountered a problem when their parachain was upgraded to a parachain as the genesis collators failed to produce blocks on the new chain.
- The reason for this was due to incompatible genesis WASM and state files.
- Manta Network has identified a solution to the issue and has requested the technical committee to fast-track the proposal to register the correct genesis state and code on Polkadot.
- This will allow their collators to begin producing blocks and launch the network.
- The proposal will not have any impact or loss of state since the chain has never produced any blocks.

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).


- The proposal is about scheduling auctions on Polkadot in 2023.
- The purpose is to make sure all auctions are scheduled properly throughout the year.
- There will be 18 auctions in total, with two actions in LP12 and LP13 each, followed by seven auctions per LP14 and LP15.
- The auctions will allow new parachains to join and existing ones to renew their slots.
- You can find the full schedule in the calendar provided in the link.

Polkadot Auction Schedule 2023

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!

Here is a summary of the SubSquare post content:

- Five more parachains have requested an HRMP channel opening with Statemint.
- The motion accepts them all and opens return channels.
- The ParaIDs for each parachain requesting the channels and proposals requesting this by the parachain teams are mentioned.
- An encoded call can be found in the post.
- The proposal requires Root origin, and Council will vote first on this external motion, and the community will make the final decision in the referenda queue.

Democracy Referenda