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

**Motion 410** is now up for vote: an ambitious proposal aiming to implement a trustless Ethereum 2.0 light client as a Substrate Pallet, which will be compatible with all parachains in the ecosystem. Connecting Polkadot to Ethereum enables the interoperability between two of the largest and most established blockchain networks, allowing for the transfer of assets, data and applications across the two networks. The technical specifications for the Ethereum 2.0 Light Client Pallet are based on the  official Consensus Eth2 Light Client specs and encompass various aspects of the client, which can be reviewed on [the proposal’s contextual information](https://polkadot.polkassembly.io/motion/410): along with budget, team information and more. 
###
Please note that, given the allocation request, this proposal is submitted as an external motion: meaning if/after Council approves, the community will have the final decision in democracy module.
###
Treasury Proposal and Contextual Information: [https://polkadot.polkassembly.io/treasury/261](https://polkadot.polkassembly.io/treasury/261)

proposal

External Motion: Development of a trustless Ethereum 2.0 Light Client as a Substrate pallet

Term: 1 January 2023 - 31 March 2023

This Treasury Proposal is an extension of our current maintenance & support contract with the Polkadot Ecosystem. The extension of the maintenance & support contract covers term: 1 January 2023 until 31 March 2023.

* [Current report that account for maintenance & support contract activities](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2023Q1.md)

[Polkascan Foundation](https://polkascan.org) is a not-for-profit infrastructure service provider and maintainer of Polkadot ecosystem open source software, such as the Polkascan Explorer and Python libraries. The Python libraries were initially funded by Web3 Foundation grants, they have a generalized nature, suitable for adoption by any Python-based project in the broader Polkadot ecosystem. 

At the time of writing [213 Github repositories](https://github.com/polkascan/py-substrate-interface/network/dependents?package_id=UGFja2FnZS04OTc2NTczNTM%3D) are depending on our libraries.


Previous activity reports can be found here:

* [October 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202010.md)
* [November 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202011.md)
* [December 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202012.md)
* [January 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202101.md)
* [February 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202102.md)
* [March 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202103.md)
* [April 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202104.md)
* [May 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202105.md)
* [June 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202106.md)
* [July 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202107.md)
* [August 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202108.md)
* [September 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202109.md)
* [Quarter 4 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2021Q4.md)
* [Quarter 1 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q1.md)
* [Quarter 2 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q2.md)
* [Quarter 3 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q3.md)
* [Quarter 4 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q4.md)
* [Quarter 1 2023](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2023Q1.md)

Links and further details:

* [The Social Contract Mechanism](https://github.com/polkascan/social-contract/blob/master/README.md)
* [The Social Contract for Maintenance & Support of Python Libraries](https://github.com/polkascan/social-contract/blob/master/polkadot/social-contract-002.md)
* [Business Plan](https://polkascan.org/wp-content/uploads/2022/03/Business-Plan-Polkascan-Foundation-v20220218.1030.pdf)

We will be available to answer the Polkadot Council's questions.

Continuation of Maintenance & Support for Python Libraries

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

**Proponent:** 12uokSRn2hmEWPZuzHK1xqnFxRgyoApLtXRBd4jFan2x2T1P

**Date:** 13.05.2023

**Requested:** 7,654 DOT (i.e USD $41,402 calculated from the [7-day EMA price](https://polkadot.subscan.io/tools/price_converter?value=41402&type=time&from=USD&to=DOT&time=1683944268) of DOT)

**Short description:**

[Dot.alert()](https://dot-alert.gitbook.io/dot.alert/) is a knowledgebase that provides practical guidelines for managing assets safely across the Polkadot ecosystem. 

As part of its mission, Dot.alert() has previously established a social contract with the Polkadot Treasury to fund its quarterly operational costs:

- Motion 263: [Treasury proposal: Dot.alert() operational costs](https://polkadot.polkassembly.io/motion/263)  |  [Q4 2022 Milestones report](https://docs.google.com/document/d/1xdOWf7m7MC9oul54q-I8bWRZ2b6zZGam/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true)
- Motion 318: [ Treasury proposal: Dot.alert() operational costs - Q1 2023](https://polkadot.polkassembly.io/motion/318)  |  [Q1 2023 Milestones report](https://docs.google.com/document/d/1kMaSz59IVMfcfbu6BMml6eFfjpfs7K06/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true)

Dot.alert() is seeking funding for its Q2 & Q3 2023 operations, so that it can continue to make progress on the objectives laid out in its annual strategic plan.

You can find the discussion related to this proposal here: [https://polkadot.polkassembly.io/post/1743](https://polkadot.polkassembly.io/post/1743)

You can find the full details of the proposal (including milestones, tasks, and costs for the period April – September 2023) here: [Polkadot Maintenance Proposal Q2-Q3 2023 – Dot.alert()](https://docs.google.com/document/d/1hyqtzlnTYQb5oBFop76n_PIWmaYgvI3v/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true).



 Treasury proposal: Dot.alert() operational costs – Q2-Q3 2023

Hi everyone! I'm Cervera, creator of [Cryptonitas](https://www.youtube.com/channel/UCsP0zGvvzB4RGyDYHkDdmUA), and I've been creating educational video tutorials for the Polkadot and Kusama community since April 19, 2021. In addition to creating educational content, I have been contributing to the community in different ways: supporting the community by answering questions on the Telegram channels and YouTube; through participation in different events (both as a speaker and as a member of the organizational team); with the creation of events, such as the Decoded 2022 viewing party in Valencia; and the creation of a Nomination Pool on both Polkadot and Kusama, among other things.

This proposal intends to continue the content creation of the [previous proposal](https://kusama.polkassembly.io/treasury/213), which includes the production of 85+ pieces of content. The main objective of this proposal is to have an informed, educated and valuable community that knows how to make real and appropriate use of the network. For more information, I invite you to read the complete proposal [here](https://docs.google.com/document/d/1gdjk6TH4nl6OA0MJe93Ok4uw6NcVVh8RXFfg8Gam2CE/edit?usp=sharing).

You can read the original discussion post [here](https://polkadot.polkassembly.io/post/1745).

Polkadot education content production extension by Cryptonitas

**Short description: To create a comprehensive overview of the current state of all things data in the Polkadot ecosystem. Funding includes the research, a Github repo, and a Website.**

Hi everyone. This is Tommi, aka Alice und Bob. You might know me from my YouTube channel [Alice und Bob](https://www.youtube.com/@alice_und_bob/videos), where I educate on the edge of edutainment and technology within Polkadot, or from [publicly talking about DeFi in Polkadot](https://www.youtube.com/watch?v=NGnD3LhpHEI) (and specifically [Mangata Finance](https://www.mangata.finance/), where I lead Growth) or from my [occasional tweets](https://twitter.com/alice_und_bob) on the bird app.

Early last year I did my taxes and started building [Subscrape](https://github.com/ChaosDAO-org/subscrape), a Python scraper for Substrate chain, to help me in the process. Over time, things became more serious and I started building [Polkalytics](https://polkaverse.com/10716/polkalytics-a-google-scale-analytics-service-for-polkadot-37079), a Google-scale analytics service for Polkadot. I have built an indexer for Polkadot that writes the complete chain into Google BigQuery and later derives additional tasks to create account reports for the purpose of filing taxes.

During my work, I discovered that there are A LOT of data-related projects in Polkadot, it's just hard to find them at first glance. I had great conversations with people from the Parity Data Team, Apexti, Subwallet, and Apillon, and think that all the people working on data in the ecosystem deserve to be much better connected so that we can make everyone's life easier.

Therefore this submission is a proposal to create a Github repository that contains a survey of the Polkadot Data Ecosystem and an accompanying website. A complete overview of everything that exists in terms of data in Polkadot.

In preparation for this proposal I opened a [discussion](https://polkadot.polkassembly.io/post/1726) and had conversations with the Parity data team, a Polkadot Wiki maintainer and a member from the Subwallet team. There were two primary requests: To publish the work as structured data and to publish the work as website. Therefore I have decided to follow both approaches, disseminate the data in a repo with structured data and then publish a website that embeds the structured data (which will also work as a proof of concept)

I am still open to any feedback and will work to integrate it if it is in line with the intention of this proposal.

[Polkadot Treasury Proposal - A Survey of the Polkadot Data Ecosystem](https://docs.google.com/document/d/1MNxSf6rWOt_z6D884K_QvQpxpwahavHwarA7M79JLmE/edit#)

A companion video for this proposal can be found [here](https://www.youtube.com/watch?v=qYlpLdnZ8gY).

Best,
Tommi

Proposal: A Survey of the Polkadot Data Ecosystem

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

This proposal aims to upgrade Collectives system parachain to runtime [v9420](https://github.com/paritytech/cumulus/releases/tag/parachains-v9420): the specific details on this upgrade please check the release notes. This release contains the changes from v0.9.41 to v0.9.42. Please note there are 4 runtime migrations for relay chain on this release (details below), in addition to the migrations mentioned above, all the migrations included in runtimes since v9380 have been included in this release, allowing to jump over a few runtimes. Preimage is submitted:

`0x89902130dbc0b878d643e0367f5b9cc85c1b8ac80c4f6cceed9013491177da15`

This Polkadot system parachain upgrade includes changes since v9370, which has several major updates. For one, it includes XCM v3.

On Collectives specifically, this update includes the [Technical Fellowship](https://github.com/paritytech/cumulus/pull/2186). It corresponds to the launch of Open Gov on Polkadot, which is included in the Relay Chain runtime. The Fellowship will manage its membership and referenda voting on the Collectives chain, while sending its decisions (e.g. to whitelist a call for the `WhitelistedCaller` track) in an XCM message to the Relay Chain.

For specific PRs included on this release, please visit: [https://github.com/paritytech/cumulus/releases/tag/parachains-v9420](https://github.com/paritytech/cumulus/releases/tag/parachains-v9420). 

This proposal is submitted as an external motion: meaning if/after Council approves, the community will have the final decision via referenda queue. 

Make sure to review and vote at your convenience!

Runtime Upgrade for Collectives Parachain To v9420

Dear Polkadot Community! 
We are submitting a proposal for a governance incentivization tool, that helps incentivize experts and leaders within the community to boost governance engagement and voter activity.

**[Get the detailed Proposal here >>](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit)**

### **Overview**
While the concept of cryptocurrencies can be considered validated, the concept of cryptocurrency governance is still evolving. The objective of “basic” cryptocurrency governance (as a decentralized management system for that particular cryptocurrency ecosystem) is to perform decentralized control over the process, support developments, and manage the ecosystem's existence. The main goal is to ensure the long-term sustainability, security, and adaptability of a network while increasing the wealth locked in the ecosystem and the holdings of its participants, which are directly connected to the ecosystem's overall wealth. “Basic” cryptocurrency governance refers to the “tactical” decision-making processes. It helps address critical issues such as protocol upgrades, funding for development, conflict resolution, and network security. Even at this level, governance encounters numerous issues and opportunistic behavior from users, such as fraud, Sybil attacks, vote borrowing, voting manipulation, and participants' opportunism, among others. 

Polkadot's governance model is designed to prioritize the growth and development of the platform's ecosystem, rather than focusing solely on partnerships or marketing. This strategic approach stems from Polkadot's L0 vision as a foundation for future Layer 1 (L1) blockchains and its Substrate framework, which simplifies the process of building and deploying customized blockchains (also platform).
We can refer to Polkadot governance as "builders" governance, which emphasizes the platform's commitment to nurturing and supporting the creation of a robust ecosystem. This type of governance fosters collaboration and innovation within the community by allocating resources from the treasury to projects that contribute to the platform's growth, enhance its functionality, or expand its capabilities. In essence, "builders" governance concentrates on strategic objectives rather than tactical ones, prioritizing the development and evolution of the ecosystem over merely maintaining its current state. This approach ensures that Polkadot continues to evolve and adapt, making it a more resilient and future-proof platform that can support a diverse range of blockchain applications and use cases.

Polkadot's governance requires voters to have deep expertise and take on significantly higher risks, both within the large ecosystem and the market as a whole. Additionally, due to the break in cause-and-effect relationships, voters must make decisions without the possibility of receiving feedback or personal benefits. Furthermore, voters must also lock up their funds in the process. This is an important aspect of the system, as it helps to ensure voters' commitment and alignment with the long-term interests of the ecosystem. 
[You can learn more about "builder" governance in our proposal >>](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit#)

However, it can be confidently said that one of the biggest challenges of this type of DAO is the enormous amount of time that needs to be spent collectively on studying community proposals. If we assume that each proposal takes 5.5 hours for adequate study (the average time spent on studying a scientific paper by an expert), then 1000 voters will spend 5,500 hours on a single proposal (excluding those who could not handle it, did not study it, or did not vote).
Then 20 proposals will take up 110,000 hours. That is 68+ full-time experts working on this exclusively.
Hence, an obvious task is to reduce the time it takes for a community member to study one proposal. The organization and simplification, preferably with added interest, can be improved in the scheme of such governance.

There are several ways to lower the barrier to entry for studying proposals and increase the chances of engaging a voter:
- Train the required number of voters  
- Delegate votes to the most motivated members, who are ready to do deep research 
- Add formal proposal compliance analyses
- Provide volunteer analyses and reports.

[Each of these solutions has its pros and cons, and you can learn more about them by following the link >>](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit#)


### **The ideal concept proposes the following solution**
Drawing from existing experience, we can create a decentralized group of competing experts who can generate reviews of proposals. Their work will significantly reduce the need for ordinary voters to deeply engage with proposals, as they will be able to prepare reports that allow for direct insight. Decentralization and competition will facilitate the formation of diverse opinions and prevent an unconstructive approach. Moreover, these experts can become vote delegates who are also in competition. This work should be minimally incentivized, as reviewers provide a public good.

### **Grabber incentivization challenge concept.**
To implement commitment, user reputation, and actual actions and delegation of allocations and payments, have a reputation system within the system. It will be able to collect and analyze experts in the system and commitment. Based on this reputational tool, collective incentivization can work: bounties will be allocated, for which different experts will compete. Users will be able to vote on whose impact was more useful to them, thereby distributing the bounty. The results of their voting will again generate on-chain events that will enrich the participants' reputations.
The general scheme of work will be as follows:

1. For each proposal, a research budget is allocated, which allows compensation for researchers' expenses (bounty). For this, an event with conditions is created in the system.
2. Researchers can register in the system and conduct research, uploading links to them in the interface. Research is done within a specific timeframe.
3. After that, the proposed posts are reviewed, and points are assigned. Together with the relevance of their experience, they receive accruals from the allocated fund. When considering the researcher's relevance, it is visible how often they vote/voted/parachain auctions/funds in the system, etc.
4. The experience of researchers improves with the number of payments they receive (this is also collected on-chain and displayed).
5. The result is deep, non-formal research from multiple authors, which significantly reduces the workload for the community.



### **Grabber: A tool with an experienced team and Polkadot traction.**

Team:
Dev: Experienced with RUST, WASM/EVM (DOT) smart-contracts, Polkadot.js, and Polkadot features.
Community: Well-connected in the Polkadot community, with existing DOT/eco communities event traction and a large existing community.

### **Battle-tested flow**

We already have:
1. User onboarding flow 
2. Community UI
3. Administration UI
4. Parachain-ready (EVM/WASM ready)

### **Interface sketches**

Track selection
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/1.jpg)

Project selection
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/2.jpg)

Project Interface
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/3.jpg)

Voting “Back office” and “event” UX
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/4.jpg)

The voting manager creates an event and provides all necessary info to Grabber through our “back office”. 
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/5.jpg)

There are many competitions that can be managed
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/6.jpg)

Results control 


User UX:

Users apply for the claim. To apply, they bind their source wallet (DOT) and their distribution wallet (Smart-contract based parachain wallet/EVM wallet). Grabber's system aggregates crowdloan and voting activity of the users and proposes to save it on-chain. (in the smart-contract based parachain).
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/7.jpg)

Grabber front-end already supports major Polkadot/EVM wallets, detects extensions and helps these wallets receive new users (check grabber.network). Also additional popups added
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/8.jpg)

### Grabber | Algem
- Fully qualified (scored) users found to fit all criteria requested by the company: 532
- Users registered in Grabber for event: >5100
- Verified their wallets in Grabber: >3100 (60.87%)
- Event registrations (on-chain): **2735**
- Impressions for event-related Tweets from [@Grabberofficial](https://twitter.com/grabberofficial): >20K
- Increase in the number of Algem’s followers after the event: 16.48%
- Grabber x Algem smart-contract: [https://blockscout.com/astar/address/0xC00ba642fbB807B6e7A45fDAC4D2061d961fd272](https://blockscout.com/astar/address/0xC00ba642fbB807B6e7A45fDAC4D2061d961fd272)

### Grabber | Astar
- Fully qualified (scored) users found to fit all criteria requested by the company: 148
- Users registered in Grabber for the event: >2100
- Verified their wallets in Grabber: >1420 (67.62%)
- Event registrations (on-chain): **957**
- Impressions for event-related Tweets from @Grabber :>41K
- Grabber x Astar smart-contract: [https://blockscout.com/astar/address/0x76d46248F66Afb7767BA7C449748550926908DC4](https://blockscout.com/astar/address/0x76d46248F66Afb7767BA7C449748550926908DC4)

[More numbers about this evets available in the Detailed Proposal: ](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit)


### **Grabber's Potential Impact**

1. Better communication with the voters
2. Engaging the audience through the activation of existing KOLs and creating new ones 
3. Significant expansion of the voting audience
4. Easier onboarding for new voters and reactivation of those who dropped out
5. A platform for spreading the vote delegation system


**[Get detailed Proposal here. ](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit)**

All the best, the Grabber team! 

Grabber, a tool that incentivizes experts and leaders within the community to boost governance engagement and voter activity.

Integritee proposes developing and deploying private transaction sidechains on both Statemine and Statemint. This proposal covers the first two phases we outlined in [our blog](https://medium.com/integritee/a-privacy-sidechain-for-all-polkadot-kusama-chains-1bb52dc9b0d7). The delivery will be operational beta sidechains. 

[Discussion thread on polkassembly](https://polkadot.polkassembly.io/post/1739)

[Detailed Proposal Document](https://docs.google.com/document/d/1W9OjcwHKYqKzA0wmobN5HMf1cyiF3AHmRMvLs1K2hLU/edit?usp=sharing)



Privacy Sidechains on Statemin*

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

Polkadot Decoded is the Flagship conference and the the biggest yearly event focused on all things Polkadot. And it's back for its fourth edition on June 28th and 29th, 2023, with a fully hybrid experience of online and in-person events. Decoded aims to evolve into a general assembly for all things Polkadot/Kusama.

In 2023 we will come to Copenhagen, Denmark with an increased capacity and there will be simultaneous satellite events hosted regionally in the USA, Europe, LatAm and China in July. These satellite events are aimed to be regionally focused. Whereas the Flagship event will be globally focused.

The program line up will be featuring presentations, panels, workshops, demos, fireside and barcamp chats. We are focusing on curating content that is more high-level for a broader audience as well as attracting decision makers and enterprises into the room. The target audience will be crossing over all six of our target personas: Business Decision Maker, Technical Decision Maker, both from startups and Enterprises interested in Polkadot, Builders from teams in the Polkadot ecosystem, DOT Holders, Developer, Polkadot enthusiasts and supporters. Polkadot Decoded aims to be a general assembly for all things Polkadot/Kusama. However, we are mainly focusing on decision makers and enterprises.

Further information on the proposal, including milestones, budget, agenda, participants and more can be found under this [LINK](https://docs.google.com/document/d/15OgE-hsNGepFpN-xgLDG1x5cHWJ55ltYroMGHaQnYQM/edit?usp=sharing).

This is the 2nd tranche request. The first tranche has been discussed under #255 and approved with Motion #382.

Polkadot Decoded 2023, tranche 2/3 (June, Copenhagen, DK)

After the submission of [referendum 112](https://polkadot.subsquare.io/democracy/referendum/112), seeking to increase the validator active set to 500, the community discussed the possibility and the need of Polkadot increasing the validators set. 

Feedback from the proposals indicates two points:

- There's interest with increasing the number of validators of the active set **but with increments**;

- There needs to be some analysis on the effects of the increase to ensure there's no security concerns.

The results indicate that participating members would like to increase the active set to 400 with increments of 5 per era. They believe that this increase would not compromise the security of the chain and allow for natural (opportunistic) leveling as the set increases. Core developers have also agreed on similar increases by value: 

“With increasing to 500, the amount of DOT needed to acquire a validator will sharply reduce from 1.7 mDOT now, to just around 370 kDOT. We think this is overall unavoidable, but we would personally suggest first increasing to 400 and re-evaluate”

This proposal aims to increase the active set of validators by 5 per era, for 20 eras. The call also executes a one-time increase by 3 to reach 400 validators by the end of the 20 eras. Note that this initiative is submitted on behalf of a coalition of 1kvP validators.

- Preimage Hash: `0xbacad43f5467717cb1edfba6317524dc1d24fe3246afbe6a8cea7ed5fae1ba5f`
- Call data: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-rpc.dwellir.com#/extrinsics/decode/0x1a0408070a0c010401000000014038000014000000fe070a14)

Please note this proposal is submitted as an external motion: meaning if/after Council approves, the community will vote in referenda queue for the final decision. 

Make sure to review and vote!

1kvP Validators Initiative: Increase Validators Active Set to 400

This is a supplementary proposal for [motion 383](https://polkadot.polkassembly.io/motion/383).
In motion 383, we applied for a 2023/3-2023/8 operational cost of 16655 DOT, which was approved at the time. The details of the proposal can be found [here](https://docs.google.com/document/d/1oJjtkZD8mgv5vRpBh_aoGmWqWlLK9tomGhP8M9esMng/edit?usp=sharing). However, when we filled in the amount of application on chain, we mistakenly wrote 500 DOT instead of 16655 DOT. Therefore, we are applying again for the remaining 16155 DOT, and we hope that the rest of the amount can be voted through as soon as possible. We appreciate your understanding and support.

Treasury Proposal：A supplementary proposal for the 2023/3-2023/8 operating cost for the nonprofit organization Polkadot Ecology Research Institute

**Proponent:** RockX Official

**DOT Account:** 14tm4js6PgrDGZttNzyy7CM4pnYiPu3LxxZDb1zhJWUc5Wpj

**Date:** 28/04/2023

**Requested allocation:** USD $93,063 (15,485 DOT)

**Proposal Summary:** Provide free RPC service for the community in 2023 across multiple parachains to encourage growth and development.

### **Project Summary**

RockX currently provides free APIs on Polkadot and Kusama up to 100,000 requests per day. However, we would like to accelerate the ecosystem’s growth by expanding our offering to eventually include free packages for more parachains.

With the Treasury’s support, we plan to add 3 Parachains every Quarter from the start of 2023 until mid-2023 for a total of 6, where we will evaluate the current ecosystem status and adjust our processes accordingly. After the initial 6 chains have been onboarded, we aim to conduct an open call with other parachains to understand levels of interest before submitting a new proposal to add more parachains. We will also expand our Polkadot node offering to include a free archive node solution.

In addition to free API requests, RockX also provides a developer-friendly portal that allows users to set up APIs across all supported chains with just a few clicks, reducing the complexity and set-up time drastically. Last but not least, developers can also subscribe to our blockchain maintenance dashboard so that they will be able to receive the latest blockchain update information about Polkadot and its ecosystem.

To support the development of the Polkadot ecosystem, RockX will be offering free plans for developers that include 100K requests per day (or 3 million requests per month) for each blockchain supported above. This will be sufficient for most developers and users. Developers can access this free API service by creating their own API Key on the RockX portal and using the provided tools to optimize their development efforts. Up to 10 API keys can be generated for free for each blockchain. If any customization is needed, RockX can also assist with setting up custom archive nodes or full nodes. Every quarter, RockX strives to improve and enhance our product offerings and infrastructure for developers in the Polkadot ecosystem, including front-end UI, connectivity, security, and reliability. New product releases can be found on RockX’s Twitter page.

In summary, we’re here to take on all the complexities of node operations and utilize economies of scale and scope to lower the developers’ barriers (time and money) to adoption.

**History & Reliability**

RockX has been providing RPCs for Polkadot and Kusama since Oct 2021 and has achieved service reliability of 99.9% for Q4 2022 ([Link](https://access.rockx.com/product/polkadot-blockchain-api-for-web3-builders)).

The duplicate Polkadot nodes setup and the automatic failover system ensure the stability of the Polkadot node. In case of a node failure incident or during the Polkadot mainnet upgrade period, the automatic failover system directs users' requests to a backup node, ensuring continuous network operation.

**Notable Recent Enhancements & Support:**

Q3/22

Upgraded analytics dashboard to provide users more visibility on API usage
Uploaded videos about "How to build on a blockchain with Access Node"
Launched IP whitelist, and origin whitelist feature to enhance user’s security when using the RPC services

Q4/22

Wrote blog post to introduce Polkadot staking. In this post, RockX delves into the details of how staking Polkadot works, and why it's important for the success and growth of the Polkadot network. RockX will continue to -create new and educational content across the Polkadot ecosystem
Launched maintenance notification dashboard to keep users informed as soon as possible on any blockchain upgrades
Launched an incognito mode that will not store user’s IP address or browser information to further protect user's privacy

Our full report including data and links can be viewed [here](https://docs.google.com/document/d/1QTP7xPki6CAar-X2Uey-yGOYprAIaru83mibcSlen5g/edit).

Our previous community post with feedback on this proposal can be viewed [here](https://polkadot.polkassembly.io/post/1630).

RockX Public RPC Node Support Q4 2022 & New Development Q2 & Q3 2023

**Proponent:** 12wWLUd5qMzLFGqBsMnHLVFeTuYJwuo5ygMAxuSywrBX1XSF

**Date:** 2023.04.07

**Requested DOT:** 43,913 DOT (277,000 USD)

**Contact:**  jeroen@k-f.co & frederik@k-f.co

---

Currently, the only bridges available to users of the Polkadot ecosystem have some limitations, including:

1. Being EVM-specific and not Substrate native, e.g. several bridges (including Axelar) have been deployed on Moonbeam EVM. While this is great for bootstrapping liquidity in those EVM networks, it complicates integrations with other parachains through XCM and adds significant overhead.

2. Centralized bridges which are reliant on multisigs, which is incompatible with the Web3 vision of the Polkadot ecosystem.

3. Bridges that only go to Ethereum mainnet, and don’t support message passing.

We believe Axelar is an ideal option for solving those problems, as it’s a decentralized protocol based on delegated proof-of-stake, with support for general message passing across all its target domains. It’s currently connected to 32 blockchains, including Ethereum, Avalanche, Celo, Arbitrum, Cosmos, and Polygon.

Axelar’s any-to-any connectivity is crucial to the success of any ecosystem. Within Cosmos, where Axelar is the most widely used interoperability platform, historically only a minority of users onboard from Ethereum mainnet, with [Polygon being the most popular option](https://axelarscan.io/transfers?sourceChain=polygon&destinationChain=osmosis). By enabling people to onboard from any ecosystem, we expand the user base of Polkadot, Centrifuge and the ecoystem. Axelar network supports General Message Passing across chains and delivers any-to-any connectivity. Most people are familiar with cross-chain activity via bridges, which can only transport wrapped representations of assets. General Message Passing goes beyond: Axelar can transport any payload. This enables more sophisticated cross-chain operations, like buying an NFT representing a RWA on Centrifuge, with an asset held on Arbitrum. [Axelar is working with Circle](https://www.circle.com/blog/composable-usdc-seamless-multichain-ux-by-axelar) to compose this functionality with CCTP, so that users can perform those operations with 0-slippage.

Centrifuge and Axelar have been discussing the need for this with the ecosystem and the following parachains have also expressed an interest in using a Substrate-native Axelar integration:
* Astar
* Acala
* Oak Network
* Parallel
* Gear
* Manta
* Clover
* Composable
* Equilibrium
* Interlay
* Peaq network
* Unique
* Watr
* OmniBTC

The deliverable for this proposal contains an Axelar-Gateway-Pallet compatible with XCM to be integrated in the BridgeHub common good parachain, an Audit of the given pallet and all work around maintenance. The given Axelar-Gateway-Pallet will also be usable for a "local" deployment so that it will help all Substrate based parachains to connect to Axelar.

The full proposal can be found [here](https://docs.google.com/document/d/1ijCKnuFh4CNOLmObysNTyOa1WW10Ou0bWuf5wxMxetg/edit?usp=sharing).

The discussion post can be found [here](https://polkadot.polkassembly.io/post/1755)

 Treasury Proposal by Centrifuge: Support Axelar General Message Passing in the Polkadot ecosystem (via BridgeHub)

Hello everyone,

As many of you might already know, smoldot is an alternative implementation of the Polkadot client focused on using as little CPU, memory, and bandwidth as possible. It can be embedded within a web page, and thus allow end users to connect directly to the Polkadot network. Smoldot is a critical component in order to properly fulfill the goal of building a decentralized blockchain.

I am now submitting a new treasury proposal in order to continue financing the development of smoldot.

You can find all the details of the proposal here: [https://docs.google.com/document/d/1iYOIe_pyOdnV27hUA6FToWVSs7uUNHxIm5bA3KrMAE8/edit](https://docs.google.com/document/d/1iYOIe_pyOdnV27hUA6FToWVSs7uUNHxIm5bA3KrMAE8/edit)

It highlights the work that has been performed, and proposes new milestones for the upcoming quarter year.

Thank you for reading.

Tomaka

Smoldot development financing Q2 2023

This is proposal for Milestones 5&6.

DOT/EUR exchange rate calculated as 5.8176 by EMA7 (EMA with 168 period frame) by [Kraken](https://www.tradingview.com/x/GIsV7yQo)

Our team proposes to design an open source hardware storage for dotsama ecosystem.

Please see complete proposal on [Skiff](https://app.skiff.com/docs/6e1d3e9f-9e2c-4413-9190-9c39cda20763#yJcS2WZZbiuFk4Pe3W5nycQ7vcjEbrXkbfcf2EKIiV4=)

[Project repository](https://github.com/Alzymologist/Kampela)

Project matrix room: #Kampela:matrix.zymologia.fi

See previous material here:

[Discussion](../post/1227)

[Proposal for milestones 1&2](https://polkadot.polkassembly.io/treasury/163)

[Proposal for milestones 3&4](https://polkadot.polkassembly.io/treasury/197)

[Milestone 1 report](https://app.skiff.com/docs/2b25845a-4a00-4bf4-aaff-3de4a70d4ad7#zSepFgAI0EetUe7eIp2Tlgu/RnhMjnAJRDecVUiVmhQ=)

[Milestone 2 report](https://app.skiff.com/docs/5dcbeadc-e5f3-4f29-8476-e8fcb7786585#ZNnc%2FdmSz3dYkUNc%2BI%2BiarGsZKa0W9uUN25ZqCySPAg%3D)

[Milestone 3 report](https://app.skiff.com/docs/a0583eb2-1b44-46f1-b921-4dc4aa8abf68#QczSiY%2BGxi93PTv%2BFAd%2BPuNnfBqh%2BCpqBIFdooAufCo%3D)

[Milestone 4 report](https://app.skiff.com/docs/984d9ed1-9271-4457-be04-a6eca0f25f39#JZdHE9gfXVn%2BtkTl7EBOqCsxCfo%2F2FRjO%2FnnOJoJM6I%3D)

Project name is Kampela, Finnish word for flounder fish. The device is envisioned as flat card mostly consisting of e-paper screen and few controls (and it allows keys to stay safely in depth).

Kampela is a hardware version of Parity Signer. It is a small card-shaped device (ideally comparable to a credit card form factor, to be carried in a wallet when needed) that accepts data through unidirectional NFC port and shows output on a monochrome electronic paper screen. It has cryptographic strongbox with elliptic curves supported by Substrate — which only stores private keys (after initial import) and performs all signing operations on-chip.

Kampela is designed to be a comparatively low-cost (below €100, in contrast to €500+ for a Signer-compatible smartphone) single-purpose device, which would only support a single seed phrase per unit, operated via a drastically simplified user interface. However, it would have all the security features of Parity Signer: a full-featured SURI account derivation system, transactions preview, metadata updates, logging.

As something that supports the same QR code output formats as Signer, it would be able to drop-in replace Signer when providing signatures back to a mobile/desktop wallet. The only challenge would be in transforming the current QR-driven input format of Signer into a suitable NFC payload. Alongside with native support in some apps (which would require software modification) this can also be achieved with a tiny “translator” app for a regular (online, not necessary trusted — one’s usual daily driver) mobile phone: it would snap a QR code with the transaction details and (statelessly, without any extra features or complicated UI) transform that into an NFC payload.

Kampela is a natural (and long-discussed) extension of Parity Signer to leverage the most out of modern hardware-based crypto chips and drastically reduce Signer’s attack surface: no mobile OS, not extra platform features, no unexpected communication methods or airplane mode to take care of.

Kampela is not a wallet! It is a signing tool, it is not able to track on-chain balances, validate things over chain-provided information or generate transactions on itself.

The scope of this proposal does not include actual production, but does result in all preliminary development required for production. Hopefully, many assembly shops would rush in to compete with us and each other!

As these last milestones were listed out long time ago, it makes sense to clarify them now with more details on planned work and deliverables:

# Milestone 5

- Fabricate another iteration of the casing (test mechanical integrity of device, usability, etc)
- Test end-of-life secure self-destruct feature: it's trigger circuit (can we rely on broken screen as self-destruct indicator? Is trigger easy to activate? Is indication clear?) and success (does the chip indeed understand wipe command and use small enough power to perform it?)
- Power circuit (test whether it supports various phones budgets and withstands some instability; make sure device can safely burn off residual power and reboot on power loss)
- User input (make sure touch pad input on E-Ink is not too frustrating)
- Test secure element powered key management (encrypt key, decrypt, check attempt counter and self-destruct features)
- NFC reception of large signed payloads

We have decided to leave RNG analysis out of scope, as that component of chip is indeed certified and tested upstream; implementing extra hashing over existing certified secure RNG device in an airgapped cold device with single baremetal app running does not seem feasible, as implementation error risks greatly outweigh probability of hardware attacks, as there is no path to pass exploit trigger event for an attacker; deploying simpler exploits that would make SE accessible to an attacker or make snapshots of onboard RAM, would be simpler for manufacturer to embed into hardware.

# Milestone 6

- Final specifications for NFC communication protocol
- Full manufacturing schematics for the device, including "hacker" edition with programming interface exposed for enthusiasts and hackers to play with, that we intend to manufacture and distribute to order right after completion of the project, as it obviously does not require any audit
- Prepare documentation on analysis of device, for community to study and for auditors to facilitate manufacturing security audit procedure
- Demonstration of fully assembled and operational device with basic functionality and interface
- Decision on whether active NFC tag dummy could be used as second factor with sufficiently secure signing of NFC responses at current level of technology without too high impact on power system of the Kampela device

Hardware signer and key storage Kampela: Milestones 5&6

**Dear Polkadot community and Councilors,**

This proposal aims at claiming funding from the Polkadot Treasury for work that has been done in SubWallet's [Milestone 3](https://docs.google.com/document/d/1O6_ftxopSHMdMfJdxYycHIsD6yNHYPv_egyajwDZp38/edit?usp=sharing) in the period from June to September 2022.

[SubWallet](https://subwallet.app/) team started building in November 2021 and we have been very focused and building fast since then. We released the [SubWallet extension version ](https://subwallet.app/download.html)on all popular browsers (Google Chrome, Firefox, Brave, Edge) in February 2022 and [SubWallet mobile app public testing phase](https://twitter.com/subwalletapp/status/1587403200105451520) in November 2022, and keep releasing our product updates on a [bi-weekly basis.](https://twitter.com/RyanDinh8/status/1557652913463275521)

![](https://pbs.twimg.com/media/FWF-pFrUcAAz-LF?format=jpg&name=4096x4096)


SubWallet got Polkadot treasury proposals for [Milestones 1](https://polkadot.polkassembly.io/motion/222) approved in July 2022 and [Milestone 2](https://polkadot.polkassembly.io/motion/253) approved in September 2022.  Below is a list of tractions and features we have completed after our Milestones 1 and Milestone 2:

- 70+ networks supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- 15,000+ organic installs and 12,000+ weekly active users on Chrome Store & Firefox Store
- Our users come from 80+ countries.
- 6,500+ community members on Twitter, Telegram, and Discord
- A member of the Substrate Builders Program
- Working with 70+ teams in the ecosystem with the ultimate goal of bringing the best UI/UX for users.
- Create, restore and import accounts
- Manage multiple accounts
- Manage multi-chain assets
- View transaction history
- Manage Crowdloan portfolio
- Manage NFT
- Compatible with Metamask and Support EVM assets
- Substrate Connect - Light Client
- Built-in XCM transfer
- Custom network, custom endpoint
- And more: [Milestone 1](https://github.com/Koniverse/SubWallet-Extension/milestones?state=closed) & [Milestone 2](https://github.com/Koniverse/SubWallet-Extension/milestone/2?closed=1)
- SubWallet on **Polkadot Community Call** on August 18, 2022: [Link](https://twitter.com/Polkadot/status/1560234806478356480)

As our vision is to become a Multiverse Gateway for the Polkadot & Kusama ecosystem that helps onboard more users to the ecosystem, we continue to add new features to SubWallet based on the development of the ecosystem and feedback/suggestions from our community.

**This proposal aims at claiming funding from the Polkadot Treasury for work that has been done in SubWallet's [Milestone 3](https://docs.google.com/document/d/1O6_ftxopSHMdMfJdxYycHIsD6yNHYPv_egyajwDZp38/edit?usp=sharing), that includes the features discussed in details below:**

**Complete set of the proposal: [(See proposal)](https://docs.google.com/document/d/1O6_ftxopSHMdMfJdxYycHIsD6yNHYPv_egyajwDZp38/edit?usp=sharing)**

- Support Ledger for Polkadot & Kusama [(Link)](https://twitter.com/Polkadot/status/1556637171611848704)
- Support Parity Signer and other QR Signers ([Link ](https://twitter.com/Polkadot/status/1556637171611848704)and [Link](https://twitter.com/subwalletapp/status/1588135819201548290))
- Support In-app Staking for Polkadot & Kusama ([Link](https://twitter.com/subwalletapp/status/1540651630206386176))
- Support XCM transfer between Polkadot and Kusama to parachains [(Link)](https://twitter.com/subwalletapp/status/1558319962447433729)
- Integrate USDT on Statemint: Display, Receive and Transfer [(Link)](https://github.com/Koniverse/SubWallet-Extension/issues/679)
- Integrate Transak and allow users to buy DOT, KSM from fiat [(Link)](https://twitter.com/subwalletapp/status/1572552943492288515)
- Update caching mechanism to optimize performance
- [And more](https://github.com/Koniverse/SubWallet-Extension/milestone/3?closed=1)

**Our tractions as of March 2023**

- 140+ networks and 400+ tokens supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- Browser extension: 43,000+ organic installs on Chrome Store & Firefox Store.
- Mobile app is in the public testing phase on both iOS and Android. 5,000+ installs [(Link)](https://twitter.com/subwalletapp/status/1587403200105451520)
- Our users come from 100+ countries.
- 8,500+ community members on Twitter, Telegram, and Discord
- Completed the Substrate Builders Program
- Working with 150+ teams in the ecosystem with the ultimate goal of bringing the best UI/UX for users. 
- SubWallet on Polkadot Community Call on November 24, 2022: [Link](https://twitter.com/Polkadot/status/1596825254982479873)
- SubWallet on Polkadot Community Call on January 20, 2023: [Link](https://twitter.com/Polkadot/status/1618228474065620999)
- We would love to hear feedback/recommendations from the community and Councils.

**All the best,
SubWallet Team**

SUBWALLET EXTENSION - MILESTONE 3: SubWallet 3rd proposal: Hardware wallet integration (Ledger, Parity Signer, Keystone), Built-in XCM transfer between Polkadot & Kusama and parachains, In-app staking for DOT and KSM, Support USDT on Statemint, Fiat on-ramp and more

**Proposal**
###
A proposal by the Polkadot Council, and later to be voted by the community for the final decision, to fix the issue with the enactment of the recently executed [referendum #113](https://polkadot.polkassembly.io/referendum/113), submitted by Watr.
###
**Context**
###
[Referendum #113](https://polkadot.polkassembly.io/referendum/113) was enacted, and after the execution of the two extrinsics from the preimage, the runtime was correct, and the header was correct, but the header got overwritten. The header was overwritten via [inherent transaction](https://docs.substrate.io/learn/transaction-types/#inherent-transactions) from the collator. This transaction was supposed to be rejected. Still, it was not rejected due to a Substrate bug: [https://github.com/paritytech/substrate/issues/9210](https://github.com/paritytech/substrate/issues/9210)
The issue now needs to be fixed by re-executing one of two extrinsics from the previously executed referendum to set the correct header of the parachain.
###
**Impact**
###
The network runtime is in the correct state after the execution of the previous proposal to reset the parachain. Still, due to the incorrect head, the parachain cannot produce blocks.
###
**Remedy**
###
The execution of one of the extrinsic to set the Watr’s parachain (2,058) head from the previously executed governance proposal will fix the issue.
###
**Proof of Authencity**
###
`We confirm the intention to reset the head of the Watr parachain (id: 2058) to 0x0000000000000000000000000000000000000000000000000000000000000000001a3a2baafaa9623dbeab06759b78f4bce878d0fbfeef992a546bce6670131e6103170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400 to resolve the issue caused by a bug in the enactment of referendum 113`
###
Signature

`0x9618272c953c90b67973d2525bead280ea74f71d0104b267767b9312f7785f28ec683f269d565d6faf4927faa4262730b4939e71fea292be50be7e5b1f9bb987`
###	
Below is the preimage:

- Hash: `0xac9ff5733f194470235d78f67d56e656a0d8ee8a908dda7782d22ed2dfb9f9eb`

- Extrinsic: `paras.forceSetCurrentHead`(2058, [newHead](https://github.com/Watr-Protocol/seedling/blob/main/watr-head-data))

Fix incorrectly enacted referendum caused by a Substrate bug

Hello DOT builders, developers, independent researchers, and community!
We would like to present to you a user behavior research product that will help improve the effectiveness of application development in the ecosystem and identify possible synergistic partnerships. Our goal is to study user behavior based on the ALREADY existing onchain information on the blockchain. 

[Original discussion post >>](https://polkadot.polkassembly.io/post/1679)

### Context of the proposal
We propose web3 user-research tool for the Polkadot ecosystem that enables developers to analyze and score user behavior on-chain, providing a deeper understanding of the current state of the ecosystem at the user, dApp, and parachain level.

With real-time detailed snapshots of the existing Polkadot community, developers can improve their products, create stronger communities, and effectively incentivize newcomers using Motif's insights. 

### Reference/experience
Our team has conducted and is actively engaged in multiple research projects to battle-test our event-based extraction method. Examples of completed and ongoing studies include:
- dYdX (complete)
- Astar (complete)
- Lido (in progress)

We have made an effort to provide a comprehensive explanation in a [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit)

In the following sections, we will present the results of these studies and demonstrate that the event-based method is sufficient for the purposes of research within the Polkadot ecosystem. 

### Problem statement
The operation of P2P systems is based on the P - peers (or people)  themselves. Due to the nature of independent economic systems with internal accounting units, users not only generate revenue but also directly influence the economic parameters of the system. It is the behavior of users that is the main lifeblood and success factor of that kind of economic systems. To operate successfully within such ecosystems, the creators of both the ecosystems themselves and the services and applications within the ecosystem must have a good understanding of user behavior, tools to influence it, and effectively track results.
- How can we identify the users who effectively and consistently use the dApps?
- How can we identify the users who fraud actions and try to deceive the system to obtain a reward?
- What motivates users to provide liquidity and how does the ecosystem incentivize them to continue doing so?
- How can we track the last actions of users who have transitioned from one ecosystem to another?
- How can we motivate average users to engage more actively with the system?
- How can we retain existing profitable users?

Answering these simple questions or finding relevant information within Polkadot is practically impossible. The main reasons for this are:
- Blockchain user data reality itself: a huge, interconnected and decentralized mess which is difficult to explore. 
- The modular multilevel structure of Polkadot is hard to overview.
- The limited number of functioning dApps and zero-to-none smart-contracts as a source of customer behavior leads to a lack of information.

### How is this problem being solved today?

One of the current solutions is one-by-one research. However, "wallet-by-wallet" research is extremely difficult. Researchers have to go to different wallets, look at the experience of interactions, compare similar wrapped/transferred tokens/coins/portfolios, actions, etc. Comparing users, let alone profiling them is almost impossible. It leaves no chance for factually understanding users' behavior and providing targeted incentivization to wallets with relevant experience. 

Due to this complexity, analysis often boils down to two simple metrics: the number of tokens on the relay chain or the number of wallets (for example, how many came and performed some action). This leads to a distortion of reality and inefficiency in analysis and results: prioritizing “big balance” leads to the dominance of "whales" behavior, while “big numbers” lead to the domination of "bot farms." However, these cases do not lead to growing the numbers of the active users, and such metrics do not allow the application to improve its efficiency. On the contrary, they provide an opportunity for potential fraud from such participants.
Even for the whole ecosystem itself these "bot farms" and "whales" can create a centralization effect, exposing the ecosystem to potential manipulation by centralized third parties. 
Therefore, a significant portion of tools based on user behavior aimed at incentivizing them, such as airdrops, retrodrops, quests, whitelists, and others, do not produce the desired results.


### Motif’s solution

Motif provides 3 main tools: 

**1. Parachain and Relay Chain Overview User State (B2B)**
This tool provides an overview of the current holders, including their profiles, assets, and level of activity. It can help identify the most active and engaged users in the ecosystem and their holding patterns. 
![](https://gateway.pinata.cloud/ipfs/QmVyzQMfwgt2veQQuS7GmstE7XSHwyhTrBPqS6p23oGwXM?_gl=1*5q5xpv*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

**2. Individual Wallet Cross-Parachain Traction Analytics for Personal Use (B2C)**
Any user can input an existing native wallet address and receive comprehensive information about the user's activity, presented in an easy-to-use format. This includes details on the assets the user currently holds or has held in the past, the specific assets they have traded, and the most active protocols or parachains the user has interacted with.
![](https://gateway.pinata.cloud/ipfs/QmPNUF5NUWu3GvCuJtdRiCCJzCcYXSNt8bUjYRtxi3PPLk?_gl=1*1s9z1iz*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

**3. Batch Scoring of User Sets (B2B)**
Motif provides the opportunity to score a set of users in a batch, allowing for research and analysis of user sets. This helps to identify the best users for DeFi, which users will hold long-term, and which users are most active members of the Polkadot community.
![](https://gateway.pinata.cloud/ipfs/QmVMTw3JordrdZjrcjYXhpC9hxN3TzKbrkRvQmsuexU3Ps?_gl=1*1s9z1iz*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

The goal of Motif is to help developers improve the user experience of their dApps and incentivize the most active and engaged users. Our core concept is to research and connect the most valuable users with the most suitable dApps to accelerate the growth of the Polkadot ecosystem.


### Research method 

Our research method at Motif is event-based, focusing on events within transactions and associated data.
We generally work in two major steps: Extraction and Calculation (or orchestration). The extraction step involves collecting and organizing data from various sources, while the calculation step involves analyzing and interpreting the data to gain insights and produce results.

You can learn more about our methodology in the [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit#heading=h.3dy6vkm)

Here we will provide an overview of the main capabilities of our proven methodologies.

**Event-based extraction method can produce enough data for the web3 research**

Furthermore, the discovered clusters can be statistically described, which can aid in making predictions about the performance of future users and their actions 
![](https://gateway.pinata.cloud/ipfs/QmdF7CKBzpjgCbmwjih38oQvhY4tcmXCG1V4JWdjbdBUMa?_gl=1*7jddbl*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)
![](https://gateway.pinata.cloud/ipfs/QmPNxxdmdPfPJZhUFzxE7BojRNM8xbJrqpSA9W9KdohbSr?_gl=1*twtwv8*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)


**Users can be profiled by their activity or assets**

Users can be profiled based on their activity or assets. This is known as user profiling, which involves dividing users into groups based on their interests.
![](https://gateway.pinata.cloud/ipfs/QmVmCqXYve9QypMMPKiXw542L8jSusC4sjzPcBtvEra2ZC?_gl=1*4fhpby*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)


**Motif can be used for dynamic research too.**

This is how the clusterization looks after event-based extraction and aggregate recombination 

![](https://gateway.pinata.cloud/ipfs/QmT1Cx4RGnfUa53a7ASc7N7EnqFkgzCbnbqMCVty1faTj1?_gl=1*dz7fmg*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

Additionally, we can use other hypotheses to define clusters, such as the economic value of the user being proportional to the amount of gas spent. The more gas a user spends, the more money they spend. This can be used to further define and analyze the clusters.

![](https://gateway.pinata.cloud/ipfs/QmWH7ggYDw4i6hRXW5y84hyMbeFyjo3rzfEchCZaSoLyHX?_gl=1*17w0ipi*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

**Event-based Method battle-test results**

- Wallets with at least 10 transactions can be studied using transaction data, which provides a variety of features (such as type, timestamp, gas spent, and method) that are suitable for statistical and machine learning analysis.
- A daily average of 80 unique active wallets (UAW) is sufficient to uncover correlations and create user profiles.
- Wallet profiles can be predicted using research data and on-chain metrics such as minimum token levels, chains, or key actions.

You can learn more about our methodology in the [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit#heading=h.3dy6vkm)


### Stakeholders benefits
**DApps**
Our goal is to improve the efficiency of dApp onboarding and operation by providing opportunities for researching users, rival dApps, and the parachain itself. This allows dApps to easily navigate different ecosystems and onboard the most relevant communities. Additionally, dApps can better understand user needs and experiences, and reward the best users for their on-chain activity and holding without fear of flipping. This can streamline dApp development and operations and save on marketing and liquidity costs.
For example, dApps can incentivize users with different profiles (Top degens, Strong Holders, Early Adopters, etc.) using modern mechanics such as retrodrops, airdrops, and claims.

**Ecosystems (parachains)**
Ecosystems will have the opportunity to onboard relevant dApps (if they want to work on top of parachains), which can increase the use of native coins and grow the user base organically. This will lead to rewards for user loyalty and experience. Additionally, ecosystems can incentivize users to explore new experiences without the risk of losing funds to bot farms or flippers.

**Polkadot community**
Polkadot community members, whether experienced or new, will have the ability to be recognized for their loyalty and experience, and will be able to receive benefits for their engagement with the ecosystem. This can include rewards for on-chain activity, holding native tokens, or participating in research and development of the ecosystem.

### New use cases for the Polkadot

**Updatable/dynamic Web3 id.** Motif offers an updatable and dynamic Web3 ID that can meet the demands of on-chain user recognition, scoring, and profiling systems. This ID can be integrated into smart-contracts or routing systems, providing enhanced security for users and customization options for dApp developers.
The general idea is to enable blockchain applications to provide personalized conditions based on a user's real on-chain experience, without using any information from outside the blockchain (off-chain can be easily manipulated). The existing "HYPE concept" of soulbound tokens does not seem suitable, as the verification should occur at the moment of interaction (there can be a gap between the emission of the SBT token and the interaction).This case can be solved by implementing a scoring smart contract standalone or within the routing circuit (as part of it or as part of the route when conditions occur). Such a "smart contract factory" can work based on the solution we propose.

**DID.** Motif can also provide a decentralized digital ID based on the user's fingerprint (user trace in one wallet types) and predicted level of on-chain activity.. 
Current solutions for user address unification based solely on public addresses are not viable as they can be easily falsified. In our view, a usable digital fingerprint is only possible with transactions that have internal economic value. This combination of transaction patterns with economic significance and related information increases the chances of a real human subject managing the given address. Again, thresholds and identification of such transactions are possible on the proposed platform.

**Web2 scoring** where Web3 data can be used by Web2 apps for various purposes.

**Web3 scoring interfaces** for the Polkadot. 

**Web3 scoring backend** for Polkadot, such as Nansen/debank look-alike dApps that currently do not exist in the ecosystem.

These use-cases can provide opportunities to onboard new dApps to the Polkadot ecosystem, increasing its potential for growth and usage.


You can learn more about our Motif in the [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit#heading=h.3dy6vkm)


We would greatly appreciate your feedback and ideas for improvement. We thank the participants of the Polkadot ecosystem and colleagues from Parity for their intensive work on this proposal.

Motif: Web3 user research platform

We have opened[ a tip for the reimbursement of this Proposal](https://polkadot.polkassembly.io/tip/0x07555c9158fdedfda115ab41335a0fa5cc4b236d04511e5c18664b28632d967f) for the return of the bond. We will re-submit this Proposal later.

Hey Polkadot Community!

My name is Alex, and I am super excited to have the opportunity to finally put a lot of thought, planning and strategy into motion and execute a set of development initiatives in order to help build Polkadot ecosystem with MVP Workshop, one of the Europe's pioneers in Web3 & Blockchain, and with my responsibility as a Web3 Founder & Business Developer.

The first step is for our team at MVP Workshop to build a UI & Front-End for DotSwap, a UniSwap V1-based DEX on Statemint.

A bit more information about MVPW:

[MVP Workshop](https://mvpworkshop.co) is a Blockchain Product Research & Development Studio, and one of the pioneers of Web3 in Europe.

We are an innovative team of 50+ engineers, developers, designers, consultants and marketers who are head-over-heels in love with the wide range of possible applications of blockchain technology. Our experience counts 70+ developed Blockchain products, and we are proud to say that our biggest accomplishments are:

- Polygon’s official implementation partner (built Polygon Edge, Nightfall Block Explorer and 5+ more products during a 3-year partnership). We are also very proud to say that Mihailo Bijelic, Co-Founder of Polygon, came from our research facility named 3327 and that we proposed the name ‘Polygon’ when it was still MATIC Network. 🙂

- Parity’s Substrate Delivery partners: 2 years ago we got in touch with Parity to build a variety of products for the Polkadot ecosystem, including Substrate Starter Kit. Although we’ve hold off scaling the Rust team, we’re now dedicated towards creating a dedicated department (and maybe even a venture) that would focus on new projects in the Polkadot ecosystem, as we’ve been in touch with Parity regarding building Parachain SDK, as well as the UI for DEX on Statemint, that we’re currently writing a Proposal for.

- Complete technology solution for Celsius Network: Although we all know what happened with Celsius, we are still proud with what we’ve accomplished, as we didn’t have anything to do with the Business or Management side, and even our company funds and my personal funds are still stuck.

Also, we’re proud to say that 3 weeks ago, we’ve managed to get into top 12 finalists out of 250+ companies on ETHGlobal’s Hackathon on building dApps on top of FVM (Filecoin Virtual Machine).

The list goes on and on, as we’ve been working closely with more recognizable industry names such as Moonbeam, Bitcoin.com, yearn.finance, created different products on Cardano, and many more.

Our DEX experience: 

Already mentioned, we have a significant experience developing Celsius, a UniSwap fork for a big CeFi product, a DEX for Bitcoin.com built on Moonbeam, Tesseract finance (supported by yearn.finance), Revuto (a DEX on Cardano) and more.

You'll find UI samples in [the full Proposal found here](https://docs.google.com/document/d/1xPFwfqGrbU2B_9h_RB8SfU6ya7gDRvGKGLUrO_NMjMg/edit?usp=sharing).

So far, MVPW Studio has been engaged in Polkadot ecosystem by:

- Creating a [Substrate-Starter-Kit](https://mvpworkshop.co/blog/proudly-presenting-substrate-blockchain-starter-kit/) (which is a tool that brings the simplicity of creating a substrate-based blockchain by simple drag and drop pallets to a codebase.

- Developed a DEX on Moonbeam as a part of cooperation with Bitcoin.com (was never launched).

Today, we’re in close contact with Parity representatives in two big initiatives:

- Parachain SDK (a tool that will offer a set of shortcuts to easily deploy Parachains in a more affordable and quick way)

- UI & Front-end for a DEX on Statemint (a project we’re writing this proposal for)

With our serious plans to dive in the Polkadot ecosystem and give our full experience and expertise into empowering it, we are planning to submit a proposal for the UI & Front-End development of DotSwap, a DEX built on top of Statemint, a generic assets parachain and the first common good project, which provides functionality for deploying and transferring assets.

In the full Proposal document, you'll find a following structure/outline of topics:

1. Requirements & Funding
2. Introduction
3. About us (Company background)
4. Context of the proposal (Our principles on building on Polkadot, Statemint challenge, MVP Workshop's solution by contributing to build a UI & Front-End for the DEX 'DotSwap', etc.)
5. Scope of Work + Project Estimates

Having lots of experience in infrastructure and enterprise business solutions, we wanted to share our input on Polkadot, in terms of what we will focus on in order to contribute to the massive adoption of the technology amongst the industry.

We've found out about this initiative from talking internally with Parity team who onboarded us fully with the project requirements and description, which only made us thrilled to scope and estimate the UI & FE development and start with MVPW's contribution to the ecosystem.

For this development initiative, we’re asking for $80,960 or 13,500 DOT on the date and time (6-March) that 1 DOT = $5,97

Thank you Stefan, Rich, Vi, Alex, Gilles and many more who contributed in the continuous support on this initiative. 🙏🏼

[Please reject] MVP Workshop Treasury Proposal: DotSwap UI & Front-End (a DEX on Statemint)

Hi everyone,

My name is Chris Veselinov, CTO of LimeChain, and I’m writing this thread to propose the development (and funding) of a Parachain Validation Conformance Testing.

With this proposal, we’re looking to identify test cases and implement conformance tests for the execution of the parachain verification function across different node implementations and wasm engines. 

This project is inspired by the currently open RFP for **[Parachain Validation Conformance Testing](https://github.com/w3f/Grants-Program/blob/master/docs/RFPs/Open/parachain_validation_conformance_testing.md)**

The ultimate/end goal is to define the baseline for the execution of parachain validation functions within a reasonable limits across different implementations. This will ensure that updating wasm engines, introducing new node implementations etc. can be done in a sane way without hoping for the best.

**Please see the official proposal document [here](https://docs.google.com/document/d/1C44lIlpoQMDaGlni9XT-SXJUtT-Ei3Et1osFoa-1W-g). Any feedback or comments are highly appreciated.**

About us: LimeChain is a blockchain development company founded in 2017 with a focus on building core blockchain infrastructure, developer tooling and dapps. We dove into the Polkadot ecosystem about 2 years ago with [Subsembly](https://github.com/LimeChain/subsembly) - a framework used to design and implement Substrate runtimes in AssemblyScript, again funded by the W3F. 
Some of the ecosystem work we’ve done involves the creation of Runtime from scratch and evolving it into fully capable frameworks for building Substrate Runtimes. Since the end of 2022, we are also actively working on [gosemble](https://github.com/LimeChain/gosemble) which is a framework for developing Substrate compatible Runtimes.

LimeChain is also leading the initiative for Polkadot Java host implementation and [research](https://github.com/LimeChain/java-host-research). This will further extend our knowledge of the PVFs and the specifics of their execution.

[Link](https://polkadot.polkassembly.io/post/1683) to the discussion.

Thanks on behalf of the whole LimeChain team!