This is a proposal whose proposer address (14DE8GdKnNvgoXCLFq62ZjNz2zsGqnxXBsRMwNpiPip2JSFJ) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Untitled Post

canceling, will recreate on OpenGov

- A proposal was made to create a special communication channel between two networks called Statemint and Composable.
- This channel will help both networks share stablecoins, which are a type of money.
- Composable’s special ID number is 2019, which is used for opening this channel.
- The proposal includes sending 20 DOT (a type of currency) from the Treasury to Statemint.
- It also includes opening the communication channel from Composable to Statemint and from Statemint to Composable.

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.

HRMP Channel Opening: Composable <> Statemint

- There has been a lot of talk about how the treasury spends money and what is gained from it.
- A team called Supercolony asked for 6,011 DOT (about $128,000) to host a conference called the "WASM Conference."
- Most of the Supercolony team is from Ukraine and had to leave because of the Russian invasion in March 2022.
- They lost access to their original funds but were given the same amount again to host the conference.
- Now, there is an account with 6,000 DOT that is marked as "lost," and the Polkadot Council has paid for the same conference twice.
- ChaosDAO suggests transferring the "lost" 6,011 DOT back to the treasury because the team received funds twice.
- They believe it’s important for the community of DOT token holders to decide what happens to these funds, not just the council.

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



Returning Supercolony lost funds back to the Treasury

This proposal was enacted via https://polkadot.polkassembly.io/referendum/113 This is no longer needed, please reject

[Please Reject] Superseded by referendum 113

- A proposal is being submitted to the Polkadot community for voting on helping earthquake victims in Turkey.
- On February 6, 2023, two big earthquakes in Turkey caused over 50,000 deaths and made 1.5 million people homeless.
- The proposal asks for about $1 million in cryptocurrency to build a neighborhood of shipping container homes for those affected.
- NeedsMap.coop, the organization receiving the funds, is working to create housing and provide care for people impacted by the disaster.
- The neighborhood will consist of about 100 containers and can help around 400 to 450 people.
- The plan includes support for 24 months to help maintain the community.
- If approved, this will be a way for the Polkadot community to support recovery and create a model for future disaster responses.

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.

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

### Summary

1. **Registration**: A parathread was registered on the Polkadot relaychain and upgraded to a parachain.
2. **Issue**: Genesis collators failed to produce blocks due to incompatible genesis WASM and state files.
3. **Consequence**: The parachain was stuck at genesis.
4. **Investigation**: Collaborated with Parity development team to identify the problem.
5. **Solution**: Proposed to correct the incompatible WASM and state files with Polkadot governance assistance.
6. **Impact**: No state loss since no blocks were produced.
7. **Extrinsics**: 
   - `batchAll()`
   - `paras::forceSetCurrentCode(2104, corrected.wasm)`
   - `registrar::setCurrentHead(2104, corrected.state)`
8. **Outcome**: Expected to efficiently resolve the issue and get the parachain running.

Fix genesis registration for Manta Parachain

- A Polkadot user accidentally sent 254.1591507553 DOT to the wrong address.
- The DOT were initially sent to a null address but were later observed to be transferred to another address.
- The user requested community help to return the mistakenly sent DOT.
- The DOT were later found to be on the Acala network.
- The user created a new proposal on the Acala network to address the issue.
- The original proposal was canceled due to incorrect token amount details.

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

Unbrick Zeitgeist Parachain

