Hello everyone,

There is [demand](https://github.com/paritytech/substrate/issues/13165) for a testing framework that simulate transactions as it would happen on-chain, this can give valuable insight before making any major change to the runtime, sc-simnode does just that and more. Developed and maintained by Polytope Labs, a blockchain research and development lab.

We are seeking financing for the continuous development and improvement of sc-simnode.

You can find all the details of the proposal here: [https://docs.google.com/document/d/1x8lFHv1LZTr0y_Ifn8YzxirNftabaH0dWzzt9zSv6ik/edit#heading=h.tcq61mlmv7q4](https://docs.google.com/document/d/1x8lFHv1LZTr0y_Ifn8YzxirNftabaH0dWzzt9zSv6ik/edit#heading=h.tcq61mlmv7q4)

Thank you for reading

Jesse Chejieh

proposalId

Treasury proposal: sc-simnode continuous development and improvement financing

Hi everyone, Daniel of Anagolay is here. 

We believe monetizing and supporting creative work should be simpler, work across platforms, and be equally accessible to everyone. And we can make it happen with the web3 infrastructure developed on top of an excellent Substrate framework while adding value to the Polkadot ecosystem. 

Throughout 2022 and early 2023, the Anagolay team has been building the foundation to make our vision possible. 

Including, most recently: 

- [public identity Verification](https://anagolay.dev/blog/multi-token-community-contributions-for-verified-creators/milestone-1/) and [Tipping](https://github.com/w3f/Grant-Milestone-Delivery/pull/708) Pallets delivered under the [W3F grant](https://github.com/w3f/Grants-Program/blob/master/applications/anagolay-project-idiyanale-multi-token-community-contributions-for-verified-creators.md)
- [verification strategy and UI](https://bafybeiai2abe5y2nbgydjopuxhg6sdicim22gu4zgkpmcvu7apurpdlguq.ipfs.anagolay.network/verify-your-domain/) for web-domains verifications
- [Anagolay browser extension](https://anagolay.dev/blog/chrome_extension/installation-and-step-by-step-tutorial/), for sending tips to verified web domains.

For more details on what we accomplished last year, feel free to check [this post](https://anagolay.dev/blog/2022-retrospective/).

# Current Proposal Scope & Objectives

Our goal is to empower and support ***independent content creators*** and ***open-source developers***. 

With Anagolay, any verified online identity, like a web (sub)domain, a social media account (Twitter, YouTube, GitHub, etc.), or any Mastodon federated identity, can be used to send and receive funds: as community contributions to support a *verified creator* or their particular project (a repository or even a specific post).

We’ll start with bringing tip-as-you-go functionality to the ecosystem, making supporting quality work much easier: both from a personal account or by suggesting a tip from the Treasury. By doing so, we are creating additional incentives to contribute to the Polkadot community growth: for the existing members and for all the creators & builders in the digital space. 

From the get-go, in the current implementation, the tips can be sent in IDI (our native token). Eventually, our goal is to enable tips & recurring contributions in any DotSama token, scale Anagolay solution, and streamline creative workflow from publishing to monetization for all independent creators.

## Value

The value of Anagolay's solution is three-fold:

- Firstly, it provides content creators and open-source contributors with additional monetization tools.
- Secondly, it creates an additional incentive for the communities within Polkadot and Kusama ecosystems to make and encourage contributions. Tips from the community become a more accessible way to show appreciation for someone's work and can even serve as an alternative to treasury spending.
- Lastly, by bringing new users into the ecosystem, the solution enhances the ecosystem's overall value.

The range of communities benefitting from Anagolay will gradually expand as we develop and implement new features: 

![Anagolay_audience_map.png](https://ipfs.anagolay.network/ipfs/bafybeigsabemad2cctftxteqhogi44blnaxjyztemd7m376qu7xmnya6dy?anagolay_audience_map.png)

Initially, we aim to put community support & incentivization functionality to the test while adding value within the context of the Polkadot and Kusama ecosystem. This will allow us to collect valuable feedback and prepare for scaling: to onboard wider creative audiences and become their gateway to the ecosystem.

Please see the [FULL PROPOSAL HERE](https://kelp.notion.site/Anagolay-community-contributions-for-verified-creators-892fef98694b401c87ee2cb72bc885e7) for more details.

Anagolay proposal: enabling community contributions for verified creators

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

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

On behalf of the Polkadot Blockchain Academy team I am posting a bounty proposal as outlined in the document shared below;

[https://docs.google.com/document/d/1N97IHOtnRG7Djt27rDdi7kjTUIUwzjVvQxQmseLQm_E/edit?usp=sharing](https://docs.google.com/document/d/1N97IHOtnRG7Djt27rDdi7kjTUIUwzjVvQxQmseLQm_E/edit?usp=sharing)

Some context; up until this point the treasury has funded various educational programs aimed at speeding the adoption of our technology, however, funding has been directed at creating and hosting the programs and has left participants to cover their own costs of attendance/participation. This limits the ability of some talented individuals who happen to live in socio-economically disadvantaged circumstances to participate in such events, which in turn stifles creation and adoption of the Polkadot ecosystem. 

Bounty Proposal: Polkadot Education Bounty

[Here](https://polkadot.polkassembly.io/post/1491) is the previous community discussion on Polkassembly. 

### TLDR;
The purpose of this bounty is to nurture and develop WebAssembly smart contracts on parachains. As Gavin mentioned in this [CoinDesk article](https://www.coindesk.com/tech/2021/05/25/polkadots-gavin-wood-webassembly-is-the-future-of-smart-contracts-but-legacy-evm-is-right-now/), WebAssembly is the future of smart contracts. However, even in the Polkadot ecosystem, EVM smart contract is the go-to-market solution now simply because lack of ecosystem toolings and dApps new developers can refer to. To bootstrap the Wasm dApps in the ecosystem, we will fund canary dApps and toolings through this bounty.

### Context of This Bounty
Please see [this post](https://forum.polkadot.network/t/we-need-to-make-ink-showcase-projects/592) first. Currently, based on the data, smart contract Parachains are leading the Polkadot ecosystem in terms of market adoption. More projects are deploying dApps on Polkadot Parachains than making Parachains today and this trend will likely continue due to the high resource requirement to deploy a chain. The core problem is that the Polkadot ecosystem only supports EVM at the time of writing this and we are reproducing something which other L1s/L2s can do. One of Polkadot’s main differentiators and default environments is Wasm. In this bounty, we would like to push Wasm smart contracts adoption. The scope is as follows:

- Create easily accessible and audited ink!/ask! smart contract showcases
- Create ink!ubator - an incubation program to support community projects built with ink! and parachains that want to expose select APIs through contracts-pallet “chain extensions”. We will also help facilitate a smart contract auditing market.
- Develop a React hooks library “useInk” - the missing front-end library for Dapps on Polkadot.

### Bounty Proposal
[Here](https://docs.google.com/document/d/1y2QECPsXQktVGZIat_yNKTlodviTecMZ6IbiLNQ4NLM/edit?usp=sharing) is the full bounty proposal.

### Curators Candidates
**Sam Ruberti from Parity Technologies (Address: 13zqqP37p8HjLuWr7sha9GcAcYiiDgjqoNS3YbSELtgvaAfb):**  Sam Ruberti is a Senior Rust Developer with ink! and has over twelve years of experience delivering full-stack products for companies including Bloomberg, Peloton, and Clear, and five years of experience building full-stack Dapps in production environments. He has built microservices, DeFi platforms, NFTs, and contributed to open-source libraries for Ethereum.

**Sota Watanabe Astar Foundation (Address: 13VyvkXX3dYyeT7oAmaipZYNHzFJXofC5V8eqMuzd1isXY84):** Sota Watanabe is the founder of Astar Network. He joined the web3 space in 2015 and started developing Astar Network in 2019. Apart from his achievements, he is a director of the Japan Blockchain Association and used to be a blockchain researcher at the University of Tokyo and a task force member of Trusted Web led by the Japanese government. In addition to that, he was chosen for Forbes 30 Under 30 Asia in the IT division and Forbes 30 Under 30 Japan.

**Hernando Castano from Parity Technologies (Address: 15FjwNSxHhaJeknJjbydSo561ti1ea8sf3Y1fA263emujzxW):** Hernando is a Core Developer at Parity Technologies. Hernando joined the blockchain space in 2017, initially curious about the world of smart contracts on Ethereum. In 2019, Hernando joined Parity Technologies to work on the Parity Ethereum client, and has since transitioned to the team working on the ink! programming language.

**Markian Ivanichok 727 Ventures (address: 16FVZ2qVefqbr2zcEGVojEQBgx3nb8GqQCdjKiaq2nSs33T8):** Founder & CEO at 727.ventures, Brushfam & Dedali Metaverse. Web3 entrepreneur, Software Engineer. Brushfam onboards businesses to Polkadot WASM. Projects: Openbrush(Openzeppelin of WASM ink!), Typechain for ink!, sol2ink (transpiler from solidity to ink!), and substrate/ink! contribution itself. Also, WASM conference, was the first web3 WASM conference and gathered ~1000 participants.

**Hang Yin from Phala Network (address: 12BZFbrNksTKwHtaBojnVtoN8BoXKmBFzT3xDnHh7P9t2Cg5):** Co-founder and CTO at Phala Network. 5 years of Web3 core development and entrepreneur experience. Author of Phala Network Technical Whitepaper. Lead the team to build an off-chain computing protocol based on ink! and Substrate with 30k online servers. Ex-Googler on Machine Learning before joining Web3.

**Michał Świętek , Development Lead at Aleph Zero (Address: 5H6AVPSNv8GjEFiDKqhtCd6U494vGMm3r5vkzr5614sbfQnx0) :** For a couple of years, Michał has been fully devoted to the Aleph Zero project. From co-designing novel consensus mechanisms, and writing the first lines of code in core repositories, to the high-level architecture of Aleph Zero node implementation.

Wasm Smart Contracts Bounty

Anti-Scam projects rewards pool. Minimum rewards 5% 

Added

Blockchain Week - Rome - May - Marco

Meetup rewards - Polkadot Meetup in Zagreb - February 16 2023 - Patrik K.

Meetup rewards - 3 Polkadot Meetups in Ljubljana - October - February 2023 - Patrik K.

Proponent: Pinknode

Date: 14/03/2023

Amount in USD: $20,093.46 

Amount in DOT:  3447.74 DOT 

DOT Rate: $5.828 (using EMA7 as of 14/03/2023)

DOT Account: 14K2YrPm8TTo8aNMqp7FJjbpysi7vm1j7QjKg86q6W6wVzPr

Proposal Summary: Costs for running secure, reliable, and scalable public infrastructure for Polkadot, Statemint, and Westend

Project Summary

Pinknode is a node-as-a-service platform focused on providing shared API endpoint and node operation services catering exclusively to the Polkadot ecosystem. We launched our MVP in June 2021 and have been providing free RPC services to the Polkadot ecosystem’s participants since Q3 2021. Our mission is to aid the Polkadot protocol in achieving its vision of a multi-chain future by providing easy-to-use, reliable, and scalable infrastructure services which remove an entire layer of complexities for developers to start building on Polkadot/Substrate.

Ecosystem participants can access our free API service by creating their own API Key on Pinknode Portal or using our public endpoints (listed at https://polkadot.js.org/apps). In a bid to reduce barriers to entry and attract more developers to the ecosystem, our premium plan, which includes archival data and higher rate limits, is also free for all builders and participants of Polkadot to utilize. We are not charging our users anything at this moment.

https://public-rpc.pinknode.io/polkadot

wss://public-rpc.pinknode.io/polkadot

https://public-rpc.pinknode.io/statemint

wss://public-rpc.pinknode.io/statemint

https://public-rpc.pinknode.io/westend

wss://public-rpc.pinknode.io/westend

Service Details

From 1 October 2022 to 31 December 2022,

Pinknode’s Polkadot RPC nodes have served an average of 7,259,280 requests per day, for a cumulative total of 675,113,094 requests for the quarter.

Pinknode’s Statemint RPC nodes have served an average of 213,150 requests per day, for a cumulative total of 19,609,835 requests for the quarter.

Pinknode’s Westend RPC nodes have served an average of 229,823 requests per day, for a cumulative total of 21,373,571 requests for the quarter.

Enhancements during Q4 2022:

-Added “Team API calls used’ on main dashboard for effective summary

-Moved request log storage to AWS S3 for faster UX

-Added toggle switch for live request viewer, to be initiated by users as opposed to default

-Upgrades to our proxy for more accurate logging

Pinknode achieved service reliability of 99.88% for Q4 2022 with one major downtime incident on 21 November 2022.

Our status page is publicly maintained.

Our full report including raw data and graphs can be viewed [here.](https://docs.google.com/document/d/18m7e6IhuKjS8eGG7QYJSGBTjEx-vxgTuCYz_p5xi7VA/edit?usp=sharing)