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

System.setCode hash: `0x5f48aacbbd94a881a3ce5a496e1d852f21cffe33d1f7592023f2140254683d20`

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

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

**Runtime**

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

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

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

**Misc**

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

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

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

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

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

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

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


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

Make sure to vote at your convenience!

proposal

Runtime Release v9360 for Polkadot

**Proponent:** 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf

**Date:**  25th January 2023

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

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

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

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

* * * * *

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

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

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

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

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

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

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

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

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

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

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

-   Served a total of 6.7 billion responses

-   Accumulated over 79.6 TB of data egress 

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

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

-   Westend had over 175 million API responses in the period

-   Statemint had over 160 million API responses in the period

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

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

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

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

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

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

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

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

-   Support for more Polkadot parachains

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

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

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

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

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


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

proposalId

High Performance Public Infrastructure (Q4 2022)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Snowbridge Funding Proposal

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

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

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

Proposal hash: `0xad5bd919076c71a6acba8ffafe12dfaf8ef83e40d69a56ee1ae1d5ffaa9f429e`

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


Approval of Wasm Smart Contracts Bounty - bounty 19

## Polkadot EVM Smart platform
- The EVM smart contract parachain PSC developed by the ChainX team uses DOT as the original Gas fee. 
- PSC will be integrated into the Omnichain financial platform OmniBTC to help us achieve PolkaDot's mission of universal chain interconnection.

## For a detailed description please refer to this:
https://github.com/OmniBTC/PSC/issues/1

Launch PSC Parachain - public proposal #21