Polkadot is a blockchain network that wants to make it easier for more people to become validators. Validators are important because they help to confirm transactions and keep the network running smoothly. Right now, there can only be 297 active validators at a time, and they need to have a lot of DOT (the network's currency) to have a chance at being chosen. This makes it hard for new, independent validators to join.

The proposal suggests increasing the number of active validators to 500, which would make it easier for more people to become validators and lower the amount of DOT needed. This would help make Polkadot more open and accessible to individuals. There are also some pictures and links provided to help explain the proposal in more detail.

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

Increase maximum active validator count to 500

### Bittensor Project Proposal Summary

- **Issue**: Bittensor used the wrong para ID (2096) in its genesis WASM during Auction #36.
- **Problem**: The chain cannot produce blocks with the incorrect para ID.
- **Solution**: Propose to update the genesis head from 2096 to 2097 using `forceSetCurrentHead`.
- **Proposal Hash**: 0x457da305f86a09bad84a8c557bb89628b9b39707819df0b12458d84a255d6354
- **Status**: Preimage submitted.

Update genesis state WASM to 2097 

Launch PSC Parachain - public proposal #21

Invalid

This is a proposal whose proposer address (14DXNLsWfpf1RZ3eZSemHaitFh7WM6ZwswJUVLxqQhRvc2ui) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

On chain council motion

- The Kapex Parachain is part of Polkadot and has been making blocks but can't upgrade due to a problem.
- A security check found bad code in the system that prevents fixing a fee recording issue.
- The problem was discovered after winning a special spot on Polkadot.
- Efforts to fix the issue without official approval failed, so new solutions were needed.
- They successfully tested a fix using special code on different networks.
- The Kapex team is now preparing for production and needs community support to fix the funding problem.
- They have taken steps for updates and proposals to resolve the issue.

### The Kapex Parachain has been producing blocks since winning and parachain slot on Polkadot, but cannot be upgraded due to an error.

> [SRLabs](https://www.srlabs.de/) conducted a security audit on the Totem Kapex pallets and identified an issue with some illegal code that impacted the Transaction Payment pallet adapted by the team. Unfortunately the team won a slot on Polkadot before the audit could have been conducted and so the issue was not discovered until the audit completed. 

## Background
The standard Transaction Payment Pallet had been forked and adapted to record transaction fees into the accounting engine of the KAPEX Parachain. the original version of this code was changed by a new team developer to use a function reserved for off-chain workers instead of the original code but as the code compiled it was not spotted until the audit. It was thought that an upgrade would fix the issue.

## Upgrade failure
As the Transaction Payment Pallet is called during an upgrade to reserve funds (even though the actual upgrade is free of charge), the illegal code was unfortunately also called to record this reservation of fees causing an error, preventing the upgrade from taking place and therefore not allowing the parachain to be fixed.

**_In addition this also meant that the XCM security vulnerability discovered in late September also cannot be fixed either at this point._**

All attempts were made to try to fix this issue without having to go to the Council and Referendum process, with help provided with gratitude from the Kilt.io team and Parity team Bastian, Alejandro and Santiago.

The new [Manual Parachain Lock](https://github.com/paritytech/polkadot/pull/5451) cannot fix our chain because [the unlocking mechanism does not allow for centrally controlled chains to unlock the parachain from the relaychain side](https://github.com/paritytech/polkadot/issues/6196). 

The fix that worked was to apply a validation code substitution using `paras.forceSetCurrentCode()` executed on the relaychain once the parachain `chain spec` had been updated accordingly and applied to the collators in our test networks. This is the subject of this proposal.

## Testing the fix

- [X] Tested the fix (`paras.forceSetCurrentCode()`) on our [Relaychain development network](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frelaychain.totem.live#/parachains) connected to the Lego development parachain.

- [X] Upgraded the Lego Parachain to version [`v1.2.0`](https://github.com/totem-tech/totem-parachains/tree/kapex-v1.2.0-audit-fix) 

- [X] Upgrade Lego to [`v1.3.0`](https://github.com/totem-tech/totem-parachains/tree/kapex-v1.3.0-polkadot-v0.9.28-alignment)

- [X] Tested the fix on the [Rococo chain](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/accounts) connected to our [Stagex](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fs-ui.kapex.network#/explorer) production staging parachain with the help of Parity devs.

- [X] Upgraded the Stagex Parachain to version `v1.2.0`

- [X] Then upgrade Stagex to `v1.3.0`

- [X] Upgraded [docker Stagex nodes](https://hub.docker.com/layers/totemlive/totem-parachain-collator/staging/images/sha256-bc6fe0e61a347e2f64150aa2fd739bb5e0b12b0702c1b8a4f7da262b39328897?context=explore) to run version `v1.3.0`

## Production preparation
- [X] Decide the block number for the transition in Kapex [chainspec](https://github.com/totem-tech/totem-parachains/blob/main/res/kapex/kapex-parachain-raw.json) - Block number `400000`

- [X] Apply the [new production validation code](https://github.com/totem-tech/totem-parachains/blob/main/res/parachain-code-substitution-wasm.wasm) to Kapex `chainspec`

- [X] Tag the code repo from the main branch in the repo as [`kapex-v1.1.0-codeSub`](https://github.com/totem-tech/totem-parachains/releases/tag/kapex-v1.1.0-codeSub)

- [X] Build a new [docker image](https://hub.docker.com/layers/totemlive/totem-parachain-collator/production/images/sha256-21857f3efd8496a57bd41646d728086173b622ac085f5204f48a015dd9e02310?context=explore) with the new Kapex `chainspec`.

- [X] Restart the Kapex Collators with the new `chainspec`.

- [X] Transfer funds to request code Substitution on Polkadot

- [X] Create Preimage hash on Polkadot `0x1ca2532cbb04d421f1b216f354354524feffd8540e7ca74b0938e58d2cdfc923` 

- [X] Create a proposal

- [X] Create Preimage on Polkadot

We are unfortunately unable to distribute our funds from the Crowdloan until this issue is fixed, so we look forward to the community supporting this proposal through the referendum as soon as possible. Thanks in advance.

The Totem Kapex Team

Kapex Parachain - Validation Code Substitution to fix broken upgrade mechanism and permit XCM Security Vulnerability upgrade.

### Summary of Proposal

- **Token Registration**: BNC native token (Bifrost on Kusama) will be registered as xcBNC on Moonriver.
- **Details**:
  - Multilocation: `{ "parents": 1, "interior": {"X2": [ { "Parachain": 2001 }, { "GeneralKey": "0x0001" }]}}`
  - Decimals: 12
  - Name: xcBNC
  - Symbol: xcBNC
- **Fee**: Initial fee is set at 35230000000000 units per second, based on the KSM/BNC price ratio.
- **Proposal**: Proposal #15 with hash `0x389689c01cc484fa3860ff93a138f0f283611243e1c6b80d3c49f25b129999fb`.
- **Technical Steps**:
  - Register the asset using `assetManager.registerAsset`.
  - Set the fee using `assetManager.setAssetUnitsPerSecond`.
  - Store a revert code using `system.setStorage` for smart contract interaction.
- **Asset ID**: xcBNC will have the asset ID `42109858202732255156900361585267092733`.
- **XC-20 Address**: The XC-20 address will be `0xFffFFFfF1FAE104Dc4C134306bCA8e2E1990aCfd`.

This is a proposal whose proposer address (16hu63GujrmJPW9ZbGibj6gFnLFe4yW8A7gDgADmRTmpaUkf) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Register Bifrost (on Kusama) native token as xcBNC on Moonriver

This is a proposal whose proposer address (12BJTP99gUerdvBhPobiTvrWwRaj1i5eFHN9qx51JWgrBtmv) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Redspot v0.1, applied by Patract Labs

Unlock manager account

- Jonathan Kleiman is a lawyer in Toronto with 10 years of experience.
- He is a candidate to become a Polkadot ambassador.
- Jonathan can verify identities using two photo IDs and a video call.
- He plans to charge 3 DOT for this verification service and offers it for free to voters of his proposal.
- He aims to make identity confirmations trustworthy, as they will have legal backing.
- Non-English IDs can be verified with help from a local lawyer.
- Additional lawyers can help if there are too many verifications to handle.

Hello. My name is Jonathan Kleiman. I am a Polkadot ambassador candidate, and I have been a lawyer in Toronto for 10 years. I am licensed by the Law Society of Ontario. You can find my website at www.jkleiman.com, and you can peruse my google reviews [here](https://g.page/kleimanlaw?share). 

As a lawyer, I am licensed to verify documents as a notary. My intention is to verify legal name identities on-chain using this same process. Specifically, I will require two pieces of photo ID, and a short video call to confirm that the person seeking identification is indeed the person on the ID's provided. 

The video call (no, a screenshot - see edit) will be recorded for verification records, but will not be shared without requestor's consent or a court order, if for some reason the requestor needs to prove that their identity was properly verified.

As a lawyer, the risk to me of publicly confirming somebody's identity incorrectly is very serious, as the public would be assured of the reliability of such verification and would be able to rely upon it as if it were notarized by me. For this reason, verifications performed by me will be completely trustworthy, without question.

I plan to charge 5 DOT (3 DOT, see edit) for the verification services. Any voters for this proposal when it reaches referendum will receive their verification for free by fee refund once the proposal is approved (unless this is disallowed)

Please feel free to send any questions or suggestions to me at [Jonathan@JKleiman.com](mailto:jonathan@jkleiman.com)

[Proof of License](https://lso.ca/public-resources/finding-a-lawyer-or-paralegal/directory-search/members/lawyer/049/jonathan-louis-kleiman)

EDITS: 

1) I am lowering the price to 3 DOT, given the recent and anticipated price appreciation

2) Pursuant to comments, I suggest that no video be recorded, but that a screenshot of the video be taken and held on offline storage.

3) I will offer to verify email, twitter, and element name as well.

4) Non-english identification can be done, but must involve a lawyer licensed to practice in the jurisdiction that the account holder resides, who can certify the identity for the Registrar.

5) In the event that there are too many for one person to handle, additional lawyers can be involved to verify identities, but the main registrar would still be responsible to ensure the process is secure and reliable. This practice is acceptable to my law society as well - I am allowed to rely on the certification of a person's identity as long as it is done by a lawyer in their jurisdiction, and I am able to confirm the lawyer's identity and their license to practice law, and receive ID of the account holder.

6) Thank you to those who have participated in the discussion, and those who have foregone staking rewards by seconding my proposal.


Lawyer to Verify Legal Names

This is a proposal whose proposer address (12jjdP15mZnY3pTNPwa6pyGSAGnz9fyr9dmqbkzB7VhSMy6Y) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Increase active collator set size to 24

This is a proposal whose proposer address (12tbKWY62Vkh9S2jgXejrxu64B2Hd7KQoU2D6w6f9ZpSTjJP) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Increase active collator set size to 32

- The proposal aimed to increase the active collator set size to 16.
- It was linked to a runtime upgrade to Zeitgeist v0.3.6 (`spec_version 40`).
- The parachain-staking pallet changed function indices after the upgrade.
- Before the upgrade, the function selector for `setTotalSelected` was `0x6e06`.
- After the upgrade, `setBlocksPerRound` took `0x6e06`, and `setTotalSelected` became `0x6e04`.
- The proposal originally intended to invoke `setTotalSelected`.
- After the upgrade, it mistakenly invoked `setBlocksPerRound`.
- The proposal should be rejected due to this error.

This is a proposal whose proposer address (1hP1j6MT33vmiSUJBzFR5oyrowYZrGcj7kRV9exh7rFYi6A) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Increase active collator set to 16

This is a proposal whose proposer address (16SqCKhH9Ew2azrzpqJKq6pRB4yZuEgrdPUbExFsbJ4uMXea) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Increase active collator set size to 28

This is a proposal whose proposer address (15MrYzj6KsJAom1V3eTH4Wgsz86FLVE65dF7SEeNkPYSsSs7) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Democracy Public Proposals