- Polkassembly helps with the governance of Polkadot and Kusama networks.
- A new plan suggests regular payments every three months for maintenance and operation costs.
- The funds will cover things like upgrades, maintenance, and infrastructure.
- The proposal will alternate between Polkadot and Kusama networks for funds.
- This payment request is for the months of October, November, and December 2022.
- The proposal shares past work and future plans.
- More information can be found in the provided document and discussion links.

proposalId

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

The proposal details the work done in past from our previous proposal and the things we plan to implement in this quarter. 

The full proposal is available [here](https://docs.google.com/document/d/1-cm0QQDljqIGu7tFXI3wQz8-PsrKXb6QN3lSMElV9lk/edit?usp=sharing).  Discussion can be found [here](https://polkadot.polkassembly.io/post/1377)

Social Contract between Polkassembly and Polkadot Treasury

- There is a new update for parachains called "v9320."
- The update includes some small changes and bug fixes.
- The word "Anonymous" has been changed to "Pure" in the proxies.
- Two links are given for authorizing upgrades and sending from Polkadot.
- A proposal hash is provided for reference.
- The proposal needs to be approved by the Polkadot Council first.
- After approval, the community will vote on the proposal.

proposalHash

The parachains [v9320 release](https://github.com/paritytech/cumulus/releases/tag/parachains-v9320) contains updates that correspond to the v9320 runtimes of the respective Relay Chain. Changes to Assets and Uniques are minimal, but the release includes the change of “Anonymous” to “Pure” proxy and minor bug fixes.

\- [Authorize Upgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x0102f02ab4af6b1b58da2805d186f87ca03e808dc0d93d3581b4dbdab4785bea95cb)

\- [Send from Polkadot](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x630001000100a10f0204060202286bee880102f02ab4af6b1b58da2805d186f87ca03e808dc0d93d3581b4dbdab4785bea95cb\))

\- Proposal Hash: 0x1c3e581368a6762a6ecc26903a1fd18345bc212df09e8a66222778def7fcf49d

This proposal is submitted as an external motion: meaning that if/after the Polkadot Council approves, the community will vote on the proposal in referenda queue for the final decision. 

Make sure to review and vote at your convenience!

Statemint Runtime Upgrade to v9320

- Chris Veselinov is the CTO of LimeChain.
- He wants to create a Go Runtime to help with blockchain development.
- The goal is to make it easier and more friendly for beginners.
- They aim to make a framework in Go, which is different from Substrate.
- This framework would allow other developers to reuse parts of it.
- LimeChain has a grant to check if this project is possible.
- They have worked on some challenges and shared their efforts online.
- LimeChain is a company that builds blockchain tools and apps.

Hi everyone,

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

With this proposal, we’re looking to diversify and simplify the blockchain (parachain) development process, making the ecosystem more approachable/beginner-friendly and potentially more stable.

**The ultimate/end goal is creating a framework in Go, which is an alternative to Substrate.** However, it will be technically challenging to go for the direct implementation without abstracting components into different modules. Given that a modular approach has been taken, the practical goal would be to formalize those modules into a framework that can be reused by other developers.

**This is why we propose to develop a framework for building Go Runtimes.**

We recently got a [W3F grant to research the technical feasibility of the project](https://github.com/LimeChain/Open-Grants-Program/blob/application/research-feasibility-go-runtime/applications/research-feasibility-go-runtime.md), as we encountered some Go-related challenges along the R&D process. We were able to get those out of the way and you [can look at our efforts here](https://github.com/LimeChain/gosemble).

**Please see the [official proposal document here](https://docs.google.com/document/d/1i8DnmVdgJz8jxHOUxO3LM6MlX4QhGP2fE33vmQI2Vgk/edit?usp=sharing). Any feedback or comments are highly appreciated.**

About us: [LimeChain](https://limechain.tech/) is a blockchain development company founded in 2017 with a focus on building core blockchain infrastructure, developer tooling and dapps. We dove into the Polkadot ecosystem about 2 years ago with [Subsembly](https://github.com/LimeChain/subsembly)  - a framework used to design and implement Substrate runtimes in AssemblyScript, again funded by the W3F. Due to AssemblyScript limitations, we were able to partially deliver on the framework specifications.

Thanks on behalf of the whole LimeChain team!

Framework for building Substrate-compatible Runtimes in Go (Parachains & Solochains)

Polkadot is introducing nomination pools to simplify staking for DOT-holders. Currently, nominators can stake a minimum of 10 DOTs and up to 50,000 nominators can participate. The top 22,500 are chosen for each era's election process and may receive staking rewards. Nomination pools aim to make staking easier and are designed to address two main concerns:

1. Encourage waiting nominators to join pools, which is mainly a task for Wallet/UI development.
2. Prevent too many waiting nominators from being created, as most may prefer joining pools instead.

To achieve these goals, the minimum nomination limit could be increased to 100 DOTs, based on the current requirement of around 200 DOTs to be an active nominator. This change would help prevent nominators from being created if they are likely to end up in the waiting queue. However, keeping a buffer of waiting nominators is important for Polkadot's economic security, so the 50,000 nominator limit should remain. With nomination pools, anyone with less than 50 DOTs should be directed to join pools instead, and their nominate transaction should be rejected.

Including contextual information form the staking team below - original discussion post [HERE](../post/1224). 

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Nomination pools are just around the corner for Polkadot, and this suggests some changes to be applied to the staking system.

First, let’s recap on the current status quo: Currently, nominators can freely set their intention to nominate in Polkadot, as long as they meet two limits: a minimum of 10 DOTs is staked, and a maximum of 50\_000 nominators is not filled. This creates a nomination market, where in every era, the top 22\_500 nominators from this open market are chosen to participate in the election process, and possibly receive staking rewards (if other conditions like over-subscription are not met).

This is a complicated and involved process. Nomination pools are exactly here to combat this and provide a simpler experience for DOT-holders to participate in staking.

Based on this, let’s cluster Polkadot nominators into two groups: **active** (in the top 22500), and **waiting**. The main concern at this point is to

-   Encourage all existing waiting nominators to join pools. This is mainly a task for the Wallet/UI development ecosystem, and is beyond the scope of this discussion.
-   Prevent too many waiting nominators to be created. The reason being that I speculate that most of these nominators have **erroneously** in the waiting queue, and prefer joining pools instead.

To achieve the second goal, we can set the nomination limits (10 DOTs, 50\_000) such that the system is not so _inviting_ to waiting nominators. In other words, the system should try and prevent nominators from being created, if they are certainly going to end up being in the waiting queue.

For example, we empirically know that the actual amount of DOTs needed to be an active nominator is around 200 DOTs as of this writing. Therefore, we can set the minimum nomination limit to a higher value such as 100.

Note that keeping a buffer of waiting nominators is a positive factor for Polkadot's economic security. It allows for buffer of waiting nominators to be ready, should a (malicious) cluster of nominators decide to chill all at once, preventing nothing at stake issues. Therefore, I am not suggesting lowering 50\_000 as well, and find that a reasonable bound. But, with nomination pools, I do think we should immediately forward anyone with less than e.g. 50 DOTs to join pools instead, and the way to do that is to immediately reject their nominate transaction.

-   [https://polkadot.polkassembly.io/post/1224](../post/1224)

Proposal: Slightly higher nomination limits

- A new plan is being discussed for Statemint, which involves collators.
- The number of "invulnerable" collators will be reduced from four to two.
- There will be six new positions that anyone can apply for by placing a bond.
- The bond amount will be set at 1,000 DOT.
- A total of six non-invulnerable collators will be allowed.
- This change needs approval from a majority of 13 councillors (7 votes).
- If people think this plan is controversial, it can be changed to a public vote.
- The plan will be open for discussion to help everyone prepare their Statemint nodes.

dest

message

As a step towards [Economic Model for System Para Collators](https://forum.polkadot.network/t/economic-model-for-system-para-collators/1010), this motion reduces the number of "invulnerable" collators on Statemint from four to two, and opens six positions that anyone can register in by placing a bond.

The call consists of three parts:

1. [Set the bond to 1,000 DOT](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x150200a0724e180900000000000000000000) (weight: 114,791,000)
2. [Reduce the Invulnerables from four to two](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x1500084c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811) (weight: 177,434,000)
3. [Set the desired number of non-invulnerable collators (from zero) to six](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x150106000000) (weight: 114,572,000)

Since `batch` calls are not expected to work over XCM in v9290, the message in this motion contains three separate `Transact` instructions.

All three of these calls require the `UpdateOrigin`, which is set to "more than 50% of the Council". Therefore, I have opened this as a motion requiring approval from 7 of 13 councillors. If discussion shows that people think that this is controversial, then we can reject the motion and make it a referendum.

I also recommend leaving this open for a few days to make sure that node operators can set up their Statemint nodes.

Open Permissionless Collator Registration on Statemint

- A proposal was made by Centrifuge to get money from the Polkadot treasury.
- They want $172,500 to help develop a tool called FUDGE.
- FUDGE helps people work with the databases of certain blockchains more easily.
- It allows users to build and change blocks without needing to connect to a network.
- This tool is very useful for testing and running commands related to these blockchains.
- Centrifuge has already created an early version of FUDGE and is using it for their own tests.
- More information about the proposal can be found through a link they provided.

**Proponent:** 12wWLUd5qMzLFGqBsMnHLVFeTuYJwuo5ygMAxuSywrBX1XSF

**Date:** 07.11.2022

**Requested DOT:** ($172,500) ~27,080 DOT

**Contact:** Frederik Gartenmeister (frederik@centrifuge.io)

***
This is a Polkadot treasury proposal by **Centrifuge** to fund the development of FUDGE (FUlly Decoupled Generic Environment for substrate-based chains). FUDGE provides a simple and generic way to interact with and manipulate the database of a substrate-based blockchain. This includes building and importing blocks locally without any kind of network or consensus, as also changing existing state and finalizing it without the need of forging a new block.

The currently most obvious use-case for FUDGE are local integration tests as the library drastically reduces time and overhead for these. But the library is furthermore useful as a core building block around clis in the Substrate ecosystem. E.g. a cli for forking-off a database of a node, tooling around analysing a chain in various states (i.e. at variaous blocks).

There already exists a PoC version of the library ([https://github.com/centrifuge/fudge](https://github.com/centrifuge/fudge)) and the library is actively used by the Centrifuge team for integration tests ([https://github.com/centrifuge/centrifuge-chain/tree/main/runtime/integration-tests](https://github.com/centrifuge/centrifuge-chain/tree/main/runtime/integration-tests)).

The full proposal can be found here: [https://centrifuge.hackmd.io/@rxJQ-iCrT9eYElX4L2WMmA/BkMfLwPli](https://centrifuge.hackmd.io/@rxJQ-iCrT9eYElX4L2WMmA/BkMfLwPli)

Treasury Proposal by Centrifuge: FUDGE - Core library for local integration-tests in Substrate

- The proposal asks for money from the Polkadot Treasury to help a Chinese group.
- This group wants to create better Chinese content about Polkadot, using easier language.
- They plan to help Chinese people learn more about Polkadot and its projects.
- The goal is to get more people interested in Polkadot and its community.
- Since March 2022, they have already received funding to operate.
- They are asking for about $104,760 to cover costs for six months.

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

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

Since March 2022, [we have established a Polkadot Treasury for our 2022/3-2022/8 operation cost, and get funding from the Polkadot Treasury](https://docs.google.com/document/d/1mTWu_x7ULOKLz5Vmk2BMNj_THXFyXkDbKbpQRvKnBCw/edit?usp=sharing). Here is our [report for the proposal](https://docs.google.com/document/d/11NSbOcxFL3d7FwrGhA8JAmO83OZdtIg-Z4x9_Db7Vuw/edit?usp=sharing). Please check our report to learn more.

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

Treasury proposal: The 2022/9-2023/2 operating cost for the nonprofit organization Polkadot Ecology Research Institute

- Patika web3 started in March 2022 to help developers in Turkey learn about web3.
- The platform has over 109,000 developers already learning.
- They plan to create a free online training for beginners called "Polkadot Rust&Substrate Practicum."
- Participants will learn together and support each other.
- The goal is to help 2,000 developers join the Polkadot ecosystem.
- They hope for at least 100 project submissions by the end of the training.

Hi everyone!

Launched in March 2022, [Patika web3](https://www.patika.dev/web3) aims to onboard developers to web3 in Turkey. Working together with leading web3 ecosystems, we introduce developers to new technologies and help them launch their projects and careers. Our online and free education platform already has 109,000+ developers from Turkey learning on the platform.

We propose to onboard these devs to the Polkadot ecosystem with the following steps:

- Learning pathway for Turkish developers: We will create a free, online, beginner-friendly and well-structured “Polkadot Rust&Substrate Practicum'' learning pathway.
- Polkadot Rust&Substrate Practicum and community events: Practicum is Patika.dev’s scalable cohort-based training model where participants complete the learning pathway together, supporting each other in their cohorts and during office hours with teaching assistants.

The aim of the project is to onboard 2000 devs to Polkadot ecosystem and get at least 100 project submissions at the end of the practicum. Please find the full proposal [here](https://docs.google.com/document/d/1tmoam1qMuat8N8KEeJ5jAeMpVshjQ6NVqOUkFDLOXzM/edit?usp=sharing).


Activating developer ecosystem in Turkey for Polkadot

- A proposal to upgrade Polkadot's system called "runtime" to version v0.9.30 has been made.
- The new proposal replaces an earlier one because there can be only one idea discussed at a time.
- The last proposal was about changing rules for special groups called nomination pools.
- There are several small tasks being worked on, like improving safety and making changes to how things are named.
- Some tasks have finished reviews, while others are still being checked.
- After the council votes, everyone in the community will also get to vote on this proposal.

The proposal aims to upgrade Polkadot’s runtime to [v9300](https://github.com/paritytech/polkadot/releases/tag/v0.9.30). More information about the release can be found on the link in this post. As the external queue can only hold one proposal at a time, yesterday's [motion 286](https://polkadot.polkassembly.io/motion/286), removing the limits on members in nomination pools, deleted previously approved [motion 285](https://polkadot.polkassembly.io/motion/285) aiming to upgrade Polkadot's runtime. This new proposal replaces motion 285.

**Runtime**

* [S] ✅ audited [#12170](https://github.com/paritytech/substrate/pull/12170) Low - Pallet-identity: be more paranoid ;)
* [S] ⏳ pending non-critical audit [#12222](https://github.com/paritytech/substrate/pull/12222) Low - Add constfeemultiplier to the transaction payment pallet
* [S] ⏳ pending non-critical audit [#11981](https://github.com/paritytech/substrate/pull/11981) Low - Breaking: rename call & event
* [S] ✅ trivial [#11738](https://github.com/paritytech/substrate/pull/11738) Low - Add inspect trait for asset roles
* [S] ⏳ pending non-critical audit [#11806](https://github.com/paritytech/substrate/pull/11806) Low - Improve base weights consistency and make sure they're never zero
* [S] ✅ trivial [#12205](https://github.com/paritytech/substrate/pull/12205) Low - Add special tag to exclude runtime storage items from benchmarking
* [S] ⏳ pending non-critical audit [#12034](https://github.com/paritytech/substrate/pull/12034) Low - [feature] part 1: add targetlist for validator ranking
* [S] ✅ trivial [#12186](https://github.com/paritytech/substrate/pull/12186) Low - Contracts: use weakboundedvec for instrumented code
* [P] [#5535](https://github.com/paritytech/polkadot/pull/5535) Low - Runtime/disputes: slashing
* [S] ✅ trivial [#12258](https://github.com/paritytech/substrate/pull/12258) Low - Breaking: rename origin
* [S] [#12230](https://github.com/paritytech/substrate/pull/12230) Low - Bound staking storage items
* [S] ✅ trivial [#12083](https://github.com/paritytech/substrate/pull/12083) Low - Make automatic storage deposits resistant against changing deposit prices
* [S] ✅ trivial [#12283](https://github.com/paritytech/substrate/pull/12283) Low - Rename anonymous to pure proxy
* [P] ✅ trivial [#6037](https://github.com/paritytech/polkadot/pull/6037) Low - Increase blockhashcount parameter
* [S] ⏳ pending non-critical audit [#12329](https://github.com/paritytech/substrate/pull/12329) Low - Add base-weight to system::extrinsic* events
* [P] ✅ trivial [#6032](https://github.com/paritytech/polkadot/pull/6032) Low - Paras: unblock offboarding when pvf-check concludes
* [S] ⏳ pending non-critical audit [#12366](https://github.com/paritytech/substrate/pull/12366) Low - [feature] add deposit to fast-unstake
* [P] [#6050](https://github.com/paritytech/polkadot/pull/6050) Low - Add fast-unstsake pallet to all runtimes
* [S] ⏳ pending non-critical audit [#12277](https://github.com/paritytech/substrate/pull/12277) Low - Add storage size component to weights

Proposal hash: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`

You can review the hash and changes in the release notes and use SRTool to verify proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after Council vote, the community will need to vote on the proposal in referenda queue. 

Runtime v9300 Upgrade On Polkadot

- Motion 286 is a proposal for Polkadot.
- It wants to remove limits on members in nomination pools.
- This change will help with the goals of Referendum 78.
- There was a mistake in the original proposal that didn't lift the limits.
- Voting on this motion is important for the community.
- Make sure to vote soon so it can be considered!

[**motion 286**](https://polkadot.polkassembly.io/motion/286) is up for vote! Please vote ASAP: this proposal removes the limits on members in nomination pools on Polkadot to fulfil the goal of the recently approved [referendum 78](https://polkadot.polkassembly.io/referendum/78). Preimage is submitted: The proposal had a mistake and did not lift the limit of maximum members per pool, therefore the pools are still unusable on Polkadot.

Make sure to vote soon on this external motion for the community to vote in referenda queue after!

Removing members' limit for the community to join nomination pools

- A new proposal is to upgrade Polkadot's system to version v0.9.30.
- The upgrades include many changes that are checked and almost ready.
- Some changes are about making the payments better and using storage wisely.
- There are new features related to ranking validators and fast-unstaking.
- The proposal has a special hash that you can check to see what changes are made.
- After the Council votes, the community will also need to vote on the proposal.

DELETED IN EXTERNAL QUEUE BY MOTION 286 - NOW REPLACED BY MOTION 287
_____________________________________________________________________________

The proposal aims to upgrade Polkadot’s runtime to [v9300](https://github.com/paritytech/polkadot/releases/tag/v0.9.30). More information about the release can be found on the link in this post.

**Runtime**

* [S] ✅ audited [#12170](https://github.com/paritytech/substrate/pull/12170) Low - Pallet-identity: be more paranoid ;)
* [S] ⏳ pending non-critical audit [#12222](https://github.com/paritytech/substrate/pull/12222) Low - Add constfeemultiplier to the transaction payment pallet
* [S] ⏳ pending non-critical audit [#11981](https://github.com/paritytech/substrate/pull/11981) Low - Breaking: rename call & event
* [S] ✅ trivial [#11738](https://github.com/paritytech/substrate/pull/11738) Low - Add inspect trait for asset roles
* [S] ⏳ pending non-critical audit [#11806](https://github.com/paritytech/substrate/pull/11806) Low - Improve base weights consistency and make sure they're never zero
* [S] ✅ trivial [#12205](https://github.com/paritytech/substrate/pull/12205) Low - Add special tag to exclude runtime storage items from benchmarking
* [S] ⏳ pending non-critical audit [#12034](https://github.com/paritytech/substrate/pull/12034) Low - [feature] part 1: add targetlist for validator ranking
* [S] ✅ trivial [#12186](https://github.com/paritytech/substrate/pull/12186) Low - Contracts: use weakboundedvec for instrumented code
* [P] [#5535](https://github.com/paritytech/polkadot/pull/5535) Low - Runtime/disputes: slashing
* [S] ✅ trivial [#12258](https://github.com/paritytech/substrate/pull/12258) Low - Breaking: rename origin
* [S] [#12230](https://github.com/paritytech/substrate/pull/12230) Low - Bound staking storage items
* [S] ✅ trivial [#12083](https://github.com/paritytech/substrate/pull/12083) Low - Make automatic storage deposits resistant against changing deposit prices
* [S] ✅ trivial [#12283](https://github.com/paritytech/substrate/pull/12283) Low - Rename anonymous to pure proxy
* [P] ✅ trivial [#6037](https://github.com/paritytech/polkadot/pull/6037) Low - Increase blockhashcount parameter
* [S] ⏳ pending non-critical audit [#12329](https://github.com/paritytech/substrate/pull/12329) Low - Add base-weight to system::extrinsic* events
* [P] ✅ trivial [#6032](https://github.com/paritytech/polkadot/pull/6032) Low - Paras: unblock offboarding when pvf-check concludes
* [S] ⏳ pending non-critical audit [#12366](https://github.com/paritytech/substrate/pull/12366) Low - [feature] add deposit to fast-unstake
* [P] [#6050](https://github.com/paritytech/polkadot/pull/6050) Low - Add fast-unstsake pallet to all runtimes
* [S] ⏳ pending non-critical audit [#12277](https://github.com/paritytech/substrate/pull/12277) Low - Add storage size component to weights

Proposal hash: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`

You can review the hash and changes in the release notes and use SRTool to verify proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after Council vote, the community will need to vote on the proposal in referenda queue. 

**High Performance Public Infrastructure Proposal**

- The proposal was made on October 6, 2022, for funding of $112,454.80.
- It aims to maintain strong and reliable public infrastructure for Polkadot and its related networks.
- Over the past three months, they provided a free service that helps users access public nodes easily.
- Key goals included making it easier for new projects to join and helping existing projects grow.
- They successfully reduced costs for customers by up to 40% and added new features to improve their service.
- New API services and better data insights have been added to help users understand their applications.
- They achieved a high uptime of 99.94% for Polkadot and expanded their service to include new networks like Avalanche and Juno.

Proposal: High Performance Public Infrastructure (Q3 2022)

Proponent: 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf

Date: 6th October 2022

Requested DOT: 16,274.212 (USD $112,454.80)

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

Previous Discusson: <https://polkadot.polkassembly.io/post/1325>

Raw Data: <https://docs.google.com/spreadsheets/d/1Q9eXw78E-VDkHmCl1nLSGwOfxlG6jc-6CsvrUMHOskE/edit?usp=sharing>

Full Report: [https://docs.google.com/document/d/1hxT4LMvntD3aV5PlmF3MnddDFhca8UnpH1sRSQu-nGY/edit?usp=sharing](https://docs.google.com/document/d/1hxT4LMvntD3aV5PlmF3MnddDFhca8UnpH1sRSQu-nGY/edit?usp=sharing)

* * * * *

## Original Motivation

Over the last 3 months (July, August and September 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

During the last quarter, we've focused on three key areas for the development of OnFinality - cost optimization, network expansion, and providing more value from our Ultimate API service.

The bear market has made many of our customers more price sensitive, and as such we've been working with them to optimise our services to provide more for less. We've reduced prices for our larger customers between 30 and 40%, and created products designed to target and onboard new chains with entry level pricing. We've also been working on new rate limiting capabilities to progressively restrict abusers of our public APIs to upgrade to paid API plans.

In the past quarter we have succeeded in our goal of onboarding two new networks, with the addition of Avalanche and Juno to our API service. This was a large amount of upfront work, extending OnFinality to allow chains outside of Polkadot/Substrate, but now that it has been done we should be able to move faster and onboard new chains each week. We hope that this means that we will be able to invite as many new ecosystem participants into Polkadot as possible with this expansion. 

Finally, providing move value from our Ultimate API service has always been a priority, and in this space we've added new API specific paid plans at competitive prices to our competition. We have also delivered the ability for our customers to better understand and learn about their users, with API Insights that tell you where your users are, what they are requesting, what methods are failing (to find bugs in your dApp), and where optimisations can occur.

We continued to execute on our efforts to provide unprecedented service stability and reliability to this ecosystem. All supported networks exceeded our 99.9% target, including 99.94% uptime for Polkadot over the last 90 days . At this stage, OnFinality is operationally striving for a minimum of 99.99% availability, which means less than an hour of downtime each year.

Between 2022-07-01 and 2022-09-30 our Polkadot API service has:
-   **Served almost 100% more traffic with only a 10% increase in cost**
-   Served a total of 21.4 billion responses
-   Accumulated over 100 TB of data egress 
-   The highest daily total was 517 million responses in a single 24 hour period for Polkadot only
-   Our rolling 7 day average at the end of this period was over 157 million responses each day.
-   Westend had almost 167 million API responses in the period
-   Statemint had over 172 million API responses in the period
-   All time totals for Polkadot is 86,820,238,239 (86 Billion) since November, 2020
-   At the end of this period the 90 day uptime for Polkadot, Statemint, and Westend was 99.94%, 99.99%, and 99.67%

## Enhancements

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

-   [API Insights](https://blog.onfinality.io/onfinality-introduces-api-insights-so-you-can-analyse-and-learn-about-your-applications-faster/) so you can analyse and learn about your API applications faster and find bugs with your dApp
-   [Cost optimisations](https://blog.onfinality.io/go-further-with-more-affordable-pricing/) to reduce pricing for our customers by up to 40%
-   [New API plans](https://blog.onfinality.io/get-ahead-with-onfinalitys-new-api-endpoints/) for our high usage customers and a way to allocate resource to [move towards a more sustainable funding model](https://polkadot.polkassembly.io/post/1270)
-   [Support for Alibaba Cloud](https://blog.onfinality.io/onfinality-collaborates-with-alibaba-cloud-to-provide-a-premium-experience-to-web3-builders/) to provide more decentralised cloud hosting options for our customers
-   [Updates to our website](https://blog.onfinality.io/onfinality-announces-a-new-ui-to-help-web3-developers-build-smarter/) to include a new Network marketplace so [you can see what networks are supported](https://onfinality.io/marketplace)
-   Support for new layer 1s - [Avalanche](https://blog.onfinality.io/onfinality-launches-beta-api-support-for-avalanche/) and [Juno](https://blog.onfinality.io/onfinality-launches-api-support-for-jun-c3-b8-network/) (in Cosmos)
-   A variety of improvements to our health metric collection tools and automated recovery scripts to ensure our 99.9% SLA is exceeded.
-   Scale improvements to our team, processes, and systems to allow us to provide this same service to any  substrate team

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

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

OnFinality High Performance Public Infrastructure (Q3 2022)

**Summary of Fix for Referendum 74**

- Fixes a previous failed execution of Referendum 74.
- Uses a batch of `Transact` instructions instead of a single `batch` call.
- Adds a sixth pair with ParaId 2030 (Bifrost) to the original five requests.
- Includes a `force_transfer` of 22 DOT: 20 for the new parachain and 2 for XCM fees.
- Requests fast tracking if it passes the Council.

Statemint HRMP Channel Establishment

<<Should Reject>> Establish Statemint HRMP Channels

- The Treasury Proposal is about continuing a support contract from July 1, 2022, to September 30, 2022.
- Polkascan Foundation helps maintain tools for the Polkadot Ecosystem.
- These tools are Python libraries funded by Web3 Foundation.
- Many projects use these libraries in the Polkadot ecosystem.
- There are activity reports from previous months and quarters available online.
- The foundation invites questions from the Polkadot Council.

Term: 1 July 2022 - 30 September 2022

This Treasury Proposal is an extension of our current maintenance & support contract with the Polkadot Ecosystem. The extension of the maintenance & support contract covers term: 1 July 2022 until 30 September 2022.

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

[Polkascan Foundation](https://polkascan.org) is a not-for-profit infrastructure service provider and maintainer of Polkadot Ecosystem Python Libraries. The Python libraries were initially funded by Web3 Foundation grants, they have a generalized nature, suitable for adoption by any Python-based project in the broader Polkadot ecosystem.  Here is [an overview of projects](https://github.com/polkascan/py-substrate-interface/network/dependents?package_id=UGFja2FnZS04OTc2NTczNTM%3D) depending on our libraries.


Previous activity reports can be found here:

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

Links and further details:

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

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

Continuation of Maintenance & Support for Python Libraries

- Sequester is a special tool for Polkadot chains to use transaction fees to buy carbon-backed assets.
- This helps make every transaction on Polkadot good for the environment, or "carbon negative."
- Sequester will gather fees, trade them for eco-friendly tokens, and retire carbon offsets quickly.
- Bitgreen is a partner helping with carbon credits in a sustainable way.
- The project will be tested with other teams like Acala and will also be featured in a White Paper.
- It is funded by a grant to create a chain that changes tokens into eco-friendly assets.
- The team will share more information through documents and videos.

Hi all!

Sequester is a toolkit that will allow any chain in the Polkadot ecosystem to easily use their transaction fees to buy carbon-backed assets and retire associated carbon credits in less than 1 day of development time.

Since Polkadot-based chains are fee-optional, transaction fees currently being used as an anti-spam mechanism can be leveraged to make every transaction on Polkadot carbon negative, without requiring any changes to the user experience. We propose a common good parathread on Polkadot, named Sequester, that provides the functionality of aggregating transaction fees, exchanging them into carbon-backed tokens, and retiring underlying carbon offsets that meet the community’s specifications.

The Bitgreen team will be our initial ecosystem partner and will be responsible for bridging Carbon Credits on-chain in a sustainable manner. As Sequester is Common Good functionality, it is important to note that it will be fully un-opinionated about where funds donated through the Sequester chain go. Specifically, once additional ESG tokens are onboarded to Sequester, teams will be able to configure the allocation of their funds with a single XCM to the Sequester Common Good chain.

We completed our first W3F grant earlier this summer and have joined the Substrate Builders Program. The development in this grant will fund our 1st SBP Milestone. For more context on our work, check out our White Paper and Polkadot Decoded Announcement with Bitgreen.

This grant will fund the creation of a common good chain that receives tokens from other chains' treasuries, swaps them via a DEX into carbon backed assets, and retires the underlying assets on chain. This will be tested on Rococo, with our partners from W3F, Acala, and Bitgreen.

Please see our [Treasury Proposal Document](https://docs.google.com/document/d/1hfmXwe6Gli92YKr5J6BCffGWU9EmKUF-FkSbLs2w-OQ/edit#) for details.

Other Information:

Price Calculation: 100,000 / 6.166 (7-day EMA) = 16,218

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

[AMA w/ Bill Laboon](https://twitter.com/BillLaboon/status/1578354625207758850)

[https://www.youtube.com/watch?v=1-aGKz0I9zY](https://www.youtube.com/watch?v=1-aGKz0I9zY)

Thanks, The Sequester Team (Brendan, Ethan, and Daniel)

Sequester Common Good Chain - Milestone 1

- A new proposal wants to add a special group called a "common good parachain" to Polkadot, which will help collectives.
- The first group will probably be called the Polkadot Alliance.
- This parachain will help other groups in the Polkadot network too.
- There won't be a similar group for Kusama, but Kusama may join some collectives.
- There will be votes to approve the creation and use of the parachain.
- The first steps include registering the parachain and allowing it to start working.
- More details will come when the official plans are released.

As outlined in a [recent blog post](https://polkadot.network/blog/proposal-for-common-good-parachains/), this discussion is about a proposal to add a new common good parachain to Polkadot focused on collectives. The first collective to form will likely be the [Polkadot Alliance](https://docs.google.com/document/d/1aXlVDDQj6v8kOTvbMXBmenBZ3Sfn5zZf0ipQbYvdipo/edit#), but this parachain will also support other collectives that are in service of the Polkadot network.

There are no plans for a Kusama counterpart to the Polkadot Collectives parachain. In fact, the Kusama network itself may join several collectives to exercise its voice within the Polkadot ecosystem. For example, the Kusama network could join the Polkadot Alliance to set the standards for Polkadot brand use.

Other collectives do not warrant two distinct groups, like the [Technical Fellowship](https://forum.polkadot.network/t/calling-polkadot-core-developers/506). This group of technical experts who have made core protocol contributions to the network, would have nearly identical member sets, as the developers most intimatly familiar with Polkadot's inner workings deploy most of their code on Kusama as a step toward Polkadot.

I intend to submit this proposal to the Council to register and onboard the Collectives parachain with a four-year lease, and posting here first to open discussion.

The full launch will include a series of referenda on Polkadot for approval by the entire stakeholder body. These will be roughly as follows:

1. This proposal, to register the parachain and set the lease period. Once on board, it should start producing blocks. However, since it is not a trusted teleporter from the Relay Chain's point of view, nobody will be able to transact on it as there won't be any DOT with which to pay fees.
1. Runtime upgrade to the Relay Chain to include Collectives as a trusted teleporter.

Finally, I would expect a referendum to initiate the Alliance, which could come before or after the Relay Chain's recognition of the parachain as a teleporter. However, this is outside the scope of this discussion; I expect the Alliance founders to propose how they would like to launch.

The call details will be finalized when Parity publishes the [Collectives genesis release](https://github.com/paritytech/cumulus/releases/tag/parachains-collectives-v9290) and the Technical Committee indicates a rough enactment timeframe, which is needed to set the first period of the lease. The call will be a batch with `registrar.force_register` and `slots.force_lease` and the appropriate parameters.

--------

EDIT: Including call info.

Call hash: `0x9ef867bcaaee9750487738c6e6537eb52a3047c7bb2f06eb30dc05073dae90d5`

For some reason Polkassembly won't allow me to add the entire Polkadot JS link for the call (guessing it is too large), but it is as follows:

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

Polkadot Collectives Common Good Parachain Proposal

- The proposal is about getting more money to keep working on important computer services for Polkadot.
- The goal is to keep running the Polkadot, Statemint, and Westend services on special computers in Sweden.
- In the third quarter of 2022, Polkadot handled 2,690,000 requests every day.
- Statemint managed 74,300 requests daily, while Westend had 43,700 requests on average each day.
- They also started using a new Polkadot computer that has been tested and is helping the community.
- There is a full proposal that can be read for more details.

This is a follow-up proposal on what we submitted in the beginning of [July](https://polkadot.polkassembly.io/motion/230), 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 Q3 2022 our Polkadot RPC node served on average **2,690,000** requests per day, and in total we served **250,200,000** requests.

During Q3 2022 our Statemint RPC node served on average **74,300** requests per day, and in total we served **6,687,000** requests.

During Q2 2022 our Westend RPC node served on average **43,700** requests per day, and in total we served **5,370,000** requests.

Since our last proposal we have launched a Polkadot boot node. The node has been tested, [added to the Polkadot binary](https://github.com/paritytech/polkadot/pull/5772/commits/0dbbe81851faa6b7f6bf8948bcea93f8a418dcc0) and is being used by the community.

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

 Polkadot RPC services Dwellir Q4 2022

- Polkadot will represent itself at the Web Summit this year.
- They want money from the Treasury to help pay for some of the costs.
- Other costs will be covered by companies that are joining.
- The event has over 70,000 attendees and big tech companies.
- Polkadot aims to promote web3 and get more people interested.
- Their goals include attracting investors and building a strong community.
- They are inviting more projects to join them in this effort.

Hello, community!

**The discussion with 96% ayes: [https://polkadot.polkassembly.io/post/1295](https://polkadot.polkassembly.io/post/1295)**

We are going to represent Polkadot on the Web Summit this year. We want to get Treasury funding to partially cover direct Web Summit costs. All other costs will be covered by participating companies.

We find it crucial to participate in conferences with key web2 players and 70,000+ attendees, as well as teams from the biggest tech companies, to promote the mass adoption of web3 and generate buzz around the Polkadot.

For Polkadot, Web Summit is a major opportunity to:
- attract attention to the web3 in general and, most importantly, Polkadot blockchain in particular;
- showcase the power of decentralized technologies;
- make a huge step to the mass adoption of web3;
- open up new possibilities of successful partnerships for Polkadot community members;
- appeal to potential investors;
- expand loyal and engaged Polkadot community.

It is crucial to start working outside of web3 bubble for web3 to become simply Web. Just the mere presence of Polkadot at such a conference sends a strong signal to web3 and the web community.

Full proposal with all calculations/details - [https://docs.google.com/document/d/1L9R-34OhkCzbWx_QxaDa-NcMquMUcEpw1rXHjZnCaZg/edit?usp=sharing](https://docs.google.com/document/d/1L9R-34OhkCzbWx_QxaDa-NcMquMUcEpw1rXHjZnCaZg/edit?usp=sharing)

The booth is in active development and is almost done (design is attached in the proposal).

We want to attract more Parachains and projects to this initiative! We need your support to showcase the power of decentralized technologies outside the web3 world together. 

We believe that even in these strict timelines, we can worthy present Polkadot at the biggest Web conference and bring mass adoption.

Treasury Proposal: Polkadot on WebSummit

- A group is working on a grant application for a conference.
- The conference was very successful and exceeded expectations.
- People learned about cryptocurrencies, especially Polkadot.
- The event helped connect communities in the Czech Republic.
- A link to the updated grant application is provided for review.

Hello, we would like to complete [our grant application](https://polkadot.polkassembly.io/post/1049#5de91eb5-1256-41ee-91b0-a7ec4eec809d) that we started before the actual event took place. The conference was a great success beyond our expectations! We educated the wider public about cryptocurrencies, Polkadot being among the most mentioned ones, and did connect Czech communities together. The [newly updated grant application](https://docs.google.com/document/d/1QVUaw6EgLqvkQMDE4HOh5X7U2sKNn1Z1ObS1yBV3DIM/edit?usp=sharing) can be found here: https://docs.google.com/document/d/1QVUaw6EgLqvkQMDE4HOh5X7U2sKNn1Z1ObS1yBV3DIM/edit?usp=sharing

UTXO.22

- Nicholas Hong and the StackUp team proposed a project in October 2022 to continue their Learn-and-Earn campaign for the Polkadot Hackathon.
- They requested $30,000 USD, which is about 4699 DOT, to complete phase 1 of the project.
- The campaign aims to teach 150 developers how to create projects on the Polkadot platform.
- StackUp offers rewards to learners for completing small tasks, called quests.
- They successfully finished the first part of the campaign and produced a report showing the results.
- After receiving $50,000 USD earlier, they now want the remaining funds to finish their project.
- StackUp plans to keep helping developers learn about Polkadot in the future.

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

**Date:** October 2022

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

Requested Allocation Through This Submission: 4699 DOT after conversion from $30,000 USD 
- (covers second payment milestone - phase 1 of this project - please see full proposal for more details - proposal link at the end of this post)
- DOT amount calculated via EMA7 on 07 OCT 2022 at GMT+8 1700hrs - 1 DOT ~ 6.383 USD. $30k USD ~ 4699 DOT

**Short description:**

On Mar 2022, with the proposal of [Proposal #97](https://polkadot.polkassembly.io/treasury/97), which resulted in the passing of [Motion #169](https://polkadot.polkassembly.io/motion/169), the StackUp Team embarked on delivering the Learn-and-Earn campaign for the Polkadot Hackathon Global Series 2022, targeting the onboarding of 150 developers onto the Polkadot ecosystem by educating them about the fundamentals of developing on Polkadot. 

The Learn-and-Earn campaign was conducted through the 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.

Upon project commencement, $50k USD of the original $80k USD was sought and obtained as the initial allocation.  Having completed the learn-and-earn campaign, we are pleased to announce the successful results, which can be viewed here: [Program Report](https://docs.google.com/document/d/1pcgDw0I3AXF7YDP6dFttETC6OgaGKAnouURdfwSRyAc/edit?usp=sharing)

Given the successful execution of the project, this proposal submission seeks to acquire the remaining portion of the allocation of $30k USD, marking the conclusion to this project. After which, the StackUp team will continue to find new opportunities to educate more developers about Polkadot and the various projects in the ecosystem.

**Key Links and References can be found in the links below:**

- Detailed Proposal for the Learn-and-Earn Campaign: [Link](https://docs.google.com/document/d/1NxH0-hxjttIXOxWgS0yURCpj2u2kJTCdT7gbFISqZSI/edit?usp=sharing)
- Polkassembly - First Treasury Proposal for the request for first Allocation: [Link](https://polkadot.polkassembly.io/treasury/97)
- Link to Motion: [Link](https://polkadot.polkassembly.io/motion/169)
- Link to Program Report: [Link](https://docs.google.com/document/d/1pcgDw0I3AXF7YDP6dFttETC6OgaGKAnouURdfwSRyAc/edit?usp=sharing)
- Link to Discussion Post for Second Allocation: [Link](https://polkadot.polkassembly.io/post/1288)

Request for Second Allocation: Learn-and-Earn for Polkadot Hackathon Global Series 2022

- Tether has registered a new token called USDT on Polkadot's Statemint platform.
- They want Polkadot governance to make USDT able to pay transaction fees without needing DOT tokens.
- There are two types of assets on Statemint: Sufficient (which can be used freely) and Non-Sufficient (which need DOT to exist).
- If USDT is approved as Sufficient, users won't have to hold DOT to create accounts.
- This change would help USDT users have more flexibility on Polkadot Network.
- The stablecoin can support various transactions and boost the ecosystem, especially for decentralized finance (DeFi).
- Tether and Polkadot both announced this proposal through their official channels.

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

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

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

**Call on Statemint**

- Encoded call: `0x3212011f00d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d282b92a000100`

- Call hash: `0x842d8a934c2aa86a909e0232f730d2f974bfc01e307703a07eefbad6efdb9e1d`

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

**Call on Relay Chain**

- Call hash: `0x5eea32679cdac9fc69d2d1ff7740104ec2bb6d412cb121505dbece9d34a239fd`

- Call data: `0x630001000100a10f0204060202286bee39023212011f00d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d282b92a000100`

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



Proposal for USDT Token Sufficiency on Statemint

- The Gossamer Development Grant is a proposal to help ChainSafe Systems improve its software called Gossamer, which works with the Polkadot blockchain.
- ChainSafe, a company started in Toronto in 2017, has a team of around 100 people and focuses on building technology for various blockchain systems.
- They want $1,998,117.60 to continue Gossamer's development for another year and make it better for users.
- Gossamer helps create blockchain nodes that can connect and communicate with networks like Polkadot and Kusama.
- The proposal includes goals like creating a full-node client, improving how transactions are managed, and supporting new programming languages.
- They plan to hire more engineers and enhance Gossamer's performance to make it more appealing to the community.
- The Web3 Foundation will assist in checking the work done by ChainSafe.

Previous discussion: <https://polkadot.polkassembly.io/post/1260>

---

- **Treasury Proposal:** Gossamer Ongoing Development Grant
- **Proponent:** AFRI, `1dvvq2sZg55LfLqFmegU493oUaPWxJfjiYysP1eyovkX6hP` (`1413`)
- **Beneficiary:** CHAINSAFE, `14gaKBxYkbBh2SKGtRDdhuhtyGAs5XLh55bE5x4cDi5CmL75`
- **Date:** 09.09.2022
- **Requested amount:** USD 1,998,117.60 in DOT on the day of submission using EMA30 rate by Subscan _(Oct 1st, 2022: EMA30 6.815 USD/DOT)_
- **Scope:** Software development / Protocol 

**Short description:** Gossamer is a Polkadot host written in Go: a framework to build and run nodes for different blockchain protocols compatible with the Polkadot ecosystem, mainly but not limited to the Polkadot and Kusama relay chains. This proposal addresses the Polkadot treasury to consider a grant for the ongoing development by ChainSafe's Gossamer team for another 12 months after the successful collaboration with the Web3 Foundation Grants Program on the initial steps of this development. 

---

**Context:** ChainSafe Systems [0], founded in 2017 in Toronto, is a Canadian blockchain development studio with more than 100 employees worldwide. Our vision is to move the various blockchain ecosystems closer, building bridges and increasing client diversity by providing alternative protocol implementations. With a strong emphasis on protocol engineering, we have been engaged by various clients and foundations, among others, in the Ethereum, Polkadot, COSMOS, and Filecoin ecosystems.

Initially funded through a Web3 Foundation grant [1], our protocol team started implementing a Go-Lang Polkadot host in January 2019. Ever since three years and 1300 merged pull requests later, the client has seen more than 40 contributors. As a result, a Gossamer node today can act as an alternative full node for chains such as Polkadot or Kusama. However, it is not yet feature complete. A treasury allocation should cover the pending developments with approval from the community. We want to continue developing and maintaining Gossamer to extend its capabilities further to grow and stabilize the Polkadot ecosystem with an alternative client implementation that is actively used by the community.

The current team consists of seven full-time protocol engineers and a dedicated project manager. The source code is available on GitHub [2] under the terms of an LGPL v3.0 license.

While the Web3 Foundation has entirely covered funding for the development in the past, this will be our first treasury proposal. Hopefully, this will secure our future operations, allow us to scale the team, and continue to broaden our scope while fostering our presence in the Polkadot ecosystem.

**Problem Statement:** The Substrate blockchain framework enables developers to quickly assemble blockchains for many different use cases. However, it is locking the ecosystem down onto a single programming language, Rust, competing for resources in areas where collaboration is desired.

Offering alternative frameworks in other programming languages should be a high-valued goal of the Polkadot community **as it opens up the ecosystem to a larger pool of engineers**. Thus far, Gossamer is not yet a generalized framework for building blockchains in Go; however, this will always be our central mission for the project.

**Objective:** The overall goal is for Gossamer to provide the functionality needed to bring true client diversity to the Polkadot ecosystem. This entails, but is not limited to:
- A **full-node client** capable of peering, synchronizing and seeding the most prominent relay chains and parachains of the Polkadot ecosystems.
- **Block-production and finality** capability for relay chains and parachains (validators, collators).
- **API services** to allow sharing chain and node states through standardized interfaces.
- **Runtimes** generated in alternative programming languages such as Go.

The primary focus of Gossamer development has been implementing the protocols of the Polkadot host, the client architecture that hosts the Wasm runtime of a Polkadot-like relay chain. The first milestone on the Gossamer roadmap is to allow members of the Polkadot community to stake cryptocurrency behind a Gossamer block-authoring node on the Polkadot Network.

**Deliverables:** The objectives of this proposal can be broken down into the following milestones in no particular order.
- **Validator specification:** Gossamer currently runs in single-node development environments or in sync with other Gossamer nodes or older Substrate versions. A desirable goal for the next year would be **implementing the latest validator specification**, which breaks down into three major components.
  - Transaction queue: Gossamer must be able to receive user-submitted extrinsics [3] and deliver them to the network. Furthermore, Gossamer must implement the transaction queue logic [4] to handle user-submitted transactions efficiently.
  - Block production: Gossamer must be able to author blocks using the latest BABE block production protocol [5].
  - Block finality: Gossamer must be able to participate in the latest GRANDPA block finalization protocol [6].
- **Sync modes:** Gossamer can currently conduct a full bootstrap synchronization to the tip of the chain. This means that the node can use the chain specification [7] of a Polkadot-like network to connect to that network and to import and verify the blocks that make up the network's canonical chain; these blocks will be stored in Gossamer's key-value database. A desirable goal for next year's development would be to **update BABE and GRANDPA implementations to the latest specification and provide alternative synchronization modes**. 
  - State Integrity: Gossamer must implement Polkadot's Patricia-Merkle trie [8] and use it to generate proofs correctly.
  - Fork Choice: Gossamer must tip-sync with a Polkadot-like network, which implies tracking multiple candidate forks at the head of the chain and following the best according to the specification.
  - Warp Sync: Besides providing a full-synchronization service, it would be desirable to provide other modes such as warp sync.
  - DB Imports: A Gossamer node should be able to bootstrap with a database snapshot at a given block height.
- **RPC APIs:** Gossamer must implement the same WebSocket JSON-RPC APIs as the Substrate Polkadot implementation (PSP-6, [9]); this means that the Polkadot-JS API [a] should be able to **work seamlessly with a Gossamer host**.
- **Telemetry:** A Gossamer client should be able to natively connect to any Polkadot Telemetry Service [b] to announce its presence. These Go-hosts should be identifiable by the Telemetry UI reporting the existence of alternative clients.
- **Performance:** To make the client attractive, it's crucial to adjust the reality to the user's performance expectations concerning CPU usage, memory usage, and synchronization time. Metrics can be comparable with Parity's implementation.

The focus for the next development cycle is **matching the latest specification to be able to bootstrap a full Polkadot node and participate in consensus**, e.g., on a public testnet such as Westend. Success metrics can be defined by passing the respective test suites provided by the Web3 Foundation; the organization will partner on this proposal as technical advisor and deliverables auditor to ensure the completed milestones are technically sound. If unavailable, an additional deliverable could entail providing test suites for the respective deliverable above.

Please note that funds are requested from the community treasury. The Web3 Foundation technical team has no control over these funds and will not be rewarded as a reviewer of the milestones. The team will serve the sole purpose of evaluating deliverables in alignment with the community approval of this proposal. This role is based on their past participation in this project. It is expected for the ChainSafe team to publish deliverable reports after the Web3 Foundation's technical evaluation and before continuing with subsequent milestones.

**Payment Conditions**: The requested amount for a 12-months ongoing development grant is USD 1,998,117.60 in DOT on the day of submission using the EMA30 rate by Subscan [c]. The allocation is asked for as a single, up-front payment to cover our ongoing development costs and for the team to be able to provide a runway to their developer resources.

The following resource table outlines the expected costs for the Gossamer team. The table consists of:
- the current base cost to operate the team,
- an 18% operational overhead to cover the costs of running the project as a team within ChainSafe Systems (e.g., operations, offices, equipment, tooling, infrastructure, legal, travel),
- the potential to grow the team sustainability by another two engineers over the course of the following year,
- as well as a 3% margin to protect against market volatility of the underlying DOT assets.

```
             | E2*    | E3*    | E4*    | TPM*   | Base Cost        | Cost +18% overhead |
| ---------- | ------ | ------ | ------ | ------ | ---------------- | ------------------ |
| Month 0    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 1    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 2    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 3    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 4    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 5    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 6    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 7    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 8    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 9    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 10   | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 11   | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| ---------- | ------ | ------ | ------ | ------ | ---------------- | ------------------ |
| USD Sum    |        |        |        |        | USD 1,644,000.00 | USD   1,939,920.00 |
| +3% margin |        |        |        |        |                  | USD      58,197.60 |
| ---------- | ------ | ------ | ------ | ------ | ---------------- | ------------------ |
| USD Total  |        |        |        |        |                  | USD   1,998,117.60 |
                                                                     ====================
```

_[*] Abbreviations: E2 - Engineer II (Mid-level Engineer), E3 - Engineer III (Senior Engineer), E4 - Engineer IV (Technical Lead), TPM - Technical Project Manager, FTE - Full-Time Employee_

The beneficiary of this proposal is ChainSafe Systems Inc, Toronto, Canada. The on-chain address is `14gaKBxYkbBh2SKGtRDdhuhtyGAs5XLh55bE5x4cDi5CmL75`. The funds' manager is Hatcher Lipton, COO at ChainSafe Systems, reachable through <hatcher@chainsafe.io> for any questions regarding the payment conditions.

For any questions about the technical nature of this proposal, you can message me, Afri Schoedon, Head of Protocol Engineering at ChainSafe Systems, at <afri@chainsafe.io>, or Dan Forbes, Technical Project Manager for the Gossamer team, at <dan.forbes@chainsafe.io>.

References:
- [0] <https://chainsafe.io/>
- [1] <https://github.com/w3f/Grants-Program/blob/master/docs/accepted_grant_applications.md>
- [2] <https://github.com/ChainSafe/gossamer>
- [3] <https://spec.polkadot.network/#_extrinsics>
- [4] <https://spec.polkadot.network/#sect-runtime-txqueue-module>
- [5] <https://spec.polkadot.network/#sect-block-production>
- [6] <https://spec.polkadot.network/#sect-finality>
- [7] <https://github.com/paritytech/polkadot/tree/master/node/service/chain-specs>
- [8] <https://spec.polkadot.network/#chap-state-spec>
- [9] <https://github.com/w3f/PSPs/blob/master/PSPs/drafts/psp-6.md>
- [a] <https://github.com/polkadot-js/api>
- [b] <https://telemetry.polkadot.io/>
- [c] <https://polkadot.subscan.io/tools/charts?type=price>


Gossamer Ongoing Development Grant

- The proposal plans to update Polkadot's and Statemint's systems to new versions, v9291 and v9290.
- It includes several improvements and fixes for Polkadot, like making some types public and fixing rewards.
- Statemint will also get updates to help with performance and prepare for new features.
- The proposal is submitted for review and must be approved by the Council and then voted on by the community.
- There are specific tasks listed in the proposal, which have different priority levels (low, medium).
- Users can vote on the proposal when it’s time.

This proposal aims to upgrade both Polkadot’s and Statemint’s runtimes to [v9291](https://github.com/paritytech/polkadot/releases/tag/v0.9.29) and [v9290](https://github.com/paritytech/cumulus/releases/tag/parachains-v9290) respectively. For this, the proposal includes a batch call including both runtime upgrade proposals. 

### On Polkadot

This upgrade fixes issues and includes:

**Runtime**

⏳ pending non-critical audit #11813 Low - Proposal: flatten allpallets and similar types

✅ trivial #12032 Low - Contracts: make chain extension state types public

✅ trivial #11670 Low - Replace t::accountid with <t::lookup as staticlookup>::source

✅ trivial #12059 Low - Revert "auto-incremental collectionid"

✅ trivial #12095 ❗️ Medium - Fix nomination pools pending rewards rpc

#12138 Low - Weight v1.5: opaque struct

✅ audited #12145 Low - Uniques: reset approved account after transfer

✅ trivial #12136 Low - Emit events for inter contract calls

✅ audited #12154 Low - [fix] make sure pool metadata is removed on pool dissolve

Proposal hash: `0x8fe3a4b4214f090c01c1da47882c41eb08e0544d379c7e1959dcdc4810e12c50`

### On Statemint: 

[C] #1454 Low - [feature] add xcm benchmark weights to statemint

[C] #1551 Low - Update cumulus to latest substrate and polkadot master

Among other things, it includes an update to the XCM weight calculations and prepares for the first Collectives parachain.

- Proposal hash: `0x076ee423671cc95bd1eb19675009154d4e6b817554d755e6627c6138094a924b` 

- Authorize Upgrade call: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x01025256522299bfb951fa5726858cbe87df3ad0794352087430a23727849d3ebc20)

![](https://i.ibb.co/C1T25Wd/Screenshot-2022-10-06-at-16-28-02.png)

Please note this is submitted as an external motion: meaning if/after Council approves, this will also be up for vote by the community to decide on the upgrades. 

### Complete batch call:

![](https://i.ibb.co/vmKqGxG/Screenshot-2022-10-06-at-18-01-57.png)

Proposal hash: `0xbc2cb73740d701dac3fa5f31b7b23e552d6160ccd40d95746e91c131c699523d`

Make sure to vote at your convenience!


Runtime Upgrade v9291 on Polkadot + v9290 on Statemint

- This proposal is from three teams in Polkadot: Bitgreen, Sequester, and Evercity.
- They want to measure the carbon footprint of the Polkadot and Kusama networks.
- The goal is to offset emissions using carbon credits from their own ecosystem.
- The proposal includes creating a dashboard to show electricity use and emissions for each parachain.
- Some parachain teams, like Acala and Astar, support this project and want to help.
- The project will be completed by November and will start in early 2023.
- The information will be available for everyone to see and use.

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

Hello everyone,

This proposal is submitted by three Polkadot teams: Bitgreen, Sequester, and Evercity, detailing a common good collaboration to measure and report the collective carbon footprint of the entire Polkadot and Kusama networks, and offset their emissions with carbon credits from within the Dotsama ecosystem. It builds on the pre-existing W3F grant issued to Sequester to develop a pallet to translate parachain treasury funds into tokenized carbon credits. The following proposal resolves a prerequisite to determine a methodology, set of measurement parameters and reporting standard to measure the electricity consumption and approximate emissions of each participating parachain with real-time periodicity and verifiable accuracy. The final deliverable will be an open-sourced dashboard and the launch of the treasury-to-carbon credits pallet. Several parachain teams have committed to backing referendum on their local chains to adopt this functionality, and are excited to integrate it pending governance approval including Acala, Astar, Interlay, Bifrost and Kilt.

The Dashboard and initial audit are scheduled to be finished by sub0 in November with the Sequester and Bitgreen parachain colaboration early Q1 2023.

Please see the document for details: 
[https://docs.google.com/document/d/19mGYD10uWB8SXwJeqdgRe8o5VayaVYnnVvPkm_TtjPw](url)

Adam & Dennis CEO and CTO, Bitgreen

Council Motions