**Sub.ID [Proposal #2](https://docs.google.com/document/d/1BgLXyCFbpcCKvv_JTBCwLR_btvFOJ0H8YArBYk5yZ_w/edit?usp=sharing)**: Alternative balances view, Account grouping, Transaction history, P&L analytics, Automated quality assurance.

Launched in 2021, the [Sub.ID](https://sub.id/) web dapp was initially designed to provide quick and convenient access to all your Substrate addresses, balances, NFTs, and other assets in one place. It was built with the Polkadot ecosystem in mind and tailored to benefit its most active members. Since then, Sub.ID has been connected to 40 Substrate chains, gained substantial traction, and got its own dedicated vision and roadmap.

In September 2022, our previous Kusama treasury [proposal for Batch One](https://docs.google.com/document/d/1RElvy5RYhnNInwnGsjibedGLI3EeBoqqazKk6Syv13M/view) was approved as [Motion #548](https://kusama.polkassembly.io/motion/548), and in February 2023 we successfully delivered the proposed features. Please refer to our [demo](https://youtu.be/FZkva4Awv4s) and [read the report](https://coda.io/@subsocial/subid-reports) to see how they look and function, or visit [Sub.ID](https://sub.id/) to try it live.

We are looking to secure funding from the Polkadot treasury for the following community-oriented features:

BATCH TWO

* **Alternative balances view**
    * UX: token-centric views (table/cards/chart), multi-account view.
    * Logic: consolidated token balances, support of multiple accounts.
* **Accounts grouping**
    * UX: list of Groups, Group management, Account page, Account management in a Group, default ‘Followers’ Group, default ‘Favorites’ Group.
    * Logic: Group entity, Group and Accounts relations, ‘Followers’ Group. members.
* **Transaction history**
    * UX: list of transactions, transaction type cards, filters section.
    * Logic: Subsquid integration.
* **P&L analytics**
    * UX: P&L dashboard, P&L charts (portfolio/tokens), multi-account aggregated view.
    * Logic: CoinGecko integration, balance changes over time.
* **Automated quality assurance**
    * Integration testing framework, balances testing, crowdloan testing, NFT testing, and real-time integration testing.

Please review the full proposal with detailed description of the costs at [https://docs.google.com/document/d/1BgLXyCFbpcCKvv_JTBCwLR_btvFOJ0H8YArBYk5yZ_w/edit?usp=sharing](https://docs.google.com/document/d/1BgLXyCFbpcCKvv_JTBCwLR_btvFOJ0H8YArBYk5yZ_w/edit?usp=sharing) 

We would love to get your feedback.

proposalId

Sub.ID Proposal #2: Tx history, Token-centric view, P&L analytics, and more

Our proposal is “Boosting Developer Adoption for Polkadot Ecosystem Projects” and we are sharing it before the official submission for community input and feedback.

We are Missing Link, an established brand in web3 recruiting in Europe, to provide these services. Missing Link has a track record of providing high-quality recruiting services to the blockchain industry, as you can see from the full proposal linked below.

As the Polkadot ecosystem continues to expand, it is critical that there are enough skilled developers to support the growth. **We propose to place a total of 15 Rust developers to different companies and projects within the Polkadot ecosystem through three milestones.** Companies who qualify and are in the Polkadot ecosystem can utilize the funds from this treasury proposal to receive recruitment services for Rust developers for their project.

In total, we are requesting three tranches of $120k USD for a total of $360k USD from the Polkadot treasury to fund this project, with each tranche being awarded before each milestone. We believe that this investment will have a significant impact on the Polkadot ecosystem, by ensuring that there are enough skilled developers to support the growth of the network.

Thank you for your consideration of this proposal and we have incorporated the community’s feedback before submitting this proposal on-chain.

[Here is the link to the full proposal](https://docs.google.com/document/d/1zON3bX38D1MXLjaIIdc0aioosxmbQ2IDlMSouM2TLHo) with all the relevant details, processes and qualifiers.

Treasury Proposal for Missing Link: Boosting Developer Adoption

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

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

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!

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.

Lease swap for Acala

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% 

Web3 Foundation - BarCamp - 30 November and 1 December 2022

Added

Web3 Foundation - Messari Mainnet - 22 September, 2022

Primavera Pro Madrid - PolkaHaus - May 2023

**Proponent:** 12wWLUd5qMzLFGqBsMnHLVFeTuYJwuo5ygMAxuSywrBX1XSF

**Date:** 2023.03.30

**Requested DOT:**  74,785 DOT ($495,000)

**Contact:** William Freudenberger (william@k-f.co)

**Discussion Post:** [https://polkadot.polkassembly.io/post/1754](https://polkadot.polkassembly.io/post/1754)

---

The [ongoing discussion](https://forum.polkadot.network/t/statemint-update-roadmap/1200/) about automated market makers (AMMs) in the Statemint roadmap is mainly focused on improving the user and custodian experience by allowing small atomic swaps natively and making Statemint a central hub for asset deposits. This addresses important pain points by enabling transaction fees to be paid in non-native tokens and facilitating interaction with the entire asset variety of the ecosystem without requiring to run custom nodes or infrastructure.

However, we believe that one aspect has been overlooked: the slow swaps of large volumes, which can be easily front-run or sandwiched. This is particularly relevant in the context of trades proposed through governance for use cases such as
1. Paying out treasury grants, bounties or even [salaries](https://github.com/paritytech/substrate/pull/13378) in less volatile currencies (ie. stablecoins).
2. Enabling parachains to build a DOT reserve which can be used to acquire a parachain lease, pay XCM fees, or [increase availability cores](https://forum.polkadot.network/t/parachain-scaling-by-parablock-splitting/341) during times of high demand (once supported).
3. Governance deciding to invest part of the treasury into a token to diversify their treasury

What we need is the opposite of what a traditional AMM provides: atomic swaps with immediate execution, even in relatively illiquid assets. A governance vote is unable to time the market and is highly predictable. Therefore, executing such a transaction as a market order on an AMM is problematic, as it will be guaranteed to be front-run. A better solution is to "dollar-cost-average" over a long period of time making it harder for price manipulation to affect the purchase.

At Centrifuge, we have researched distinct approaches of how to achieve hard-to-front-run slower transactions. In our opinion, the most elegant solution is [TWAMM (Time Weighted Automated Market Maker](https://www.paradigm.xyz/2021/07/twamm). We are of the firm conviction that the implementation of this model represents the most efficacious approach for executing token swaps in the context of slower and passive procedures, such as governance.

TWAMM (Time Weighted Automated Market Maker) eliminates front-running vulnerabilities of traditional AMMs when executing large orders, especially in the context of passive procedures, such as governance. The proposed solution will be executed as a seamless extension to [pallet-asset-conversion](https://forum.polkadot.network/t/statemint-e-swap-discussion), thereby enhancing its capabilities as an embedded AMM.

The deliverables of the proposal contain the TWAMM-pallet,  associated runtime APIs, associated research for further optimizing and extending the pallet, a security audit of the pallet and a frontend.

The full proposal can be found [here](https://centrifuge.hackmd.io/Q4AZOW2WRPq7Q0Ti3ee8Og?view).

**EDIT**
* Link discussion post

Treasury Proposal by Centrifuge: On-Chain Automated Treasury Management (with TWAMM)

Web3 Weekends Tashkent #1 WASM/Polkadot/Web3 https://twitter.com/Alex_PromoTeam/status/1632642736472858626?s=20

Web3 Weekends Workshop #2 WASM/Polkadot/Web3 https://twitter.com/Alex_PromoTeam/status/1638053451904045058?s=20

As discussed with the team, we would appreciate if the council could reject our 3 existing proposals ([#247](https://polkadot.polkassembly.io/treasury/247), [#248](https://polkadot.polkassembly.io/treasury/248), [#251](https://polkadot.polkassembly.io/treasury/251)) and reimburse their combined deposits by way of this tip.