Hello, Dotsama community! This is a social contract between PolkaWorld and the Polkadot Treasury. This proposal is aimed to cover the community operation costs from **June 2022 to August 2022**.

PolkaWorld is the Polkadot community in China and has gathered more than 50,000 followers, we have collaborated with the Polkadot ecosystem and Web3 Foundation to build a strong community since 2019. And received a community grant from W3F, and then make a social contract with Polkadot Treasury, so far we have got 4 times Polkadot Treasury funds, and you can find all our monthly reports here: 

[April 2022](https://docs.google.com/document/d/15RzUEMrxTTmIbelmq6vMxKyQHPHaeT76nbSLRQGeX-o/edit#heading=h.dkwc058ylu6g)

[March 2022](https://docs.google.com/document/d/15eizS-ZpTHYlPJm9djge9kH4_QZ3I38it7mkaT4e4aQ/edit)

[February 2022](https://docs.google.com/document/d/18KD3kWMOk0JUO_uOS4OmCz6njaiT9ThY8yv-0JIDElo/edit#heading=h.dkwc058ylu6g)

[January 2022](https://docs.google.com/document/d/1D_u-1LWN_fjSez-zD7DjPtWvNl4342qjFAhZnKo6pW4/edit#heading=h.dkwc058ylu6g)

[December 2021](https://docs.google.com/document/d/17lbpcpzSvz3Kc8WCOQoOX0QlB6R7f9jYk_rXPxenFhM/edit#heading=h.dkwc058ylu6g)

[November 2021](https://docs.google.com/document/d/1XVD8z9FhZUuTxLKwiXt9mWdWg_2oQnMxsgSQ84TbHe0/edit)

[October 2021](https://docs.google.com/document/d/1jRmXQOnKuG-ulXSA-JMjJ-Bdzi5ZZDfBKcNqxLh4Obk/edit#heading=h.dkwc058ylu6g)

[September 2021](https://docs.google.com/document/d/1NmTMLoPfZ3LgRnnunN-01E7NcHC1VzsDxfk-cjccXpg/edit#heading=h.dkwc058ylu6g)

[August 2021](https://docs.google.com/document/d/11Tl9WeB7tW-VTGcTVl5bO4DsQz1rJw5rbZIbAqX_BAc/edit#heading=h.dkwc058ylu6g)

[July 2021](https://docs.google.com/document/d/1rfFq1Qqsr-E1oCjIlClBgq5nqBpnawp2C21hujDSFK0/edit#heading=h.dkwc058ylu6g)

[June 2021](https://docs.google.com/document/d/1XZItg6tBjvSomlybY0jEhBwmDOCzYfsxiNSRYXQYjCE/edit)

And this post is our fifth proposal to apply for the fund support from Polkadot Treasury to continue to run the Chinese community. 

You can find the [milestones and budget here](https://docs.google.com/document/d/1caGbLfa-BUTukVQGHtZtOZKXJ8YkkVAcSdvzjD2b0Oo/edit?usp=sharing) for the next 3 months!

We'd love to hear your feedback or any advice/suggestions here. Please feel free to comment! 

Thanks




proposalId

PolkaWorld Ops and Maintenance proposal:  2022/6 - 2022/8

Web3 Foundation, together with the parachain teams of PureStake (Moonbeam), Enjin (Efinity), BOTLabs GmbH (KILT), Trace Labs (OriginTrail), Robonomics, and Bit.country to participate in one of the most influential global events; the Annual Meeting of the World Economic Forum (WEF) 2022. In order to achieve real change for tomorrow, we need to educate the leaders of today, many of whom attend the WEF: this presents a unique opportunity to build brand awareness and interest for Polkadot, build connections with enterprise audiences, business, tech, and mainstream media groups so that they better understand blockchain technology, take part in the Web3 roadmap and see Polkadot as the best technology platform for building blockchain projects.
The goals of this proposal are:

- to build Polkadot awareness among policymakers, business executives and CEOs, top-tier journalists and technologists, as these people are usually not part of our audience

- to create interest and establish strong relationships with them

- to present Polkadot products/networks/platforms/solutions

- to show the business audience how they could benefit from Polkadot products/networks/platforms/solutions and how Polkadot is already applicable in real-life cases, beyond DeFi

- to make the media audience understand blockchain technology and Polkadot and how blockchain can impact the way we live and do business

- to educate the leaders of today in order to deliver real change for tomorrow.

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

Furthermore, discover Polkadot and Join the Web3 Movement at Davos on [THIS LINK](https://wef22.polkadot.network/).

**Treasury Payment Conditions:**

- Rate of CHF/USD calculation based on [Swiss National Bank foreign exchange rate](https://www.snb.ch/en/iabout/stat/statrep/id/current_interest_exchange_rates#t3). 
- Rate of USD/DOT calculation based on [EMA30 by Subscan on 19.05.2022](https://polkadot.subscan.io/tools/charts?type=price).


proposalHash

 Proposal: Polkadot at Davos during the World Economic Forum’s Annual Meeting 2022

**Proponent:** Tribe/AngelHack 13Ghf2T883ZobjngC1BAgR1BWvK2P7qP37gGxHDVFf3fjbmw

**Date:** May 30, 2022 - July 11, 2022

**Requested Allocation:** $297,000 USD

*DOT amount calculated via EMA on 17 May 2022 at GMT+0 0721hrs - 1 DOT ~ 14.34 USD.
$297,000 USD ~ 20,711.2971 DOT

**Short description: **
Continuing the success of Polkadot Hackathon: APAC Edition (in collaboration with Web3 Foundation and Parity Technologies) that took place in Quarter 4 2021, AngelHack aims to continue with the organisation and execution of the Polkadot Global Series with the focus on the North America region next.

Bringing the North America edition to new heights, the hackathon will focus even more on the following four categories - creating understanding of technology, bridging gaps in the Web3 space, incentivising with larger prize pool and tightening operations. 

This is to ensure a seamless and positive experience for the participants, while aiming to achieve the following goals

- Attract more developers to the Polkadot ecosystem

- Encourage community participation

- Promote building and participation across parachains

- Provide learning opportunities for builders and developers

- Increase the amount of Substrate developers

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


Proposal: Polkadot Hackathon: North America Prize Pool

I am a professor in engineering at the University of Texas of Austin. I am proposing an effort that enables infrastructure for the benefit of the community. This infrastructure will be managed by University/College based Blockchain clubs from across the world, beginning with clubs in the USA and India.

Please find the proposal here: https://docs.google.com/document/d/1vG0_mdUj9R-K6HvcavhTvoEw-IPR1XRFy6XWGjvSmT4/edit?usp=sharing

I would greatly appreciate your feedback on this proposal.

Enabling Common-Good Infrastructure at University/College Blockchain Clubs Across the World

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

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.20). On the runtime side, you can check the changes in the link above. Other improvements on the client side for this release include a PR [aiming to reduce bandwidth](https://github.com/paritytech/polkadot/pull/5164) to improve parachain block times, in response to [the issues described on this post](https://kusama.polkassembly.io/post/1424)  

- Call hash for Polkadot upgrade: `0xf94667fb9411092c1c0b2f157021ff871d92c60becfe8cd467a16e6d6ccf4a92`

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!

Polkadot Runtime Upgrade to v9200

Following the successful delivery of the book, I would like to request for the final payment.

**Amount Requested: $10,240 (731 DOT)**

**Subscan EMA 30: $14/DOT**

## The book can be found [here](https://linktr.ee/polkadotbook).

![](https://i.imgur.com/xb3HVDf.jpg)

Thus far, here are the results of book adoption from only a few tweets by the community, most notable of which is [this](https://twitter.com/nachortti/status/1521387662891966465?s=20&t=G0TuAvt1gNf0YCAvIY9VcA).

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

The previous proposal can be found [here](https://polkadot.polkassembly.io/motion/123).

Polkadot Book for Beginners (final payment)

This proposal requests reimbursement for the social experiment on the validator recommendation algorithm. All the infos can be found [here](https://polkadot.polkassembly.io/post/1036)

Funding for the Social Experiment to Test the Validator Recommendation Algorithm

So far, five parachains have requested an HRMP channel with Statemint. This motion accepts them all and opens return channels.

## Opening Notes

### Handy Info

- Treasury Address: `13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB`
- Treasury `AccountId`: `0x6d6f646c70792f74727372790000000000000000000000000000000000000000`
- Statemint Address: `13YMK2edbuhwMBxeUWm9c643A2wyYHwSVh1bCM7tShtg7Dtk`
- Statemint `AccountId`: `0x70617261e8030000000000000000000000000000000000000000000000000000`

### Parachains that want channels

- 2011
- 2000
- 2004
- 2006
- 2012

### Channel Config

- `maxCapacity: 1,000`
- `maxTotalSize: 102,400`

### HRMP Config

- `hrmpSenderDeposit: 100,000,000,000`
- `hrmpRecipientDeposit: 100,000,000,000`

## Call Construction

These are constructed **backwards.** That is, the call to use as the proposal is at the **end.**

### Relay Chain Call to Execute

First, we need the call that Statemint will execute on the Relay Chain. This accepts all channel requests and returns channel requests to the initiators.

![](https://i.imgur.com/azd1Ygm.png)
![](https://i.imgur.com/zWItDfE.png)

Encoded Call Data:

```
0x1a02283c01db0700003c01d00700003c01d40700003c01d60700003c01dc0700003c00db070000e8030000009001003c00d0070000e8030000009001003c00d4070000e8030000009001003c00d6070000e8030000009001003c00dc070000e803000000900100
```

### Message from Statemint

The above message needs to come _from Statemint._ So we put it into an XCM (the "Transact" instruction) along with purchasing some execution capacity and returning any leftover fees to the Treasury.

![](https://i.imgur.com/i3SHuZV.png)
![](https://i.imgur.com/eXXtCrw.png)

Encoded Call Data:

```
0x1f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01db0700003c01d00700003c01d40700003c01d60700003c01dc0700003c00db070000e8030000009001003c00d0070000e8030000009001003c00d4070000e8030000009001003c00d6070000e8030000009001003c00dc070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

### Proposal on the Relay Chain

But, governance is on the Relay Chain, not Statemint. So take some DOT from the Treasury (100 DOT for 10 channels at 10 DOT each plus 2 DOT for fees) and send a message to Statemint telling it to send a message back. This is the proposal to vote on.

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

Encoded Call Data:

```
0x1a02080502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d8bc7ced630001000100a10f0204060202286beeed021f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01db0700003c01d00700003c01d40700003c01d60700003c01dc0700003c00db070000e8030000009001003c00d0070000e8030000009001003c00d4070000e8030000009001003c00d6070000e8030000009001003c00dc070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

Call Hash:

```
0x6306b068f6a71eb1db5abd9609a0ffbbe7c441c9144ecf8a49e7c2bc19f7f6e9
```

## Appendix: Relevant Storage Items

**`configuration.activeConfig: PolkadotRuntimeParachainsConfigurationHostConfiguration`**

```json=
{
  maxCodeSize: 10,485,760
  maxHeadDataSize: 20,480
  maxUpwardQueueCount: 10
  maxUpwardQueueSize: 51,200
  maxUpwardMessageSize: 51,200
  maxUpwardMessageNumPerCandidate: 10
  hrmpMaxMessageNumPerCandidate: 10
  validationUpgradeCooldown: 14,400
  validationUpgradeDelay: 600
  maxPovSize: 5,242,880
  maxDownwardMessageSize: 51,200
  umpServiceTotalWeight: 100,000,000,000
  hrmpMaxParachainOutboundChannels: 10
  hrmpMaxParathreadOutboundChannels: 0
  hrmpSenderDeposit: 100,000,000,000
  hrmpRecipientDeposit: 100,000,000,000
  hrmpChannelMaxCapacity: 1,000
  hrmpChannelMaxTotalSize: 102,400
  hrmpMaxParachainInboundChannels: 10
  hrmpMaxParathreadInboundChannels: 0
  hrmpChannelMaxMessageSize: 102,400
  codeRetentionPeriod: 14,400
  parathreadCores: 0
  parathreadRetries: 0
  groupRotationFrequency: 10
  chainAvailabilityPeriod: 10
  threadAvailabilityPeriod: 10
  schedulingLookahead: 1
  maxValidatorsPerCore: 5
  maxValidators: 200
  disputePeriod: 6
  disputePostConclusionAcceptancePeriod: 600
  disputeMaxSpamSlots: 2
  disputeConclusionByTimeOutPeriod: 600
  noShowSlots: 2
  nDelayTranches: 89
  zerothDelayTrancheWidth: 0
  neededApprovals: 30
  relayVrfModuloSamples: 40
  umpMaxIndividualWeight: 20,000,000,000
  pvfCheckingEnabled: false
  pvfVotingTtl: 2
  minimumValidationUpgradeDelay: 20
}
```

**`hrmp.hrmpOpenChannelRequests: Option<PolkadotRuntimeParachainsHrmpHrmpOpenChannelRequest>`**

```json
[
  [
    [
      {
        sender: 2,011
        recipient: 1,000
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,000
        recipient: 2,035
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,000
        recipient: 2,034
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,000
        recipient: 2,032
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,012
        recipient: 2,000
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,000
        recipient: 1,000
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,004
        recipient: 1,000
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,006
        recipient: 1,000
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
  [
    [
      {
        sender: 2,012
        recipient: 1,000
      }
    ]
    {
      confirmed: false
      age: 0
      senderDeposit: 100,000,000,000
      maxMessageSize: 102,400
      maxCapacity: 1,000
      maxTotalSize: 102,400
    }
  ]
]
```


First Statemint HRMP Channels

[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!

calls

Polkadot India: Follow up treasury proposals

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

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

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

Untitled - treasury proposal #109


`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

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

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)

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

Untitled - treasury proposal #98

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

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!