- Polkadot India is a community of developers in India focused on Substrate, a tool for building blockchains.
- They want to educate more people about Polkadot and Substrate.
- They proposed to hold 3 DotFriday Webinars and 6 Substrate Bootcamps.
- They have received funding before for similar projects that worked well.
- They are asking for a total of 6026.9 DOT in two treasury proposals.
- One proposal asks for 328 DOT and the other for 5698.9 DOT.
- This proposal combines two requests to make it easier for the council to review.
- People are encouraged to vote on the proposal.

calls

[Polkadot India](https://www.polkadotindia.org/), a pan India community of Substrate developers, submitted a proposal for vote to further educate the Indian blockchain community about Polkadot and Substrate. The team is requesting funding for the next set of 3 DotFriday Webinars and 6 Substrate Bootcamps - context, milestones and budget can be found on the proposal below. They have received funding for this before with great results (the report on the latest status report can be found [HERE](https://polkadot.polkassembly.io/motion/140#18bf1a6d-dcf4-467d-aca5-ef0593ea36ea)). 

---

Please note that this council motion is a `batchAll` motion - the proposal includes to treasury submissions: 

1. On-chain [treasury proposal #111](https://polkadot.polkassembly.io/treasury/111) - Requested amount: 328 DOT
2. On-chain [treasury proposal #113](https://polkadot.polkassembly.io/treasury/113) - Requested amount: 5698.9 DOT

Total grant requested as in the proposal and as a sum of above: 6026.9 DOT - the team made a mistake on the first submission and this is the reason why two proposals are now up for vote. To ease the work of Council, I have combined them in one `batchAll` call. 

You can find the contextual intormation of the proposal, with budget, success metrics and other requirements on the links above. 

Please vote at your convenience!

Polkadot India: Follow up treasury proposals

- A person asked for 7,404 DOT on May 6, 2022, to help pay for important services on Polkadot, Statemint, and Westend.
- For the past three months, they have provided a free public API, making it easier for people to access high-performance nodes.
- This service helps grow the community by making it easier for projects to use the network and test how it works.
- In January, they had over 340 million responses in one day, showing strong demand for their services.
- They achieved an amazing uptime of 99.99%, meaning their service was very reliable.
- Between January and March, they served more than 17 billion responses and processed over 110 TB of data.
- They are working on solutions to improve traffic handling and serve even more users in the future.

proposalId

**Proponent:** 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf

**Date:** 6th May 2022

**Requested DOT:** 7,404 DOT

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

**Raw Data:** https://docs.google.com/spreadsheets/d/1XhhzxTO8pC9tQMG12Uf8NnHZah6O_TIhMaerzsEBAVY/edit?usp=sharing

## Original Motivation

Over the last 3 months (January, February, March 2022) we've provided a scalable free public API service so that everyone can access public pools of managed Polkadot, Statemint, and Westend 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

This last quarter has been huge for Polkadot and OnFinality, the demand for our services continues to be another  unprecedented period. January had a larger activity than the rest of the quarter which also had our highest daily Polkadot response count (for Q1)  of over 340 million responses in a single day. [Raw data is here.](https://docs.google.com/spreadsheets/d/1XhhzxTO8pC9tQMG12Uf8NnHZah6O_TIhMaerzsEBAVY/edit?usp=sharing)

This quarter was all about service stabilisation as part of the promise we made to this ecosystem to provide enterprise grade services to the community. Our services all exceeded our 99.9% target, with 99.99% uptime for Polkadot over the last 90 days. This is an important measure as we surpassed our largest ever day, with over a billion API responses processed by our service in a single 24 hour period in late January.

You’ll note that there was a significant increase in the amount of data egress over the previous quarter (55% growth to 110TB). We’ve been constantly scaling our nodes to meet this rising level of demand while maintaining our target 99.9% uptime (actual was 99.99%). We are currently working on new load balancing solutions to better route this traffic to different node types and expect that we will soon be able to handle more traffic with less resources.

Between 2022-01-01 and 2022-03-31 our Kusama API service has:

- Served a total of 17,841,881,373 (17 billion) responses
- Accumulated over 110 TB of data egress (up 44% on Q4, 2021)
- The highest daily total was 340,585,751 responses in a single 24 hour period
- Our rolling 7 day average at the end of this period was over 201 million responses each day.
- Westend had over 465  million API responses in the period
- Statemint had over 302 million API responses in the period
- All time totals for Polkadot is 1,919,138,536,720 (1.9 Trillion) since November, 2020
- At the end of this period the 90 day uptime for Polkadot, Statemint, and Westend was 99.99%, 99.98%, and 100%

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

OnFinality High Performance Public Infrastructure (Q1 2022)

- A proposal suggests lowering the deposit for HRMP channels on Polkadot.
- The current deposit is 20,000 DOT, and it may be changed to 1,000 DOT.
- This proposal was meant to be part of another motion but was forgotten.
- The change should happen around the same time as an upcoming upgrade.
- A one-way channel costs 1,000 DOT, while a two-way channel costs 2,000 DOT.
- There might be delays in applying changes, so parachains should wait before opening new channels.
- This will help them save money with the new lower deposit.

proposalHash

This is a proposal to change the HRMP channel deposits on Polkadot from about 20,000 DOT to 1,000 DOT. I meant to include this in [motion 191](https://polkadot.polkassembly.io/motion/191) but forgot. It should be enacted at a similar time to the enactment of the v9190 or later runtime upgrade. Two notes:

1. The deposit is per one-way channel, so a bi-directional HRMP channel will require 2,000 DOT per parachain.
2. Configuration changes can take a few sessions to take effect, depending on other pending changes in the parachains protocol. Therefore, parachains should wait until the new configuration takes effect before opening channels if they want to take advantage of the lower deposit.

![preimage](https://i.imgur.com/P12Rv1H.png)

Update HRMP Channel Deposits on Polkadot

In light of discussion in Polkadot Direction, I've added a competing motion to the [1,000 DOT proposal](https://polkadot.polkassembly.io/motion/192) with a 10 DOT proposal.

![preimage](https://i.imgur.com/EVedUmA.png)

Lower HRMP Channel Deposits to 10 DOT

- OneBlock wants to get money to hold the 2022 Summer Polkadot Hackathon in China.
- They have organized two successful hackathons before in March and June 2021.
- The hackathons help teach and promote a tool called Substrate for developers.
- OneBlock is partnering with Parity Asia to have two more hackathons in June and December 2022.
- The previous hackathons helped students learn and build projects using Substrate.
- They received positive feedback from developers about the events.
- This proposal is to ask for money to support the upcoming hackathons.

This proposal aims provide funding for the 2022 Summer Polkadot Hackathon by Oneblock in China - for operations and winners prizes.

OneBlock, in collaboration with Parity Asia, successfully organized, operated and promoted the two Polkadot Hackathons in [March 2021](https://polkadot.polkassembly.io/treasury/30) and [June 2021](https://polkadot.polkassembly.io/treasury/62). OneBlock propose to continue the Polkadot Hackathon program in the year of 2022, an essential part of the Substrate promotion and adoption initiatives in China, to promote Substrate as an open-source framework for developers and convert the Substrate learners from OneBlock’s ongoing Substrate courses to Substrate builders. 

OneBlock, aligning with Parity Asia’s Substrate initiatives, plans to run two Polkadot hackathons in June 2022 (potentially along with Polkadot Decoded on June 29-June30 2022) and December 2022 (exact dates TBD). 

The polkadot hackathon in 2021 was a success and it indeed helped to promote Substrate as an open-source framework for developers and convert the Substrate students from our ongoing Substrate courses to actually use Substrate to build projects. Receiving warm feedback from the developers, OneBlock decided to have 2022 polkadot hackathon and hereby submit this proposal for the necessary financial support on this event.

here and you can get all details [here](https://docs.google.com/document/d/1aGzWrQVfuWdAJND80bTxKi-u4htjjypGEtnDAWcJvBc/edit?usp=sharing).

Please feel free to comments!



OneBlock  The 2022 Polkadot Hackathons proposal 

- This proposal is about upgrading Polkadot and Statemint.
- The Relay Chain will have a new version called 0.9.19, which includes helpful updates like child bounties and crowdloan migration.
- Users are encouraged to vote on the proposal after it is approved by the Council.
- Statemint will launch its version 900, which allows moving DOT (Polkadot's currency) easily between the Relay Chain and Statemint.
- With Statemint v900, users can also open channels and manage NFTs without any problems.

This proposal is for a batch that will upgrade both the Relay Chain and Statemint.

## Relay Chain

This proposal aims to upgrade Polkadot runtime to version [0.9.19](https://github.com/paritytech/polkadot/releases/tag/v0.9.19): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.19). On the runtime side, this release includes, among others, child bounties, and a PR enabling migration of slot depositors in crowdloan migration for parachains to be able to swap slots, among other things. 

Feel free to use srtool yourself to check the proposal hash. If passed by the Council, this proposal should be voted by the community and enacted after. Make sure to vote at your convenience!

## Statemint

Statemint v900 ([release notes](https://github.com/paritytech/cumulus/releases/tag/parachains-v9.0.0)) marks the true launch of Statemint and its functionality. With audits having been complete for several months, the only thing Statemint needed was a way to get DOT from the Polkadot Relay onto Statemint. With the enabling of disputes and XCM on the Relay Chain as of v9190, this is now possible. The v900 release allows users of Statemint to teleport DOT from the Relay Chain, teleport it back, open HRMP channels, and perform all asset/NFT operations without restrictions.

This Statemint release also includes some minor Uniques pallet improvements in preparation for XCM V3, which will allow users and applications to use NFTs over XCM.

## Call

![preimage](https://i.imgur.com/UdvUEmX.png)

![statemint auth](https://i.imgur.com/Wcmmg8m.png)

Polkadot Relay Chain v9190 and Statemint v900 Upgrades

This is a treasury proposal whose proposer address (12Vv2LsLCvPKiXdoVGa3QSs2FMF8zx2c8CPTWwLAwfYSFVS1) 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.

Untitled Post

- Multisig is a tool used in Substrate networks for managing funds and permissions.
- The Subscan multi-sig app helps users create and manage multi-signature accounts easily.
- Since 2021, they have fixed bugs and added new features while improving the user experience.
- New features are being developed in three milestones, with the first two already completed.
- Users can import and export multi-signature accounts, making it easier to manage them.
- The app supports different networks and allows custom configuration for new chains.
- Future plans include more features based on community requests and educational materials.
- They are seeking funds to support the development and maintenance of the tool.


`Multisig` is an important module in the Substrate ecological network, which is of great significance for the fund management and permissions. It is widely integrated into the runtime by the networks that developed based on Substrate, and is gradually accepted and used by more users. Subscan multi-sig app is designed to help users create and manage multi-signature accounts and extrinsics. We keep working to provide users with a more convenient multi-signature tool, and will aim for this goal in the future.

Since [the grant delivery](https://github.com/w3f/Grant-Milestone-Delivery/blob/master/deliveries/multisignature_management_tool_milestone_2.md) in Aug 2021, we have also fixed some disturbing bugs, and have been adding many new exciting features and enhancing UI/ UX for the multi-sig tool. The goal of this proposal is to seek funds for the new features developed for **Subscan multi-sig app** ([Github](https://github.com/itering/subscan-multisig-react)). 

**These new features are divided into 3 Milestones:**

- **We have already completed Milestone 1 and 2**, and released (open sourced) it for anyone to use. Welcome to use and experience the [Subscan multisig tool](https://multisig.subscan.io/). 

- We sincerely welcome suggestions and feedbacks from the community to help us improve UX. **Over the next 3 months, we will complete Milestone 3 and add more community-requested features**.

**More details can be found on Github:**

- [Milestone 1: August-December 2021](https://github.com/itering/subscan-multisig-react/milestone/1)
- [Milestone 2: January-March 2022](https://github.com/itering/subscan-multisig-react/milestone/2)
- [Milestone 3: April-June 2022](https://github.com/itering/subscan-multisig-react/milestone/3)

It can be seen that the number of commits is much more than Issues. Many small features are not recorded here, and the actual workload will be more.

In summary, our work focuses on two points:

**- Make it more convenient for users to use multi-signature related functions.
- Improve compatibility and facilitate more network integration.**


**Here are some details of the main features:**

- Custom endpoints for new network
The default support networks include Polkadot, Kusama, Darwinia, Crab and Pangolin. Users can now add custom substrate-based chain by configuring name, endpoint and explorer(optional).
With this function, we can now serve all networks with standard multisig modules, without the trouble to deploy another fork instance. Thus, it becomes a convenient facility in the Polkadot ecosystem, and users without coding experience can configure networks with ease.
![](https://media.githubusercontent.com/media/subscan-explorer/treasury-proposals/master/multisig-treasury-proposal-2022-Aug//custom-endpoint.png)
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/78)

- Historical multi-sig extrinsic indexing
Historical multi-sig extrinsics (including confirmed/cancelled ) are stored and indexed using SubQuery.  Accounts(member account + threshold) with extrinsic history will be stored as well. This is a prerequisite for importing multi-sig account from url.
![](https://media.githubusercontent.com/media/subscan-explorer/treasury-proposals/master/multisig-treasury-proposal-2022-Aug/history-extrinsics.png)
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/88)

- Import a multi-sig account (which has multi-sig extrinsic history) from url. (e.g. [https://multisig.subscan.io/account/1x8aa2N2Ar9SQweJv9vsuZn3WYDHu7gMQu1RePjZuBe33Hv#r%3Dwss%3A%2F%2Frpc.polkadot.io](https://multisig.subscan.io/account/1x8aa2N2Ar9SQweJv9vsuZn3WYDHu7gMQu1RePjZuBe33Hv#r%3Dwss%3A%2F%2Frpc.polkadot.io)）
We know that a multi-signature account can be assembled and saved locally for the sent multi-signature extrinsic, according to the threshold and member accounts. Thus, when a user shares a url containing an endpoint and a multi-signature address, the corresponding threshold and member accounts are queried and saved locally for information viewing and further operations.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/137)

- Import & export a multi-sig account through json file
Creating a multi-sig account by manually input dozens of member accounts can be quite annoying. This feature can save us the trouble of doing so.
![](https://media.githubusercontent.com/media/subscan-explorer/treasury-proposals/master/multisig-treasury-proposal-2022-Aug/export.png)
![](https://media.githubusercontent.com/media/subscan-explorer/treasury-proposals/master/multisig-treasury-proposal-2022-Aug/import.png)
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/121)

- Optimize the acquisition method of call data to adapt to more usage scenarios
When a member initiate an extrinsic from other tools such as [polkadot.js/apps](https://polkadot.js.org/apps/#/explorer), the call data may not store on chain, and user can manually input the call data which will be verified correspondingly.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/61)

- Compatible with metadata v14 upgrade
Some related data structure have changed, such as call data stored on chain. We’ve made relevant adjustment to make it compatible with metadata v14 upgrade.

**UI/UX improvement:**

- Refine the general UI layout.
- Show estimated reserve amount when submitting an extrinsic.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/84)

- Optimize call data display in extrinsic list on account detail page.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/119)

- Distinguish between cancelled extrinsic and confirmed extrinsic.
- Add connection timeout message.
- Optimize wallet list.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/148)

- Show multi-sig account balance.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/94)

- Improve performance and load speed.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/149)

Future plans:

- Optimize network configuration architecture, support external chain submit RPC endpoint and subquery GraphQL endpoint configuration by PR.

    We are committed to building multi-sig tools as an open, highly compatible infrastructure like the polkadot.js app. In order to achieve this goal, we still need to complete these tasks: [Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/157)

    - Open source SubQuery schema/template so that external chain can deploy and host the node by themselves.
    - Submit PR to include the RPC endpoint and subquery GraphQL endpoint into the menu.
    - Automatically check the format and usability of PR (subsequent manual review will be carried out).
    - Update README to provide instructions.


- Batch import/export multi-sig accounts
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/138)
- Deploy the SubQuery service for networks that have frequent  multi-sig extrinsics.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/151)
- Simplify transfer operations.
Currently it requires user to select module and call to make transfer extrinsic. To make it easier, we plan to add a separate entrance for transfer.
![](https://media.githubusercontent.com/media/subscan-explorer/treasury-proposals/master/multisig-treasury-proposal-2022-Aug/transfer.png)
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/136)

- Add “favorite” and “share” multi-sig account features.
[Issue & PR related](https://github.com/itering/subscan-multisig-react/issues/143)
- Add more community-requested features.
- Add user education docs, videos, etc.


---

**Funding**

development and maintenance cost:

- [Milestone 1: August-December 2021](https://github.com/itering/subscan-multisig-react/milestone/1): $32,100
- [Milestone 2: January-March 2022](https://github.com/itering/subscan-multisig-react/milestone/2): $35,800
- [Milestone 3: April-June 2022](https://github.com/itering/subscan-multisig-react/milestone/3): $34,400

**Total proposed amount: $102,300**

---

**Funding usage:**

The above-mentioned funds are used for the labor cost of subscan multi-signature tool milestone1-3 (9 months in total) development. Here is the detail:

- Front-end development engineer: 1 full-time, 1 part-time
- Product Manager: 1 part-time
- Test Engineer: 1 part-time
- UI & UX Designer: 1 part-time

The average monthly labor cost is **$11k**. Due to the different working hours of part-time staff each month, the funds applied for each milestone are also slightly different.

---

2022-04-21 06:04:54 (+UTC), Block #9967626

DOT EMA30 Price ( USD ):  `19.389`

Number of DOT: `102,300 USD -> 5,276.305 DOT`

[https://polkadot.subscan.io/tools/price_converter?value=102300&type=time&from=USD&to=DOT&time=1650522208](https://polkadot.subscan.io/tools/price_converter?value=102300&type=time&from=USD&to=DOT&time=1650522208)

Please refer to the previous discussion: https://polkadot.polkassembly.io/post/981


User experience optimization and new function development of Subscan Multi-sig Tool

- Phala parachain is currently stuck or "bricked."
- The team wants to fix this by asking for help with a special call to change its code.
- Phala Network became a parachain recently.
- They found a mistake in their setup that prevents upgrades.
- Both sudo and democracy are turned off, making it hard to add new features.
- Without help, the parachain will stay stuck forever.
- More details about the issue and their plans are available in a discussion link.

TL;DR. Phala parachain is bricked. The team is requesting a Motion to fast-track a `Paras.forceSetCurrentCode` call to unbrick the parachain.
_______________
Phala Network (id: 2035) became a parachain recently. However, during the progressive launching process, the team noticed that there's no way to upgrade the runtime due to the misconfiguration in the genesis runtime. Specifically, the genesis runtime has both sudo and democracy disabled. Without the help from the relaychain side, the parachain will be "bricked" forever -- all the functions need to be enabled by runtime upgrades which is infeasible due to the problem.

Proposal hash: `0x7af427aa7665a073ca61b83c04791f185d9170ea2e49a8a7be323650cea8b75f`

More info on the misconfiguration of the runtime, force runtime update on relay chain and team's roadmap can be found in the discussion link: [https://polkadot.polkassembly.io/post/1005](https://polkadot.polkassembly.io/post/1005). Preimage is submitted by the team. 



Unbrick Phala Network Parachain (at team's request)

- This is a proposal for more money to help with RPC services.
- RPC services are important for Polkadot, Statemint, and Westend.
- They want to keep these services running on special computers in Sweden.
- They have had many users, with Polkadot getting over 8 million requests every day.
- Statemint has about 245,000 requests daily and Westend has around 27,000.
- The proposal includes one goal, or milestone, to achieve.

This is a follow-up proposal on what we submitted in the beginning of [January](https://polkadot.polkassembly.io/treasury/81), 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.
### Report

During Q1 2022 our Polkadot RPC service served on average **8,122,333** requests per day.

In mid Q1 2022 we also turned on public RPC services for Statemint and Westend. Since the start, Statemint has served on average **245,000** requests per day, and Westend has served **26,900** requests per day.

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

Polkadot RPC services Dwellir Q2 2022

- RadiumBlock is a service that helps with Web3 and focuses on the Polkadot and Kusama networks.
- They want to submit a proposal to keep their validator snapshot service running for the first quarter of 2022.
- This service provides important information (snapshots) for both Polkadot and Kusama communities.
- They have planned to ask for money from the Polkadot Treasury this time and will ask from Kusama next time.
- RadiumBlock is trying to involve different places and companies for better support.
- They adjusted their request to 100 DOT and have changed their fee estimate to 8% due to price changes.
- They would like feedback on their proposal and thank everyone for considering it.

Hello Polkadot Treasury

[RadiumBlock is an aspiring Web3 infrastructure service provider](https://radiumblock.com/) focused on the Dotsama ecosystem. We would like to submit a treasury proposal for the maintenance of radiumblock.com's [validator snapshot service](https://radiumblock.com/snapshots) for Q1 2022. The snapshot service provides both polkadot and kusama snapshots. The detailed proposal can be found [here](https://radiumblock.com/proposals/polkadot/2022/Polkadot_Snapshots_Q1_2022.pdf).

Although this service benefits both Polkadot and Kusama communities, we believe that the amount is reasonable enough to request it from the Polkadot Treasury. We plan to alternate between Kusama and Polkadot treasury per quarter. 

Very much in the spirit of decentralization, we have explicitly tried to provide both geographical as well as infrastructure provider diversity. Here is a summary table of the snapshot providers and information about their infra and geographical we compiled(to the best of our knowledge).

Snapshots | Infra Provider | Geo Location

RadiumBlock.com | Hetzner | Finland

Polkadots.io. | Google Cloud | US

Polkachu.com | Digital Ocean | EU

Parasnaps.io | ? | ?

Based on instructions we have adjusted the DOT amount to 100 DOT using todays DOT rate (EMA30) from https://polkadot.subscan.io/tools/charts?type=price
Given the increased volatility we have seen the last few days we have slightly adjusted the slippage to 8%(vs 5% listed in our original proposal). 
We request the payment to be made to our DOT wallet(same as the proposer address) 13GtCixw3EZARj52CVbKLrsAzyc7dmmYhDV6quS5yeVCfnh1


We welcome your feedback.

Thank you for your consideration!

RadiumBlock



radiumblock.com's Dotsama validator snapshot service for Q1 2022

please see the [proposal](https://polkadot.polkassembly.io/post/949) for details.

Proposal for Ask! v0.4 (original Ask-lite v0.1, ink! in AssemblyScript)

- Paulo Zago is a member of the Portuguese-speaking Polkadot community.
- He creates videos, podcasts, and articles about cryptocurrency for Polkadot.
- He started his YouTube channel on July 25, 2021, and has made 23 videos.
- His YouTube channel has almost 24,000 views and 528 subscribers.
- Paulo shares tips that have been recognized by the Polkadot and Kusama council.
- He moderates the Portuguese Telegram group for Polkadot and Kusama.
- Paulo plans to make 36 educational pieces in three months to help beginners.
- He translates content into Portuguese to make it easier to understand.

Hello,
my name is Paulo Zago, I am an active member of the Portuguese-speaking Polkadot community. I produce cryptocurrency content and tutorials for the Polkadot ecosystem on my [YouTube](https://www.youtube.com/c/PauloZagoYT) channel, [Podcast](https://open.spotify.com/show/3WUO44czt7om3nbn45hARe) and [Articles](https://app.subsocial.network/5562).

I started creating content on my YouTube channel on the 25th of July 2021 and I have already produced 23 videos about the Polkadot and Kusama ecosystem. 
I currently have a total of 23,990 views and 528 subscribers on my YouTube channel. 

Due to my dedication to contribute to the development of the Polkadot ecosystem, some Tips of my content were requested and endorsed for the Polkadot and Kusama council and I am currently the moderator of the Polkadot and Kusama Portuguese Telegram group.

My proposal is to create 36 educational contents during a period of 03 months with the frequency of 03 contents per week. These contents will be developed for the Polkadot ecosystem in 3 different media formats. Each content will be produced specifically for each graduate.

I try to research and study the content produced around the world by the Polkadot community and translate it into Portuguese with a simple and easy to understand language to help beginner users.



See the full proposal [here](https://docs.google.com/document/d/1CwX86-WTrfOuKRDc33craMR93azh6AzRmjEdFOh1Gog/edit?usp=sharing).

Discussion page Polkassembly [here](https://polkadot.polkassembly.io/post/956). 

[Tweet](https://twitter.com/paulo__zago/status/1506706392148844557?s=20&t=gk8UIo0cZw1lomLn2f3OPw) with community feedback

Feel free to leave a feedback below. 
All opinions are welcome.


Proposal for production of Polkadot Ecosystem content in Portuguese language Q2

This is a treasury proposal whose proposer address (1hBsvxbKZwmAGyTbpfctcq5nTZWGqtDSw6L8sdajnPRJj7z) 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.

- The university has a program to engage students.
- They want to request £60,000 for funding.
- This money is for hackathon prizes and team grants.
- They need £3,950.96 specifically based on recent average calculations.
- The funding will help with the costs of running an accelerator.
- There are reports available for more information on the funding.

As part of our university engagement programme (see [here](https://docs.google.com/presentation/d/1LLFxCpO7y1fyIfcdTpDQGkbuPoGy2mFvlusYb1tTe74/edit#slide=id.gc2bb29227c_0_1294l)), we would like to request our fourth and fifth phases of funding (£60,000) to pay hackathon prizes.

The amount we are therefore requesting is 3950.96 (based on the 30 day moving average of 19.919 according to Subscan) to pay grants to accelerator teams and cover the cost of running the accelerator.

Please find a report the report of tranches 4 and 5 [here](https://polkadot.polkassembly.io/post/934).


Encode Club Polkadot Club - Tranche 4 and 5 funding

The Statemint v800 runtime upgrade is relatively low impact, especially as teleports and asset creation are not enabled yet. However, this sets the stage for v900, in which I plan to propose lifting all restrictions on Statemint. The purpose of upgrading to v800 is to ensure that Statemint is on the same version as Westmint and Statemine such that testing the v900 w/r/t migrations is as similar as possible.

Statemint Upgrade v800

- The proposal is to upgrade Polkadot to version 0.9.18.
- Important changes include logging in two parachains, and adding new types for contracts.
- The upgrade will allow for the use of a special function called set_code.
- A specific call hash is mentioned for the upgrade.
- The Council will vote on the proposal, and then the community can vote as well.
- Everyone should remember to vote when it's their turn!

This proposal aims to upgrade Polkadot’s runtime to version [0.9.18](https://github.com/paritytech/polkadot/releases/tag/v0.9.18): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.18). This release includes, among others, PR 4772 (login two parachains to swap slots), PR 10947 (bringing back maxnominators as a meatada constant), PR 4851 (adding proxy types for Kappa Sigma Mu) and PR 10690 (upgradable contracts using set_code function).

- Call hash for Polkadot upgrade: `0xa9ad07f0ea8e95c15247ba05a2754405acbf4de6cea8fe0cfdb94196c6093670`

Feel free to use srtool yourself to check the proposal hash. If passed by the Council, this proposal should be voted by the community and enacted after. Make sure to vote at your convenience!

Runtime Upgrade v9180 - Polkadot Network

- The Polkadot Ecology Research Institute wants help from the Polkadot Treasury for six months of operating costs.
- They plan to create fun and easy-to-understand Chinese content about Polkadot.
- Their goal is to help Chinese users learn about Polkadot in a friendly way.
- They also want to share updates about important Polkadot projects.
- This work will help more people know about Polkadot and participate in its growth.
- They previously received funding from the Polkadot Treasury and completed their goals.
- They are asking for about $104,760 for the next six months.

The proposal aims to seek support from the Polkadot Treasury for the 2022/3-2022/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 2021, [we have established a Polkadot Treasury for our 2021/9-2022/2 operation cost, and get funding from the Polkadot Treasury](https://docs.google.com/document/d/19is5Ihn_0HEfOwUbsaDQzX7n89oRlWYwpt6eDWeabw0/edit). We have completed all the goals. [Please check our report to learn more.](https://docs.google.com/document/d/1sNjxO6lPnA_fdtThuM3hgU1eM62irpEHOMVG6kgfwtY/edit?usp=sharing)

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

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

- The Composable Finance team had a problem on the Picasso chain in Kusama.
- There was a mistake in the weight calculations for something called "pallet-democracy."
- This mistake could cause the chain to stop working after a certain time.
- A public file for using the software can be found online.
- There is a design related to preimages shared with a picture.
- A preimage hash was also provided, which is a special type of code.
- The original message about this problem can be found in a post online.

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`

(Please note that preimage has been already submitted).

Original post: [https://polkadot.polkassembly.io/post/961](https://polkadot.polkassembly.io/post/961).

Help Composable Finance Unbrick Their Chain

- A new Polkadot brand font is being created using open-source design.
- The font will have three styles: light, regular, and bold, plus a special variable version.
- It will connect the Polkadot community visually and help developers.
- The font will include a wide range of characters from the Latin alphabet and a "pan-African" character set.
- Cyrillic letters will also be added for more international use. 
- The proposal includes tracking the font's value in USD and EUR.
- The total cost will include taxes.

We propose the completion of an open source Polkadot brand typeface based on existing initial creative. The final fonts will be in three weights; light, regular and bold, as well as a cutting-edge variable font. The brand font will visually link the eco-system on a typographic level and offer value you to the development community as a visual asset.

We propose to extend the font's usability by extending the core latin-based alphabet to include a wide-ranging 'pan-african' character set. We also propose adding the cyrillic script to further bolster international use of the font.

[Read full proposal](https://docs.google.com/document/d/1aRcL-xlOnEklvhaBoBnl8u7bL1jLjX_QRKK9_wHanFs/edit?usp=sharing)

- DOT Rate based on [30day avg tool by Subscan](https://polkadot.subscan.io/tools/charts?type=price): 18,70 USD / 17 EUR.

- Total allocation includes TAX.

Opensource Brand Typeface

- This is a proposal to tidy up the bounty proposals.
- It will close three bounties that have been waiting for a long time.
- The bounties being closed are numbers 9, 12, and 14.
- People who made these bounty proposals will lose their bond.
- Everyone is encouraged to vote whenever they can.

This motion is a bit of housekeeping and cleans the bounty proposal queue: closing 3 bounty proposals with no contextual information for more than a few weeks already. This proposal includes the closing of bounty proposals 9, 12 and 14.

Please note that bounty proposers will lose their bond to the closing. Please vote at your convenience!

- [https://polkadot.polkassembly.io/bounty/9](https://polkadot.polkassembly.io/bounty/9)
- [https://polkadot.polkassembly.io/bounty/12](https://polkadot.polkassembly.io/bounty/12)
- [https://polkadot.polkassembly.io/bounty/14](https://polkadot.polkassembly.io/bounty/14)

Rejecting Bounty Proposals with No contextual Information

- There is a proposal for a bounty that can be found online.
- The proposal gives a budget of 100,000 DOT, which is about €1,600,000.
- This budget is for 12 months and helps the foundation with its work in 2022.
- The foundation will use this money for research, engineering, and community support.
- They will also use it for managing their hosted platform.
- The foundation can ask for more money twice a year in the future.
- More details are available in the link mentioned.

bountyId

Details of the bounty proposal can be found [here](https://polkadot.polkassembly.io/post/924).

The allocation of a 12-month budget of 100.000,00 DOT (~€ 1.600.000,00) for the foundation’s 2022 activities by means of the (Child)Bounty Treasury Spending Instrument. The budget allows for periodic reimbursement of the foundation’s research, engineering, community support activities of its open-source repositories and the budget allows for periodic reimbursement of the foundation’s service management activities of its hosted platform. Future Governance requests are limited to bi-annual budget extensions for subsequent budgeting terms.

More info on the link above. 

Bounty Proposal - Polkascan 12-month budget 

This is a CouncilMotion post. It can only be edited by the proposer of the post .

- The Polkadot Ambassador program has grown to 2,247 members in less than a year.
- Ambassadors help teach people about Polkadot and organize community events.
- To celebrate their hard work, they are giving awards called Ambassador's badges.
- The badges will be given as physical items and also as digital NFTs.
- There will be a special event called PolkaOscar on December 28, 2021, where winners will be announced.
- A physical award ceremony will happen at the Polkadot Decoded event in June 2022 in several cities.
- Ambassadors who can’t attend the event will receive their awards by mail.
- The badges can be shaped into characters, allowing people to create their own unique collection.

It’s time to celebrate!

Polkadot Ambassador's program has grown significantly in a little less than a year (we are currently 2247 candidates and ambassadors according to the data provided on October 31, 2021) and our amazing community continues to grow. It is a fact that our Ambassadors have made an enormous contribution to the success of the Multichain future by educating our community about Polkadot technology, organising workshops and meetups, and pushing forward Web3 technologies for mass adoption.

We want to award each ambassador for the relevant work done which has made Polkadot a success. With these Ambassador’s badges, both in a physical form and as a NFT; we, the Ambassador’s community celebrate the success of the Polkadot Community and Network.

Following the online PolkaOscar ceremony that took place online on December 28, 2021, we began minting and distributing ambassador’s NFT badges.Our original plan was to only post 3D badges to all ambassadors; but thanks to the Polkadot Decoded event in June we’ll have the opportunity to meet and hand some awards in person. We believe that taking the chance to host a physical PolkaOscar award ceremony will add spark to our movement.

The Polkadot Decoded event will take place in Berlin, Mexico City, New York, and Shanghai on June 29th & 30th 2022. Therefore, we will only post badges to those ambassadors who won’t be able to make it to the physical event. This way we will increase the chances that everyone will be awarded, and we will add a physical and virtual chapter to the wonderful history of our community.

The printing process must begin as soon as possible in order for the printing company to finalise 3d works, package the figurines and ship them to the event destination or to individuals on time for the event. About Polkadot Kings & Queens Characters: The very idea of ​​assembling and varying characters fits very well with the social story. Games like the Sims, where you collect a hero similar to yourself or Memoji from Apple, all works and plunges us somewhere into our childhood.

Ambassador’s Badges are the characters made from cubes that you can assemble yourself, according to your taste and colour preferences. Your first badge can be the beginning of a regular collection - small and static, or something big and dynamic: games, cartoons, merch, the metaverse. This project is about personalities, anyone can find himself in a chelobrik and can build his own little cheloworld. Kusama Princes & Princesses and Polkadot Kings & Queens are a symbol of the Power of The Community and The Power of an Individual in this ecosystem. We are Decentralised but United by the ideal of building a new creative, decentralised and fairer world.

Link to the proposal discussion [here](https://polkadot.polkassembly.io/post/730)
You can find the proposal (with a breakdown of costs) [here](https://docs.google.com/document/d/1bTjb9CwnLnKbpQaHoASMJ9sTSee6eA22_yr5sADStmw/edit?usp=sharing)

3D Badges for Polkadot Ambassadors for PolkaOscar, June 2022

- The Polkassembly platform wants to make improvements to help users better understand and use it.
- They plan to change the look and feel (UI & UX) of the platform to make it easier and more fun to discuss and manage things.
- New features will include tools for money tracking, events, and learning resources about Polkadot.
- The team is dedicated to adding more features based on what the community needs, and they will work hard every quarter.
- Some new things being developed are better website performance, custom notifications, and rewards for users who help out.
- They have already made changes like creating a homepage and adding community discussions to attract more people.
- In the future, they want to add more educational content and improve the way users can create proposals.
- Overall, they aim to make the Polkassembly platform a favorite place for information on governance in the Polkadot ecosystem.

This submission proposes new features on the Polkassembly platform. The product roadmap outlines the transition and development of Polkassembly platform to improve UX, enhance UI and add some features which will bring a lot of value to the users of the platform.

### Product philosophy + Milestones/Features
Please find our Pitch deck here - [Link](https://docsend.com/view/yzq59fr3zzquvkns)

**Note** - The product roadmap is flexible when it comes to prioritizing feature development and timelines are subject to change based on community requirements for features but consistent efforts will be made to ensure that every quarter there are more tasks done than mentioned in the milestones.

**Product plan**

The product roadmap primarily focuses on 3 things-

- Improve UI & UX of existing platform to ease governance discussions
- Add new features like treasury analytics, parachains info, events calendar, etc..
- Educate the community on Polkadot and substrate ecosystem and simplify the learning process for people moving from web2 -> web3(Tentative pipeline - [Link](https://docs.google.com/spreadsheets/d/1esbMkfIfZSYoLHor-y5v97pLHrDF8GnnoSrYg60INiU/edit?usp=sharing))

**Milestones**

[![](https://i.ibb.co/tm5CyPZ/pitchdeck.png)](https://ibb.co/r7Jynfb)


**Additional features that are in development in this quarter include**
- Create treasury proposal from Polkassembly platform(enhanced UX)
- Other features as requested by Council members, community and partner chains - Flexibility for adding more features beyond our defined roadmap will help Polkassembly become user’s go-to place for Governance and information on Polkadot ecosystem.
- Merge sign-in/sign-up process
- Improve website performance and load speed
- Introduce an option to select network when signing in
- Merge the treasury proposal creation process to provide a simplified UX to complete entire process on Polkassembly platform
- Treasury analytics page - Detailed treasury spend and inflow with latest events
- Personalized Notifications to stay updated on latest activity for a custom list of protocols
- Introduce rewards & NFTs for contributing voters and participants
- Make polkassembly live for multiple chains
- Addition of child bounty support: Feb W3
- Aggregation of data across multiple parachains: March W3
- Increased focus on educational content and ecosystem updates: Feb W3 
- Experience Overhaul & Upgrade for the Product (Polkassembly)
- Launch of updated Product Home: March W1
- Launch of update for all Product pages: April W1
- Enhanced landing page for each protocol. The protocol page will have the following information
- Description of protocol
- All relevant links - discord, twitter, github, reddit, youtube, etc
- An option for protocol owners to add custom links would be created later
- All relevant links - discord, twitter, github, reddit, youtube, etc
- News & Events and activity feed for that protocol
- Custom Calendar view for each protocol
- Enhanced view for various tabs - Treasury, Bounty, Tips, etc. 

Please find the mock design below along with the link to figma design file

![](https://i.ibb.co/h9PYtmg/homepage.png)
![](https://i.ibb.co/sH6w0jQ/calender.png)

Figma Design files for 

- [Home page](https://www.figma.com/proto/42APiTcMqSnnqT2zttgf9M/Polkassembly-Final?node-id=136145%3A256226&scaling=scale-down-width&page-id=136145%3A256110&starting-point-node-id=136145%3A256226&hide-ui=1)
- [Calendar](https://www.figma.com/proto/42APiTcMqSnnqT2zttgf9M/Polkassembly-Final?node-id=136155%3A230768&scaling=scale-down-width&page-id=136145%3A257324&starting-point-node-id=136155%3A230768&hide-ui=1)
- [Link Multisig](https://www.figma.com/file/ko3Sks2oLSnW7ogk7UoMQO/Link-Multisig?node-id=0%3A1)
- [Child bounty](https://www.figma.com/file/u6eNe9N0G1257aEyDpNFfK/Untitled?node-id=0%3A1)

**Features Completed**

**Polkassembly Website & Social**: Dec’21 to Present

- Creation of a homepage for Polkassembly to build towards the vision of educating users about governance in the Polkadot ecosystem
- Creation and development of social channels to increase the audience for governance discussions and build awareness

**Multi-Sig & Proxy**: Jan’22

- Integration of the ability to add multi-sig and proxy on Polkassembly, adapting the platform based on community feedback

**Moonbase Integration**: Jan’22 to Feb’22

- Launch and integration of feedback from the Moonbase team to bring the community to Polkassembly for Governance

**Design & Experience changes**: Jan’22

- Improving experience on login, settings and navigation
- Addition of error messaging

**Dashboard view for independent parachains**: Jan’22 to Present

- Improving the experience for users by allowing them to view all on-chain activities in a dashboard view for each parachain
- Viewing news, upcoming events, and much more as a part of the dashboard

**Calendar Integration**: Feb’22 to Present
- Integration of an on-chain + off-chain calendar for events in the polkadot ecosystem in a parachain agnostic form
- Allowing users to create events for greater visibility along with the option of adding events to their google/social calendar

**Improving integration of Treasury functions**: Jan’22 to Present
- Visibility on treasury proposals along with stats from the treasury
- Creation of treasury proposal from Polkassembly | The PRD and design is for Tips but the same would be used to develop it for Treasury Proposal
- [Design](https://www.figma.com/file/vLHdo4BJMDl0sliebC20MU/Create-treasury%2FTip-proposal?node-id=0%3A1)
- [Short PRD](https://www.notion.so/Create-Treasury-Proposal-20f975684aff48a088db8aff52ce8527)
- Linking discussion post to treasury
- Integration of treasury analytics

**Tip calculation and threshold data**: 
- Improved tips calculations and started showing proposer’s tip, expected tip and list of council members along with a status against each Jan’22


Total Proposal amount: 4690 DOT

Link to Proposal: [https://docs.google.com/document/d/1TRgHh5DJoVxlUUhCaaxV95ACcwCiErJ73ES6uAhji6o/edit?usp=sharing](https://docs.google.com/document/d/1TRgHh5DJoVxlUUhCaaxV95ACcwCiErJ73ES6uAhji6o/edit?usp=sharing)

Council Motions