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

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.

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

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

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

Invalid

Untitled - public proposal #17

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

Fix genesis registration for Manta Parachain

This is a kind request to reset Zeitgeist's Parachain genesis state and wasm. More information at [https://hackmd.io/PXotv7zMTSOphZFg4f99iQ](https://hackmd.io/PXotv7zMTSOphZFg4f99iQ).

Unbrick Zeitgeist Parachain

The Bittensor project participated in Auction #36, however it was unfortunately using the incorrect para ID in its genesis WASM (para ID 2096) due to previously obtaining para ID 2096. 

We have explored all solutions to this problem and it appears that there is no way to have the chain produce blocks when its lease begins unless we update the genesis head. Therefore, we've created this proposal to update the genesis head from 2096 to 2097 using forceSetCurrentHead.

Proposal hash: 0x457da305f86a09bad84a8c557bb89628b9b39707819df0b12458d84a255d6354
Preimage is submitted.

Update genesis state WASM to 2097 

Untitled - public proposal #19

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

Untitled - public proposal #16

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

Untitled - public proposal #14

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.
