> This is a follow up proposal to what we submitted before:
[#151 Subscan | Infrastructure Costs of Subscan for Polkadot & Westend & Rococo Networks](https://polkadot.polkassembly.io/treasury/151)


**Overview**

Subscan is an essential block explorer and analytics tool for the Polkadot network, providing valuable insights to the Polkadot community. However, the maintenance and operation of Subscan requires a significant investment of resources, including server infrastructure, security, and personnel costs. Therefore, we propose reimbursing the operation and maintenance fee for Subscan from July to December 2022 from the Polkadot treasury to ensure its continuous operation and maintenance.

**Total**

We believe that this reimbursement proposal will help to ensure the continuous operation and maintenance of Subscan, and benefit the growth and development of the Polkadot network. This time, we plan to apply for a total of 190,244 USD in Polkadot, the amount of DOT will be converted based on the EMA7 price on the day of the official submission.

Billing details can be read [here](https://docs.google.com/document/d/13whK83g_MXYCfQ4WyJmQuM_aTclCGsB9Ww9Pq3lP6dY/edit?usp=sharing).



Subscan | Infrastructure Costs of Subscan for Polkadot & Westend & Rococo & Statemint & Rockmine  Networks (from July to December 2022)

Polkadot Decoded’s Flagship event will be held at the end of June 2023 at the Øksnehallen in Copenhagen. This is the biggest yearly conference focused on all things Polkadot. It brings together the Polkadot community, web3 enthusiasts, new/curious DOT holders, and builders to hear about developments in the Polkadot ecosystem. To align with the global Flagship event and continue the excitement with the regional focus at the strategic local markets of the Polkadot community, a grand satellite event covering the Asian region ( China, Japan, Korea, Singapore and the rest of SEA) will be held on July 15th and July 16th at Shanghai/China (exact location is TBD and the dates will align with the rest of the regional satellite events).

The 2023 Decoded China event will therefore create pivotal experience to the fast growing Polkadot China community and the nearby markets such as Korea, Japan, Singapore, Vietnam and the rest of SEA. The China satellite event will feature presentations, panels, workshops, demos and aligned regional events (i.e. regional hackathon), delivered in the language of Chinese or English. The latest update and news of the Polkadot ecosystem teams, Parity, the Web3 Foundation and the community KOLs from Asia will be shared. The event is focusing on the content curated for a higher-level and border audience, as well as for decision makers, investors, entrepreneurs and Web3 Medias.

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 China aims to be a general assembly for all things Polkadot/Kusama happening in Asia with a main focus of the China market.

Along with one main stage with the presentations, demos, panels and flagship event (Decoded Copenhagen) highlight playbacks, 2023 Decoded China satellite event will have networking areas, private meeting areas, exhibition areas (for parachain and ecosystem teams) and one after-party to celebrate with the community. The China satellite event aims to have between 300-500 attendees, 25 speaking slots (presentations, demos, panels and Copenhagen highlight session playbacks are all included), 20 exhibition booths (for selected parachain teams and the Substrate-based ecosystem projects), and one Substrate job fair.

The 2023 Polkadot Decoded China satellite event will be facilitated and hosted by Aitijia’er, an event agency based in China, who produced the 2020 Web3 Form @ Shanghai (Web3 rebranded towards China due to the regulation concern) and 2022 Decoded China @ Hangzhou.

More details of the proposal, please see this link [here](https://docs.google.com/document/d/1gn64J66dlZLheQxNa1R19AOqdkyboxn1vHyUOD1rmPw/edit#)

Polkadot Decoded 2023 China (Satellite Event) July 15-16, 2023 in Shanghai China

**Requested Allocation:** $104,000 

*DOT amount calculated via EMA7 on 6 June 2023 at GMT+0 1100hrs: 1 DOT ~ USD$5.235. USD$104,000 ~ 19,866.2846 DOT

**Proponent:** EasyA 5FQqvRHgBEUZG17qs9cNFH6ZSSVyAwhb7D6dKjGWb8xgKFkP


Hey Everyone!

We’re delighted to give a full update on our progress so far!

**Progress Summary**

In summary, we have now successfully achieved Milestone 1 and Milestone 2! We started by opening this educational opportunity to more parachains/projects and preparing the full content framework. We have now collected key feedback from developers and parachain/project teams and utilised it to create the content for the challenges. We have also created a totally new design and UX for the Polkadot challenges to make them stand out. We are in the very final stages of approving all the content to go live in the app for release. 

We’re super excited that on the IRL hackathons side, we have also finalised the hackathon dates and locations. We have been inviting key developer groups and Polkadot parachains to attend the hackathon and will be leveraging our connections with core blockchain clubs to ensure a brilliant pipeline of builders at the hackathons!

Our next step is to make a huge push to get everyone building on Polkadot in the run-up to the IRL hackathons. We’re currently working with the participating parachains/projects on a detailed social media and activations strategy!

**Full Progress Report**

We have written up the fully comprehensive progress report for Milestones 1 and 2 [here](https://docs.google.com/document/d/1tvSCM9w8fSKxUBgTIuXNbhrdNWZUzpQHtORZxtyVAKE/edit?usp=sharing) for the community!

**Milestone 2 Requested Allocation Breakdown**

We would therefore like to request our Milestone 2 allocation so that we can proceed to Milestone 3 (hosting the 2 hackathons). 

Details for this milestone were discussed in our original discussion post [here](https://polkadot.polkassembly.io/post/1585), with the precise milestone and allocation breakdown [here](https://docs.google.com/document/d/1oyip_eVdevsjijQQSkL_GPOE5YF-AEGgE_xhwCFLnt0/edit#bookmark=id.x3kscjjklocs). Our first milestone was approved (and second milestone request discussed) [here](https://polkadot.polkassembly.io/motion/353).

We're already seeing huge excitement around #60DaysOfPolkadot and can’t wait to see what everyone builds at the hackathons! See you there!

Milestone 2 Proposal: Polkadot Developer Hackathons and Crash Course for 1,000 Developers (#60DaysOfPolkadot)

This is a [follow-up](https://polkadot.polkassembly.io/post/1535) proposal on what we submitted in mid-January earlier this year, to further fund the development of the RPC services and to cover the maintenance costs of them.

This new proposal includes one Milestone.

Milestone 1: Continue to run the Polkadot, Statemint and Westend RPC services on dedicated hardware, located at small independent co-location sites in Sweden and in Tunisia.


### Report from Q1 2023

- Our Polkadot RPC node served on average **3,065,667** requests per day and in total **275,910,030** during the last quarter. 
- Our Statemint RPC node served on average **158,022** requests per day and in total **14,221,980** during the last quarter.
- Our Westend RPC node served on average **69,447** requests per day and in total **6,250,230** during the last quarter.

Our full proposal can be [read here](https://docs.google.com/document/d/1v5kotmRSFE6nQQghbZwZlcPgeAvTKLC60KDnu4SO4R0/edit#).

Polkadot RPC services Dwellir Q2 2023

**Proponent:** 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf (OnFinality)

**Date:** 2nd May 2023

**Requested DOT:**  12,141.2773 (USD $64,834.42)

**Short description:** Ongoing costs for the running of high performance, scalable, and reliable public infrastructure for Polkadot, Statemint, Collectives, Westend, and Encointer.

**Full Report:** [Polkadot Q1 2023 Full Report/Proposal](https://docs.google.com/document/d/1T9LnHNap-81QswfQ2yur80rISJAPcHkVzQfc0U54PNM/edit?usp=sharing)

**Raw Data:** [Polkadot Data Q1 2023](https://docs.google.com/spreadsheets/d/1iJpJZlqeeLqMJgmk9zNT-RKx_h1HNbMkFs1PMNySOGk/edit?usp=sharing)

* * * * *

Original Motivation
===================

Over the last 3 months (January, February, and March 2023) we've provided a scalable free public API service so that everyone can access public pools of managed Polkadot, Statemint, Westend, Collectives, and Encointer nodes. This provides the following three outcomes:

-   Grow the ecosystem by reducing the barriers to entry to access a high performance nodes

-   Help scale existing projects in the ecosystem by providing reliable infrastructure services

-   Assist with the testing of all networks by providing valuable data back to the community on how nodes are running, what calls are causing errors, and where traffic is originating from

Service Details
===============

During Q1 of 2023, we've made a large number of stability improvements to our Ultimate API service to allow us to add a large number of new parachains over the last quarter as well as support for multiple chains outside of Polkadot.

For customers that do sign up for paid API keys, we've been adding more and more features to provide a better experience. Geolocation insights provide statistics about where in the world communities are to help influence decisions around where to expand infrastructure and to view the effectiveness of regional BD initiatives.  We can also now automatically upsize the storage on nodes to prevent the risk of any downtime.

Our customers are building cross-chain wallets, running some of the largest block explorers, and are indexing multiple networks - they've all benefited from these API access restrictions, improved monitoring, and the larger number of supported Polkadot chains.

Between 2023-01-01 and 2023-03-31 our Polkadot API service has:

-   Served a total of 4.3 billion responses

-   Accumulated over 50,000 GB of data egress 

-   The highest daily total was 62 million responses in a single 24 hour period for Polkadot only

-   Our rolling 7 day average at the end of this period was over 49 million responses each day

-   Westend had over 110 million API responses in the period

-   Statemint had over 102 million API responses in the period

-   All time totals for Polkadot is 97,192,546,788 (97 Billion) since November, 2020

-   At the end of this period the 90 day uptime for Polkadot, Statemint, Westend, Encointer and Collectives was 99.98%, 99.99%, 99.96%, 99.74%, 99.95% respectively

Enhancements
------------

Additionally, we are proud to have delivered some key service enhancements that benefit the Polkadot ecosystem in the last quarter. This includes:

-   [Auto Expand Storage](https://blog.onfinality.io/onfinality-developer-update-auto-expand-storage-for-dedicated-nodes/) - When the node's storage reaches 85% utilisation, the storage size will be automatically increased by 10%. Saves developers and devOps time on having to constantly check on and manually upgrade their node storage size

-   [Partnership with POKT network](https://blog.onfinality.io/onfinality-partners-with-pocket-network-to-unlock-access-to-unstoppable-infrastructure/) to bring in more external developers into the Polkadot ecosystem

-   [Geographical Insights](https://blog.onfinality.io/onfinality-adds-geolocation-insights-for-dapps-and-api-apps/) - API key owners can view statistics about where in the world your community are to help influence decisions around where to expand infrastructure and to view the effectiveness of regional BD initiatives

-   [Clarify our IP address handling](https://blog.onfinality.io/how-does-onfinality-deal-with-personal-information/) - OnFinality does not, and will never, correlate or link specific wallet addresses to the IP address or request origin making the RPC request

-   We're testing access to various unsafe methods like traceBlock and subscribeStorage that will help developers create applications that utilise XCM - contact us if you would like to be part of the beta

-   Reduced our exposure to any single cloud provider - Progressively migrated resources away from AWS to other cloud providers for lower cost and exposure.

-   Expanded our OnFinality for Startups Programme to support teams from the Substrate Builders Programme and Scytale Ventures

-   Added support for a number of new networks, including Ajuna, Unique, Clover, SORA, Composable Finance, Collectives, xx network, as well as Polygon, BNB, Fantom, Gnosis and Evmos from outside the ecosystem. OnFinality is a new one stop shop for all of your RPC needs from multiple ecosystems.

-   A variety of improvements to our health metric collection tools and automated recovery scripts to ensure our 99.9% SLA is exceeded.

-   Scale improvements to our team, processes, and systems to allow us to provide this same service to any  substrate team

You can always see live data on our API service on our public [status page](https://status.onfinality.io/) and [network analytics page](https://onfinality.io/networks).

**Full report can be read here:** [https://docs.google.com/document/d/1T9LnHNap-81QswfQ2yur80rISJAPcHkVzQfc0U54PNM/edit?usp=sharing](https://docs.google.com/document/d/1T9LnHNap-81QswfQ2yur80rISJAPcHkVzQfc0U54PNM/edit?usp=sharing)

OnFinality - High Performance Public Infrastructure (Q1 2023)

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

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)

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

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

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

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*

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

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

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

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

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

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

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!

Parachain Validation Conformance Testing

Talisman (talisman.xyz) is a community-owned wallet and web application that enables users to “traverse the Paraverse” with ease. We believe in a future where everyone has freedom via true agency over their intentions and finances, and we believe that DotSama will bring this to fruition. 

For more on Talisman’s mission and approach, please see Agyle’s talk at Polkadot Decoded: [Polkadot Decoded 2022: Traverse the Paraverse: How Talisman is bringing multi-chain to the masses](https://www.youtube.com/watch?v=c7tZjVv70Jk)

And Jonathan’s talk about wallet UX at the Sub0 developer conference:
[Talisman: The UX Chronicles: How To Deliver A Substrate Experience To The Masses](https://www.youtube.com/watch?v=a_xiMaDAEiQ)

Today, because of its early stage of development and complex multi-chain architecture, both Polkadot and Kusama are changing rapidly and the user experience (UX) can be confusing for end users. It’s our goal to solve that using design, storytelling, and engineering. We abstract away the complexity of underlying implementation and provide a friendly user experience when using DotSama and a way to discover new applications and services available to end users, while keeping them safe and educated about the actions they are taking.

In this proposal, we are seeking to fund improvements to Talisman Portal, Talisman’s “one stop shop” web application that enables users to discover and access Polkadot ecosystem activities with a focus on simplicity and ease of use. This is an open source dapp that supports multiple Polkadot Ecosystem wallets, including: Polkadot.js (500,000+ users), Talisman (20,000+ users), SubWallet (20,000+ users), and Enkrypt (20,000+ users).

The Talisman Portal is an open source dapp hosted at [https://app.talisman.xyz](https://app.talisman.xyz). It targets the Polkadot Adventurer, a crypto user who believes in the Polkadot vision and spends a large chunk of time exploring and participating in ecosystem activities, including:

- Viewing, managing and organizing multi-chain assets (tokens, NFTs) and accounts
- Generating a return on investment for their portfolio (we do not provide financial advice, but rather allow users to better understand their positions and opportunities)
- Discovering and participating new dapps and services available in the ecosystem, such as crowdloans (live) and governance (targeted for later in 2023)
- Education and learning about Polkadot, the ecosystem and dapps and services that are available

Directly enabled by the work in this proposal, includes the UX work around Talisman’s nomination pools, which has led to Talisman's nomination pool garnering the largest amount of DOT since launch (>1 million DOT). This is a testament to the simplicity of the staking experience provided by Portal, combined with our trusted brand for new and experienced users. We hope to continue to enable users to stake easily no matter how much or little DOT they have in their accounts.

More than just providing a feature set, Portal is designed with the user first, because UX and design are incredibly hard problems in a multi-chain and quickly-evolving environment. Polkadot Adventurers are committed to being in Polkadot, but they need trusted tools that simplify the experience and enable them to become evangelists that ultimately bring new users into the ecosystem.

The following feedback is from a recent user survey in Feb 2023 about Talisman Portal:

- “Being easy to use is why I recommend it to my normie frens”
- “I consider the strength to be viewing cross-chain assets all in one place”
- “Definitely better UI/UX and easier to use than Polkadot.js”
- “Awesome design and an essential tool for day to day use of Polkadot”
- “The super simple interface gives me peace of mind when dealing with my money”
- 90% consider staking easier to use than Polkadot.js or the most convenient way to stake DOT




The full proposal is [here](https://docs.google.com/document/d/1OlJB4a2kcgWe-TZTC4ZR5cU9ZEIk8IoC85IJv2_2rdc/edit?usp=sharing).

This submission follows from the following forum discussion: [link](https://polkadot.polkassembly.io/post/1699)


Talisman Proposal: Portal Web Application supporting Nomination Pools and more - Milestone 1

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)

As three more parachains have requested an HRMP channel opening with Statemint, this proposal aims to accept and open return channels - the following batch call aim to be executed on this proposal for each of the parachains:

1. A `forceTansfer` of 20 DOT from the Treasury to Statemint sovereign account.
2. A `forceOpenhrmpchannel` from Statemint (1,000) to [ParaID].
3. A `forceOpenhrmpChannel` from [ParaID] to Statemint (1,000).

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

- BitGreen: ParaID 2,048
- SubSocial: ParaID 2,101
- Manta Network: ParaID 2,104

Encoded Call:

`0x1a040c1a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000000080000e8030000009001003c0700080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000035080000e8030000009001003c0735080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000038080000e8030000009001003c0738080000e8030000e803000000900100`

Proposal Hash: 

`0xaed18f873e30ac5f2e80c5323fcca4c654c7a6eb2ffd0dc1755028ba87eb6352`


Three New HRMP Channels batch On Polkadot

**EXTRA NOTE ON THE REJECTION SUGGESTION:**
###
While the proposal moved to external queue to be voted by the community after Council approval, the Acala team noticed an issue with the runtime release: The XCM weight isn't benchmarked for Polkadot and the base weight is used, which assumes each XCM instruction takes 64k proof size. For XCM message with 1D weight, a default proof size of 64k is used. This means xcm buy weight with limited 1D weight will fail on [this line](https://github.com/paritytech/polkadot/blob/f1a45b39db6dbb7610c80b82d7cfca45a807619d/xcm/xcm-builder/src/barriers.rs#L96): this only impacts XCM V2 instructions using limited weight. Unlimited weight is fine.

The teams are now studying on what appropriate value should be put into the proof size weight component for BaseXcmWeight: once this is decided, a new release will be cut and the proposal will be submitted for vote again. 

For now, this proposal can be cancelled/rejected.
###
__________________________________________________________
###
This proposal aims upgrade Polkadot relay chain to runtime [v9381](https://github.com/paritytech/polkadot/releases/tag/v0.9.38-rc12) and Polkadot System Parachains (Statemint/Collectives) to runtime [v9382](https://github.com/paritytech/cumulus/releases/tag/parachains-v9382): the specific details on this upgrade please check the release notes. This release contains the changes from v0.9.39-1 to v0.9.38-rc12. **Among other things, this upgrade includes XCMv3 on Polkadot**. Please note that two calls for the System parachains upgrade are `xcm.send` extrinsics that send `authorize_upgrade` messages to Statemint and the Collectives, while for the relay chain upgrade is `setCode`
###
- Call Hash: `0x1f099c751e66ce10f619564a25f2c6d7b6cbc4fdc29baa2ea991762f1a782bcf`

- Preimage is submitted and can be reviewed [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot.api.onfinality.io%2Fpublic-ws#/preimages).


**Relay chain Runtime**

- [S] ✅ trivial [#13065](https://github.com/paritytech/substrate/pull/13065) Low - Allow duplicate topics in smart contract events

- [S] ✅ trivial [#13105](https://github.com/paritytech/substrate/pull/13105) Low - Scheduler is already at v4

- [P] [#4097](https://github.com/paritytech/polkadot/pull/4097) Low - Xcm v3

- [P] ✅ trivial [#6490](https://github.com/paritytech/polkadot/pull/6490) Low - Enable treasury.spend by root origin for polkadot network before gov2

- [P] ⏳ pending non-critical audit [#6573](https://github.com/paritytech/polkadot/pull/6573) Low - Allow auctionadmin to use scheduler

- [S] ✅ audited [#13214](https://github.com/paritytech/substrate/pull/13214) ❗️ Medium - [fix] countedmap::set now takes counter into account

- [S] ✅ audited [#13204](https://github.com/paritytech/substrate/pull/13204) Low - Contracts: deprecate random interface

- [S] ✅ trivial [#13194](https://github.com/paritytech/substrate/pull/13194) Low - Correct arithmetical semantic of perdispatchclass

- [S] ⏳ pending non-critical audit [#11637](https://github.com/paritytech/substrate/pull/11637) Low - Add proof size to weight output

- [S] ✅ trivial [#13235](https://github.com/paritytech/substrate/pull/13235) Low - Migrate new benchmarking syntax from frame_support::benchmarking to frame_benchmarking::v2

- [S] ✅ trivial [#13216](https://github.com/paritytech/substrate/pull/13216) Low - Remove uncles related code
###
This proposal is submitted as an external motion: meaning if/after Council approves the motion, the community will have the final say in referenda queue.  

Make sure to vote at your convenience!

[TO BE REJECTED] Runtime Upgrade v9381 for Polkadot and v9382 for System Parachains

**Proponent:** 5D5TJ7cNZWuRgXYe4oxizBqWG31eJ1iFpY24JU2jzDccEiwY

**Date:** 10 April 2023

**Requested DOT:** 4201.0828

**Short description:** Ongoing costs for 2022, for the running of public-good SubQuery Dictionary Projects which serve pre-computed indexes of each block for most Polkadot and Kusama parachains. These public projects enable the parachain teams and teams within their ecosystem to increase the data indexing speed of their SubQuery projects by up to 10 times.

**Full Proposa:** [https://docs.google.com/document/d/1SjoBgDzX-fJmVWLXQPhQlpy29oimRbHD42tQjGdqgdY/edit?usp=sharing](https://docs.google.com/document/d/1SjoBgDzX-fJmVWLXQPhQlpy29oimRbHD42tQjGdqgdY/edit?usp=sharing)

**Raw Data:** <https://docs.google.com/spreadsheets/d/17829KgXp5aXKXkaPw7A7oCgjMBB8vEuCg2Pyk1MGQnY/edit#gid=0>

Original Motivation
===================================

SubQuery is the universal data indexing toolkit facilitating the construction of Web3 applications of the future. A SubQuery project is a complete API to organise and query data from Layer-1 chains. Currently servicing Polkadot, Kusama, and other layer-1 chains in Substrate, Avalanche, Algorand, Terra, NEAR, and Cosmos projects, we provide data for developers to use for a wide array of projects (wallets, explorers, custom chains, or any other decentralised app). In the future, the SubQuery Network intends to replicate this scalable and reliable solution in a completely decentralised manner.

Throughout the whole of 2022 (01/01/2022 - 31/12/2022) we've provided public SubQuery Projects, termed Dictionaries, for most parachains in the Polkadot and Kusama ecosystem to dramatically increase indexing performance (up to 10x faster) and so far these dictionaries have served over 1 billion requests.

A SubQuery dictionary is a special SubQuery Project which scans over the network, and records metadata of every event and extrinsic on each block. When other SubQuery projects index data on any of these chains, they can ask the dictionary what blocks a filtered list of events/intrinsics appear on. Rather than having to search through each block, dictionaries reduce the amount of data that the indexer obtains from the chain, reduces load on free RPC endpoints across the ecosystem, and reduces the number of "unwanted" blocks stored in the local buffer. For example, instead of SubQuery inspecting each block of Polkadot's massive chain (600GB of unstructured data on over 12 million blocks) which can take many hours, dictionaries skip through to the exact right blocks.

Adding the dictionary  to optimise indexing performance is as easy as adding the relevant network dictionary endpoint to your SubQuery Project. This has been added by default to all of our starter projects to make it default to use.

Here you can find detailed documentation on how dictionaries work: <https://academy.subquery.network/academy/tutorials_examples/dictionary.html#>

SubQuery Dictionaries have been created for most parachains to the public here <https://github.com/subquery/subql-dictionary> and have been deployed to our Managed Service. If any other team would like a dictionary created - we are more than happy to help out.

Future Targets for Our Dictionaries
===================================

- We're proud of our record on stability and reliability. One of our core values is to be blockchain's most reliable indexer, and we don't intend to lose sight of this as we onboard more chains and expand the number of customers relying on our hosted service for their production applications. Our goal for 2023 is 99.99% uptime, we're starting off strong with 100% so far as seen [here](https://status.subquery.network/uptime/f3j5qtmn4rhd).

- Through 2022 we ran 24 dictionaries for the in-demand parachains that we believed would add most value to the dApp developers in the Polkadot and Kusama ecosystems. Moving forward we want to be able to offer the increased indexing performance to all active block-producing parachains, our goal will be to add 20 more dictionaries to our suite of tools in 2023.

- Being on the cusp of 1 billion requests to our dictionaries in 2022 has left us hungry to smash records in 2023. This year, with the launch of our decentralised SubQuery Network and ongoing Business Development efforts, we are looking to hit (and surpass) a target of 10 billion requests to our dictionaries.

- Github Contributors. Our [dictionaries are completely open source](https://github.com/subquery/subql-dictionary), and SubQuery is a community project with a goal of complete decentralisation. Already last year, we welcomed contributions to our dictionaries from developers at Nodle and Subscan. We are working on making it easier for new parachains to assist us with creating dictionaries.

Service Details (Polkadot)
==========================

Between 2022-01-01 and 2022-12-31 our Polkadot Dictionaries have:

- Served an extraordinary total of 733,069,683 (over 700 million) requests

- The Polkadot Dictionary alone served 630,818,299 (over 630 million) requests

- The highest daily total of the Polkadot Dictionary was 19,219,650 requests in a single 24 hour period occurring on 22nd July 2022

Maintained availability at >99% uptime via our SubQuery Managed Service ([see uptime monitoring here](https://status.subquery.network/))


**Full proposal found here:** [https://docs.google.com/document/d/1SjoBgDzX-fJmVWLXQPhQlpy29oimRbHD42tQjGdqgdY/edit?usp=sharing](https://docs.google.com/document/d/1SjoBgDzX-fJmVWLXQPhQlpy29oimRbHD42tQjGdqgdY/edit?usp=sharing)

High Performance Data Indexing Tool (2022)

The proposal aims to seek support from the Polkadot Treasury for the 2023/3-2023/8 operating cost for the Chinese non-profit organization Polkadot Ecology Research Institute, in order to create more original and quality Chinese content, and to relay the otherwise boring technical language to Chinese users in a colloquial way, so that Chinese users can have a real knowledge of Polkadot and increase the breadth of Polkadot in the Chinese market. On the other hand, we will also follow up on the outstanding projects of the Polkadot ecology to keep everyone informed of the latest developments of the Polkadot ecology.

Polkadot's success cannot be separated from the prosperity of the Polkadot Ecological Projects. Our goal is to make more people aware of Polkadot and also to make more people aware of the development of Polkadot ecology, which in turn will lead them to join in the participation and construction of Polkadot ecology, so that Polkadot and Polkadot ecology can flourish.

Since September 2022, [we have established a Polkadot Treasury proposal for our 2022/9-2023/2 operation cost, and get funding from the Polkadot Treasury](https://docs.google.com/document/d/1-b_DQXHVyRuAoYubCtL9dk0R6a_ev7xbwYMV518ONpo/edit?usp=sharing). Here is our [report for the proposal](https://docs.google.com/document/d/1nTIn83LJ9qcq4jPfZDHM-6-xA9Me1JyQ_pCxgPFXYO0/edit). Please check our report to learn more.

So this is a proposal for our six months operation cost. We apply approx 104,760.00 USD total allocation for 2023/3-2023/8 and [you can get all details here](https://docs.google.com/document/d/1oJjtkZD8mgv5vRpBh_aoGmWqWlLK9tomGhP8M9esMng/edit?usp=sharing).

Treasury proposal: The 2023/3-2023/8 operating cost for the nonprofit organization Polkadot Ecology Research Institute

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

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

**Link to Full Proposal**:
[Connect the DOTs - Proposal](https://docs.google.com/document/d/1CduiRi_ZF9StcKSSWeJqYzVOU_hwsFoImirZOhqBfsc/edit?usp=sharing)

**The Current Problem with Polkadot**
 
Today, information within the Polkadot ecosystem is located across individual parachain/project websites, social media sites, and videos/podcasts. Information remains siloed and difficult to access for users depending on their purpose. The “hub” sites that do exist fall victim to Polkadot’s achilles heel: technical heavy, data repository interfaces that don't focus on the user experience. Polkadot has some of the best tech in the world and we want to help make this beautiful technology accessible to masses. 

The end result of this: Polkadot is being held back from its full potential. The average new user does not know where to begin or gets scared off when they’re asked to interact with developer style interfaces. We can see this across a broad depth of market data. Polkadot always leads in developer activity, and yet gets nowhere near the activity and traction as many ecosystems that are less developed and less impressive technically. 

**The Solution** 

Our overarching objective is to help participants better navigate the Polkadot ecosystem: increasing exposure and understanding by aggregating “everything Polkadot” and presenting digestible, key information in a simple user interface (“UI”). We will accomplish this by collecting and gathering information via a variety of sources, maintaining a community database, and building a user-friendly front end website. 

Our project will always focus on the end user. Whether the user is new to crypto or a seasoned veteran of the industry. Being a one-stop-shop can be daunting, so we will start with two smaller goals:

1. Be the best, intuitive onboarding tool for new users

2. Connect with teams, collaborators, investment teams, foundations, etc to define and curate the proper direction on where the ecosystem is headed

We do not want to present data merely because we collected it. Rather, we want to synthesize the disparate data and present it in a way that users can easily interact with in a simple manner. 

Collectively, this encompasses our main objective: making the Polkadot ecosystem easy to understand and navigate regardless of who you are.

**The Results**

As part of our process, we will be focusing on specific results in order to determine if our efforts are paying off. The first result will be general traffic to our website. Every visit that goes to a website that focuses on Polkadot and the surrounding ecosystem will help drive awareness and adoption. The more eyeballs and clicks we can get, the broader the reach becomes.

The second result will be to drive traffic to DApps of teams. Onboarding users is where everyone must start, but from there we want to help users take full advantage of the ecosystem. By helping explain what DApps can accomplish, curating different ways in which they can be used, and providing links to DApps themselves as well as helpful content from around the internet, we will be able to leverage our user reach to help benefit all DApps across the ecosystem. 

Connect the DOTs

Contextual Information from the team, below:

**Proposal**

A proposal requested by the Watr team to reset the blockchain back to seedling. Contextual information can be found below.

**Context**

We tried to reset a technical genesis (pre-commercial deployment of runtime) of Watr. The current parachain model doesn't allow privileged operations such as a reset without either tokens in the sudo account, on-chain governance accounts or relay chain governance. However the tokens generated in this genesis block are locked and unusable. So we are unable to perform the reset and progress to commercial deployment. As such the network is locked and unusable without intervention from relay chain governance.

**Impact**

The network is locked and cannot be used or reset without intervention from relay chain governance. Whilst Devnet is active, the reset will be purely a technical rollback since our Parachain has not gone live to user transactions or funds yet. There is no risk to other applications, other Parachains or the relay chain.

**Remedy**

We have explored all other solutions and after discussion and advice from Parity experts, have created this proposal to reset the Parachain to seedling state so we can progress to commercial deployment of the Watr Parachain.

**Proof of Authenticity**

We submit the following proof of authenticity, signed by the registrar of the Watr Parachain (id: 2058) `13DgtSygjb8UeF41B5H25khiczEw2sHXeuWUgzVWrFjfwcUH`,

- Text: This proposal has been submitted to Polkadot governance by the Watr Team with pre-image hash `0x2929e149de9d487466fed4093f721f68cfcdce1600e8d44e4b5b5c725efebcc3`. We confirm our intention to update the genesis state to `0x0000000000000000000000000000000000000000000000000000000000000000001a3a2baafaa9623dbeab06759b78f4bce878d0fbfeef992a546bce6670131e6103170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400` and the runtime to (Blake2-256) `0x900f07dfc7cfa4567f2f8ee94fb18793c79d46f233331913516c82a8ea379095`

- Signature: `0xa096627fbd5cd2ec0ad77fc7687e7201aedc5d793bede53df7dd7dc74d45a12d6d30a88bd4cde6fc72456524577c80f6bf2fd62099ca7065b445a564a9631387`

**Preimage**

Below is the preimage:

- Hash: `0x2929e149de9d487466fed4093f721f68cfcdce1600e8d44e4b5b5c725efebcc3`

- Extrinsic: 

utility.batchAll(

paras.forceSetCurrentCode(2058, [newCode](https://github.com/Watr-Protocol/seedling/blob/main/watr_runtime.compact.compressed.wasm)),

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

)

**Make sure to vote at your convenience! Please note this proposal is submitted as an external motion: meaning if/after Council votes, the proposal will pass to referenda queue for the community to make the final decision.**

Reset Watr Parachain

Hello everyone,

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

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

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

Thank you for reading

Jesse Chejieh

Treasury proposal: sc-simnode continuous development and improvement financing

UPDATE: please reject.
The deposit was returned to the team via a Tip approved with OpenGov Referenda #28
Motion 377 was a proposal submitted with the goal of funding the development of cross-platform tip-as-you-go functionality by Anagolay to streamline community support for verified creators and builders. The motion didn't reach majority vote, with little feedback provided by the Council. After careful consideration, the team has decided to not pursue Treasury funding at this time and concentrate our time and efforts on a different route.

UPDATE: We ask the Council to reject this proposal, and endorse the tip for the reimbursement of the deposit: [500 DOT](https://polkadot.polkassembly.io/tip/0x8fb68b374450ee4780db4770a44194d1fc0cc0ad6402c36d18d89ec5987e7783)

Hi everyone, Daniel of Anagolay is here. 

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

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

Including, most recently: 

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

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

# Current Proposal Scope & Objectives

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

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

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

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

## Value

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

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

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

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

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

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

Anagolay proposal: enabling community contributions for verified creators

Contextual Information by the team, below:
###
ETH Denver, the flagship event of the Ethereum community draws in a lot of the active community as well as newcomers to the space. By showing up at ETHDenver awareness and builder and developer leads with high interest in blockchain are generated - newbies looking to build their first project and/or contribute to the tech stack, as well as teams already building in the Ethereum community and looking for new project opportunities. In addition to new leads, the event is a great opportunity to connect with those already familiar with Polkadot, and grow the relationship.

Polkadot successfully participated in last year’s edition as a Diamond sponsor, and organized several ETH Denver BUIDLWeek talk sessions. For this year’s event, the goal is to give Polkadot and the ecosystem teams even more visibility and to book a higher-level sponsorship package. The participation would encompass a Cypher sponsorship package, and a mini summit during BUIDLWeek.

The following teams have confirmed their participation at ETHDenver activities: **Astar, Unique Network, Phala Network, Zeitgeist, Gear, RMRK, OAK Network, Pendulum, Moonbeam, InvArch, Apillon, Crust, Acurast, Manta, Solang, DAM Finance.**

Further information on the proposal, including milestones, budget, agenda, participants and more can be found on [**THIS LINK!**](https://docs.google.com/document/d/1WUawdiqvX08wG-BNf0Jc2pYQROfGv7Xj2XZA5x-ofGY/edit)

Polkadot @ ETHDenver 2023, February 24th - March 5th in Denver, Colorado

Proponent: Pinknode

Date: 14/03/2023

Amount in USD: $20,093.46 

Amount in DOT:  3447.74 DOT 

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

DOT Account: 14K2YrPm8TTo8aNMqp7FJjbpysi7vm1j7QjKg86q6W6wVzPr

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

Project Summary

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

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

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

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

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

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

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

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

Service Details

From 1 October 2022 to 31 December 2022,

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

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

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

Enhancements during Q4 2022:

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

-Moved request log storage to AWS S3 for faster UX

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

-Upgrades to our proxy for more accurate logging

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

Our status page is publicly maintained.

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

Pinknode Public Endpoint for Polkadot in Q4 2022

- Proponent: Simon Hipkins (Key Pictures)

- Beneficiary: Ihtiyac haritası (NeedsMap.coop) 1haY6iHgLopw2WWmPhcdCy2jwzL2jthbNL515rUyJtnmhUt (verification [here](https://twitter.com/ihtiyacharitasi/status/1632116990390288391?s=20)).

- 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 project that will help people recover from this terrible disaster.**

- Proposal discussion post can be found [HERE](https://polkadot.polkassembly.io/post/1672)
- Onchain submission, taken into account community feedback: [HERE](https://polkadot.polkassembly.io/treasury/253)
- Proposal document can be found [HERE](https://docs.google.com/document/d/102KiQRMjDSemj8eSNCYJe8VSwOc_aMbqBU6mXbjJbms/edit).

Please note that given the amount of the requested allocation, this is submitted as an external motion: if/after approved by the Council, this proposal will be voted in referenda queue by the community for the final decision. 

External motion proposal hash: `0x60d0920c817310650378d7227c3bd7de10135479822262b088c2db361dbceac1` (preimage is submitted).

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

**Proponent:** 16HqymHVxdLtK8jtbur7DusQrfLAVEJZfsQijfxVwhQHiTgU

**Date:** 17.03.2023

**Requested DOT:** 76,620.00

**Requested USD:** 463,627.62

**EMA7:** 6.051

**Short description:** Development of an open-source web API system to ‘bridge’ enterprise IT and the Polkadot blockchain ecosystem.

Please note this motion is a batch call, rejecting [treasury proposal no. 247](https://polkadot.polkassembly.io/treasury/247) and [treasury proposal no. 248](https://polkadot.polkassembly.io/treasury/248) and approving [treasury proposal no. 251](https://polkadot.polkassembly.io/treasury/251): while submitting, the Aventus team made mistakes on submissions regarding the amounts for the first two proposals, and they need to be rejected. 

Contextual information for the treasury proposal to be reviewed and vote can be found [HERE](https://polkadot.polkassembly.io/treasury/251). 

Discussion post can be found [HERE](https://polkadot.polkassembly.io/post/1647). 

Polkadot web2/web3 API middleware development

**Proponent:** 126jig5aDPSkrR6dkdZY3smcPHAbq7GAQyDSwf4KpPgCNZGu

**Date:** 16.03.2023

**Requested DOT:** 15008 DOT (USD $89,058)  (Rate: 5.934 USD/DOT based on a EMA7 rate on [subscan](https://polkadot.subscan.io/tools/charts?type=price) on 16th March, 2023)

**Short Description:**  [Blockchained India](https://linktr.ee/blockchainedindia), the oldest and the largest blockchain community in India, is proposing the "60 Days of Bootcamp" program, aimed at supporting the Polkadot network in connecting with the developer community and helping developers enter the Polkadot and Substrate ecosystem. With a focus on training and support, this program is designed to help developers in India, the second-largest developer community in the world, become proficient in the Polkadot ecosystem. Blockchained India has a proven track record of working with leading blockchain protocols, including Polygon, Cosmos, Zilliqa, ConsenSys, Binance, and is well-suited to guide developers on their journey into the world of Polkadot.

**Recognition of Successful Programs Conducted by Blockchained India**

[100 Days of Code with Zilliqa](https://koinpost.com/2020/09/02/want-to-become-a-blockchain-developer-in-100-days-check-out-100-days-of-code-by-indian-blockchain-community/)

[India’s Largest Dapp Fest](https://www.thehindu.com/sci-tech/technology/india-dapp-fest-2019-first-global-blockchain-meet-up-bengaluru/article27762404.ece)

[ConsenSys India Launch by Blockchained India](https://archive.factordaily.com/ethereum-joseph-lubin-interview-india/)

**Goal**

The goal is to address the challenges facing Indian developers who want to learn and build on the Polkadot network. Through the "Polkadot Developer Bootcamp - India" initiative, we aim to provide access to experienced Web 3.0 teachers and trainers, as well as industry experts, to help young and talented developers learn about the Polkadot network. We also aim to create a supportive and sustainable ecosystem for working developers who want to transition from Web 2.0 to Web 3.0 and explore building solutions on the Polkadot network. This proposal would significantly improve the experience of Indian developers in the Polkadot network and would help build a strong and sustainable community in India.

Please find the full details of the proposal (including current problem, solutions, milestones, tasks, timelines and costs for the proposal) here:  [Polkadot Developer Bootcamp - India 2023](https://docs.google.com/document/d/1vpYrY2aBIuzXf0NaQc2UKL9s6isVbtPDbJHZQhpgEdE/edit?usp=sharing)

Thanks for taking out the time to read through, we would appreciate your feedback and comments. We hope you have a blessed year ahead, full of prosperity and success!

Polkadot Developer Bootcamp - India

Greetings Council Members!

As we all witness the rapid growth of WEB3 technologies, it's crucial that we make sure the adoption of these technologies is inclusive and reaches every corner of the world. 

That's why we're excited to introduce **1TRIBE**, a digital multimedia education initiative that empowers Africans to participate in the decentralized WEB3 economy, with a focus on the **Polkadot** ecosystem 


After engaging with the community for [feedback](https://polkadot.polkassembly.io/post/1534) through platforms like **AAG** and **The Kusamarian**, we're thrilled to have received a lot of community support. 

However, some council members abstained from voting and following feedback from members of council and community, we have refined our proposal to better articulate our project.

As a **pro-African** WEB3 multimedia platform, we know that using all available mediums to disseminate our message of WEB3 education and empowerment to African youth is crucial. That's why we've made it our mission to incorporate an **online radio** format into our platform. Our hybrid platform allows us to convert our series of themed video content into online-radio format, ensuring that our message reaches a wider audience and that none of our content goes to waste.

Our goals for 1TRIBE are simple:

- **Foster** a diverse community of Africans, Africans in the diaspora, and people of African descent from around the world who are interested in Web3 and the Polkadot ecosystem.

- **Drive** interest in Web3 and Polkadot by seamlessly incorporating African lifestyle, music, art, and innovation.

- **Educate** Africa's budding entertainers, artists, musicians, and students about the potential of Web3 and Polkadot.

- **Provide** a platform for discussions and education about Web3 and Polkadot.

- **Encourage** the development and growth of the Web3 ecosystem in Africa.

By achieving these goals, we firmly believe that 1TRIBE will play a vital role in bridging Africa to the future with Polkadot. 

- **The Kusamarian** talking about 1TRIBE: [here](https://twitter.com/i/spaces/1OwGWwvRQRRGQ) - kindly start from 1:38:00
-  **AAG** YouTube live.- [here](https://twitter.com/thekusamarian/status/1615133275944816642?s=46&t=KDYfuaY2d2OeeQpz_7wo6g) - Kindly skip to 14:00

You can find all details in our full proposal [here](https://docs.google.com/document/d/1rbFrMr7vxaObJjHW8MSzfYpI-vfyRY6kEV3QIPFgF10) 

Our weekly and Daily Programming [here](https://docs.google.com/document/d/15REymnJj8Fq0mWzaG9dmkulNXHzhyXzcxjfLi_BgoO0)

Our total budget breakdown [here](https://docs.google.com/spreadsheets/d/1K2HSYvIpxoMMgXPPc_XSu7iBd-bDd_Gd6YQiR3L4HT8) 

1TRIBE KPIs and metrics [here](https://docs.google.com/document/d/1wnyE0Bd6I9EaCqUwQe89IkMONJx2RSUb-CiD0foY80w)


1TRIBE Team [here](https://docs.google.com/document/d/1lSs2UCPODcvVOT0J98IdU_Kn1oJ6MAn0VdOs_aLfO8k) 


Ankh Wedja Seneb

1TRIBE

1TRIBE: Bridging Africa to the Future with Polkadot

Hello community,

Thank you for your support and feedback on our original [discussion on the forum ](https://forum.polkadot.network/t/polkadot-purple-paper-token-morphism-guidelines/2023)for conducting legal research around DOT token morphism. 🙏
We are now presenting this proposal after absorbing feedback.

### Context
In earlier phases of Web3 - namely 2017 and 2018 - there was extensive debate about the legal nature of tokens and the process for getting those tokens acknowledged by regulatory bodies such as the SEC. Amidst the frenzy of the latest bull run, those debates have somewhat subsided. In a post-FTX market, with even more scrutinous regulatory eyes fixed upon crypto, those debates and the need for best practices for undergoing regulatory recognition have reemerged as even more critical pieces of knowledge for web3 builders. In this environment, Polkadot’s efforts and ultimate success in the regulatory arena warrant study and dissemination to the wider web3 community. It is in this spirit that we submit our grant request to the treasury

We have already had informal discussions with the individuals most involved in the DOT related regulatory process, who all expressed initial interest in contributing to the initiative. Given this, we feel confident in our ability to fully develop our research themes.

The professionals we spoke with who manifested in general terms willingness to support the initiative are:

[Joshua Ashley Klayman](https://www.linkedin.com/in/joshua-ashley-klayman/)

[Angela Dalton](https://www.linkedin.com/in/angela-dalton/)

[Chrissy Hill](https://www.linkedin.com/in/chrissy-hill-aa76828/)

[Daniel Schoenberger](https://www.linkedin.com/in/daniel-schoenberger-9107836/)

We aim to produce a Research paper regarding the SEC DOT regulatory process, outcomes and recommendations for Dotsama and the wider Web3 ecosystem. [See full proposal here.](https://docs.google.com/document/d/1oIJ22m_Q07lB832x8gIMwHVjzfUEIkgAK_NsqrhsTiI/edit?usp=share_link)

Polkadot Purple Paper / Token Morphism Guidelines

Polkadot Developers Conference // sub0 is the conference for developers building at every level of the Polkadot tech stack — from custom layer-1 blockchains to dApps and smart contracts, infrastructure, tooling, cross-chain interoperability solutions, and more.

In 2023 sub0 will return to Lisbon and is seeking funding from Polkadot Treasury. The last edition took place in LX-Factory in Lisbon on November 28th and 29th, 2022, Web3 Foundation, together with the teams of Apillon, Phala Network, Astar Network and Manta Network in representation of the entire Polkadot ecosystem brought together the global Polkadot developer community.

Sub0 will again provide an open introduction to next-generation multichain networks, as well as a chance for existing Polkadot and Substrate developers to deepen their skills and connect with each other. For this year's edition we want 50% of our audience to be new developers from outside of our ecosystem. This includes people who are not building on Substrate but are curious to learn more. By opening our doors to developers who are not (or only slightly) familiar with our tech, we can bring in more potential builders and expand our market reach and visibility. 

THIS IS THE FUNDING REQUEST FOR MILESTONE 1 AS PER THE BUDGET DETAILED IN THE DOC BELOW.

Further information on the proposal, including milestones, budget, agenda, participants and more can be found on [THIS LINK](https://docs.google.com/document/d/11eaFr7OlOGOIQpskRopBUR_KizmHRmd3U-QRmcyA_g0/edit?usp=sharing)!

Polkadot Developers Conference // sub0 Europe // Milestone 1

Hi, community！

This is a [follow-up proposal ](https://docs.google.com/document/d/16X0L0F5MOj_PDJKf8gkxKBMmn7DnuoaZTWc4KjwjLnI/edit#) from PolkaWorld to seek to cover the next three months (March 2023 to May 2023) of ops and maintenance costs to further promote and support community education for the entail Polkadot ecosystem.

PolkaWorld converted the W3F community grant to an open social contract with Polkadot Treasury in June 2021. Up to now, we have summit 7 Motions, and all works are done in very high quality. And in 2022, we have:

- published a total of 576 articles and received 412,000 views in the WeChat ecosystem in 2022
- hosted 42 online broadcasts on Wechat Channel and 21,551 people joined us
- made 35 education videos, got 28,759 views on Wechat Channel and [YouTube channel](https://www.youtube.com/playlist?list=PLxPIfUrFmx1PBx0-BL7hUT9a0W5EBhSKV)
- interview with 23 teams in the Polkadot ecosystem, all are posted on our [YouTube channel](https://www.youtube.com/playlist?list=PLxPIfUrFmx1NIVhwiuYYatONMImf9cyre)
- hosted 14 online meetups, and 8,348 people joined us online

You can also learn some of the delivery [here](https://polkadot.polkassembly.io/motion/297#25f51256-08f9-4e89-a4d5-faef86081edd).

PolkaWorld will continue contributing to the Polkadot ecosystem in 2023. Please check all the delivery reports, details for the next 3 months’ milestones, tasks, and the budget [here](https://docs.google.com/document/d/16X0L0F5MOj_PDJKf8gkxKBMmn7DnuoaZTWc4KjwjLnI/edit#). Love to hear all your advice or any feedback.

PolkaWorld Ops and Maintenance proposal：2023.3 - 2023.5

Dear community,

We're proud to present our next proposal from the Sublab team which primary focus is on developing tools for developers in Substrate ecosystem. This proposal is published after 10 days since the discussion was published.

Please feel free to read the full proposal document at this link: [https://docs.google.com/document/d/10ipyb2_d1d9FCYY4Xp3aRi5CZmZJOzbqBZ50hQMerUI/edit?usp=sharing](https://docs.google.com/document/d/10ipyb2_d1d9FCYY4Xp3aRi5CZmZJOzbqBZ50hQMerUI/edit?usp=sharing)

![](https://sublab.dev/logo.png)

**Context of proposal**

[sublab.dev](https://sublab.dev) is the California based company designated to develop fully native open-source libraries for mobile platforms in Polkadot and Kusama ecosystems, covering everything with reliable unit-tests and providing rich documentation to the developers community. 

We've recently finished our [very first proposal](https://kusama.polkassembly.io/motion/532) within which we created 13 Swift and Kotlin repositories to operate with Substrate networks. While we have basic functionality, we still need to develop more features to reach current ecosystem state and its functionality. Also, we agreed to collaborate with a couple of projects in ecosystem to develop base SDKs for their services in Swift and Kotlin, and chose extra providers to develop SDKs for, which cover most popular functionality in mobile applications. Furthermore, we now seek to make our Kotlin libraries be written fully in Kotlin and use only Kotlin libraries so that we can make our libraries ready for Kotlin Multi Platform.

This proposal is expected to be a first step out of two in series of milestones to come as close as possible to current ecosystem state. Also next milestone is suppose to cover improvements/fixes to existing libraries and more collaborations.

**What we're trying to accomplish within this milestone**

Most of our efforts are projected to be put into Substrate client we made for Swift and Kotlin. 

Primary purpose is to create pre-created set of models and functionality like popular and common between all networks constants, storage queries, functions and events, so end developer will not need to always write boilerplate code. This potentially saves thousands of hours if we take into consideration multiple teams working with these libraries. Also we want to boost our extrinsic service to have all day-to-day methods in it: fees estimation, transfers, batch requests, and so on.

Secondly, we want to develop special manager which will be capable of handling hundreds of simultaneous clients at the same time. Mobile devices even though they're powerful nowadays still not almighty. Application sandbox is limited, thus in order to work with many networks in parallel we wish to create set of functions and classes which will be responsible for turning on and off all clients depending on current app function optimizing CPU and RAM usage. 

To make this manager it's also needed to have some caching mechanism: we propose to create a database which will be responsible for storing everything from these multiple connections, work with pre-defined common constants, storage queries, functions, and events, combining everything together to speed up and optimize cold and hot starts of Substrate client instances.

Last but not least part of Substrate client improvements in this milestone is to provide support to work with all existing parachains. Every network has their own runtime which sometime differs very much. So we look forward to create as many as possible unit tests to check compatibility of our Substrate client with every existing parachain today. Indeed this would require a lot of internal client changes. So we will do our best to keep our codebase clean and tidy, and at the same time powerful to handle dozens of different networks, and hundreds of connections.

Also, in this proposal we're looking forward to making a set of small libraries to provide SDK interface to most popular block explorers which are used for fetching history and many more: SubQuery, Subsquid and Subscan. For now, we decided to develop basic interface so that we don't dive too deep into all functionality and get burden of supporting it all. In this proposal we want to provide functionality that allows developers to use all of the service features, but maybe with small tweaks. However, we might find some solutions to do later to optimize and avoid this extra customization. As extra, there will be couple of token/fiat exchange rate resolvers to choose from.

In parallel, there are two small projects. Provide Combine interface in our Swift libraries so that Swift developers can choose what asynchronous approach they would like to use in their application. And Kotlinization. This is very special project for us: we have created a few of libraries in Kotlin from scratch like schnorrkel algorithm. And since we still rely on some Java libraries, it is not that easy to make our Kotlin libraries compatible with Kotlin Multi Platform. This technology opens a big opportunity to use our libraries in many different platforms from mobile applications to web, so we're encouraged to make our libraries ready for this bright future.

**Our mission**

We want the Substrate ecosystem developers to just do brand new features to make the ecosystem richer and be recognizable by even more people around the globe, while we can hold their backs by doing a great infrastructural work. We want to see more mobile apps in the ecosystem either from existing parachains to launch their own apps or absolutely new mobile wallets with more innovative functions. Same we want to help existing applications by solving their core issues within our works and help them adopt our products. Also we aim to partner with as much as possible existing networks and/or companies who already deliver their services to ecosystem, so that even their products might be easy accessible via reliable SDKs.

**Proposal financing and deliverables**

We're requesting $259,500 for the current milestone which includes improvements to existing Substrate clients, SDKs for block explorers and currency exchange rate providers, adding Combine interface to Swift libraries and migrating our Kotlin libraries to use only Kotlin, not Java dependencies. Each part is planned to be released separately and sequentially along with publications to public package managers' repositories, as well as on our GitHub for a review. Also we're planning announcements on our Telegram channel and future Medium blog with a brief description of deliverables. And in the end when we finish documentation part we're going to publish on-chain report with appropriate links to the open source code, package managers' repositories, our articles on Medium, and links to documentation website ([https://docs.sublab.dev](https://docs.sublab.dev))

**Epilogue**

We look forward to hearing from you any constructive feedback and/or questions regarding our planned works. Feel free to refer to our [proposal document](https://docs.google.com/document/d/10ipyb2_d1d9FCYY4Xp3aRi5CZmZJOzbqBZ50hQMerUI/edit?usp=sharing)

Sincerely,
Sublab team

Sublab proposal #DOT-1: Substrate client improvements, ecosystem tools, and Kotlinization

This proposal aims to change the configuration of three operations on: Fast-unstake pallet, Staking pallet, Nomination pools pallet, particularly:

1. Increasing the minimum number of tokens to create a nomination pool **from 200 DOT to 500 DOT**.

2. Increasing the bond size required to become a direct nominator from **100 DOT to 250 DOT**.

3. **Enabling fast unstake** on Polkadot: this has been well tested in Kusama, and is ready to go 🚀. Read about fast unstake [here](https://forum.polkadot.network/t/path-to-fast-unstake-in-polkadot-kusama/1539) or [here](https://twitter.com/Polkadot/status/1625550205960523780).

4. Increasing the number of validator candidates **from 1200 to 1500** in anticipation of an increase in the active set of validators

5. **Increasing the number of pools to 256**: given the successful launch of Pools so far on Polkadot, and the network having almost the full list of 128 pools, I propose doubling the maximum count again to 256.

The previous discussion on this proposal can be found [here](https://polkadot.polkassembly.io/post/1650). 

- Call data: `0x1a000c28020100000007160100a89c13460200000000000000000000000001dc0500000000270b0001005039278c040000000000000000000001000100000000`

- Call hash: `0x4d779af12cec076f6dfe5b6087746b501592222bbcee70ff6ec51825eb389dde`

Preimage can be checked [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a000c28020100000007160100a89c13460200000000000000000000000001dc0500000000270b0001005039278c040000000000000000000001000100000000).

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

Make sure to vote at your convenience!

Adjusting Nomination Configuration

Polkassembly is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for January, February, March of 2023. We are requesting the Polkadot treasury to provide funds this time.

The full proposal is available [here](https://docs.google.com/document/d/1q3Byq4BN-OJAA0l4v51H3ye71SiorweoYPabB-jF41I/edit#). 

Discussion is [here](https://polkadot.polkassembly.io/post/1641)...

Social Contract between Polkassembly and Polkadot Treasury Q1'23

A proposal requested by the Manta team to register a new genesis wasm. Contextual information below:

**What Happened**

Our parathread was registered on the Polkadot relaychain, obtained a parachain slot and was upgraded to a parachain. However, we encountered a minor setback when the genesis collators failed to produce blocks on the new chain. It turns out that the registration process contained incompatible genesis WASM and state files, which caused our parachain to be stuck at genesis.

**Impact / why fast-track?**

After the acquisition of a parachain slot, Manta Network’s core development team has begun a sequence for launching the network. Not having this parachain producing blocks would prevent and delay that launch. The extrinsics called in our proposal affect just our 2104 parachain and it has not completed genesis, so there are no XCMP channels to worry about either, the relaychain should be unaffected by this.

**Remedy** 

After thorough investigation and collaboration with the Parity development team, we've identified a solution to the issue. With assistance from Polkadot governance, we can correct the incompatible parachain state & WASM files that were originally registered. This correction will not have any impact or loss of state since the chain has never produced any blocks. We believe that this is the most efficient and effective solution to get our parachain up and running.

**Council Proposal**

We humbly request that the technical committee fast-track the proposal to register the correct genesis state and code on Polkadot. This will allow our collators to begin producing blocks.

We have submitted the Preimage for the below proposal:

hash: `0x2d1b0d07d86ebe11297eb5a732d5d56e2b118eb1e8e55b0bdc801c5d313371c9`

in extrinsic [https://polkadot.subscan.io/extrinsic/14362712-2](https://polkadot.subscan.io/extrinsic/14362712-2) from the same account as was used to originally register the paraID/parathread in [https://polkadot.subscan.io/extrinsic/13905786-2](https://polkadot.subscan.io/extrinsic/13905786-2).

**Extrinsics called:**

`batchAll()`

`    - registrar::setCurrentHead(2104, corrected.state)`

`    - paras::forceSetCurrentCode(2104, corrected.wasm)`

New WASM file can be found [HERE](https://github.com/Manta-Network/Manta/actions/runs/4234987640).

registrar.paras(2104) => manager: 15ynbcMgPf7HbQErRz66RDLMuBVdcWVuURhR4SLPiqa6B8jx

Gist by the CEO of Manta Network Shumo Chu: [https://gist.github.com/stechu/9c97c7766951d377accd8835e5da79fb](https://gist.github.com/stechu/9c97c7766951d377accd8835e5da79fb)

Message Text:

"This shall serve to testify that the following Polkadot governance referendum has been initiated and is endorsed by the Manta Network team  - Referendum number: TBD - Proposal hash: 0x2d1b0d07d86ebe11297eb5a732d5d56e2b118eb1e8e55b0bdc801c5d313371c9 - Polkassembly discussion: https://polkadot.polkassembly.io/motion/362"

signature from the account that registered paraID 2104: `0x2478a5e64e8c7915e12ca048a2dfb5d04ff97f188fc1f7948bd77c19446fd421af3555a96ebbb1720b7ac1c548877ff8fc9ad12dcbf095f0aef9d8f54b444087`

Fix genesis registration for Manta Parachain

Proponent: Polkadot Now India: 16G7wZerqxib8YMDn3FKVfSMp1hky159JdhcGqHzy65F6RXE

Requested DOT: 41, 621 DOT

*41, 621 DOT (USD $295,807) (Rate: $7.107/DOT based on an EMA7 rate on [Subscan ](https://polkadot.subscan.io/tools/charts?type=price)on 24th Feb, 2023).

Hi Everyone ,

I am Rishant Kumar (Rish) Growth Lead, APAC for KILT Protocol and a long-term blockchain and Polkadot enthusiast. I am proposing a 2-day conference in India executed in my personal capacity – " Polkadot Now India 2023 – India's first-ever Polkadot Conference " in Bangalore, India, aimed at educating and engaging developers, investors, press and industry leaders in India on April 1-2, 2023.

The blockchain community has been growing rapidly in India over the past few years, helped by the huge number of Indian developers and the government’s official [strategy to make India a leader in blockchain technology.](https://www.meity.gov.in/writereaddata/files/National_BCT_Strategy.pdf)

However, while blockchain networks like Polygon and Solana have a significant presence in the country, DOT has minimal representation. Many developers are not aware of either Polkadot and the advantages it has over other technologies, or Substrate. Equally, Polkadot is not highly visible for industry leaders or enthusiasts. To raise Polkadot’s profile in India and promote education and engagement, along with others with connections to industry and the Indian blockchain communities, I am organizing **Polkadot Now India**. The conference aims to bring together developers, researchers, media, investors, and other stakeholders to experience the Polkadot ecosystem, share knowledge and discover new collaboration opportunities for the entire ecosystem.

Follow Us: [Telegram ](https://t.me/PolkadotNowindia), [Twitter](https://twitter.com/PolkadotNowInd).

[Website ](https://www.PolkadotNowIndia.com)will go live on 28th Feb, 2023. followed by opening of registrations on 6th March, 2023.

Our comprehensive proposal can be accessed via the [link ](https://docs.google.com/document/d/1RfYNmAShEARdmsAOCL0nQChWK7rzSK2Yy4UyU43Eijs/edit?usp=sharing)provided.

Polkadot Now - India, 2023 - India's first ever Polkadot Conference

As you may have heard recently, Chainsafe has built an early version of [Multix](https://multix.chainsafe.io), an interface to manage complex multisigs.
The alpha version is already live! 

We are aware that the multisig interface landscape has been busy in the past weeks, but we believe that we provide a solution that is outstanding:
- it's already live,  you can already see the power of what we will iterate on.
- unlike any other solution proposed out there, it's based on proxies, giving immense flexibility while keeping a great UX. 
- it's trust minimized and open. There is no private database needed other than a Subsquid indexer. You are not locked-in and can still use polkadot-js/apps in parallel if you want.
- it's open source, because we believe in healthy competition. Our ideas will be copied, hopefully with attribution!

Polkadot and Kusama have the lego pieces ready to use for enterprises and DAOs to create multisigs that are flexible enough for their needs. However, the actual day-to-day handling of these multisigs is a huge burden. It is not user friendly, error prone, and time intensive. From our interviews with businesses and DAOs that use multisigs, they all use at least one proxy, and often even many more. This gives them the flexibility they need, but it also makes the management of the multisig harder when using polkadot-js/apps. Also we believe that flexible multisigs should be accessible to everyone, not only businesses.   


If you build a multisig with your friends Alice and Bob, and Bob looses his private key, you will have to create a new multisig and transfer your funds/NFT. You may even be locked for a while because of staking/voting. Also your address will be different! This is dramatic! Unlike any solution out there, Multix uses proxies,  thanks to this, you can change Bob's key, and you won't have to touch the funds/NFTs or unstake. Also very important, you don't have to understand deeply how proxies work, the interface is easy to use regardless.  


Thanks to our deep experience of the ecosystem, Multix was built in a record time. If you want to know more about it [see this article](https://blog.chainsafe.io/multix-a-simple-interface-to-manage-complex-multisigs-on-polkadot-97328be26f9d).  

We would like to request ~150 000$ from the treasury to fund the development of new features for the next 5 months.
See the full [proposal here](https://docs.google.com/document/d/1euTuMEFSBwFf4cRVLK8sshI9PgdR5-Qg4ciDN4WJpaA/edit?usp=sharing)

For those who want to have a quick look at Multix, I made a video to showcase why proxies are awesome, and how you can swap a multisig behind a proxy, with a couple clicks. This feature isn't live yet, but I have it mostly done already, as you can see.

[Check it out here](https://www.youtube.com/watch?v=APxPsawebJw)


Multix - A simple interface to manage complex multisigs

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

[YieldBay](https://list.yieldbay.io/) is a yield farm aggregator for the dotsama ecosystem. Our goal with YieldBay is two-fold:

1. To reduce information asymmetry and lower the barrier to entry for liquidity providers and yield farmers
2. To make it easier for protocols to acquire liquidity for their token pools


This is a follow-up to [our previous treasury proposal](https://docs.google.com/document/d/1fssDqgPtIjdwO0XfJW5po94JHMf1ozdjeLwM2a40zJ8/edit?usp=sharing) ([Motion #262](https://polkadot.polkassembly.io/motion/262) on Polkassembly) to build further on our goal of reducing information asymmetry in finding and participating in liquidity pools and yield farms in the dotsama ecosystem.

As outlined in our previous proposal's problem statement and illustrated below in the screenshot of feedback from community members — participating in yield farms in the dotsama ecosystem is a tedious and time consuming process.

<img src="https://i.postimg.cc/nL86ZKgm/collage.png" width="400px" alt="Information asymmetry in finding and participating in liquidity pools and yield farms" />


With our previous proposal, we built an aggregated list of yield farms, which allows users to discover all major yield farms across the ecosystem and allows protocols to increase visibility of their liquidity pools and yield farms. The current version of this product is live on [https://list.yieldbay.io/](https://list.yieldbay.io)

In this proposal, we are seeking to fund the development of an aggregated yield farming dashboard to allow users to participate in dotsama yield farms as well as monitor and manage their positions from one central location.

 

**Progress so far:**

- [YieldBay list](https://list.yieldbay.io), the yield farm listing platform funded by the Polkadot Treasury as [Motion #262](https://polkadot.polkassembly.io/motion/262) on Polkassembly tracks over **$92M+ TVL** across **15 protocols**
<img src="https://i.imgur.com/HayNXAN.png" width="300px" alt="YB List Metrics" />
- The platform has had **4.3k** unique visitors who spent an average time of over **3min** on the site
<img src="https://i.imgur.com/UT5Mu23.png" width="600px" alt="YB List Metrics" />

**NOTE:** This submission is only for the first milestone. We shall make separate submissions for payment of the remaining milestones upon completion of delivery.

Please see the [full proposal here](https://docs.google.com/document/d/1GQQOEZ3ZW3wQ9GH0fv7na8evmBcBc_Tamf2ulor2bqI/edit?usp=sharing).

YieldBay Proposal Phase 2: Yield Farming Dashboard for Dotsama

This proposal aims upgrade Polkadot to runtime [v9370](https://github.com/paritytech/polkadot/releases/tag/v0.9.37): the specific details on this upgrade please check the release notes. 

- System.setCode using Utility.withWeight: `0x56ee5c8542848bfa5c8f5be09ebf74857984031841b50679f2d5009ecfb41f6e`

- Call data can be found [HERE](https://i.ibb.co/wCRwt3j/Screenshot-2023-02-22-at-11-48-59.png).


**Runtime**

- [S] ✅ trivial [#12721](https://github.com/paritytech/substrate/pull/12721) Low - frame_support::storage: add storagestreamiter

- [S] ✅ audited [#12307](https://github.com/paritytech/substrate/pull/12307) Low - Add callbackhandle to pallet-assets

- [S] ✅ audited [#12883](https://github.com/paritytech/substrate/pull/12883) Low - Contracts: improve contract address derivation

- [S] ✅ trivial [#12963](https://github.com/paritytech/substrate/pull/12963) Low - Fix fast-unstake for accounts with slashing

- [S] [#12765](https://github.com/paritytech/substrate/pull/12765) Low - Nfts 2.0

- [S] ✅ trivial [#13010](https://github.com/paritytech/substrate/pull/13010) Low - Ignore empty authority changes

- [S] ⏳ pending non-critical audit [#12967](https://github.com/paritytech/substrate/pull/12967) Low - Add ensure-ops family methods

- [P] ✅ trivial [#6465](https://github.com/paritytech/polkadot/pull/6465) Low - Deploy scheduler agenda cleanup migration

- [S] ✅ trivial [#13045](https://github.com/paritytech/substrate/pull/13045) Low - Selectable on-runtime-upgrade checks

- [S] ✅ trivial [#13043](https://github.com/paritytech/substrate/pull/13043) Low - Remove copy from ensure* traits

- [P] ✅ trivial [#6498](https://github.com/paritytech/polkadot/pull/6498) Low - Co #13045: selectable on-runtime-upgrade checks

- [P] ✅ trivial [#6546](https://github.com/paritytech/polkadot/pull/6546) Low - Update weights (0.9.37)

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

Make sure to vote at your convenience!

Runtime Release v9370 for Polkadot

**Requested Allocation:** $50,000

*DOT amount calculated via EMA7 on 15 February 2023 at GMT+0 1100hrs: 1 DOT ~ USD$6.27. USD$50,000 ~ 7974.4817 DOT

**Proponent:** EasyA 5FQqvRHgBEUZG17qs9cNFH6ZSSVyAwhb7D6dKjGWb8xgKFkP

**Short Description:** EasyA is developing a crash course for developers educating them on Polkadot and its parachains/projects. EasyA will then hold 2 in-person hackathons in world-leading hubs London, UK and Boston, US for developers to participate in the final showdown and showcase what they’ve learnt. We aim to get 1,000 developers completing the crash course fully, and 400 developers to our 2 in-person hackathons. The goal: educate thousands of developers on Polkadot, reach millions on social media, and get #60DaysOfPolkadot trending in developer communities worldwide!
This builds on the massive success of the original ['Hello World' Polkadot Gitcoin challenges](https://gitcoin.co/hackathon/polkadot/), which kickstarted the whole Polkadot developer community.

This proposal is supported by the Acala, Astar, Composable, and Moonbeam parachains, as well as ecosystem projects including Subsquid, Gear and others. All ecosystem teams are welcomed to get involved too!

**Objectives:**
* Educate 1,000 developers on Polkadot and the ecosystem
* Produce 100 new projects on Polkadot and parachains by the end of the hackathon series
* Maximise the quality of submissions at Polkadot hackathons
* Increase awareness and adoption of Polkadot and parachains
* Introduce individuals to programming on Polkadot and parachains
* Create long-lasting content to benefit newcomers to Polkadot and parachains

**See the proposal link [here](https://docs.google.com/document/d/1dgfiAwKU3cM-2MmWfCkULHNZYlrMU9ayJ5oDKvmZMQQ/edit?usp=sharing)**!

Milestone 1 Proposal: Polkadot Developer Hackathons and Crash Course for 1,000 Developers (#60DaysOfPolkadot)

Hello Polkadot Council. 

Thank you for checking out our proposed spend for 6-months maintenance of **[The Kusamarian](https://twitter.com/TheKusamarian)**, a Polkadot-centric media brand. We are a platform upon which the stories of Builders and tokenholders are spoken and shared.

 

*Quick Links*:

[6-month Maintenance Proposal](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit?usp=sharing)

[Budget](https://docs.google.com/spreadsheets/d/1yWEE0PbYdkJ3Imd7WPXGS0CLlnSBw6kdPsnlWRhlkD8/edit#gid=0) $284,154/59198.75 DOT

[Original Discussion Post](https://polkadot.polkassembly.io/post/1572)

[Live Readthrough of Discussion proposal](https://youtu.be/6bQCFORep5I)

[The Kusamarian](https://twitter.com/TheKusamarian)

 

A [discussion of this proposal](https://polkadot.polkassembly.io/post/1572) was shared on January 26th with a poll included. Changes leading up to the final submission are noted *[here](https://docs.google.com/document/d/1l0fuqSfQRH7j3SdSEplNvl4rIyIZauxZGHDS4EPriU0/edit?usp=sharing)*.

We're very pleased with the feedback and support we've received from tokenholders and would ask further comments to be added to the [original discussion](https://polkadot.polkassembly.io/post/1572)!

Councillors are encouraged to leave any questions or comments below.

 

***Easily jump to sections of interest below:***

[Relevant Media 6 Days a Week](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.ob5n4uemdojq)

[Media Standards](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.b0dfkv4g0fju)

[Challenges 🤝 Solutions](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.l8gdwgo0eug8)

[Twitter First Strategy](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.dviqozedhpo)

[Promotion Strategy](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.k2t917l25ohw)

[Budget](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.q4awbxlbdfri)

[The Kusamarian Team](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=kix.u27xx1up3ji)

[Payment Conditions](https://docs.google.com/document/d/12b5dPQaPvu-59j2Bf4LoJYRwV_xjIM95t8kCHpMhTPY/edit#bookmark=id.8a77h77t4ryt)

 

We thank you for your consideration of this proposal! The Kusamarian is committed to continue serving Token Holders in the best way possible. If you see room for improvement or growth please let us know.

Thank you Polkadot! ❤️

The Kusamarian - 6 Month Maintenance Funding

Hi Community,

We recently increased the usability of Polkawatch, particularly on mobile devices, tripled  its computation capability, rolled out infrastructure improving our community engagement and created APIs, documentation and examples to integrate decentralization analytics in other community projects. 

We also released the [State of Decentralization report for Polkadot 2022](https://pwh.li/dot22rr)

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem in general and our validation process in particular.

The interest peaked with the [deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are sharing with you our next Proposal: on top of Continued Operation for a period of 9 months, we are proposing to:

- Port decentralization analytics for staking pools  to Polkadot (already rolled out on Kusama)
- Multi-Wallet integration
- Assist partners with integration of decentralization analytics.

You can download our [Detailed Proposal](https://pwh.li/dot23h1p) for additional information.

Treasury Proposal: Polkawatch, Decentralization Analytics, Continued Operation and Development

Five more parachains have requested an HRMP channel opening with Statemint. This motion accepts them all and opens return channels - the following calls aim to be executed on this proposal for each of the parachains:

- A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
- A force_open_hrmp_channel from [ParaID] to Statemint (1,000).
- A force_open_hrmp_channel from Statemint (1,000_ to [ParaID].

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

- HydraDX -> 2,034 - [https://polkadot.subsquare.io/post/7](https://polkadot.subsquare.io/post/7)  
- Ajuna -> 2,051 - [https://polkadot.subsquare.io/post/10](https://polkadot.subsquare.io/post/10)
-  Kapex -> 2,007 - [https://polkadot.subsquare.io/post/11](https://polkadot.subsquare.io/post/11)
- Pendulum -> 2,094 [https://polkadot.subsquare.io/post/12](https://polkadot.subsquare.io/post/12) 
- Litentry -> 2,013

Encoded call can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a04141a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000f2070000e8030000009001003c07f2070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000003080000e8030000009001003c0703080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000d7070000e8030000009001003c07d7070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e80300002e080000e8030000009001003c072e080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000dd070000e8030000009001003c07dd070000e8030000e803000000900100). 

Encoded call data: `0x1a04141a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000f2070000e8030000009001003c07f2070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000003080000e8030000009001003c0703080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000d7070000e8030000009001003c07d7070000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e80300002e080000e8030000009001003c072e080000e8030000e8030000009001001a000c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000dd070000e8030000009001003c07dd070000e8030000e803000000900100`

Proposal hash: `0xe91253279d2f83810f4275cb3f100046fac5ced92a9f0b8a06518d2e78e32141`

Since this call requires Root origin, Council will vote first on this external motion and the community will make the final decision in referenda queue. Make sure to review and vote at your convenience!

A New Batch Of HRMP Channels: HydraDX, Kapex, Ajuna, Pendulum, Litentry

As per the discussion [here](https://polkadot.polkassembly.io/post/1561), Encode Club is requesting tranche 1 of 5834.21 DOT (£30k, based on the 30 day EMA on [Subscan](https://polkadot.subscan.io/tools/charts?type=price)) to cover an 8-event online education series and 4-week online hackathon.

The full proposal can be found [here](https://docs.google.com/presentation/d/1msKUzE5xK6Y1pV3b0dA_J2pWJt3ecYiG0OXjFpz5K6Y/edit#slide=id.g179c6775f75_0_7).

A reminder of the tranches:

Now: £30k for 8 event online educate series and 1st online hackathon

April: £25k to pay hackathon prizes and run 2nd online hackathon

July: £70k to pay 2nd hackathon prizes and run an in-person hackathon

October: £40k to pay in-person hackathon prizes, run a 3rd online hackathon and accelerator

December: £10k to pay 3rd online hackathon prizes

Encode Club 2023 Proposal Tranche 1

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

Polkadot Hub proposes educational activities for 2023 aimed at the development of the dev community and projects on Polkadot and Kusama, continue to educate existing users of the network and integrate new ones into the ecosystem

.1.- Development of the Spanish Developer Community through educational programmes aimed at teaching Substrate technology, Ink and Rust programming language to support and generate new projects for the Polkadot and Kusama Ecosystem. The possibility of taking the Rust, Ink! and Substrate courses in Spanish will give participants a global understanding of the framework and language on which Polkadot technology is based and will allow them to develop projects in the ecosystem.

2.- Development of educational video tutorials about Polkadot and Kusama. Community online sessions.

3.- Build the first complete Polkadot Js guide in Spanish

[Link full proposal](https://docs.google.com/document/d/1AGmcx-j0wGhcGuJFkxtEG1pfx9KlKCaUwjktpAa9cZ8/edit)

[Link Dicussion](https://polkadot.polkassembly.io/post/1547)

POLKADOT EDUCATIONAL HUB IN SPANISH - ROADMAP 2023 Educational development and courses

Based on the conversations the Zeitgeist team had with TC in the last days, and taking into account the same issue appeared for the team on Kusama and the fix was approved by the community (see [HERE](https://kusama.polkassembly.io/referendum/251)), this proposal is now submitted as external motion for consideration of the Council, before making it to referenda queue for the final decision. 

You can find the contextual information on this proposal by the Zeitgeist team [HERE](https://hackmd.io/PXotv7zMTSOphZFg4f99iQ) or below:

### What Happened

The runtime that is now deployed on Polkadot was prepared before the ParaId was obtained. During local testing rococo-local was used as the relay chain. The parachain was onboarded using another ParaId than the one within the runtime and the parachain was capable of producing blocks and functioning as expected. Assuming that everything is fine, the same runtime was used to bid in the parachain auction using a different ParaId than the one noted in the prepared runtime. As it turns out, the parachain is uncapable of producing blocks on Polkadot due to a ParaId mismatch.

About the same time Zeitgeist also bid for a slot on Kusama to execute a slot lease swap. The testing procedure was the same and also resulted in success, however the chain was also uncapable of producing blocks. If those two events were temporaly further apart, the human error would only have happened once. Unfortunately we are forced into the highly aggrevating situation to ask the governance body twice to fix our Parachain, once for Kusama (proposal) and once for Polkadot.

### Remedy

To fix the bricked chain, the chainspec used for Zeitgeist’s parachain on Polkadot must use 2092 within ParachainInfo::ParaId. To inform Polkadot about the new state root that results from the updated chainspec, paras.forceSetCurrentHead(2092, genesisHead) has to be invoked by the Root origin, whereas genesisHead is set to the resulting genesis state head that is derived from the new chainspec.

We also want to supply a new runtime. It is much more recent (polkadot-v0.9.29 instead of polkadot-v0.9.19).

### Council Proposal

We are aware of the recent discussion around the technical council circumventing due process on governance here: [https://forum.polkadot.network/t/how-to-recover-a-parachain/673/23](https://forum.polkadot.network/t/how-to-recover-a-parachain/673/23) and withdrawing from fixing broken parachains. However there is currently not a best practice solution other then avoiding mistakes.

Our humble request to the Technical Committee is to fast-rack this proposal, this is purely a technical hotfix to get the chain started the first time. 

### Proof of Authenticity

To proof that this request is authentic, the manager of ParaId 2092 does provide a signed statement of approval.

Manager (`registrar.paras(2092)`): `15Q7heNtPy5vaZ79c3eUt7M42Ao3okf7PKKdRDULBz3Z4UyF`

Statement: [1675099734007] I hereby approve the deployment of the genesis state `0x000000000000000000000000000000000000000000000000000000000000000000c2e17f26b505c2be4dcefd0ebfd3abe4536fcc86ded7329af33ddd0a9496db9a03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400` and the genesis wasm with the blake2-256 hash `0xa4fe96b65d8f78a7f92d1b7eb917ca501518b6910bee573565d16a911fb91a14` for ParaId 2092 on Polkadot

Signature: `0x6a87523b11d4dd17411c3d9ebed91175dafed6b570014b164074b54b3b2c2b147574a9a5e3f2a25dfcd15340617c4df0730302f51016d5264257e7e8b0c39880`

### 

**PLEASE NOTE THIS PROPOSAL IS SUBMITTED AS AN EXTERNAL MOTION: MEANING IF/AFTER COUNCIL APPROVAL, THE COMMUNITY WILL HAVE THE FINAL DECISION ON THE PROPOSAL IN REFERENDA QUEUE. ALSO NOTE [REFERENDUM 103](https://polkadot.polkassembly.io/referendum/103), SUBMITTED BY THE ZEITGEIST TEAM, AIMS TO EXECUTE THE SAME PROPOSAL: HOWEVER THE TEAM HAS PUBLICLY DISCUSSED 56 DAYS FOR ENACTMENT IS A LONG TIME TO WAIT FOR A FIX. IF THIS PROPOSAL PASSES, THEN REFERENDUM 103 WILL NEED TO BE CANCELED OR DOWNVOTED.**

### 

Make sure to review and vote at you convenience!

Unbrick Zeitgeist Parachain

Talisman (talisman.xyz) is a community-owned wallet and web application that enables users to “traverse the Paraverse” with ease. We believe in a future where everyone has freedom via true agency over their intentions and finances, and we believe that DotSama will bring this to fruition. 

For more on Talisman’s mission and approach, please see Agyle’s talk at Polkadot Decoded: [Polkadot Decoded 2022: Traverse the Paraverse: How Talisman is bringing multi-chain to the masses](https://www.youtube.com/watch?v=c7tZjVv70Jk)

And Jonathan’s talk about wallet UX at the Sub0 developer conference:
[Talisman: The UX Chronicles: How To Deliver A Substrate Experience To The Masses](https://www.youtube.com/watch?v=a_xiMaDAEiQ)

Today, because of its early stage of development and complex multi-chain architecture, both Polkadot and Kusama are changing rapidly and the user experience (UX) can be confusing for end users. It’s our goal to solve that using design, storytelling, and engineering. We abstract away the complexity of underlying implementation and provide a friendly user experience when using DotSama and a way to discover new applications and services available to end users, while keeping them safe and educated about the actions they are taking.

This proposal is for a business-friendly multisig frontend to lower the difficulty for teams and businesses when running their financial operations on Polkadot. Teams currently face many difficulties when trying to perform these operations, risking mistakes along the way, and leading them to choose convenience over security. We will apply Talisman’s UX and design philosophy to create improvements for standard workflows for Polkadot multisig usage (based on the current multisig pallet), and eventually integrate upgrades when improvements to the multisig pallet itself are available.

We have spoken to a number of stakeholders in the ecosystem and have strong validation for our proposed solution:
- “Creating child bounties in pjs is time consuming and error prone, you have our full support” - Zoe Mechbach, VP, Phala Network
- “We will definitely use it because we need it!” - Shun P, Head of Ops and Finance, Astar
- “We would use it for sure” - Dennis & Alexandra, CTO & Marketing Director, Bitgreen
- “If there was a multisig with better UX that allowed us to craft and verify multisig transactions faster we'd use it” Bruno, Founder, RMRK
- “If you can improve the UX to make it easier for non-technical users to initiate and safely sign transactions, we will switch” - Daniel, Founder, Tapio

The full proposal is [here](https://docs.google.com/document/d/1KohKDEYypNw_KJING2_uHXnC0LJwUxpPHMzBRfrH68M/edit?usp=sharing).

This submission follows from the following forum discussion: 
https://polkadot.polkassembly.io/post/1569

Talisman Proposal: Business-Friendly Polkadot MultiSig

The proposal, submitted as an **external** motion for the **RMRK** team, aims to fund the development of all RMRK NFT 2.0 and Marketplace pallets (rmrk-substrate-pallets): adaptable to the entire ecosystem. In the team's words: "flexible tools are needed to assist the builder's productivity. It is thus that the RMRK seeks to bring to the Polkadot community sophisticated NFT tooling - to help foster greater innovation in, and adoption of, the Polkadot project and Substrate development framework, and to help grow our influence as a cohesive and innovative community". 

Please note that due to the value requested, the proposal has been passed as an external motion, meaning that after/in case of Council approval the proposal will be voted as a referendum: **leaving the final decision to the community**.  You can find the budget, roadmap and deliverables in the contextual information the team has provided. 

Contextual Information: [Treasury Proposal no. 222](https://polkadot.polkassembly.io/treasury/222). 

Proposal hash: `0xaa386b403d0677a56c6c432ce4313a30d8a1c4b6818c1005fb197907bf572949`

External Motion: Funding Request for Continued Production of RMRK Substrate Pallets

Dear Polkadot community,

We are TeachMeDeFi, a German language hub for web3 education, founded in 2022. Our mission is to deliver high-quality educational resources and foster a thriving community of web3 users, with a focus on simplifying and promoting decentralized technologies through our content and partnerships. We have already made significant strides in this mission and our portfolio thus far includes podcasts, interviews, educational videos, a community hub and a structured website.

We understand that bringing more awareness to Polkadot and doing more professional, targeted marketing has been a topic of discussion in the community and many have requested it as it has been somewhat lacking, even though the technological progress of Polkadot has been impressive. Furthermore, it has been a topic of discussion that diving into the Polkadot ecosystem can be complicated for new users.

This is why we are submitting a funding proposal to support the creation and promotion of content in order to increase awareness of the Polkadot ecosystem, reach a wider audience and significantly simplify the onboarding journey for new users.

We have already received support from key players in the Polkadot community and are excited to share our proposal.

You can read the full proposal document [here](https://docs.google.com/document/d/10RNESvTjTVY1KUMkb1q6vJ5yrw5O-oZ8J2itQfJnRuQ/edit?usp=sharing) (live google doc) or [here](https://crustipfs.art/ipfs/QmRLHMXg3EFCS7J2MjmaDpnqLtt1SFPsgWF9unqR44vS2z) (ipfs pdf doc).

In this document, we describe in detail (1) the challenge Polkadot is facing, (2) the unique opportunity that the German language market represents and (3) the solution we propose which consists of several deliverables and a targeted marketing strategy.

You can find the original discussion post with feedback from the community [here](https://polkadot.polkassembly.io/post/1560).

Thank you for your consideration,

The TeachMeDeFi Team

Proposal by TeachMeDeFi for a German Educational Platform for Polkadot

An [incentive programme](https://polkadot.polkassembly.io/post/1352) was initiated to reward high quality nomination pools. The exercise was completed and reviews all pools prior to the expansion of the pool base which occurred shortly after block 13686541.

The programme seeks to reward pools which have met the following criteria:

- Has metadata

- Pool creator has verified identity

- Has nominees

- Is Open

- Has more than 10 members

The analysis is supported by an open source tool developed by **Polkagate** which allows for a more objective analysis. The results of the analysis was posted (see last post) for public scrutiny for which none was received. With this said, we would like to proceed with rewarding 22 pools with 250 DOT as well as issuing a payout to PolkaGate of 250 DOT as well for developing the tool. Please note that rewards would be shared among all pool members and isn't submitted to the pool creator.

Call data for this motion: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x1a005c13030b00a89c134602006d6f646c70792f6e6f706c73010100000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010200000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010400000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010500000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010600000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010700000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010800000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010a00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010b00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010d00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73010f00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011300000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011400000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011500000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73011c00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73012700000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73012b00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73012c00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73013600000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73013d00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73013f00000000000000000000000000000000000013030b00a89c134602006d6f646c70792f6e6f706c73014000000000000000000000000000000000000013030b00a89c1346020004f3da939fa351c562c7e06e1e3716976b5e14230e83a45995cbad9086f49e17).

Executing Nomination Pools Incentives

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

After incorporating feedback and adding more documented usage examples, a more in-depth focus on the cli tool and pallet migration verification testing documentation at the community's request, the treasury proposal for **Uptest** that aims to be the tool for testing Pallet functionality before and after runtime upgrades is brought up for a vote once again. 

The tool is bringing more options for developers to test runtime upgrades to the ecosystem by making it easier for developers to quickly pinpoint needed runtime migrations and test pallet functionality before and after runtime upgrades. You can find further info, the budget, roadmap and deliverables on the post below. Please make sure to review and vote at your convenience! 

**Original Treasury Proposal here:** [https://polkadot.polkassembly.io/treasury/186](https://polkadot.polkassembly.io/treasury/186). 

**Comment on changes based on feedback:** [https://polkadot.polkassembly.io/treasury/186#6f279923-82ff-42f1-8455-c75451df189b](https://polkadot.polkassembly.io/treasury/186#6f279923-82ff-42f1-8455-c75451df189b).


Treasury Proposal by Rust Syndicate: Uptest funding proposal (2nd vote after incorporating feedback)

Blockchain Training Alliance (BTA) has created a Substrate-specific course that will allow developers to learn how to effectively build on Polkadot. BTA is requesting the second and final phase of payment. This training and partnership provides new developers from the Web2 space to learn Polkdadot technology and increase developer activity within the Polkadot ecosystem. 

The training course can be found here: [https://blockchaintrainingalliance.com/products/polkadot ](https://blockchaintrainingalliance.com/products/polkadot)

Course Overview: 
In this course students learn how the Polkadot platform works, from an understanding of the governance and treasury process to hands-on lab environments for writing code. Technologies covered in this course are Polkadotjs, Substrate, WASMI, libp2p and Rust and more. Whether students want to add to their blockchain skills for career prospects or want to learn how to build a blockchain solution that has ability to communicate with multiple blockchains into a single network, this course will be the ideal fit. 

Link to proposal: [GOOGLE DOC LINK](https://docs.google.com/document/d/1RsaYOijzSRVDQxhrlkMXPt28HF5t3Hqe/view)

Substrate Training Course and Certification

**NOTE**: Due to an issue with the length of the call when submitting an external motion 333 on Polkadot.js Apps (already fixed by this [PR](https://github.com/polkadot-js/apps/pull/8899))the previous motion won't execute successfully. Motion 333 is replaced by this one.


This proposal aims upgrade Polkadot to [v9360](https://github.com/paritytech/polkadot/releases/tag/v0.9.36): the specific details on this upgrade please check the release notes. 

System.setCode hash: `0x5f48aacbbd94a881a3ce5a496e1d852f21cffe33d1f7592023f2140254683d20`

Hash wrapped on Utility > withWeight call: `0x1daf74e45c1db64e50a5fa01b20ec2e8101e589bed278841b2946d4c4d258f78`

![](https://i.ibb.co/10xqxjy/Screenshot-2023-01-27-at-10-40-07.png)

**Runtime**

- [S] ✅ trivial [#12889](https://github.com/paritytech/substrate/pull/12889) Low - Staking: store last min-active-bond on-chain

- [S] ✅ audited [#12582](https://github.com/paritytech/substrate/pull/12582) Low - Automatic withdraw_unbonded upon unbond

- [S] ✅ trivial [#12894](https://github.com/paritytech/substrate/pull/12894) Low - Warn on missing pallet::call_index

**Misc**

- [S] ✅ trivial [#12875](https://github.com/paritytech/substrate/pull/12875) Low - Use log_target in consensus related crates

- [S] ✅ trivial [#12889](https://github.com/paritytech/substrate/pull/12889) Low - Staking: store last min-active-bond on-chain

- [S] ⏳ pending non-critical audit [#12537](https://github.com/paritytech/substrate/pull/12537) Low - Try-runtime revamp and facelift

- [S] ✅ audited [#12582](https://github.com/paritytech/substrate/pull/12582) Low - Automatic withdraw_unbonded upon unbond

- [P] ✅ trivial [#6440](https://github.com/paritytech/polkadot/pull/6440) ‼️ HIGH - Fix wrong rate limit + add a few logs.

- [S] ✅ trivial [#12894](https://github.com/paritytech/substrate/pull/12894) Low - Warn on missing pallet::call_index

- [P] ✅ trivial [#6450](https://github.com/paritytech/polkadot/pull/6450) Low - Update weights (0.9.36)


Please note this proposal is submitted as an external motion: meaning if/after the Polkadot Council approves, the proposal will be up for vote by the community in democracy module for the final decision.

Make sure to vote at your convenience!

Runtime Release v9360 for Polkadot (replacing motion 333 due to length issues)

Dear Polkadot community and Councilors, 

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

[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** on all popular browsers (Google Chrome, Firefox, Brave, Edge) in February 2022 and keep releasing our product updates on a [bi-weekly basis](https://github.com/Koniverse/SubWallet-Extension/releases).

**While using the browser extension, our community constantly asked about a more convenient mobile app**, which can provide them with a homogenous wallet experience in the whole Polkadot & Kusama ecosystem, and we listened. At the moment, there hasn’t been a native wallet on the Polkadot & Kusama ecosystem that offers this **comprehensive and consistent multi-platform experience from Extension through to Mobile** to users. That is why we decided to start building the SubWallet Mobile App in June 2022.

**This is SubWallet Mobile App's 1st proposal for Milestone 1 - 20 Weeks: From July 2022 to October 2022 (which is completed):**


- Full proposal for Milestone 1 with a detailed description, costs, tractions, and future plans: [Link ](https://docs.google.com/document/d/16phPsThpob4cQqvqsNIv-jVN1IWbrklS-LF6--pqm7Y/edit#heading=h.v6is2ta0txr1)
- More details and progress: [Link](https://github.com/Koniverse/SubWallet-Mobile/issues?q=is%3Aissue+is%3Aclosed)
- Community Dicussion: [Link](https://polkadot.polkassembly.io/post/1493)
 
**Complete set of the proposal: ([See proposal](https://docs.google.com/document/d/16phPsThpob4cQqvqsNIv-jVN1IWbrklS-LF6--pqm7Y/edit#heading=h.v6is2ta0txr1))** 

- Mobile App Architecture Design
- React Native Core Module (Android & iOS)
- Basic React Native Element (Android & iOS)
- Basic Features: Account Management, Send & Receive Assets, XCM Transfer,... (Android & iOS)
- NFT Feature: Display, Send (Android & iOS)
- Crowdloan Feature (Android & iOS)
- Staking Feature (Android & iOS)
- In-App Browser (Android & iOS)
- Performance Optimization (Android & iOS)
- And [more here](https://github.com/Koniverse/SubWallet-Mobile/issues?q=is%3Aopen+is%3Aissue)
 
**Our tractions as of Jan 2023**

- 140+ networks supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- Browser extension: 38,000+ organic installs on Chrome Store & Firefox Store.
- The mobile app is in the public testing phase on both iOS and Android. 3,000+ installs (**[Link](https://twitter.com/subwalletapp/status/1587403200105451520)**)
- Our users come from 100+ countries.
- 8000+ community members on Twitter, Telegram, and Discord
- A member of the Substrate Builders Program
- Working with 100+ teams in the ecosystem with the ultimate goal of bringing the best UI/UX for users. 

We would love to hear feedback/recommendations from the community and Councils.



**All the best,**

**SubWallet Team**

SubWallet Mobile App 1st proposal: Comprehensive and consistent multi-platform experience. Account Management, Built-in XCM Transfer, NFT Management, In-app Staking, In-app Browser, Performance Optimization

**NOTE: Due to an issue with the length of the call when submitting an external motion on Polkadot.js Apps (already fixed by this [PR](https://github.com/polkadot-js/apps/pull/8899)) this proposal won't execute successfully: we ask councillors to vote against it, or not to vote. A new motion will be submitted shortly.**
-------------

This proposal aims upgrade Polkadot to [v9360](https://github.com/paritytech/polkadot/releases/tag/v0.9.36): the specific details on this upgrade please check the release notes. 

System.setCode hash: `0x5f48aacbbd94a881a3ce5a496e1d852f21cffe33d1f7592023f2140254683d20`

Hash wrapped on Utility > withWeight call: `0x1daf74e45c1db64e50a5fa01b20ec2e8101e589bed278841b2946d4c4d258f78`

![](https://i.ibb.co/10xqxjy/Screenshot-2023-01-27-at-10-40-07.png)

**Runtime**

- [S] ✅ trivial [#12889](https://github.com/paritytech/substrate/pull/12889) Low - Staking: store last min-active-bond on-chain

- [S] ✅ audited [#12582](https://github.com/paritytech/substrate/pull/12582) Low - Automatic withdraw_unbonded upon unbond

- [S] ✅ trivial [#12894](https://github.com/paritytech/substrate/pull/12894) Low - Warn on missing pallet::call_index

**Misc**

- [S] ✅ trivial [#12875](https://github.com/paritytech/substrate/pull/12875) Low - Use log_target in consensus related crates

- [S] ✅ trivial [#12889](https://github.com/paritytech/substrate/pull/12889) Low - Staking: store last min-active-bond on-chain

- [S] ⏳ pending non-critical audit [#12537](https://github.com/paritytech/substrate/pull/12537) Low - Try-runtime revamp and facelift

- [S] ✅ audited [#12582](https://github.com/paritytech/substrate/pull/12582) Low - Automatic withdraw_unbonded upon unbond

- [P] ✅ trivial [#6440](https://github.com/paritytech/polkadot/pull/6440) ‼️ HIGH - Fix wrong rate limit + add a few logs.

- [S] ✅ trivial [#12894](https://github.com/paritytech/substrate/pull/12894) Low - Warn on missing pallet::call_index

- [P] ✅ trivial [#6450](https://github.com/paritytech/polkadot/pull/6450) Low - Update weights (0.9.36)


Please note this proposal is submitted as an external motion: meaning if/after the Polkadot Council approves, the proposal will be up for vote by the community in democracy module for the final decision.

Make sure to vote at your convenience!

Runtime Release v9360 for Polkadot: [EDIT] Please check the note above of contextual information

**Proponent:** 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf

**Date:**  25th January 2023

**Requested DOT:**  10,859.582767 (USD $67,459.73)

**Short description:** Ongoing costs for the running of high performance, scalable, and reliable public infrastructure for Polkadot, Statemint, Westend, and Encointer.

**Raw Data:** [Polkadot Data Q4 2022](https://docs.google.com/spreadsheets/d/1Z5ayTVPj_cbw9ewQPUQIsE3EmM9fHAadVKJgWoVwuPo/edit#gid=1173353638)

**Full Report is here:** [https://docs.google.com/document/d/1BBjcxgdhu6NnfhtrprJcnqvr-KM8H2Twq45rgJ9mDkM/edit?usp=sharing](url)

* * * * *

Original Motivation
===================

Over the last 3 months (October, November, December 2022) we've provided a scalable free public API service so that everyone can access public pools of managed Polkadot, Statemint, Westend, and Encointer nodes. This provides the following three outcomes:

-   Grow the ecosystem by reducing the barriers to entry to access a high performance nodes

-   Help scale existing projects in the ecosystem by providing infrastructure  services that can be depended on

-   Assist with the testing of all networks by providing valuable data back to the community on how validator nodes are running and scaling as the network traffic increases (we've made GitHub issues based on behaviour we've observed)

Service Details
===============

During Q4 of 2022, we've made a large number of stability improvements to our Ultimate API service. We've finished significant work on advanced rate limiting on behalf of our customers. This means that we can continue to provide generous public API endpoints for over 40 different networks for common-good applications, but restrict access to high volume users that abuse this free service. We've been able to manage our costs significantly on behalf of our customers as a result.

For customers that do sign up for paid API keys, we've been adding more and more features to provide a better experience. API access restrictions allow our customers to restrict their API keys to work only from 'Allowed' origins and/or IP addresses, preventing unauthorised consumption of their service. We also provide more detailed monitoring of failed requests through our service to help customers identify and fix bugs before they get to production.

Our customers are building cross-chain wallets, running some of the largest block explorers, and are indexing multiple networks - they've all benefited from these API access restrictions, improved monitoring, and the larger number of supported Polkadot chains.

Between 2022-10-01 and 2022-12-31 our Polkadot API service has:

-   **Reduced cost to the Polkadot treasury by almost 50% from Q3** (Q4 was a slower period however our continued infra optimisations have had a significant impact on costs)

-   Served a total of 6.7 billion responses

-   Accumulated over 79.6 TB of data egress 

-   The highest daily total was 126 million responses in a single 24 hour period for Polkadot only

-   Our rolling 7 day average at the end of this period was over 73.5 million responses each day.

-   Westend had over 175 million API responses in the period

-   Statemint had over 160 million API responses in the period

-   All time totals for Polkadot is 93,192,546,788 (93 Billion) since November, 2020

-   At the end of this period the 90 day uptime for Polkadot, Statemint, and Westend was 99.86%, 99.99%, and 100%

**Note that we have added support for the Encointer common good parachain for the first time in this proposal.** We have supported Encointer since the 9th of February 2022 but as a contribution to the ecosystem, we've been proud to provide over 7 months of free support at our own cost. From subsequent quarters, we expect to support more common good chains and include them in these proposals.

Enhancements
===============

Additionally, we are proud to have delivered some key service enhancements that benefit the Polkadot ecosystem in the last quarter. This includes:

-   [API Access Restrictions ](https://blog.onfinality.io/onfinality-rolls-out-three-new-features-on-its-enhanced-api-service/)--- a new security feature to help you securely manage access to your OnFinality API endpoints

-   [Detailed Error type breakdowns](https://blog.onfinality.io/onfinality-rolls-out-three-new-features-on-its-enhanced-api-service/) on your API Insights dashboard

-   A new [Integration tab](https://blog.onfinality.io/onfinality-rolls-out-three-new-features-on-its-enhanced-api-service/) to help you get connected quickly

-   Support for more Polkadot parachains

-   [New enhanced deployment automation processes](https://blog.onfinality.io/onfinality-delivers-new-network-automation-tools-for-web3-developers-to-build-smarter/) to allow our network partners to automate deployment of their networks with OnFinality

-   Support for [Ethereum](https://blog.onfinality.io/onfinalitys-highly-scalable-rpc-api-helps-ethereum-scale-faster-than-ever/)

-   A variety of improvements to our health metric collection tools and automated recovery scripts to ensure our 99.9% SLA is exceeded.

-   Scale improvements to our team, processes, and systems to allow us to provide this same service to any  substrate team

You can always see live data on our API service on our public [status page](https://status.onfinality.io/) and [network analytics page](https://onfinality.io/networks).


Full Report is here: [https://docs.google.com/document/d/1BBjcxgdhu6NnfhtrprJcnqvr-KM8H2Twq45rgJ9mDkM/edit?usp=sharing](url)

High Performance Public Infrastructure (Q4 2022)

- **Treasury Proposal:** Snowbridge Funding Proposal
- **Beneficiary:** 12UDxESUsqUZi5R5MpovTZLpAWZXPVWHJQkEprcT6MVdKh3A
- **Amount:** USD 2,448,000.00 based on EMA7 rate by Subscan
- **Scope:** See the [full funding proposal](https://spinamp.mypinata.cloud/ipfs/QmehcCU8LjXRpj962YZYVJfHzwecvvdxbRH9BMEmiumcb9) for more details

# Overview
Snowbridge is a fully trustless, permissionless and general purpose bridge between Polkadot networks and Ethereum. The proposal covers a request for a 28 months worth of runway for all operations for the Snowbridge team, with the goal to launch as a common-good bridge on Kusama and Polkadot.

Our bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot.

The proposal includes a motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as incentives for successful execution, launch and long term running of the project.

# Changes
The original Polkassembly post was created 4 weeks ago with extensive community discussion around the project here: [https://polkadot.polkassembly.io/post/1341](https://polkadot.polkassembly.io/post/1341)

This final proposal is the same as in the above post, though a few small changes have been made:

- Added more details about the bridge hub, with XCMv3 and Statemint XCM as an extra milestone of work on our roadmap
- Add 1 month to the launch date to account for the extra work needed for XCMv3 changes for to bridge hub
- We've extended the runway to 28 months instead of 24 month, but we're keeping the price the same and will cover the additional months with a small reduction in costs

# History
Snowfork is one of the longest running teams contributing to the Polkadot ecosystem. For over 2 years we've been working on Snowbridge, a fully trustless and permissionless bridge to Ethereum. We successfully built and completed an initial version of this bridge in September 2021, based on an Ethereum Proof of Work light client and on Parity's original BEEFY proof system funded by an initial grant from the Web3 Foundation.

# Purpose
Polkadot already has a few live Ethereum bridges across various parachains, but these all compromise on Polkadot's security and trust model. Some are secured by trusted multi-sigs, some are secured by alternative insurance collateral, but none are secured by Polkadot and none of the Ethereum or ERC20 assets that exist in the Polkadot ecosystem today are secured by Polkadot's security and trust model.

We believe that without a fully trustless bridge that is secured by Polkadot itself, the security of the wider Polkadot ecosystem is put at risk and that Snowbridge's trustless design is essential to a healthy ecosystem that can support Ethereum-based assets. Similarly, trustless support for Polkadot assets across the Ethereum ecosystem will be a valuable boon for us all.

Snowbridge is also general-purpose, supporting arbitrary message passing and cross-chain smart contract calls, so any kinds of applications can be developed on top of it beyond plain asset transfer.

Additionally, as a common good service, longer term Snowbridge will be able to provide new value for the DOT token itself and generate an additional source of income for the treasury, or an additional lockup/burn mechanism for reducing the DOT supply.

## Funding Request
This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team *(16 months retroactive, 12 months in future)*, with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal has been uploaded to IPFS separately, and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project.

We request that anyone looking to meaningfully contribute to this discussion also reads through this full proposal.

This initial funding requests will be created alongside a secondary request on Kusama:

- **Requested USD on Polkadot:** USD 2,448,000.00 based on EMA7 rate by Subscan.
- **Requested USD on Kusama:** USD 612,000.00 based on EMA7 rate by Subscan.

There is an additional request for around USD 10,000,000.00 of long term economic incentives tied to key success milestones on the bridge, tied to measurable impact on the Polkadot ecosystem, although this payment will not be part of this first requested allocation.

We're planning to push out this proposal in the next month, and so are looking for early feedback and discussion from the community before going live with the proposal.

## Roadmap
1. Support XCMv3
2. Mint wrapped assets on Statemint
3. Governance and upgradability
4. Dynamic circuit breaker on withdrawals 
5. Security Audits
6. Deploy on Kusama (April 2023)
7. Deploy on Polkadot (July 2023)

See the [full funding proposal](https://spinamp.mypinata.cloud/ipfs/QmehcCU8LjXRpj962YZYVJfHzwecvvdxbRH9BMEmiumcb9) for more details.

Snowbridge Funding Proposal

This is a follow-up proposal on what we submitted [in mid-October last year](https://polkadot.polkassembly.io/treasury/177#88ca13f3-fd36-4772-8f0a-25bf109ba9f0), to further fund the development of the RPC services and to cover the maintenance costs of it.

This new proposal includes one Milestone.

**Milestone 1:** Continue to run the Polkadot, Statemint and Westend RPC services on dedicated hardware, located at small independent co-location sites in Sweden and Tunisia.


### Report from Q4 2022

- During Q4 2022 our Polkadot RPC node served on average **5,291,405** requests per day, and in total we served **486,809,279** requests. 
- During Q4 2022 our Statemint RPC node served on average **411,342** requests per day, and in total we served **37,843,427** requests. 
- During Q4 2022 our Westend RPC node served on average **56,764** requests per day, and in total we served **5,222,275** requests. 

Since our last proposal we have launched a [cluster in Tunisia](https://twitter.com/DwellirOfficial/status/1610539637583536128?s=20&t=2XsNIazwTRxOSXbhDJQ6XA), North Africa. The nodes in Tunisia are in production. 

Our full proposal can be [read here](https://docs.google.com/document/d/1ahopx0ALXjxuf0JEod-JFEelP_EcxQZp9kWIWVKhPkY/edit?usp=sharing).


**DOT price is based on EMA7 on the day of the submission: $6.068/DOT.**

Polkadot RPC services Dwellir Q1 2023

Messari is looking to renew its [existing engagement](https://polkadot.polkassembly.io/treasury/79) with Polkadot continuing to provide recurring research while expanding the scope and including more governance-specific work.

From this time last year, we have 3x our headcount with a team of over 150 after raising a Seris B led by Brevan Howard Digital. We’ve used that to significantly scale our research, data science, and engineering resources to build out our quarterly reporting and research capabilities. This has enabled us to bring all of our research in-house so we can have dedicated sector-specific analysts assigned to each protocol to cover them each quarter and continue to build up expertise.

We have also been working extensively on growing the distribution of these reports to further their reach and have signed deals with Bloomberg, S&P Global, and Refinitiv three of the largest traditional research platforms which are now distributing our quarterly reports.

We are proposing a continuation of the ecosystem-wide report along with quarterly reports while adding a governance deep dive. The total will be $190k payable in DOT with the same 10% premium to account for market volatility.

You can find more details in the [full proposal](https://docs.google.com/document/d/14eA2ZQhxru51xY2KeOtzN31Z9cT7blas_4sXWCNKfew/edit#) as well as the [forum discussion](https://polkadot.polkassembly.io/post/1521). 

Continuation of work through Messari Protocol Services

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 seeking financing for the maintenance and development of smoldot through treasury proposals. This post is here to gather your feedback on the proposal before submission on chain.

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

Thank you for reading

Tomaka

Treasury proposal: smoldot development financing

This motion aims to approve the [Wasm Smart Contracts Bounty - bounty 19(https://polkadot.polkassembly.io/bounty/19).

Proposed by coalition of teams to encourage and promote the adoption and development of WebAssembly smart contracts on Polkadot parachains, the goal is to create audited Ink!/Ask! smart contract showcases, an incubation program, and a React Hooks library called “UseInk”.  Please note that due to the value requested the proposal has been submitted as an external motion. Meaning, that after/in case of Council approval, the proposal will be up for community vote via Referendum for the final decision. For information on budget, roadmap and scope of work of the bounty, please visit the bounty's contextual information: [https://polkadot.polkassembly.io/bounty/19](https://polkadot.polkassembly.io/bounty/19). 

Please note the preimage for this proposal is submitted already, however, since the proposal is wrapped on an external motion call to be voted first by the council, the preimage is not noted on Polkadot.js Apps (this is an application issue). If the proposal passes to external queue, then the preimage will pair automatically. 

Proposal hash: `0xad5bd919076c71a6acba8ffafe12dfaf8ef83e40d69a56ee1ae1d5ffaa9f429e`

![](https://i.ibb.co/QQtPkQN/Screenshot-2023-01-23-at-11-17-39.png)


Approval of Wasm Smart Contracts Bounty - bounty 19

Hello everyone

I am [Jörg Oechssler](https://www.awi.uni-heidelberg.de/professuren/with2/joerg_oechssler.html), Professor at the University of Heidelberg (Germany) and I conduct experimental economic research as part of my job. I am generally interested in auction theory and have been approached by W3F researchers some time ago to investigate the exotic candle auction format that is employed by Polkadot to allocate parachain slots. Not much has been done in academia so far to measure this novel approach and how well the mechanism performs. We spent some time preparing a rigorous design to mimic the environment that the auctions take place, while keeping mechanisms and influences controllable.

Our method of choice is to analyze the auction in a laboratory experiment with students from the university. It is common practice in the field of experimental economics to test theories/models with students and pay them to participate.

With this proposal, I request **5720 EUR** (DOT rate to be calculated based on 7 day EMA rate: https://polkadot.subscan.io/tools/charts?type=price)) to pay those participants. **100% of the funds requested are to pay the students** (and to cover some exchange fees). Neither I, nor my team members receive any compensation from this proposal. All remaining funds will be send back to Treasury after the study ends. We are ready to start the experiment as soon as funds arrive. The experimental software is already programmed and we ran a pilot successfully.

The goal of this study is to publish it in a peer-reviewed journal.

Please find much more details on the background, design, and budget --> [here](https://docs.google.com/document/d/1pMbE0TvXfU-f9ZVncXbXeF05my5pfn-NR9lSg9ZLL5s/edit?usp=sharing) <--

Team Members:

* Jörg Oechssler (University of Heidelberg) - Beneficiary of the Proposal
* Jonas Gehrlein (Web3 Foundation)
* Samuel Haefner (University of St.Gallen, formerly Web3 Foundation)
* Florian Franzen (Web3 Foundation) 

- FT rate EUR to USD: EUR 5,720 = USD 6179,80
- 7 day EMA rate for DOT: 5.60 USD
- Total allocation requested: 1103.57 DOT

Experimental Analysis of the Candle Auction for Academic Research

Invalid

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.

This proposal aims to enable pre-checking for runtime upgrade on parachains: With pre-checking enabled a parachain is only allowed to upgrade their runtime **after validators have tried compiling it and they agree it is good**, as opposed to just accepting it blindly and then fail when the parachain tries to produce blocks with the new runtime. This is just generally a good idea, exists for a while already and has been successfully tested on Versi, Rococo and Westend. It is also required for rolling out slashing as it helps reducing the risk of unjustified slashes.

Parachains need to support the `go_ahead_signal,` but that should be a non issue as this has been introduced over a year ago.

 - Call to be enacted: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.dotters.network%2Fpolkadot#/extrinsics/decode/0x332901).

Preimage is submitted. Make sure to review and vote at your convenience!

Setting pvfCheckingEnabled In The Configuration To TRUE

**Original post by Kian:** https://hackmd.io/sP9KlLUBRpukfhL6GyPa2w

**The Problem**

On Polkadot, there is a fixed block time of 6 seconds. Only a relatively small portion of that time can be used for computation: 2 seconds (we need the extra 4 seconds to account for delay in propagation, time it takes for another node to import a block, among other things): even if every machine running a node was a super computer, we would have some upper limit to the amount of computation we can do in 2 seconds. **It is a must to try and keep our validator specs relatively within consumer hardware limits**. We cannot make crazy requirements on the network for running nodes.

We have reached the block in which the NPoS solution had to do the on-chain fallback. The block took about a minute on a local node to be imported, but all in all, the network was shaken for a solid ~ 30minutes until all nodes managed to recover and catch up. The core cause of this is that the staking pallet weights were re-measured again, and the weight for `submit_election_solution` increased almost two-fold. Regardless, **sooner or later NPoS size will be so big that the weight will become too much.**

**The Possible Solutions**

**First temporary solution:** https://github.com/paritytech/substrate/pull/7215 - This is a move toward **DNPoS**, since we are effectively limiting the number of active nominators. **The issue stands in limiting participation to small token holders.**

The immediate patch with PR 7215 (to be deployed soon) will partially remove a number of least staked nominators in favour of fitting the solution on chain. 

1. Some council members seem to favour the idea of **setting a minimum threshold to nominate**: combining this with ways in which small stakeholders can delegate nomination votes. 

- For some, it might be a good idea to set a minimum nominate amount in DOT: above 100 DOT. Like this, very small amounts will not nominate or must increase holding.
- Another idea involves allowing something like a central contract to hold many small nomination holdings and do one nomination for all of them, maybe incentivising 3rd party service to develop around this.
- A third idea is to incentivise the development of offchain nomination pools. 
- As a mid-term/long-term solution, it was also suggested to switch to a more lazy model for nominator slashing and reward.

2. Some of the council members **opposed the idea of setting a minimum amount to participate in staking**, while others stated that a low barrier to entry for governance and operation is a good principle but lack practicality and does not scale well: "...in terms of making usable governance/staking systems with the tools we have available today, that implementing certain thresholds for participation would be a positive thing (...) Our staking system would not be able to handle 1 billion 1 dot stakers as it is written today."

All in all, the idea that seems to be **the most supported** is implementing some participation threshold (based on the first points above) combined with a like-DAO-mechanism for users with smaller amounts of DOTS to collect and act as a single strong voice on Polkadot, i.e: having a hard limit of 100 DOTs to be a nominator, and a DAO so that any number of users can collect 100 dots together and use their own internal governance to choose validators could solve any scaling issues. Someone with less stake would get less flexibility choosing which validators to back than someone with more stake: if you have 1 DOT today you can select 16 validators of your choice to back. In this future scenario, you would simply need to find a DAO (or any other design) who would want to select those same 16 validators. Maybe you can't find that perfect group, but if a DAO supports 14/16 of the people you wanted, you would join them.

Thus the DAOs would convert a potential 7 billion human users into 10,000 groups which the pallet can handle. **Complementing the DAO proposal**, it was suggested to also charge some (optional) percentage fee for delegated participation in order for nominators to make better decisions: this already exists to some extent in a very ad hoc way, as some Validators offer a "controller as a service" for nominations.

A middle point between both POVs was suggested: implement vote delegation with the ability **to immediately withdraw** as the best tradeoff between technical scalability and giving everyone a voice.

**Coming soon?**

A design establishing a min threshold for nomination + DAO design to aggregate small token holders with an option percentage fee for delegated participation seems to be the most popular approach.

In the long-run, It was suggested to take advantage of dedicated system parachains which will offload computation of staking, democracy, etc onto dedicated parachains. We may even have those parachains have longer block times, which would extend the amount of computation that can be done in one block.


Polkadot discussion summary: NPoS solution size limit

[Tether](https://tether.to/en/) registered USDT on Statemint (asset ID `1984` - it can be verified here). The team is requesting Polkadot governance to make it sufficient such that it can pay transaction fees and exist on accounts without DOT. Tether's announcement can be found [HERE](https://tether.to/en/tether-tokens-usdt-live-on-polkadot/). Polkadot's announcement can be found [HERE](https://twitter.com/Polkadot/status/1573299786266050561).

On Statemint, assets can be Sufficient or Non-Sufficient. To hold a Non-Sufficient asset, the Statemint account needs to exist on-chain. This is different from Ethereum where a non-existent account can hold ERC-20 tokens, as users need to ensure that the receiver account has at least 0.1 DOT which is the Existential Deposit for a Statemint account. However, if an asset is Sufficient, the Existential Deposit in DOT on the receiver account is not needed to create the account; the asset itself is sufficient. The team is requesting this property to be voted by governance.

This proposal would allow much more flexibility for holders on Polkadot Network and the stablecoin will power transactions on Polkadot’s Statemint needed for asset deployment and balance-keeping of fungible and non-fungible tokens flowing across the web of blockchains. Many in the community believe as well that a stablecoin like USDT can boost the ecosystem and support an increase of transactions, specifically on DeFi-focused chains.

**Call on Statemint**

- Encoded call: `0x3212011f00d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d282b92a000100`

- Call hash: `0x842d8a934c2aa86a909e0232f730d2f974bfc01e307703a07eefbad6efdb9e1d`

![](https://i.ibb.co/smBWXHt/Screenshot-2022-09-26-at-09-23-00.png)

**Call on Relay Chain**

- Call hash: `0x5eea32679cdac9fc69d2d1ff7740104ec2bb6d412cb121505dbece9d34a239fd`

- Call data: `0x630001000100a10f0204060202286bee39023212011f00d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d282b92a000100`

![](https://i.ibb.co/XLwTgc6/Screenshot-2022-09-26-at-09-24-29.png)



Proposal for USDT Token Sufficiency on Statemint

Original post with multiple alternatives to solve this: https://polkadot.polkassembly.io/post/84

Polkadot's current design allows **validators to change the commission they receive for their work**, affecting the rewards nominators might receive for backing them up. The changes are virtually instant and without prior notice to nominators. Although this can help nominators to be alert on the changes in their set, it is not ideal.

We want to introduce one particular solution and open a poll for it: **invalidate nominations on commission increase**.

This alternative assumes that **changing the conditions (by increasing commission) of a tacit agreement should follow the cancellation of the agreement in question**: increasing commissions is ultimately changing a contract with a nominator. If a validator wants to do this, the result would be the cancellation of the agreement between both.

- Although a very effective solution to protect nominators' rewards, this option can become an issue for validators' setup, given it is expected for validators to create and develop a community around them. 
- The solution would work **only** when a validator increases the commission, **not** when a validator decreases it.
- If a validator goes offline, the commission is reset to zero and the validator has to set it again. The nominations are lost as well given the validator is offline, so going from 0 to whatever commission the validators chooses will not have a direct effect on nominations, since the validator already lost the nominations when the node went offline. For this reason offline status does not interfere with the mechanism. 


The solution seems to offer the most customization while incentivizing honorable behavior - we have opened a poll here for your vote to understand the preference of the community. Please vote to the right and leave your comment, if any, below! 

Please note that this is non binding and, if more than 50% of the participants on the poll are in favour of this solution, this will mean the Council will push for a serious discussion on implementation. If not, we will move to alternative solutions for discussion

Reopening The Discussion: Increase of Commissions by Validators, a Poll On Invalidating Nominations.

With the v26 runtime being in polkadot, [a bug](https://github.com/paritytech/substrate/pull/7384) that caused immature slashing of candidacy bonds in council was fixed, and now's the time to proceed with refunding affected accounts. 

**Context And Problem**

In the `elections-phragmen` pallet, each candidate has a life cycle with 3 possible stages, namely Candidate, Member or Runner-up. First, accounts can `submit_candidacy()`, and the pallet will reserve `CandidacyBond`. If the account makes it into the Members or Runners-up list, then this bond is kept. Else, a loser candidate will always lose their bond (`slash_reserved()`). Moreover, members and runners-up must also `renounce_candidacy()` in time. If they lose their spot in an election round (i.e. no longer hold any role), they also lose their bond as the consequence. 

Due to an API confusion, we sometimes mis-calculated the outgoing runners-up, thus slashing them prematurely. Furthermore, we mistakenly slashed members and runners-up when they moved in between the roles.

This did not affect all accounts, but some bonds were taken by this error. The team discovered that the root of the issue was in the `election-phragmen` pallet. **The bug is now fixed in v26 (and 2026 in Kusama).**

We have gathered info about this in the last few weeks. Kian, from the Parity team, [recorded a short video](https://youtu.be/7tiGwqiaPZM) for transparency of what happened and how we intend to fix it. 

- A more detailed write-up about the event, including details of how the refund is calculated and can be reproduced: https://hackmd.io/HZVxUWuKTHSVHdjRVtwE0g
- Spreadsheet of current calculated refunds: https://docs.google.com/spreadsheets/d/1dHch86flQ-yXw-BJcnjWLqND2nxOcp4p-hppcuD_DqA/edit?usp=sharing

**Steps Going Forward**

1. **Discussion by the council**, questions and comments on the incident;

2. **Reimbursement of the affected accounts**: The reimbursement process can happen in two ways:

- Tipping from the treasury pallet: Opening one tip per user for the calculated amount and requesting endorsement by council members.
- Wrapping all of the reimbursement calls inside a `utility.batch`, creating a single batch of force transfers from the treasury to the affected accounts, to be voted by the community.


Feedback on the steps going forward is welcome!

Incorrect Slashing on Council Caused by elections-phragmen Pallet Bug

Corect link for Kusama's Polkassembly: https://kusama.polkassembly.io/post/446

Final Review: Lottery Pallet in Kusama Network

After reaching the 300 validators milestone on Polkadot, we are reviewing network metrics to decide on further steps.

The full report can be found [HERE](https://drive.google.com/file/d/1_Z7AWK_5e2IcDQV7_G7ViX6YEerot2mB/view?usp=sharing). 

Recommended steps:

- BABE and GRANDPA are running smoothly with up to 1000 validators, but the parachains consensus logic is far heavier and more complex and **will need optimization to reach that point**. As such, the parachains team is planning to only use some limited subset of the validators initially (perhaps 50, 100, or 200) randomly selected each session for parachain consensus. Those selected validators to do parachain consensus will receive the bulk of the rewards for each session. Over time, the amount of rewards each validator receives will be roughly equal, but **increasing the validator count relative to the amount of validators participating in parachains will lead to increased variance of rewards. For that reason, the parachains team recommends keeping the amount of validators low** to achieve an outcome of low reward variance, an earlier launch of parachains and consensus stability.

- Closely monitor the `MinStake/AvgStaked` ratio as we increase the numbers of validators in a future proposal.

- Continue with the plan to produce and distribute educational resources for new nominators focusing on what to look for when choosing validators. The resources should review the differences between nominating new/small validators and established ones. Furthermore, encourage validators to produce reports and for nominators to those use as signals of confidence when staking.

Performance Report I: 300 Validators milestone, Polkadot Metrics and Next Steps

To gradually increase the number of slots for validators, I propose scheduling the increase over time for 200 slots. The scheduled event mechanism (submitted by external motion to council and then pass to referenda queue for vote) aims to increase the number of validator slots steadily upon certain conditions. In the case of Polkadot:

- An increase by 1 every era (24hs)
- A repetition of the increase for 100 eras for now.

This mechanism can be canceled or completed after 100 eras, and at that moment the community will be able review network metrics. The proposal aims to avoid an abrupt increase in the number of validators on the network and follows the recommendation of the parachains team as noted [**here**](https://polkadot.polkassembly.io/post/263). 

Increase of validators slots to 500 - last suggested increase until further notice by Parachains team

Without a fairly deep and expert-led look at the website/whitepaper/code, it is difficult to distinguish between good and bad players in the ecosystem. I’d like to explore the idea of the **Kusama** and **Polkadot** councils agreeing on a pact as sovereign entities, to **discourage bridging to rival Polkadot-style relay-chains**. This initiative is based on the principle of **_the least number of relay chains_** (link below): a first step aiming to judge new potential relay chains connecting to the overall ecosystem.

The Polkadot and the Kusama Councils **should aim to align efforts in protecting our community and, as representatives of passive stakeholders, make a pact outlining specific actions encouraging community members to support these initiatives**.

In this spirit, the document below frames actionable items related to this goal. This post is open for feedback by the Council and community in general. Please note [**_the principle of least number of relay chains_**](https://gist.github.com/sorpaas/d64a0ff2529058416ce6e223f32d3b1b), originally thought by Wei Tang, is useful to encourage a minimum number of relay chains in the ecosystem and to not spend resources to unnecessarily create new ones. After defining the principle, further points in the document try to define actionable items based on this. The pact is meant as a framework for action against relay chain projects that are not deem necessary at current network conditions: If additional infrastructure is not needed, but existing infrastructure can be used without drawbacks then we should keep using the existing infrastructure, and If something can be connected to an existing relay chain, then we should connect to it instead of creating a new relay chain.

This agreement has the ultimate goal of avoiding using resources from Polkadot and Kusama to develop these chains and providing any type of information to the community about proposals or teams whose roadmap includes this goal, as well as discouraging bridging to these. 

The document can be found [HERE](https://docs.google.com/document/d/1il54_VL1dAHN78t9Dl3qeU3atHmBOpku_dqhJReDClo/edit?usp=sharing).

Polkadot Alliance Pact: Protecting the Integrity of Our Relay Chains and Parachain Communities

[Wei](https://social.that.world/@wei), one of Polkadot Councillors and long-time member of the Polkadot community, shared some ideas related to Polkadot's governance improvements. Specifically, introducing "blind voting", the option to "abstaining" and Council voting process restructuring. The three write-ups can be found here:

- [58-BVOTE: Blind voting for Polkadot](https://specs.corepaper.org/58-bvote) 
- [59-ABVOTE: Allow explicit abstain in adaptive quorum biasing](https://specs.corepaper.org/59-abvote)
- [60-CKA: Council Keep-Alive](https://specs.corepaper.org/60-cka)

The goal is to try to boost interest for people to discuss improving Polkadot's governance mechanics design, increase participation and reduce inactivity, hold community members accountable (including Council members) and make the overall process more efficient. 

Please leave your feedback and questions on these notes, now up for discussion!

Polkadot Governance Improvements by Wei

We'd like to summarize the different actions taken to increase the number of validators on Kusama Network, aiming to open the discussion on the best way to do so on Polkadot Network moving forward. In the past 4 months, there were three mechanisms used to increase the numbers of validator slots on the network:

**Public referenda pushed by community members and external motions by Council:**

This mechanism was the first one used on Kusama to increase the number of slots: A community member submits a proposal for public referenda or an external motion (if the proposer is a councillor) that will after pass to the referenda queue. The proposal suggests what the new number of validators should be. The main weakness of this approach is the random choice regarding the number of validator slots to add to the set. The value randomness does not take into account factors such as network stability, minimum and average staked, number of nominators and number of waiting validators. 

Although this mechanism was widely used at the beginning, we have moved to more controlled and gradual increase mechanisms. This is being used on Polkadot right now, as reflected in [Referendum 2](https://polkadot.polkassembly.io/referendum/2) aiming to increase the number of validators to 236 slots. 

**Scheduled events via democracy:**
	
The scheduled event mechanism (submitted also either via public referenda or external motion to council) aims to increase the number of validator slots steadily upon certain conditions. In the case of Kusama, we reached the 500 validators milestone by using a scheduled mechanism decided by the council and proposed by a council member. Starting at a particular block number in the future, the number of validator slots would increase by 2 every 3600 blocks (which in Kusama speed means 6hs/1 era). This mechanism was repeated for about 150 eras until Kusama reached the 600 validators milestone. After, it was canceled to review network health metrics and develop the third mechanism, explained below. 

**Automatic increase function**

After the 600 validators milestone was reached on Kusama, the council decided to propose a pause in the increase of validator slots to: 1. Analize metrics concerning network health, stake distribution and network bandwidth; 2. Come up with a mechanism that would allow an automatic increase of slots based on these metrics. 

With this in mind, a mechanism proposed by the Parity and W3F teams is being implemented by a member of the community. The mechanism is based on the Minimum/AvgStaked ratio and follows 2 specific rules:

**Rule 1:** If the bottom 1% of validators (more precisely, ceil(0.01 k) validators) have an average staked value strictly above 40% of the global average, in the next era increase the number of active validators by 1%, i.e. k <-- min{K, k + ceil(0.01 k)}.

**Rule 2:** If the bottom 2% of validators (more precisely, 2 ceil(0.01 k) validators) have an average stake value strictly below 20% of the global average, in the next era decrease the number of active validators by 1%, i.e. k <-- max{100, k - ceil(0.01 k)}.

The goal of the function is to increase/decrease the number of validators based on the network's current status, taking into account the ratio explained above. The desired value of the ratio is configurable in the function, meaning the value depends on the decision of the community: on Kusama, we suggest a 40% value for the ratio. The mechanism will be tested soon. 

The summary's goal is to open the discussion on the best way to handle validator slots increase. We invite all members of the community to leave feedback, comments and questions to move to a call to action on Polkadot in the future.

Opening the discussion on the increase in the number of validators on Polkadot Network

As mentioned by the Staking team on [this message](https://matrix.to/#/!FdCojkeGzZLSEoiecf:web3.foundation/$YNsqfhHKXoRbW_QKvtG5EKn8HodUGFts6abJJdSAoVA?via=matrix.parity.io&via=matrix.org&via=corepaper.org), Polkadot currently has 22500 nominators and the configuration of the staking system prevents further nominators to join. 

The team suggests to update the staking parameters as soon as the next runtime upgrade happens today. The proposal has the goal to increase the minimum bond to allow new nominators above the threshold to participate in the network’s security mechanism, and for less staked nominators to be chilled. Note that after 9080, the existing nominators can always update their preference at all conditions. 

The proposal the team suggested will change the staking parameters to allow more nominators with higher backing stake be able to join the staking system. The existing parameters as as follows:

* minimum validator bond: None
* maximum validator count: `1200`
* minimum nominator bond: `40` DOTs
* maximum nominator count: `22500`

The new proposed parameters will update one value:

* new minimum nominator bond: `80` DOTs 

and set a new parameter that did not existed before:

* chill-threshold: 90%

The reasoning behind the new minimum nominator bond: Polkadot onboards ~150 nominators per day. That means if the network has 4500 empty slots, they will be filled in 30 days. The team aims to increase the limit enough so that we won't need to do another tweak for at least a month. Changing this parameter to `80` will almost expose 4500 nominators. 

The new chill-threshold will ensure that the permissionless `chill_other` can only be used when more than 90% of "maximum nominator count" is used.
note that to ensure polkadot's stability until the parachains launch, this motion does not yet include an increase in the total count of nominators. Multiple tracks of optimization are ongoing by the development team, and you can read more about them in this [issue](https://github.com/paritytech/substrate/issues/9511).

Please note that doubling the value of the parameter to `80` DOTs will hopefully give the team more time until the new threshold is reached and we have made progress on a more permanent solution. Please leave your comments and feedback on the proposal. Keep in mind these measures are temporary, and the overall goal is the stability and security of the overall network.

Increasing Nominators’ Minimum Bond on Polkadot

Any wallet that can make a `remark` call on Polkadot is able to be used to cast your vote. At the moment, only the [Polkadot extension](https://polkadot.js.org/extension/), [Parity Signer](https://www.parity.io/technologies/signer/), [Ledger](https://www.ledger.com/) and any wallet that supports QR signing can be used to sign your call. Below are some instructions on how to sign using the different wallets.

## Before You Cast Your Vote

Before you vote, you need to make sure the account you will be using to vote is added to the [Polkadot extension](https://polkadot.js.org/extension/). After installing the extension on your browser, make sure to follow these steps:

### a. Voting Directly Using The Polkadot Extension

Before you start, if the account you want to vote with is not in the extension already you can restore it with its 12 words mnemonic phrase following [these instructions](https://support.polkadot.network/support/solutions/articles/65000169952-how-to-restore-your-account-in-polkadot-js-and-the-polkadot-js-browser-plugin). After you have imported your account, you are ready to vote.

### b. Using Parity Signer

Before you start, make sure to import your account on Parity Signer in the Polkadot extension using the generated QR code from the account you want to vote with. For this, first click on the gear icon on the top right corner of the extension and enable **“Allow QR camera Access”**.

![](https://i.ibb.co/YyC2mwJ/Screenshot-2021-10-27-at-11-07-18.png)

Then click on the **+** sign next to the gear icon and choose **'Attach external QR-signer account'**. 

![](https://i.ibb.co/F6NjLsM/Screenshot-2021-10-27-at-11-09-01.png)

Select your account in Parity Signer and scan the QR code on your screen to add the account to the extension: do not worry, your private keys will not be stored in the extension! After scanned, your address should appear listed in the extension:

![](https://i.ibb.co/PQY3zWj/Screenshot-2021-10-27-at-11-09-56.png)

And add the account by clicking on the orange button.

### c. Using Ledger 

Before you start, make sure to import your Ledger account in the Polkadot extension following [these instructions](https://support.polkadot.network/support/solutions/articles/65000175387-how-to-add-your-ledger-through-the-polkadot-js-extension). 

**NOTE FOR NANO S USERS**: In order to participate in the vote you’ll need to have the XL version of the Polkadot app installed. Check [this article](https://support.polkadot.network/support/solutions/articles/65000179210-ledger-error-not-supported) for more information and how to install it. Also, please keep in mind that the XL version is not compatible with Ledger Live.

## Cast Your Vote

1. Scroll down the voting website until you see the window to connect your extension to the application:

![](https://i.ibb.co/tMvMp1N/Screenshot-2021-10-27-at-11-10-34.png)

2. Click on Connect and authorize your extension to connect to the application.
3. Authorize the Extension to connect to the application:

![](https://i.ibb.co/m5pwqhP/Screenshot-2021-10-27-at-11-11-11.png)

4. Select the account you wish to vote with and distribute your votes to your preference:

![](https://i.ibb.co/hZR8t1P/Screenshot-2021-10-27-at-11-11-49.png)

5. Sign the transaction by clicking on Cast my Vote. A pop-up window from the extension will open up asking to sign the transaction. 

a. If you’re signing with an account directly in the extension, all you need is the account's password. 

b. If you’re singing with Parity Singer, scan the generated QR code with your Signer and present the generated QR code on your phone to your computer’s camera. 

c. Finally, if you’re singing with your Ledger, you need to APPROVE the extrinsic on the device. 

6. Once you have signed the transaction, the following window will appear:

![](https://i.ibb.co/gt2BdCP/Screenshot-2021-10-27-at-11-12-38.png)

You can confirm your vote using any block explorers to the left (for a list of all available block explorers, check [this article](https://support.polkadot.network/support/solutions/articles/65000178909-what-block-explorers-can-i-use-for-the-polkadot-and-kusama-ecosystems-). Continue voting with a different address included in your extension or leave some feedback! 

## How To Verify Your Extrinsic

It is always good practice to verify the extrinsic you’re about to sign before actually signing it. A remark call costs only a few cents in fees. But if you’ve found yourself on a phishing site, you could be sending all your funds to a scammer, if you don’t pay attention. So keep reading and if you want to learn more about verifying extrinsics, check [this article](https://support.polkadot.network/support/solutions/articles/65000179161-how-can-i-verify-what-extrinsic-i-m-signing-).

### How to verify the extrinsic in Polkadot Extension
On the pop-up window that opens up, pay special attention that the method of the call is the extrinsic `system.remark` along with the vote distribution you chose, as shown below.

![](https://i.ibb.co/vD2q35y/Screenshot-2021-10-27-at-11-13-20.png)

If what you see in the extension is something different, **DO NOT** sign the transaction and contact support@polkadot.network! It is possible you are on a fraudulent site or using a fraudulent extension!

### How to verify the extrinsic when signing with Ledger
Like above, pay special attention that the method of the call is the extrinsic `system.remark` along with the vote distribution you chose. However, the information of the extrinsic is shown on the Ledger device as well. Verify on your device that the extrinsic is indeed `system.remark`, like in the picture below:

![](https://i.ibb.co/gTqvxRM/Screenshot-2021-10-27-at-11-14-01.png)

Then proceed through the following screens to APPROVE signing. 

If the extrinsic call is not `system.remark` **DO NOT** sign the extrinsic! Proceed to the last screen to REJECT it and contact support@polkadot.network! It is possible you are on a fraudulent site or using a fraudulent extension!

### How to verify the call data on Ledger
Before reaching the “APPROVE” screen on your Ledger, the call data of the extrinsic is shown on the screen. At the moment, there is no straightforward way to verify that call data corresponds to the message shown in the extension window, but if you are a security-minded user, read below to learn an indirect way to verify it: 

1. First select the text of the remark (without the quotation marks), right click on top of the selection and click **Copy**:

![](https://i.ibb.co/PWKpYdD/Screenshot-2021-10-27-at-11-14-35.png)

2. On [Polkadot-JS UI](https://polkadot.js.org/apps), go to Developer > Extrinsics,
3. In the first field select your Ledger account,
4. In the second field, select “system” on the left and “remark” on the right,
5. Then in the field below paste the message you copied in Step 1,
6. The call data will correspond to the extrinsic’s details and you can cross-check it with what you’re seeing on the device:

On Polkadot-JS UI:

![](https://i.ibb.co/6vrbnJJ/Screenshot-2021-10-27-at-11-15-12.png)

On the Ledger device (this is the first of three screens showing the call data):

![](https://i.ibb.co/R4vGRnv/Screenshot-2021-10-27-at-11-15-48.png)

### How to verify your extrinsic when signing with Parity Signer
Unfortunately it’s not possible to verify your extrinsic when signing with Parity Singer. To learn more why that is, please check [this article](https://support.polkadot.network/support/solutions/articles/65000179161-how-can-i-verify-what-extrinsic-i-m-signing-). So, **double-check** you are visiting[ https://vote.polkadot.network/](https://vote.polkadot.network/), the padlock sign is shown in the address bar, you have installed the **official** [Polkadot extension](https://polkadot.js.org/extension/) and that you have made the vote distribution you wanted before initiating the signing.

Brand On-Chain Vote: Can I Vote With Any Wallet?

Polkadot's current design allows **validators to change the commission they receive for their work**, affecting the rewards nominators might receive for backing them up. The changes are virtually instant and without prior notice to nominators. Although this can help for nominators to be alert on the changes in their set, it is considered by many as not ideal. 

Below, a brief summary of an ongoing discussion on this and some possible solutions presented by the Parity team and external contributors to regulate changes on commissions:

Two main solutions come to mind when discussing the topic:

**1. Implement a `MaxComissionChange` parameter, which is a configuration a validator will set as the max amount of commission they will be able to increase or decrease per era. **

`MaxCommissiomChange` is a preference the Validator would set for themselves, such that they cannot change their commission + or - more than that amount per era. So if a validator says their value is 10% and their commission is currently 5%, trying to set a 20% commission the next era will fail: This would have no effect on Nominators and removing nominations.

**2. add a `RemoveNominationOnComissionChange` parameter for a nominator, where they would specify if they would remove a nomination if the validator changes their commission (perhaps by some threshold).**

Both can help prevent Validators from pulling the rug from nominators, but demand storing more state on-chain. While the first protects validators, the second one seems to **reinforce the idea that there is a type of contract between the parties** to take care of.

**3. A third opinion was to invalidate all nominations on commissions' change, following the rationale that changing the conditions of a tacit agreement should follow the cancellation of the agreement in question.** 

Although a very effective solution to protect nominators' rewards, this option can turn problematic for validators' setup, given it is expected for validators **to create and develop a community around them**. Furthermore, if a validator lowers its commission to become more attractive to nominators, this would not be beneficial in the end for both parties, as nominators would stop backing up the validator and the validator would lose support, even by benefiting nominators. 

**4. Regarding off-chain solutions:** an alternative is to build a server to monitor the commission change, and send an email to subscribers if it increases. Seems like an idea that the Polkadot treasury can support. This solution, although practical is deemed not very privacy friendly. A possible solution for it would be to use [Ryabina's telegram bot](https://github.com/Ryabina-io/substratebot) as a way to notify the parties.

There is an open issue about the topic to review [here](https://github.com/paritytech/substrate/issues/6920). 

Feel free to add your comments on this post as well. 


Increase of Commissions by Validators: Summary of the discussion.

As many of you know, [Supercolony](https://supercolony.net/) requested funding from treasury to organize the **first Smart Contracts on Polkadot - WASM conference** and bring the community together to discuss this particular topic. The proposal was approved, after some discussions regarding budget and platform for online event, by [motion 152](https://polkadot.polkassembly.io/motion/152) a few days ago (more information on budget, milestones, roadmap and agenda can be found there). 

The conference website can be visited [HERE](https://wasm-conference.com/). 

Given recent events, and since the main organizers of the conference are located in Ukraine, they had to move from Kyiv for safety purposes. The holders of the beneficiary multisig for the proposal (`16PtCn76c7SB8mMDnuWsq5BjtaDetH8apZh5hRrHtLA3ce1W`) unfortunately lost access to the address while going away from Kyiv and have asked me what the alternatives to recover the funds, given they are still working to deliver the conference to the community.

I want to present two alternatives to the community for feedback, for action: 

1. The Council cancels the scheduled transfer ( approved proposal 82 - to be executed in approx. 6 days) and opens a new proposal for the exact amount to an address that is controlled by the party (after on-chain identity verification by a Registrar).  This could be designed as a `batch` call containing both actions.

2. [Motion 152](https://polkadot.polkassembly.io/motion/152) is executed next week: after, the community can vote in referenda queue for a `forceTransfer` call that moves the funds from the old multisig to the new one (after on-chain identity verification by a Registrar).

We will work with Toma, from Supercolony, to ensure the new beneficiary address for any of the alternatives above is verified for security purposes. And to make sure they have the safest setup possible. Other alternatives the community would like to present can also be included on this post. This proposal is opened for the community to give feedback. 

Helping Supercolony Recover Funds From Treasury Proposal

This proposal is explained as suggested by Kian from the Staking team.

**NOTE**: this proposal is using the new terminology introduced in [the February newsletters](https://docs.google.com/document/d/1bisngPfte-P2vMuP_JrV6fIpNnd04uCWrqt4UbFklF8/edit#heading=h.kdyyexvr13fu), please refer to that for a recap.

This proposal aims to alter the limits on the nomination intention for Polkadot, namely lowering them since they are not strictly needed anymore.

As of release of runtime 9170, pallet-bags-list has been [fully enabled in Polkadot](https://docs.google.com/document/d/1bisngPfte-P2vMuP_JrV6fIpNnd04uCWrqt4UbFklF8/edit#heading=h.z30dvegsxvsi), and setting the intention to nominate should now be made possible for a larger audience. In essence, the number of intentions need no longer be bounded by 22,500. The bags-list will take care of picking up the top 22,500 nominations (those who become “electing”). Thus, we propose the following:

1. Increase the number of possible intentions to **50,000**. 

**NOTE**: that this number could be lifted altogether, but we suggest keeping an upper bound that’s dynamically controlled by the governance as an extra safety measure, at least for the time being.

2. Decrease the amount of stake needed to submit a nomination intention to **10 DOT**.

**NOTE**: Similarly, this number could also be lowered back to 1 DOTs, which is the existential deposit, but we suggest doing that as a next step within the next few months, and for now keep this small limit to prevent a massive sudden influx of intentions. 

Call design:

![](https://i.ibb.co/RczyGyY/Screenshot-2022-03-09-at-09-57-10.png)

Encoded call data: `0x071700e87648170000000000000000000000000000000000000000000000000000000150c3000001b0040000015a00000000`

**Urgency**: Ideally, this proposal should be enacted before the number of total nominators in Polkadot reaches 22,500 (the value for which at the time of this writing is 21,214). If it does, the ‘nominate’ transaction will become unavailable to all stakers. This proposal should have no negative effect on any stakers, as it will only relax the limits to submit for nomination intentions.

Polkadot Proposal: Lowering Nomination Intention Limits

To gradually increase the number of slots for validators, I propose scheduling the increase over time.

The scheduled event mechanism (submitted by external motion to council and then pass to referenda queue for vote) aims to increase the number of validator slots steadily upon certain conditions. In the case of Polkadot:

- An increase by 1 every era (24hs)
- A repetition of the increase for 100 eras.

This mechanism can be canceled or completed after 100 eras, and in that moment the community can review network metrics. The proposal aims to avoid an abrupt increase in the number of validators on the network.

What is left to decide is if we could request the Technical Committee to fast-track the proposal, in order to avoid a long waiting period until execution. Open to hear your thoughts on this.

A proposal to gradually increase the number of validators

Based on the income to the treasuries, the amounts getting burned and the amounts going to proposals, the treasury can be utilized more: this includes spending more funds, extending the categories of proposals, experimenting more and encouraging more participation.  We are at a point where we should think about ways to scale this and incorporate additional means of supporting nascent parts of the ecosystem.

Many other ecosystems have started funds to deploy to their ecosystems: both for the purpose of funding new teams but also to deploy to initiatives like liquidity programmes that try and encourage adoption. The end goal is to encourage value accrual: either for the treasury itself, the projects building in the ecosystem or the communities and end users participating in the Kusama and Polkadot ecosystems. 

## The Treasuries As Liquidity Providers

One thing that other ecosystems have started are initiatives around liquidity incentives to kickstart projects. What this might look like is approving allocations towards DeFi protocols (or parachains, in Polkadot's case) to encourage an increase in user metrics. Considering a lot of the use cases and features that cross-chain interoperability brings to Polkadot, it would be extremely useful to kickstart projects with liquidity for borrowing / lending, money markets, derivatives/options, synthetics, DEX / AMM pools, protocol owned liquidity and other primitives that allow for applications to attract end users. These sorts of programmes have worked extremely well for other ecosystems and Polkadot / Kusama is missing out on a lot of opportunities in their absence.

However, this won’t come without some paired risks: therefore some considerations in place for any sorts of proposals related to liquidity provisioning is needed: mainly for the purpose of mitigating potential downsides. **This document aims to provide specific guidelines for governance participants to review and vote on liquidity proposals, as well as proposers to draft their submissions.**

## Considerations for Proposals

A key expected outcome of launching such programs will be to substantially increase on-chain activity in the form of increasing active users, transaction volume and TVL in the long-term. These proposals should have the goal to primarily achieve increasing levels of TVL resulting as well in increasing active users, transaction volume but also specifically attracting more builders to Polkadot and Kusama ecosystems. While **liquidity subsidies proposals** have been dominant among parachain teams' proposals (direct participation in a protocol to increase market depth and lower transaction costs by reducing slippage), proposals might also focus on: 

1. **Reward Subsidies** (direct rewards used to incentivize users to add liquidity to protocols) 
2. **Bridge subsidies** (rewards paid to incentivize users who hold tokens on other base-layer ecosystems to bridge them over to the target ecosystem). 

These guidelines are intended to target parachains proposals that seek liquidity subsidies as well as protocols building on top of them. Liquidity proposals should ideally incorporate the following elements:

- **How large is the requested rewards subsidy?** Are there any matching conditions from the protocol? This ensures commitment and is an objective and quantifiable metric to determine reward subsidy amounts. 
- **Audit report** and proving working record of the protocol. 
- **Time horizons:** with regards to when the ecosystem can see the first results on the proposal and when the allocation or its accrued value will be returned (if any);
- **Projected yield:** ideally a specific definition to take as success metric is needed for the community to judge the final result of the proposal. Make sure to include what is the current traction of the protocol (MAU, TVL, trading volume, fees). This will allow the community to assess future metrics. Ideally, the project can also provide data source for auditable tracking the usage and success of reward subsidies.
- **On-chain instruments in which the funds will be used**, along with a description and the way these will be deployed: what are the planned use cases for the subsidies?
- **Any potential risks** resulting in the loss of funds;
- **Projected incentives to the wider ecosystem** and how the allocation will help increase adoption: what is the mechanism and timeline for distributing rewards to users?
- Other success metrics.


When drafting a proposal and when reviewing it, participants should judge the proposals based on these specific requirements:

- When thinking about liquidity proposals we should ask ourselves: "*is this proposal aiming to increase DOT velocity and utility? And is this compatible with the treasury requesting some sort of accrued value over time from this proposal?*".
- These proposals should be designed with the partial goal of accruing qualitative value to the treasury and thinking of this instrument as a sort of loan that will be returned to the community via network effects: showing that these funds result in profit for the overall network. This might not be a requirement for all use-cases but it can be included and requested as one by the community.
- Funds given for liquidity provisioning should be done in a completely trust minimized or trustless way: ideally where the treasury itself can directly put and withdraw liquidity into these opportunities (What this might look like practically is in the form of XCM related transactions). Alternatively, and if limited by the current tech stack, the team requesting the funds can open the management of these funds to their community in a transparent way. 
- A specification on how the beneficiary address is set up, who controls it and how will be the management work for the address is to be described in the proposal.
- Has there been any on-chain events which stop the parachain from progressing for at least 1 week in the last 3 months? Stability is important in the ecosystem, and we need to make sure parachain teams are prepared to deal with stalling issues. 

All of this should happen in a trust-minimized environment, if possible. Once granted, subsidies will be deployed from the Treasury to the grantee’s protocol. The logic will hold the tokens and distribute them to users according to the parameters of the contract.

[This proposal template](https://docs.google.com/document/d/1HUvsAi-D-MWXZOtfGCGZkDpN04sOsGVyjKZ6CsnazkA/edit?usp=sharing) has been designed to help teams provide all information to the community: a copy of the template can be made to complete with all requirements above.

Standard Guidelines to judge Liquidity Treasury Proposals on the governance side - Kusama and Polkadot

The **Composable Finance** team has had [the same issue](https://kusama.polkassembly.io/motion/427) essentially as on Picasso chain on Kusama, so one particular cause: The team had a stray [todo!](https://github.com/ComposableFi/composable/blob/094d4668400c7832ccd601863a175eeb931782e3/runtime/picasso/src/weights/democracy.rs?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L117) in the weight calculations for pallet-democracy [which doomed the chain to be bricked once the launch period elapses](https://github.com/paritytech/substrate/blob/542a8585339d2581e641df339d254d7dd22b1456/frame/democracy/src/lib.rs?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L1758-L1763).

- Public wasm file to use can be found here: [https://github.com/ComposableFi/composable/releases/tag/v2.1.2](https://github.com/ComposableFi/composable/releases/tag/v2.1.2)

- Preimage design:

![](https://i.ibb.co/sjtNZqF/Screenshot-2022-03-28-at-09-53-06.png)

- Preimage hash: `0xad2813b46b52fe8f38cb5af7da9c7f0f66416900070b949daa62cf92bbdc6fd7`


Help Composable Finance Unbrick Their Chain

We, Raul and Otar of JUST Beteiligungen GmbH, are proposing retroactive funding from the Polkadot Treasury to recognise our contributions to the ecosystem, which encompassed a variety of activities, including supporting and executing runtime upgrades and various configuration adjustments, facilitating OpenGov implementation, providing guidance on hundreds of treasury proposals along with initiating motions as well and offering ongoing assistance to ecosystem stakeholders.

So far, these efforts have been undertaken at our own expense. Unfortunately, sustaining this level of commitment independently is not feasible in the long term. Therefore, we are seeking retroactive funding from the Polkadot Treasury to support our past contributions effectively.

We invite the Polkadot community to review [the detailed proposal here](https://docs.google.com/document/d/14DqrsaVty31Q_HQvyaUUpI-TBRZ29bfWUjLFTJqx8xg/edit#heading=h.v6is2ta0txr1) and vote on the proposal. Please leave your feedback below as well!

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

JUST Retroactive Compensation for Contributions to the Polkadot Ecosystem

[Motion 341](https://polkadot.polkassembly.io/motion/341) was a proposal submitted with the goal to fund the continued production of RMRK Substrate pallets: adaptable to the entire ecosystem. As it is accustomed with treasury proposals higher than 500k USD, this was submitted as an external motion, to be voted by the Council and after in referenda queue by the community for the final decision. 

The Council failed to pass the motion, and we suggested to the team to submit this as a public proposal to put it up for vote by the community. The team requested to withdraw their application. This tip aims to return the 500 DOTS deposit for the submission proposal to the team to after reject the treasury proposal and slash the deposit. 

Returning submission deposit for RMRK in order to reject treasury proposal 222

This proposal is submitted on Auction Admin track: coretime is already scheduled to be enacted during LP17 and this proposal aims to have a safeguard for a more cautious approach and schedule 8 auctions during LP17 for LP18 in case coretime is not ready in time. If coretime enacts successfully (as in Kusama Network) these auctions **won’t be needed** and their cancellation will happen directly with the next runtime upgrade, which includes the migration to coretime. 

These will be 8 auctions for LP18, auctions happening on LP17.

![image](https://i.ibb.co/mFJvkXX/4773-rtti5220-1716972653572.png)

Schedule hash: `15cc5a33781f3b0514473401a7ca5806a74c9123502d22f6bbc7b978b3fe337c`

Proposal Hash: `0x4031a089a8ca3a085d53387fc9a1a510d9a1371be578fe99ccef8307a5220556`  

Preimage is submitted: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-polkadot.luckyfriday.io#/extrinsics/decode/0x0a00e81a0404010287a871b4d621f0b973475aafcc32610bd7688f1502338acd00ee488ac3620f4c00d5470101491e020008000000004800e2a5010048

Please make sure to review and vote at your convenience!

Proposal: Adding More Auctions For LP18 On Polkadot

Due to Gavin not being inducted on Fellowship as an active member (something all Fellowship members need to execute) [referendum 814](https://polkadot.polkassembly.io/referenda/814) did not execute successfully. Therefore, I am resubmitting the proposal (same track, same preimage):

## Member Details

- Member e-mail: gavin@parity.io
- Polkadot address: 16SDAKg9N6kKAbhgDyxBXdHEwpwHUHs2CNEiLNGeZV55qHna
- Current rank: "VI Dan: Grand Architect" (to be promoted to "VII Dan:  Free Master", as per the [Fellowship manifesto](https://github.com/polkadot-fellows/manifesto/blob/main/manifesto.pdf): requirements and obligations in the document) 
- Date of initial induction: November 2022
- Area(s) of Expertise/Interest: Technical design, Protocol evolution, Socio-political direction

Almost seven years after writing [the Polkadot Whitepaper](https://polkadot.network/whitepaper/) (well above the strict minimum of 6 years required for VII Dan), please find some of the most prominent contributions from Gavin to the ecosystem:

## Reporting period
Start date: 2023/05/16
End date: 2024/05/28

## Areas of contribution

**Polkadot SDK:**

- Specification & implementation of Agile Coretime (brokerage system).
Specification of Agile Coretime (interface). [RFC 1](https://github.com/polkadot-fellows/RFCs/blob/main/text/0001-agile-coretime.md) & [PR 14568](https://github.com/paritytech/substrate/pull/14568), [RFC 5](https://github.com/polkadot-fellows/RFCs/blob/main/text/0005-coretime-interface.md).

**Improvements to XCM:** 

- Tools for uniquely referencing messages, [PR 7234](https://github.com/paritytech/polkadot/pull/7234)
- Bound number of assets which can be withdrawn to pay for execution, [PR 7641](https://github.com/paritytech/polkadot/pull/7641).

**Improvements to FRAME:**

- FRAME: Revamp Preimage pallet to use Consideration, [PR 1363](https://github.com/paritytech/polkadot-sdk/pull/1363)
- FRAME: Create `TransactionExtension` as a replacement for `SignedExtension`,  [PR 2280](https://github.com/paritytech/polkadot-sdk/pull/2280).

**Roadmap/Vision:** 

- Deviser of the Open Governance Model on Kusama and Polkadot Networks: [https://medium.com/polkadot-network/gov2-polkadots-next-generation-of-decentralised-governance-4d9ef657d11b](https://medium.com/polkadot-network/gov2-polkadots-next-generation-of-decentralised-governance-4d9ef657d11b)
- Founder and ideator of the [Polkadot Technical Fellowship](https://wiki.polkadot.network/docs/learn-polkadot-technical-fellowship) and author of the [Fellowship Manifesto](https://github.com/polkadot-fellows/manifesto/blob/main/manifesto.pdf).
- Specification for JAM Protocol, [Graypaper](https://graypaper.com/) and [ongoing refinements](https://github.com/gavofyork/graypaper).

**In-depth conversations on the philosophy behind Polkadot:** 

- Within the ecosystem: Polkadot Decoded 2023, sub0 Asia 2024 ([Keynote: Gavin Wood sees Polkadot as a global Supercomputer](https://www.youtube.com/watch?v=GIB1WeVuJD0), [Keynote: JAM A-Z](https://www.youtube.com/watch?v=tdvqkKdFTlw)). 2) with the general public: Space Monkeys, [Gavin Wood - Is Polkadot OpenGov’s Democratic? Games & Consensus](https://www.youtube.com/watch?v=RvbsSq1a_8g), [Behind the Code: The Graypaper interview](https://www.youtube.com/watch?v=O3kRAVBTkfs). 

**Presentations on the Polkadot network and protocol:** 

- With peers from other ecosystems and/or industries: [Decentralized Lugano](https://www.youtube.com/watch?v=Yw3mQNJ5UJQ),[ sub0 Asia 2024](https://www.youtube.com/watch?v=_gpFm0IZ34M), [Token2049 Dubai 2024](https://www.youtube.com/watch?v=xTMiE0UcZUo).
- With the wider academic community and/or industry: [Protocol Berg](https://www.youtube.com/watch?v=j7b8Upipmeg), [The Journey Man](https://www.youtube.com/watch?v=9SAxnF2sys8). 

**Comment(s):**

- Gav was originally meant to be seeded into the Fellowship at Rank 7. However, this could not happen as the manifesto specifies that induction at Rank 7 can only be done via the community vote: more specifically on Fellowship Admin track. For any members to be promoted to rank VII a vote from the community needs to happen. 
- Gav's contributions to the ecosystem are invaluable and his work has shown a clear vision with regards to where Polkadot should be in the future, what the challenges and the opportunities are in the industry and how a truly unstoppable, scalable and interoperable network should look like.


Make sure to review the above and cast your vote!