- This proposal is about a bounty program called bounty #13 for finding bugs in the Open Runtime Module Library (ORML).
- A total of up to 100,000 DOT is available as rewards for reporting bugs.
- To participate, people must study ORML's source code and report vulnerabilities to the Acala Bounty program on Immunefi.
- A curator is proposed to manage the bounty, with a specific anonymous address.
- The curator team includes five experts from Acala, Parity, and Manta.
- Each expert has a unique address that can be verified through different platforms.
- This program helps improve the safety and quality of ORML used in Polkadot and Kusama.

bountyId

curator

# ORML Security Bounty Curator

This proposal aims to propose a curator for the [bounty #13](https://polkadot.polkassembly.io/bounty/13).

To recap, bounty #13 allocates up to 100,000 DOT for covering bug bounty rewards for [Open Runtime Module Library (ORML)](https://github.com/open-web3-stack/open-runtime-module-library). ORML is a community-maintained collection of Substrate runtime modules, widely used across the Polkadot/Kusama parachains.

For people whom want to participate this bounty, please study the source code of [Open Runtime Module Library (ORML)](https://github.com/open-web3-stack/open-runtime-module-library) and report vulnerability to Acala Bounty program on [Immunefi](https://immunefi.com/bounty/acala/).

You can find submission guide for Immunefi platform [here](https://medium.com/immunefi/a-hackers-guide-to-submitting-bugs-on-immunefi-1e6b7ada71a9). Please make sure your report meets the bounty requirement stated on the Acala Bounty program page.

A payout will be made by creating a child bounty with payout amount, with a curator address controlled by Acala team or Immunefi team. The child bounty will be awrared to the bounty submitter and the curator fee will be paid to Immunefi as platform fee.

## Proposed Curator

The proposed curator address is: `13f2dPGgzj33ARCdKCQsCZ19JfCDUfsNqoAphVjASCMbZgBc`

This is an anonymous proxy that is controlled by a 3/5 multisig wallet `1puBSM7WmLTBw3WN7Sdw2Gi5e6cRcWsk7gWbocR7rknYWaZ` with signers of:

**Bryan Chen @ Acala**  
Bryan is the co-founder & CTO of Acala as well as the initiator and core contributor of ORML. He is also one of the top community contributors to Substrate and Polkadot.  
Address: `14DsLzVyTUTDMm2eP3czwPbH53KgqnQRp3CJJZS9GR7yxGDP`  
Address can be verified via onchain identity

**Shaun Wang @ Acala**  
Shaun is one of the core developers at Acala, and core contributor of ORML. He is also an active contributor to Polkadot, Substrate and Cumulus.  
Address: `16PNhcMEvGbTYdCht9vLy6gj8qehRehEpb2EfmXB7xShZUVX`  
Address can be verified via Github: https://github.com/shaunxw

**Shawn Tabrizi @ Parity**  
Shawn is one of the Lead Developers at Parity Technologies working on Substrate, Polkadot, Kusama. He specializes in FRAME, Runtime development, and benchmarking.  
Address: `12hAtDZJGt4of3m2GqZcUCVAjZPALfvPwvtUTFZPQUbdX1Ud`  
Address can be verified via onchain identity

**Wei Tang @ Parity**  
Wei is one of the core developers at Parity Technologies. He maintains Frontier, the Ethereum-compatibility layer for Substrate.  
Address: `14ShUZUYUR35RBZW6uVVt1zXDxmSQddkeDdXf1JkMA6P721N`  
Address can be verified via onchain identity

**Shumo Chu @ Manta**  
Shumo is a co-founder of manta.network, the privacy layer for Web3 using zkSNARK. He was serving as research scientist at Algorand and assistant professor at UCSB before Manta.  
Address: `15ynbcMgPf7HbQErRz66RDLMuBVdcWVuURhR4SLPiqa6B8jx`  
Address can be verified via https://github.com/stechu

Assign curator for ORML Security Bounty

- A proposal suggested by Kian from the Staking team aims to change nomination limits in Polkadot.
- The goal is to increase the maximum number of nomination intentions from 22,500 to 50,000.
- It also suggests lowering the stake needed to submit a nomination intention to 10 DOT.
- This change is possible because of new features released in Polkadot's runtime 9170.
- The proposal should be acted upon before the number of nominators reaches 22,500 to avoid issues.
- There should be no negative impact on current stakers with this proposal.

proposalHash

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

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

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

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

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

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

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

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

Call design:

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

Encoded call data: `0x071700e87648170000000000000000000000000000000000000000000000000000000150c3000001b0040000015a00000000`

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

Link to discussion post: [HERE](https://polkadot.polkassembly.io/post/921). 

Polkadot Proposal: Lowering Nomination Intention Limits

- The project is proposed by Nicholas Hong and focuses on helping developers learn about Polkadot and Substrate.
- The total money needed for the project is $80,000, and they are asking for $50,000 to start.
- The project aims to improve the quality of hackathon submissions by teaching developers before the hackathons.
- They want to help 150 global developers get better at using Polkadot and Substrate.
- The learning will happen through "Learn-and-Earn" campaigns on a platform called StackUp.
- StackUp rewards developers with money for completing small tasks or "quests" that help them learn.
- This approach makes learning fun and encourages developers to complete more tasks.

proposalId

**Proponent:** NicholasHong/Tribe/StackUp `1FJCfJzPnuPTeSZnpwMetY5yZi56t2RRxvHsrAYkzwvfCFC`

**Date:** March 2022

**Overall Project Allocation:** $80,000 USD 

**Requested Allocation Through This Submission:** $50,000 USD *(covers first payment milestone -  phase 0 of this project - please see full proposal for more details - proposal link at the end of this post)*

- DOT amount calculated via EMA on 11 Mar 2022 at GMT+0 1111hrs - 1 DOT ~ 18.135 USD. $50k USD ~ 2757 DOT

**Short description:**

Reviewing Polkadot Hackathon: APAC Edition that took place in Quarter 4 2021, the organising team at AngelHack (a subsidiary of Tribe) identified gaps in the participants’ level of knowledge when attempting to learn Substrate, impacting the quality of the hackathon submissions received. By raising the number of quality of submissions, the Polkadot ecosystem can become even more vibrant.

With the series of 2022 hackathons planned by AngelHack together with Web3 Foundation, the team at Tribe aims to level up the participant’s prior knowledge of the Polkadot Ecosystem and fundamentals of Substrate pre-hackathon, in hopes to result in better submission quality.

Specifically, Tribe proposes to provide Learn-and-Earn campaigns to onboard global developers onto the Polkadot developer ecosystem, growing Polkadot’s active developer base with new developers that are equipped with strong foundational knowledge and hands-on development experience. Targeting 150 global developers to be onboarded through this engagement.

The Learn-and-Earn campaigns will be conducted through StackUp - Tribe's newest business offering - a platform that rewards developers with monetary incentives for completing tasks that level up their skills and knowledge. StackUp breaks the typical learning journey into smaller, bite-sized pieces (that we call quests), offering users real currency rewards for finishing each quest. This format of smaller exercises with incremental rewards, encourages learners to tackle more quests and learn more, as well as encourages them to follow through and finish the quest.

Full Proposal Link: [Link](https://docs.google.com/document/d/1NxH0-hxjttIXOxWgS0yURCpj2u2kJTCdT7gbFISqZSI/edit)

Proposal: Learn-and-Earn Campaigns for Polkadot Hackathon Global Series 2022

- The document is a proposal for transferring money.
- It is meant for the Polkadot Treasury account.
- The owner of the document claims all information is true.
- They say they will create another proposal after 30 days to redistribute the funds.
- An Ethereum signature is included to verify the claim.
- A special coded message (preimage) is part of the proposal.

[Context](https://gw.crustapps.net/ipfs/QmdonRnfQKQUyvmKQrDJ6sHkT3E21ucPnGS4FeUQjkzXhV?filename=Proposal%20for%20a%20force%20transfer.pdf)

Signing message

```
I am the owner of this document: https://gw.crustapps.net/ipfs/QmdonRnfQKQUyvmKQrDJ6sHkT3E21ucPnGS4FeUQjkzXhV?filename=Proposal%20for%20a%20force%20transfer.pdf. I attest that all the information in it is truthful and I'm the beneficiary of this proposal.
```

Signature

```
0x601616878d2aa0b8bd3612a8468c751182477ec36375545b6b589d062db5576660e1950af7bd3b3bf33b388029d12e0c9c825aeeee6088054813e306142bce8d
```

Signer: `13gWjtGEYraF2FucNzgEz6W24wVhvGpkqSWSXYiChbDDM3cW`


Eth signature
```
{
  "address": "0x9A94771E7E73f9D8d6E880cfB12CAb4e9573C45E",
  "msg": "I am the owner of this document: https://gw.crustapps.net/ipfs/QmdonRnfQKQUyvmKQrDJ6sHkT3E21ucPnGS4FeUQjkzXhV?filename=Proposal%20for%20a%20force%20transfer.pdf. I attest that all the information in it is truthful and I'm the beneficiary of this proposal.",
  "sig": "0x636f48d70e6e5af005f79512b297a6f18283ead111c1bd26f6adb0941cd8f91c747ed96de76f2dcf3e06a5f61be426d08102428d24ebc41d6816f63f10fc40811b",
  "version": "2"
}
```

Proposal Preimage: 
```
0x1a03000186e1b030f80cb6608e81ced788003b3bc321d06256c53af96bc8932c4e7f14de0504006d6f646c70792f7472737279000000000000000000000000000000000000000000
```

This is a transfer all to Polkadot Treasury account. Another proposal will be created after 30 days to redistribute this fund.

Unblock fund

This bounty aims to allocate up to 100,000 DOT for covering bug bounty rewards for Open Runtime Module Library (ORML). ORML is a community-maintained collection of Substrate runtime modules, widely used across the Polkadot/Kusama parachains.

Read more [here](https://polkadot.polkassembly.io/bounty/13)


Security Bug Bounty for Open Runtime Module Library (ORML)

This is the proposal for crowdloan extensions discussed [here](https://polkadot.polkassembly.io/post/911). The included crowdloans were based on comments from the thread and confirmed with contacts from each team. Four teams either declined an extension or did not respond to the discussion.

- 2003: Darwinia
- 2008: Crust
- 2011: Equilibrium
- 2013: Litentry
- 2026: Nodle
- 2035: Phala
- 2038: Geminis

Extend Current LP7 Crowdloans

- Supercolony is organizing the first Smart Contracts on Polkadot - WASM conference.
- They received funding approval from a treasury proposal, known as motion 152.
- The conference will have an online platform and aims to bring the community together.
- The main organizers, who are in Ukraine, had to move for safety reasons.
- They lost access to funds because of their move and are looking for ways to recover them.
- A new plan involves creating a new treasury proposal using a new account to retrieve the funds.
- The funds from the old account will be marked as "Lost" since they can't be accessed anymore.

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

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

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

After discussion with the community regarding the two original alternatives to help save the funds, a third one and more viable was presented: to vote on a new treasury proposal with Supercolony's new account (the comment that originally suggested this can be found [here](https://polkadot.polkassembly.io/post/904#eeec650b-7afc-42c0-b7eb-3ffa6c9fe0ab)). 

- New address (with verified identity): [14QZaDL6Pj8TWdjoe2honAsoVKSytSc74rNcTZxfnJqSwaxc](https://polkadot.subscan.io/account/14QZaDL6Pj8TWdjoe2honAsoVKSytSc74rNcTZxfnJqSwaxc).
- Original discussion to help recover the funds can be found [here](https://polkadot.polkassembly.io/post/904).
- The proposal aims to fund the **Smart Contracts on Polkadot - WASM conference (Virtual)**: the specs of the proposal, including budget, agenda, speakers and other elements can be found on [the original proposal](https://polkadot.polkassembly.io/motion/152).**The old funds will be marked as "Lost" since they cannot be moved, and the account will be monitored**. 

Helping Supercolony Recover Funds From Treasury Proposal - A new vote on the proposal

- A proposal is made for a batch call that upgrades Polkadot and Statemint together.
- The Polkadot upgrade will change its runtime to version 9170, improving block time issues and other features.
- The Statemint upgrade will change its runtime to version 700, adding new tools for NFT creation and fixing previous problems.
- The proposal includes important call hashes for both upgrades.
- Developers need to be aware of changes related to transferring assets between networks.
- The upgrades will allow more flexibility with assets in the Polkadot network.
- Community voting will be necessary for the proposal to be enacted.

Please note this is a `batch` call proposal, combining the Polkadot upgrade with the Statemint upgrade: 

- Batch call hash: `0xbf60cbdd406036e0b6a3028763bfe20d9569780c0ffddc75cf209358fce3111c`
- Call design: [here](https://drive.google.com/file/d/1emtVtvZ-4skQnKDJj5r0_fP1bm-q4l4l/view?usp=sharing).

The **Polkadot runtime** will be upgraded to **v9170** - Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.17-rc4). This release improves the block time degradation issues, as seen [on Kusama](https://github.com/paritytech/polkadot/issues/4911). It also includes new changes in the runtime: like optimised weights and contains the PR to fully enable the bags list on polkadot, which **removes the need of having a strict maximum count for nominators** and also fully alleviates the phantom nominator issue. Both of these are explained further [in the January issue of "Polkadot Staking Progress”](https://docs.google.com/document/d/12MPnxGzoiRcJJYAGOYVU8dGUkqybuhoQX7wg5ouGfgU/edit?usp=sharing). 
- Call hash for polkadot upgrade: `0x8eb2806cbdf1a4ba91334669b2476870134db3af5c77f418152af0ad354d3b32`
 
The **Statemint runtime** will be upgraded to [v700](https://github.com/paritytech/cumulus/releases/tag/parachains-v7.0.0-rc8):

-  The Uniques pallet includes an [extra storage item](https://github.com/paritytech/substrate/pull/9940) linking class owners to their NFT classes. This storage map comes in handy for UI developers, especially around the UX of creating and minting NFTs.

- With the inclusion of [Polkadot 4470](https://github.com/paritytech/polkadot/pull/4470) and [Cumulus 831](https://github.com/paritytech/cumulus/pull/831), parachains that have HRMP channels with Statemint will finally be able to use them in both directions. For parachain developers, note that this is a breaking change and if you've used reserve backed transfers from Statemint then you will need to migrate some storage items.

- It addresses all issues found by independent auditors regarding the Statemint runtimes. For Statemint, this means that once teleportation is ready (pending some final disputes related features) it should be OK to lift the call filter restricting asset/unique creation, opening the door for fungible and non-fungible assets in the Polkadot network. 

As usual, the Statemint proposal will dispatch an `authorizeUpgrade` message. All info about the upgrade can be found on the link above. 

- Hash for XCM call (council motion) can be found [HERE](https://drive.google.com/file/d/1BvnGFDK2KVjvFNMxs6qA9evkeSyniOdS/view?usp=sharing).
 - Hash: `0x8adb4ccdf996f05fa7941ce3b56ecec6dd49a88d9db445963e813ac10cadd326`.
- Encoded call: `0x01028adb4ccdf996f05fa7941ce3b56ecec6dd49a88d9db445963e813ac10cadd326`
- Runtime release can be found [HERE](https://github.com/paritytech/cumulus/releases/tag/parachains-v7.0.0-rc8).

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 v9170 and Statemint Runtime Upgrade to v700

Subscan is a tool that helps people explore blockchain networks that use Substrate. Here are some key points:

- It supports different chains like Polkadot and Kusama.
- Subscan offers features beyond just basic services, like fixing bugs and improving user experience.
- They have noticed more users, which makes it harder to keep everything working well.
- Subscan is starting to earn money to support their work.
- They want to keep costs low for users while still providing good services.
- In 2021, they spent a lot on infrastructure with totals over $38,000 for several months.
- They mainly use services like Google Cloud for their operations.


Subscan is an aggregated Blockchain explorer for Substrate-based chains. We have supported several chains:

- Relay chain: Polkadot, Kusama
- Testnet: Westend, Rococo
- Public parachain: Statemine

We not just provide basic explorer services for the above networks, and develop new features, optimize the ux and fix bugs as always.
Please refer to the version update document:
> https://medium.com/subscan

Over the past few months，We have seen an encouraging trend in the number of users and their level of activity. However, with the rapid growth of users, stability and reliability in infrastructure are becoming a challenge. As a result, Subscan has to expend more resources to ensure the quality of the service. 

Actually, Subscan is starting to generate some revenue, which mainly comes from the development fee and O&M fee to support the new network. As our original supporters, Parity/W3F helped a lot in the early stage of Subscan. We don't want to charge the team a high premium O&M fee to gain profits, instead we will do more development and research to provide better explorer services to repay the ecosyetem. Therefore, we decided to only apply the necessary infrastructure costs as O&M fees, and the rest of the cost such as human resources and development will on the subscan team. We look forward to growing rapidly and taking on more and more responsibilities.

## Current Service Scale of Subscan

Below are some metrics from Cloudflare and Subscan's monitoring system for the last few weeks.

*Subscan traffic overview:*
![](https://github.com/itering/subscan-treasury-proposals/raw/master/infrastructure-costs-2021-Sep-to-Dec/subscan-cloudflare.png)

*Subscan API traffic and distribution:*
![](https://github.com/itering/subscan-treasury-proposals/raw/master/infrastructure-costs-2021-Sep-to-Dec/subscan-qps-per-network.png)



## Billing Info

The infrastructure cost refers to what we have spent on Google Cloud Platform.

### September 2021

![](https://github.com/itering/subscan-treasury-proposals/raw/master/infrastructure-costs-2021-Sep-to-Dec/09_2021.jpeg)

Subtotal in September: $9,370.69

### October 2021

![](https://github.com/itering/subscan-treasury-proposals/raw/master/infrastructure-costs-2021-Sep-to-Dec/10_2021.jpeg)

Subtotal in October: $8,495.50

### November 2021

![](https://github.com/itering/subscan-treasury-proposals/raw/master/infrastructure-costs-2021-Sep-to-Dec/11_2021.jpeg)

Subtotal in November: $10,057.64

### December 2021

![](https://github.com/itering/subscan-treasury-proposals/raw/master/infrastructure-costs-2021-Sep-to-Dec/12_2021.jpeg)

Subtotal in December: $10,349.90


### Total Amount

**$9,370.69 + $8,495.50 + $10,057.64 + $10,349.90 = $38,273.73**

*Compute Engine*, *Cloud Logging*, and *Cloud SQL* are the three primary services, among which *Compute Engine* alone constitutes around **75%** of the total cost. Detailed billing info and other relevant proof are available upon request.

The estimated infrastructure cost we spent on Polkadot, Kusama, Westend, and Rococo adds up to **$28,705** according to the request distribution chart. Therefore, the amount we are requesting is **1483 DOT**.
> 1 DOT ≈ 19.355 $USD (EMA 30: 2022-02-24 08:33:42)


## References

- Subscan for Polkadot Network: https://polkadot.subscan.io/
- Subscan Service Status: https://subscan.statuspage.io/

The source code of this proposal is hosted on [GitHub](https://github.com/itering/subscan-treasury-proposals/blob/master/infrastructure-costs-2021-Sep-to-Dec/).


The Infrastructure Costs of Subscan for Polkadot Network from Sep 2021 to Dec 2021.

- Subscan is a special tool that helps people explore blockchain systems like Polkadot and Kusama.
- They started using a service called Cloudflare Enterprise to make their website faster.
- The Cloudflare service has been working well for the last six months.
- This proposal is about asking for money to pay for Cloudflare from January to April.
- The total cost for the Cloudflare service is $15,300, but they are only asking for 85% of that amount this time.
- They are requesting $13,005, which is about 671 DOT (a type of digital money).
- Subscan plans to keep improving and will aim to pay for more costs by themselves in the future.

## About Subscan

Subscan is an aggregate high-precision blockchain explorer for Substrate-based chains. We have been supporting several influential blockchains, including Polkadot, Kusama, Rococo, and Westend. For many users, Subscan is their first stop in the blockchain world. As we continue to deliver new features and support more blockchains, our user base is on the steady rise. Therefore, high robustness and availability are currently among our major concerns.



## About the previous proposal

In the [previous proposal](https://polkadot.polkassembly.io/treasury/60), we explained **Why We Can't Do Without a Firewall?**
and **Why We Need the Cloudflare Enterprise Plan?**

We greatly appreciate the support from Polkadot Treasury and all the community members, Subscan has integrated with Cloudflare Enterprise since August 16th, the enterprise plan really helps us reduce the service latencies significantly. It has been working smoothly for the past 6 months, with no noticeable Cloudflare incidents up to now.

![](https://github.com/itering/subscan-treasury-proposals/raw/master/cloudflare-enterprise-2022-Jan-to-Apr/cloudflare-data.png)


The previous proposal was for advance payment, now I am here to update the whereabouts of the money. Although Subscan has integrated with Cloudflare Enterprise since August 16th, due to trial and commissioning, the first two months are free and the formal payments began on October 15. The invoice is as follows:

![](https://github.com/itering/subscan-treasury-proposals/raw/master/cloudflare-enterprise-2022-Jan-to-Apr/cloudflare-invoice-10.png)



## Total Amount

This time we apply for the fee from January 15, 2022 to April 14, 2022, and the invoice is as follows:

![](https://github.com/itering/subscan-treasury-proposals/raw/master/cloudflare-enterprise-2022-Jan-to-Apr/cloudflare-invoice-01.png)



This proposal is for Subscan's Cloudflare enterprise plan (mid-January to mid-April), the Cloudflare enterprise service fee is **$15,300**. 

In the last proposal, we applied for 100% of the cost of Cloudflare enterprise service. As Subscan grows, we will strive to cover more and more costs. This time, we decided to reduce the application proportion to 85%, and it will be less and less in the future until complete financial independence.

Therefore,  the amount we are requesting is :

**15,300 * 85% = 13,005 $USD**

**1 DOT ≈ 19.355 $USD (EMA 30: 2022-02-24 08:33:42)**

**13,005/19.355 ≈ 671 DOT**

In case we missed any information or you have any questions, please feel free to send us an inquiry.

## References

- Cloudflare Enterprise plan: <https://www.cloudflare.com/plans/enterprise/>
- Cloudflare Argo: <https://www.cloudflare.com/products/argo-smart-routing/>

The source code of this proposal is hosted on [GitHub](https://github.com/itering/subscan-treasury-proposals/tree/master/cloudflare-enterprise-2022-Jan-to-Apr).


Cloudflare Enterprise Plan for Subscan from January 2022 to April 2022

- A new proposal wants to temporarily increase the limit for nominations to 160 DOTs.
- This change helps keep the Polkadot nomination system active.
- The previous proposal had a mistake: it used the wrong unit of measurement.
- Instead of DOTs, the proposal should have used PLANKs, which are smaller units.
- The right amount for the bond is actually 1,600,000,000,000 PLANKs.
- All other values in the proposal stay the same, except for the minimum nominator bond. 
- There are specific codes called call data and call hash related to this proposal.

This new proposal aims to enact the same as [motion 157](https://polkadot.polkassembly.io/motion/157): to temporarily increase the nomination limit to `160` DOTs. This allows for the permissionless `chill_other` transaction to be used and prune the number of nominators, in order to keep the nomination ecosystem of Polkadot active, whilst we wait for the enactment of the next runtime upgrade on Polkadot.

The enacted proposal unfortunately contained a major flaw: the numerical values are not in DOTs, but rather in PLANKs, the smallest unit of the DOT currency. Thus, the correct value for minimum nominator bond should have been set to `160 * (10^10)`, i.e. `1600,000,000,000`.
 
All values are unchanged except for `minNominatorBond`.

The correct call hash and data:

- Call data: `0x071700806e877401000000000000000000000000000000000000000000000000000001e457000001b0040000015a`

- Call hash: `0xbdf1c925dbca9e1e55de029db3786ea71949ff872e5b53588f46d0db6ccae379`

Polkadot’s Update to 160 DOTs as minimum nomination limit: A follow-up proposal fixing a unit mistake

- The BrightTreasury app is being improved to help users submit proposals and understand the Treasury module in Polkadot and Kusama networks.
- The project is run by a team called Bright Inventions, which has 70 skilled members, including developers and designers.
- They want to add new features based on user suggestions and connect better with Polkassembly.
- There will be four main steps, called milestones, to achieve these improvements, including sharing ideas and adding new functions.
- Each milestone has specific tasks and costs in a digital currency called DOT.
- The team believes in working together and helping clients grow their ideas.
- The project started with support from the Web3.0 Foundation and is currently funded by Treasury funds.

**About the project**
The goal of the proposal is to fund new features for the BrightTreasury app. The first version of the app is already available at treasury.bright.dev. We would like to further integrate with Polkassembly and add some improvements based on user feedback as well as integrate Tips and child-bounties mechanism. More details about the planned scope can be found in the description of each milestone.

Project Link : [https://treasury.bright.dev](https://treasury.bright.dev)
Link to any documentation already published: [https://github.com/bright/bright-tresury](https://github.com/bright/bright-tresury)

BrightTreasury is a standalone web application along with a PWA representation that allows performing basic actions on the Treasury module of Polkadot and Kusama Substrate networks (with a potential to support any Substrate-based network with Treasury module). It allows a more intuitive and lightweight flow of submitting proposals as well as an overview of the Treasury related actions.

Our focus is on the regular user’s actions rather than the council perspective for this first release. We want to attract more professionals who could contribute to the community with their ideas and skills but at the same time may not be as fluent in blockchain customs and terminology.

The first development phase of this project was funded by the Web3.0 Foundation Grants Program. Currently, BrightTreasury maintenance is funded by Treasury funds and is available in the production environment at https://bright.treasury.dev. 

**The Team behind it**

Bright Inventions is a team of 70 developers, project managers, UX/UI designers and operations specialists - experts in mobile and web applications, systems integration, IOT devices and Blockchain platforms. 

We believe that building a software product is about people working together in a collective way. By offering complex support – mobile and web development as well as IT consultancy we try to eliminate roadblocks towards engaging clients as partners at every step of the process. 

We support startups, digital agencies as well as medium to big businesses. We cooperate with startups, accelerators and incubators. Whatever the client profile is, we always  aim to establish a satisfying partnership for both sides. Since 2012 we have built software for more than 40 businesses worldwide.

The BrightTreasury team currently consists of:

Agnieszka Olszewska - Technical Lead, blockchain specialist. 
She is a senior backend developer with a main interest in data modeling. She started her software development career 10 years ago and from then she began discovering a lot of new technologies. Among them there are JavaScript, TypeScript, React, Postgres, Node.js, NestJS. Most recently she’s been engaged in developing blockchain based solutions with Substrate.

Alisa Kashytska - UI/UX design
She is a UI/UX designer with a passion for digging deep into the product domain and understanding the user's perspective. She has worked on the design for multiple web/mobile solutions and lately has been responsible for UI redesign of Parity Building Blocks Android and web apps.

Łukasz Kuderewski - fullstack developer
He is an optimist, always willing to learn new things. Mechatronics engineer who fell in love with programming. He has always been interested in a holistic approach to programming problems, which is why after working as a frontend, he is now fulfilled as a fullstack.

Robert Koprowski - fullstack developer, blockchain specialist
He is an experienced and ambitious blockchain enthusiast. Graduated from the University of Edinburgh, he lived in various locations around the world to settle now in Gdańsk. Originally a Backend Developer who decided to extend his skills and become Fullstack Developer, always trying to learn something new.

Katarzyna Łukasiewicz - Project Manager
She has been working with agile methods for over 10 years, both as a researcher and a practitioner. She believes in teamwork and a power of user centered mindset. With experience in leading international projects, she knows how to support and encourage timely and high quality deliveries.

**Costs and budget**

The total cost is a sum of budgets for the four milestones.

The cost covers all necessary development, design and management efforts performed by the team introduced in the "Team behind it". 

After each milestone a summary of what has been accomplished along with a link to documentation and guidelines how to test will be posted in the Discussion of the proposal.

**Milestones**

Milestone 1 - Add proposals’ and bounties’ description and title to Polkassembly  
Dates: 2022-02-28 to 2022-02-28  
Cost: 393.4 DOT  
Currently BrightTreasury displays the Proposal and Bounty information that were added through Polkassembly. The goal of this milestone is to support the flow other way around. We want to allow users to share to Polkassembly the Proposal or Bounty contextual information they add via BrightTreasury. Whenever a user converts an Idea to Proposal or adds a new Bounty using BrightTreasury, she/he will be asked if they want to share the description to Polkassembly as well. If the user agrees, she/he will need to confirm the identity and the description will be shared automatically. There will also be the possibility to do it later. 
It will include the following user stories:

- US.1 Ask user if description can be shared to Polkassembly
- US.2 User identity confirmation 
- US.3 Convert BrightTreasury structure to Polkassembly structure (+ information “This proposal was added through BrightTreasury. For more info & discussion, check BrightTreasury link...”)
- US.4 Preview Polkassembly post (no editing) 

Milestone 2 - Improvements & change requests  
Dates: 2022-03-14 to 2022-04-03  
Cost: 936.68 DOT  
Within this milestone we would like to present the users with a set of smaller features that were suggested to us in the testing phase of the app. They should improve the overall user experience and engage the community in discussions. 
It will include the following user stories:

- US.5 Import blockchain identity context info & add blockchain avatar for all types of accounts 
- US.6 Deleting own account by the user 
- US.7 Tagging users in the discussions (+search/filter users) 
- In-app notifications
- Mail notifications
- US.8 Add reactions for comments in discussions (thumbs up & down) 
- US.9 Add markdown interpretation for description fields (Ideas/Proposals/Bounties) with preview 
- US.10 Password reminder/recovery 

Milestone 3 - Implementation of child-bounties  
Dates: 2022-04-03 to 2022-05-02  
Cost: 1064.75 DOT  
In this milestone we want to integrate the new child-bounties pallet in BrightTreasury Bounties module.
It will include the following use stories:

- U.S. 11 As a curator I can create a child-bounty within a curated active bounty.
- U.S. 12 As a curator I can share child-bounty description to Polkassembly
- U.S, 13 As an anonymous user I can view the child-bounties list
- U.S. 14 As an anonymous user I can view the child-bounty details
- U.S. 15 As a curator I can propose a child-bounty curator and his fee
- U.S. 16 As a child-bounty curator I can accept the nomination
- U.S. 17 As a child-bounty curator I can reject the nomination
- U.S. 18 As a parent-bounty curator I can unassign the child-bounty curator (and slash his deposit)
- U.S. 19 As a curator I can edit the contextual info of a child-bounty (title, description, people who do the work) and report progress.
- U.S. 20 As a child-bounty curator I can award a chosen beneficiary for the child-bounty
- U.S. 21 As a bounty or child-bounty curator I can claim the payout of the child-bounty (the reserved amount will be paid out to the beneficiary account)
- U.S. 22 As a bounty or child-bounty curator I can close an active or added child-bounty
- U.S. 23 As a user, I can view the details of closed child-bounties (only for Polkadot and Kusama networks)
- U.S. 24 As an anonymous user I can see the parent-bounty value left
- U.S. 25 As a logged-in user I can discuss the child-bounty 
- U.S. 26 As a child-bounty owner I can get the discussion email and in-app notifications
- U.S. 27  As a user taking part in discussion I get the email and in-app notifications

Milestone 4 - Add Tips mechanism  
Dates: 2022-05-02 to 2022-05-23  
Cost: 891.71 DOT  
The main goal of this milestone is to integrate the Tips funding mechanism to BrightTreasury, in a similar manner as Proposals and Bounties. Users will be able to browse through tips, introduce a new one or support an already added tip. Tips module will also include Polkassembly integration - two way sharing of the contextual information.
It will include the following user stories:

- US.28 As a logged-in user I can create a tip request 
- US.29 As an anonymous user I can see the on-chain tips list
- US.30 As an anonymous user I can filter the tips by the status
- US.31 As an anonymous user I can see the on-chain tips details
- US.32 As an anonymous user I can see the polkassembly tips details
- US.33 As a tip owner I can share tip details to polkassembly
- US.34 As an anonymous user I can see the tippings list  
- US.35 As a logged-in user I can discuss the tip 
- US.36 As a tip owner I can get the discussion email and in-app notifications
- US.37 As a user taking part in discussion I get the email and in-app notifications 
- US.38 As a tip owner (in-app owner, finder) I can claim the tip pay out
- US.39 As a tip owner (in-app owner, finder) I can cancel the tip
- US.40 As an anonymous user I can view the tips history (list, details, discussion)  

Link to this proposal info & discussion in BrightTreasury app: [https://treasury.bright.dev/proposals/93/info?networkId=polkadot](https://treasury.bright.dev/proposals/93/info?networkId=polkadot)




BrightTreasury - v. 2.0 improvements & features

calls

[See discussion](https://polkadot.polkassembly.io/post/863)

Polkadot 2022 Parachain Auction Calendar

- A proposal is made to raise the DOT nomination limit from 120 to 160.
- This change is temporary until a bigger upgrade (0.9.16) is done on Polkadot.
- The upgrade will allow nominations to change based on demand, instead of having a fixed limit.
- There were some problems with the upgrade after it was tested on Kusama, so it hasn't been proposed for Polkadot yet.
- More people are allowed to nominate, reaching a total of 22,500.
- This temporary increase will help keep the nomination system active while waiting for the main upgrade.
- The proposal keeps all other values the same, except for the minimum nomination amount.

This is a short term upgrade proposed to increase the limit of DOTs for nomination from 120 DOTs to 160, maintaining the increase of 40 DOTs that the network has had throughout this period of updating the nominator limit through governance. The reason for this is the combination of the following:

- Polkadot’s [0.9.16](https://github.com/paritytech/polkadot/releases/tag/v0.9.16) upgrade was scheduled to contain a fix that would completely remove the 120 DOTs limit. This explained thoroughly in the monthly staking report of [January 2022](https://gist.github.com/kianenigma/aa835946455b9a3f167821b9d05ba376#january-2022). After the 0.9.16 update, the nomination limit would move to a dynamic system based on demand, rather than a fixed entry barrier.  
- Due to some unforeseen issues arisen after the deployment of 0.9.16 in Kusama, 0/9.16  has not yet been proposed to Polkadot.
- In the meantime, the number of nominators in Polkadot has been increased to reach the 22500 limit. 

As a consequence, we propose to temporarily increase the nomination limit to **160** DOTs. This allows for the permissionless `chill_other` transaction to be used and prune the number of nominators, in order to keep the nomination ecosystem of Polkadot active, whilst we wait for the enactment of runtime 0.9.16 on Polkadot.

 Proposal details: All values are unchanged except for `minNominatorBond`.

![](https://i.ibb.co/vz2vcdj/Screenshot-2022-02-21-at-18-31-17.png)

- Call hash: `0xb2286cbfdd18c265572d3305754b0dbe8ba1fd8da40ef48ff0d5ef40912f2291`

- Call data: `0x0717a00000000000000000000000000000000000000000000000000000000000000001e457000001b0040000015a`

Preimage is submitted. 

Polkadot’s Update to 160 DOTs as minimum nomination limit: The Reason

- Omni is a special computer program for businesses that helps users manage their digital assets.
- It works with something called Polkadot.js Apps and helps users see everything they need in one place.
- Users can do many tasks, like managing money and voting, all at once without much effort.
- The program is designed to be very safe and easy to use.
- The Nova Foundation team talked to businesses to understand what they needed for the software.
- There are plans and proposals for making this software even better.


**Omni Software Requirement Specification:**
[https://docs.google.com/document/d/1jFQ43ybWIPpXa205Q2UsSkVsTpVmq20afh7ZPfRjrZo/](https://docs.google.com/document/d/1jFQ43ybWIPpXa205Q2UsSkVsTpVmq20afh7ZPfRjrZo/)

**Omni: Polkadot Enterprise desktop app Treasury Proposal - Milestone 1:**
[https://docs.google.com/document/d/1L9v0aK4IPEzrtfWEuJeKeIj2BRCE3OZ8_Y0r1SH25Nw/](https://docs.google.com/document/d/1L9v0aK4IPEzrtfWEuJeKeIj2BRCE3OZ8_Y0r1SH25Nw/)

![](https://i.ibb.co/vh15Cvm/Omni-SRS.png)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Omni is a desktop enterprise application** that works around the limitations of Polkadot.js Apps and can provide a single point-of-view for stakeholders with advanced needs in the entire ecosystem. It should sync shards (i.e. multi-sig & proxies should not need manual construction for each signatory), support complex proxy/multi-sig combinations, should amalgamate multiple operations into a single transaction, and handle staking, asset management, and voting across all shards in a single user-operation.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The goal is to primarily **handle all of these situations with minimum effort from the user side**. Focused on security, Omni aims to provide convenient access for complex token management & create complex operations which may involve several shards.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;For past 3 months, the Nova Foundation team conducted interviews with enterprise stakeholders to create initial **Omni Enterprse software requirements specification**: [Omni SRS](https://docs.google.com/document/d/1jFQ43ybWIPpXa205Q2UsSkVsTpVmq20afh7ZPfRjrZo/)
\
\
\
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Please feel free to review **M1 treasury proposal**: [Omni M1 treasury proposal](https://docs.google.com/document/d/1L9v0aK4IPEzrtfWEuJeKeIj2BRCE3OZ8_Y0r1SH25Nw/)

Omni: Polkadot Enterprise desktop app Treasury Proposal - Milestone 1

- PolkaWorld is a big group in China for the Polkadot community with over 50,000 followers.
- They want money to help pay for their work for the next three months.
- In 2021, PolkaWorld shared 584 articles and got almost 1 million views on Wechat.
- They hosted 43 online events that 48,551 people attended.
- PolkaWorld made 100 videos on Wechat with 182,759 views.
- They had meetups in 5 Chinese cities, with 2,149 people signing up.
- They also hosted a special metaverse meetup that 1,300 people joined.

This is a proposal from PolkaWorld to cover the next 3 months (March 2020 - May 2022) ops and maintenance costs.

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 in the following ways, and in 2021:

- PolkaWorld published a total of 584 articles and received 993,051 views in the Wechat ecosystem in 2021;
- Hosted 43 online broadcast on Wechat Channel and 48,551 people join us;
- Published 100 videos in Wechat Channel, got 182,759 views;
- Build a new website, and published 565 [articles](https://polkaworld.pro/) and 237 [timely news](https://polkaworld.pro/alerts)
- Published 110 videos on [YouTube](https://www.youtube.com/c/PolkaWorld), got 36,000 views
- Hosted 9 meetups in 5 different cities (Beijing, Shanghai, Shenzhen, Hangzhou, Chengdu, Xi’an) in China, 2149 people registered the meetup and more than 50% of people came to meet each other;
- Host 1 [Polkadot metaverse meetup](https://polkaworld.medium.com/recap-for-polkadots-first-metaverse-meetup-a-bitter-sweet-experience-e26a77a27b28) in DCL, 1300+ people jump into the meetup;

Please find more in our monthly reports:

 - [https://polkadot.polkassembly.io/treasury/63](https://polkadot.polkassembly.io/treasury/63) 

- [https://polkadot.polkassembly.io/treasury/74](https://polkadot.polkassembly.io/treasury/74) 

Milestones and budget can be find [here](https://docs.google.com/document/d/1-M31dUIWSB3ecsZBvysekMpLDrC8CoQoYnEaurdUD_M/edit).


PolkaWorld Ops and Maintenance proposal for 3/2022 - 5/2022

- Motion 154 is a proposal for a vote.
- It wants to pick one person as the curator for the Polkadot Pioneers Prize bounty.
- The person chosen has a special code: `151fSxLtpjaBRLGoo1DQB8n8ERLNR6ZduBnmjyzpypegJQp9`.
- The curation fee for this is 0.00 DOTs, which means it’s free.
- You can find more details about the plan and who is involved in the project.
- There are links to more information on how things will work and the reporting plan.
- This proposal is part of a bigger prize effort in the Polkadot community.

[**Motion 154**](https://polkadot.polkassembly.io/motion/153) is now up for vote: The proposal aims to elect

 `151fSxLtpjaBRLGoo1DQB8n8ERLNR6ZduBnmjyzpypegJQp9` 

As the curator for the [Polkadot Pioneers Prize bounty](https://polkadot.polkassembly.io/bounty/10). Identity of the proxy can be found [here](https://polkadot.polkassembly.io/bounty/10#e15a0df4-96c5-49c6-81d6-cc99c3665c43).

More info on the composition of the curator wallet, identity, roadmap and plan ahead can be found [HERE](https://polkadot.polkassembly.io/bounty/10#e15a0df4-96c5-49c6-81d6-cc99c3665c43). Note the curation fee is 0.00 DOTs. 

Information about the parties in the multisig, challenge categories, challengers and the submissions process, administrative Curator first order of business and reporting plan to Council can be found [HERE](https://docs.google.com/document/d/192BNBTsix7ZOOO6S4DvosELWqmYYSmDa9gbUTdgPFv8/edit).

Election of curator for Polkadot Pioneers Prize bounty

- Motion 153 is for voting on a proposal.
- The proposal wants to make someone a curator for an anti-scam bounty.
- The person chosen is identified by a special code: 151fSxLtpjaBRLGoo1DQB8n8ERLNR6ZduBnmjyzpypegJQp9.
- You can find more information about this person and what they'll do.
- There is no cost to the curation, which means the fee is 0.00 DOTs.

[**Motion 153**](https://polkadot.polkassembly.io/motion/153) is now up for vote: The proposal aims to elect

 `151fSxLtpjaBRLGoo1DQB8n8ERLNR6ZduBnmjyzpypegJQp9` 

as the curator for the [anti-scam bounty](https://polkadot.polkassembly.io/bounty/11). Identity of the proxy can be found [here](https://polkadot.polkassembly.io/bounty/11#d76dc9ac-002b-47a5-84e8-e6ca737dfaf6).

More info on the composition of the curator wallet, identity and roadmap ahead can be found [HERE](https://polkadot.polkassembly.io/bounty/11#8268b422-2001-4693-ba67-e563062c1b1e). Note the curation fee is 0.00 DOTs. 

Election of curator for anti-scam bounty proposal

- A virtual conference called "Smart Contracts on Polkadot - WASM" is being organized.
- The goal is to bring people together to talk about WASM and its role in building applications.
- The conference will last one day and will be held online using the Hopin platform.
- Supercolony has contributed a lot to WASM and the Polkadot ecosystem.
- They plan to hold 3-4 events next year, including the Polkadot Hackathon.
- Feedback on marketing and the agenda is welcome.
- Collaboration with WASM-related projects is encouraged.

Hi there!

We are going to organize the first **Smart Contracts on Polkadot - WASM conference** to bring the community together. Our plan is to collaborate with WASM stakeholders and discuss and answer questions like  - “Why the WASM is the base layer of decentralized application development.” From our side, we've already done a huge contribution to WASM, ink!, Polkadot ecosystem, and OpenBrush(like the OpenZeppelin, but for ink!) as [Supercolony](https://supercolony.net/)

**This proposal is for a 1-Day Virtual conference event.**

**[Proposal Document here](https://docs.google.com/document/d/15GwKbLImLXyBcozf6PkAmL7UJ9Bzll7kajoNca1UwPc/edit#)**

Streaming platform: We`re planning to use Hopin as the conference platform. Moreover, the subscription is designed for the year, and we're already planning the next event - Polkadot Hackathon. Our aim is to organize approximately 3-4 events in the next year!

Would love to get feedback on this plan regarding the marketing, agenda development and ideas.
We are welcome to discuss the collaboration with WASM-related projects/teams too!

Smart Contracts on Polkadot - WASM conference (Virtual)

- Scams are a big problem in our community, and this proposal aims to help fight them.
- The goal is to get people and companies involved in protecting users from scams.
- This plan will expand on an earlier project that focused only on scam websites.
- It will create different tasks, called child bounties, to tackle various scam issues.
- The tasks will mostly use tools outside of the blockchain system at first.
- There will be changes to the tasks based on community feedback and experience.
- The three main goals are to work more on the blockchain, be community-led, and cover more areas within the Polkadot ecosystem.

## Purpose of the bounty

Scams are plaguing our ecosystem, as they do the entire industry. However, as a community, we have shown time and again that we take scams seriously and strive to create a safe ecosystem for users.

This bounty proposal aims to incentivise the community, both individuals and companies, to fight against scams and protect users from falling for them. We believe that anti-scam response should be a community endeavour and this is what this proposal aims to build.

This proposal expands on the [community initiative targeting scam sites](https://docs.google.com/forms/d/e/1FAIpQLSf2iXCCvdkQ70WrfDPtG5uQA3RrCfvb0VDlZjti26q0yb17sg/viewform?pli=1) that has been ongoing for several months now with high levels of success. However, the current initiative is focused only on scam sites, while overlooking other aspects of scam fighting where we could be doing more.

With this proposal we aim to create a holistic solution that addresses the problem from several aspects, while bringing awareness to the community, and educating users, of both the problems and the efforts to address them. The bounty for this proposal is meant to be open-ended, with the funds being distributed through child bounties that cover several aspects of the anti-scam response.

The tasks described in the child bounties utilise mostly off-chain tools and processes, but it is the goal of this initiative to evolve to bring as much of that as possible on-chain. These tasks came from feedback from the community and the experience garnered from the current initiative.

The child bounties will be opened gradually as potential implementers come forward, and more will almost certainly be added along the way. They are described in this proposal with varying levels of details, but all parameters of each child bounty, in terms of implementation, participation and rewards, will be defined in detail before the child bounty is opened.

And because this is an evolving process, changes to the bounties are almost certain as we gain more experience and get more feedback from the community. But the three main evolution goals of this initiative are:

- To move it on-chain as much as possible

- To have it being driven and coordinated exclusively by the community

- To become an anti-scam umbrella over the broader Polkadot ecosystem, covering parachains, other relay chains and projects

Finally, all rewards are subject to change as we evaluate the efforts needed, receive feedback from implementers, curators and the community at large, and in case the price of DOT is very low or very high for prolonged periods of time.

Details on the proposed child bounties and rewards can be found [HERE](https://docs.google.com/document/d/1V-39ktdgpvATPpV1cfI8iZlS8_3oBDAHdlcMDd_3jpo/edit).

Anti-Scam Bounty 

- Polkadot, Statemint, and Westend are digital networks that provide public services through APIs.
- In the last three months, their API answered over 23 billion requests, which is a big increase.
- They used a lot of data, around 71 terabytes, to serve these requests.
- The highest single-day response was more than 515 million.
- Westend had 377 million responses, and Statemint had 295 million.
- Due to high demand, they had to improve their technology to keep up with the requests.
- The total running cost for these services is about $101,122.20.

***Ongoing costs for the running of high performance, scalable, and reliable public infrastructure for Polkadot, Statemint and Westend. Posted here for any discussion before moving to a Treasury Proposal***

Over the last 3 months (October, November, December 2021) we've provided a scalable free public API service so that everyone can access public pools of managed Polkadot, Statemint, and Westend nodes.

Between 2021-10-01 and 2021-12-31 our Polkadot API service has:
- Served an unprecedented total of 23,897,857,938 (23 billion) responses (an increase of 334% on the previous quarter)
- Accumulated over 71 TB of data egress (up 313% on Q3)
- The highest daily total was 515,417,945 responses in a single 24 hour period
- Our rolling 7 day average at the end of this period was over 227 million responses each day.
- Westend had over 377 million API responses in the period
- Statemint had over 295 million API responses in the period
- All time totals for Polkadot is 35,146,213,629 (35 Billion) since November

![Q4 Data](https://docs.google.com/spreadsheets/d/e/2PACX-1vSRvBZAOy2Zz2F5FygZHdSHFFGbdpvka9rz_zLzdz0JDaTBZVkrlX1FdnA4tIUjroW0-pms0Q06N-YN/pubchart?oid=1506257754&format=image)

This last quarter was huge for Polkadot and OnFinality, the demand for our services was unprecedented. In early November we experienced a surge of activity coinciding with the announcement of the Polkadot Parachain Auctions that took us to our highest daily response count of over 515 million responses in a single day.

Towards the end of this period we also noticed additional load on the compute component of our resourcing that we believe is due to the first 5 parachains connecting to the main relay chain and the additional block verification that resulted. We scaled up the compute component of our infrastructure to maintain service levels as a result. Additionally we are closely watching the work that Dwellir is doing in the ecosystem to propose improvements to the RPC nodes.

Additionally, our experience shows significant performance improvements in terms of response times when the CPU usage is less than 50%. We observed a noticeable drop of service quality (in terms of response times) when the node is under load.

This proposal includes combined running costs for our infrastructure for Polkadot, Statemint, and Westend. The total combined running cost is USD $101,122.20

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

OnFinality - High Performance Public Infrastructure (Q4 2021)

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

- **Libwallet** is a lightweight library for making cryptocurrency wallets. 
- It is easy to use and understand. 
- The wallets can work on different platforms like apps, websites, and even special devices. 
- The project is asking for **1273.95 DOT** to help with its development. 
- It plans to finish the work in **6 weeks**. 
- For questions, you can contact them via email or on their chat channel.

# Libwallet spending proposal

_**License:** GPLv3_  
_**Requested amount:** 1273.95 DOT_  
_**Timeline:** 6 weeks_  
_**Contact:** 📧 [contact@virto.team](mailto:we@virto.team); 🗨️ [#virto-network](https://matrix.to/#/#virto-network:virto.community)_  

Libwallet is a lightweight and very portable library with simple to understand and use abstractions that allow creating chain-agnostic crypto wallets able to run in all kinds of environments like native applications, hosted wallets, the browser or even embedded hardware.

**🔗 More information in the original [discussion](https://polkadot.polkassembly.io/post/825) 🔗**

 Libwallet treasury proposal

Sorry everyone, this was a misclick. Please vote NAY.

Vote Nay

- The Polkadot Pioneers Prize is a program that gives prizes to encourage new ideas on the Polkadot network.
- It will have different challenges, with the first two about zero-knowledge research and improving Polkadot’s infrastructure.
- The goal is to attract new people with skills to help build the Polkadot community.
- The program will include special prizes called child bounties, which will be shared by an elected curator.
- Details about the challenges will be shared by the middle of 2022.
- A Council will approve the program and elect the curator to manage the prize money.
- Everyone can check more information and vote on the plan.

The bounty proposal, an incentive prize program called the **Polkadot Pioneers Prize**, aims to structure a series of challenges created with the goal of propelling technical innovation on the Polkadot network. The first two of those challenges will be announced later this year and will cover categories including **zero-knowledge research** and **Polkadot infrastructure improvements**. The expectation is also for the bounty to provide the Polkadot ecosystem with an influx of new talent.

The incentive prize program will be structured as a set of [child bounties](https://github.com/paritytech/substrate/pull/10309) (to be included in the next runtime upgrade upon community approval), the details of which will be communicated in the second or third quarter of 2022 and will be decided by the general curator: to be elected by this Council. Due to the new design of the child bounties pallet, we can earmark funding now and announce the upcoming program, and then the elected curator can divide bounty payouts within the prize categories based on the sub-prizes and elect child bounty curators, which will be determined before the program launch. 

Please note this is the first stage for the bounty: if approved by the Council and after the bounty status is marked as active, the Council will elect a bounty curator -  the proposal includes a suggestion to Council for this role as well (a multisig composed by a group of community members). 

**Reasoning behind the idea, requested allocation, categories and further suggestions can be reviewed on [the Polkassembly post](https://polkadot.polkassembly.io/bounty/10)**. 

Councillors: please vote at your convenience!

Council Motions