For a detailed description please refer to this: [https://hackmd.io/@t9B1coeOQ1GlARb2EZRx3g/Hy0mnACdo](url)

The bitgreen parachain was upgraded from a shell runtime to our latest runtime code at block 191202.

The upgrade executed without issues and the parachain continued to produce blocks. The upgraded parachain runtime introduced a couple of new pallets, the pallet-parachain-staking among them. This new pallet was responsible to assign new validators to session pallet and by extension the aura pallet. After the runtime upgrade, when a new session was triggered, it set the new authorities to an empty set since the pallet-parachain-staking was not set with any initial values.

We have explored all other solutions and after discussion and advice from Parity devs have created this proposal. Our humble request to the TC is to fastrack this proposal, this is purely a technical rollback since our chain has no user transactions or funds yet. We would like to distribute token rewards as soon as possible. Similar parachain resetshave been fastracked by the TC in the past and we request that our proposal be fastracked aswell.

Unbrick Bitgreen Parachain

Untitled - public proposal #17

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

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

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

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

Setting pvfCheckingEnabled In The Configuration To TRUE

The Bittensor project participated in Auction #36, however it was unfortunately using the incorrect para ID in its genesis WASM (para ID 2096) due to previously obtaining para ID 2096. 

We have explored all solutions to this problem and it appears that there is no way to have the chain produce blocks when its lease begins unless we update the genesis head. Therefore, we've created this proposal to update the genesis head from 2096 to 2097 using forceSetCurrentHead.

Proposal hash: 0x457da305f86a09bad84a8c557bb89628b9b39707819df0b12458d84a255d6354
Preimage is submitted.

Update genesis state WASM to 2097 

proposalHash

votingPeriod

delay

[Here](https://polkadot.polkassembly.io/post/1491) is the previous community discussion on Polkassembly. 

### TLDR;
The purpose of this bounty is to nurture and develop WebAssembly smart contracts on parachains. As Gavin mentioned in this [CoinDesk article](https://www.coindesk.com/tech/2021/05/25/polkadots-gavin-wood-webassembly-is-the-future-of-smart-contracts-but-legacy-evm-is-right-now/), WebAssembly is the future of smart contracts. However, even in the Polkadot ecosystem, EVM smart contract is the go-to-market solution now simply because lack of ecosystem toolings and dApps new developers can refer to. To bootstrap the Wasm dApps in the ecosystem, we will fund canary dApps and toolings through this bounty.

### Context of This Bounty
Please see [this post](https://forum.polkadot.network/t/we-need-to-make-ink-showcase-projects/592) first. Currently, based on the data, smart contract Parachains are leading the Polkadot ecosystem in terms of market adoption. More projects are deploying dApps on Polkadot Parachains than making Parachains today and this trend will likely continue due to the high resource requirement to deploy a chain. The core problem is that the Polkadot ecosystem only supports EVM at the time of writing this and we are reproducing something which other L1s/L2s can do. One of Polkadot’s main differentiators and default environments is Wasm. In this bounty, we would like to push Wasm smart contracts adoption. The scope is as follows:

- Create easily accessible and audited ink!/ask! smart contract showcases
- Create ink!ubator - an incubation program to support community projects built with ink! and parachains that want to expose select APIs through contracts-pallet “chain extensions”. We will also help facilitate a smart contract auditing market.
- Develop a React hooks library “useInk” - the missing front-end library for Dapps on Polkadot.

### Bounty Proposal
[Here](https://docs.google.com/document/d/1y2QECPsXQktVGZIat_yNKTlodviTecMZ6IbiLNQ4NLM/edit?usp=sharing) is the full bounty proposal.

### Curators Candidates
**Sam Ruberti from Parity Technologies (Address: 13zqqP37p8HjLuWr7sha9GcAcYiiDgjqoNS3YbSELtgvaAfb):**  Sam Ruberti is a Senior Rust Developer with ink! and has over twelve years of experience delivering full-stack products for companies including Bloomberg, Peloton, and Clear, and five years of experience building full-stack Dapps in production environments. He has built microservices, DeFi platforms, NFTs, and contributed to open-source libraries for Ethereum.

**Sota Watanabe Astar Foundation (Address: 13VyvkXX3dYyeT7oAmaipZYNHzFJXofC5V8eqMuzd1isXY84):** Sota Watanabe is the founder of Astar Network. He joined the web3 space in 2015 and started developing Astar Network in 2019. Apart from his achievements, he is a director of the Japan Blockchain Association and used to be a blockchain researcher at the University of Tokyo and a task force member of Trusted Web led by the Japanese government. In addition to that, he was chosen for Forbes 30 Under 30 Asia in the IT division and Forbes 30 Under 30 Japan.

**Hernando Castano from Parity Technologies (Address: 15FjwNSxHhaJeknJjbydSo561ti1ea8sf3Y1fA263emujzxW):** Hernando is a Core Developer at Parity Technologies. Hernando joined the blockchain space in 2017, initially curious about the world of smart contracts on Ethereum. In 2019, Hernando joined Parity Technologies to work on the Parity Ethereum client, and has since transitioned to the team working on the ink! programming language.

**Markian Ivanichok 727 Ventures (address: 16FVZ2qVefqbr2zcEGVojEQBgx3nb8GqQCdjKiaq2nSs33T8):** Founder & CEO at 727.ventures, Brushfam & Dedali Metaverse. Web3 entrepreneur, Software Engineer. Brushfam onboards businesses to Polkadot WASM. Projects: Openbrush(Openzeppelin of WASM ink!), Typechain for ink!, sol2ink (transpiler from solidity to ink!), and substrate/ink! contribution itself. Also, WASM conference, was the first web3 WASM conference and gathered ~1000 participants.

**Hang Yin from Phala Network (address: 12BZFbrNksTKwHtaBojnVtoN8BoXKmBFzT3xDnHh7P9t2Cg5):** Co-founder and CTO at Phala Network. 5 years of Web3 core development and entrepreneur experience. Author of Phala Network Technical Whitepaper. Lead the team to build an off-chain computing protocol based on ink! and Substrate with 30k online servers. Ex-Googler on Machine Learning before joining Web3.

**Michał Świętek , Development Lead at Aleph Zero (Address: 5H6AVPSNv8GjEFiDKqhtCd6U494vGMm3r5vkzr5614sbfQnx0) :** For a couple of years, Michał has been fully devoted to the Aleph Zero project. From co-designing novel consensus mechanisms, and writing the first lines of code in core repositories, to the high-level architecture of Aleph Zero node implementation.

Wasm Smart Contracts Bounty

Anti-Scam projects rewards pool. Minimum rewards 5% 

Polkadot Meetups in Goma - Abraham Mugisha - Jan.30 -> Sept 31 2022

Polkadot Meetups in Gulu - Brian Ahimbisibwe - Jan.30 - April 3 - June 12 2022

Academy Open Nights - Jose Belossi (Pepe) - Jan 19th, 25th, and Feb 1st, 2023

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

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


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

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

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


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

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

<br />

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

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

YieldBay Proposal Phase 2: Yield Farming Dashboard for Dotsama

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

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

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

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

Substrate Training Course and Certification

1.5 year of moderating | translating key announcements | 24/7 user-support for Korean Polkadot Community as a Head Ambassador: https://t.me/polkadot_korea_official