- The parachains v9360 release has important updates for its system.
- Statemint, a part of the release, has changes in the Assets section that affect how transactions work.
- Wallets need to be updated to match these changes.
- The Collectives Parachain now has a new role called "Fellow."
- The new "Fellow" role combines the old Founder and Fellow roles and takes away veto power.
- Fellows can also choose to step back to a role called Ally.
- More details can be found in the release notes.

proposalHash

The parachains [v9360 release](https://github.com/paritytech/cumulus/releases/tag/parachains-v9360) contains updates that correspond to the v9360 runtimes of the respective Relay Chain. For Statemint, this contains updates to the Assets pallet that breaks transaction version; wallets should update accordingly. For the Collectives Parachain, this merges the Founder/Fellow roles into one “Fellow” role, removes veto power, and allows Fellows to step down to Ally. See the release notes for more details.

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

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

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

Proposal Hash: `0xa730cdb8c4b933b9e9ced277e63e79f0f52c0159f78bf60037f6ba312324051f`


Upgrade Polkadot System Parachains v9360

- Dot.alert() is a guide for keeping assets safe in the Polkadot system.
- They want to get 5,705 DOT, worth about $25,712.
- This funding is for their work in the first part of 2023.
- Dot.alert() has made a deal with the Polkadot Treasury for support in the past.
- They have a plan with specific goals and tasks for their work.
- More details and discussions about their funding request can be found online.

proposalId

**Proponent:** 12uokSRn2hmEWPZuzHK1xqnFxRgyoApLtXRBd4jFan2x2T1P

**Date:** 28.12.2022

**Requested:** 5,705 DOT (i.e USD $25,712 calculated from the 7-day EMA price of DOT)

**Short description:** 

[Dot.alert()](https://dot-alert.gitbook.io/dot.alert/) is a knowledgebase that provides practical guidelines for managing assets safely across the Polkadot ecosystem. As part of its mission, Dot.alert() has previously established a social contract with the Polkadot Treasury to fund its quarterly operational costs. 
Dot.alert() is seeking funding for its Q1 2023 operations, so that it can continue to make progress on the objectives laid out in its annual strategic plan. 

You can find the discussion related to this proposal here: [https://polkadot.polkassembly.io/post/1495](https://polkadot.polkassembly.io/post/1495)

You can find the full details of the proposal (including milestones, tasks, and costs for the period January – March 2023) here: [Polkadot Maintenance Proposal Q1 2023 – Dot.alert()](https://docs.google.com/document/d/1gvu4aNTC5ahP8fhiZzNg8N845C4U2o25/edit?rtpof=true&sd=true).


Treasury proposal: Dot.alert() operational costs - Q1 2023

### Polkadot Treasury Proposal Summary

- **Term**: 1 October 2022 - 31 December 2022
- **Purpose**: Extends the maintenance and support contract for the Polkadot Ecosystem.
- **Organization**: Polkascan Foundation, a non-profit that maintains Python libraries for the Polkadot ecosystem.
- **Impact**: 176 GitHub repositories currently depend on these libraries.
- **Reports**: Detailed activity reports are available for previous months and quarters.
- **Social Contract**: The maintenance and support are governed by a social contract mechanism.
- **Business Plan**: A detailed business plan is available for further reference.
- **Support**: The team is available to answer questions from the Polkadot Council.

Term: 1 October 2022 - 31 December 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 October 2022 until 31 December 2022.

* [Current report that account for maintenance & support contract activities](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q4.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. 

At the time of writing [176 Github repositories](https://github.com/polkascan/py-substrate-interface/network/dependents?package_id=UGFja2FnZS04OTc2NTczNTM%3D) are 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)
* [Quarter 4 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q4.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

- The IBC team submitted a treasury proposal for some important events and programs.
- These include Hackathons, Education, Certification, DeFi competitions, and Start-up Pitch Competitions.
- The goal is to attract new projects and talented people in blockchain to a conference organized by the Indian State Government.
- This is a special call to approve the current proposal and reject a wrongly submitted one.
- More details about the budget and technical information are available in the original proposal link.

calls

Submitted to vote at the request of the team, the treasury proposal by **IBC** for Milestone 2 of Hackathons, Education & Certification programme, Defi competitions and Start-up Pitch Competitions converging into an Indian State Government led the conference with the goal is to raise the bar for attracting prospective projects and bringing in top-line blockchain talent on a common platform. 

Please note that this is a `batch` call approving the current proposal and rejecting the wrongly submitted proposal by the team (200). Full information, along with the budget and technical details, can be found below:

Original Treasury Proposal here: https://polkadot.polkassembly.io/treasury/201


treasury proposal by IBC for Milestone 2

- Open Runtime Module Library (ORML) was created by the Acala team in late 2019.
- ORML helps to solve problems and create useful features for developers.
- It is made to be shared with developers in the Polkadot and Kusama communities.
- By late 2022, many teams started using and contributing to ORML.
- Acala is the biggest contributor to ORML's development and upkeep.
- There is a proposal for payment to support ORML from January to October 2022.
- Community members can review the proposal and ask questions.
- People are encouraged to share how ORML helps their projects.

Open Runtime Module Library, or ORML, originally created by Acala's co-founders in late 2019. It is a collection of modules that Acala team created to solve issues that we encountered, to produce features that we wish existed, at the same time making it not specific to our chain but generic, so we can share them with our fellow developers in the whole Polkadot/Kusama community and help in some way.

Fast forward to late 2022, ORML is widely used by many teams in the ecosystem, and is receiving contributions from different teams. Acala remains the biggest contributor in development and maintenance of ORML.

This proposal (link to doc [here](https://docs.google.com/document/d/1BGvDnc_fHgowSUXE83hhPGsDPBF7cHWMbA4a14k_AyM)) is seeking payment to cover development and maintenance of the widely used Open Runtime Module Library between Jan 2022 and Oct 2022.

Community members, please kindly review the proposal and ask questions you may have, we are happy to address questions before moving onto next step. You are also welcome to share how ORML is useful for your project(s). :)

ORML development and maintenance

- The Bitgreen team upgraded their parachain code to a new version at block 191202.
- The upgrade went well, and the parachain continued working without any problems.
- A new feature called "pallet-parachain-staking" was added during the upgrade.
- This new feature helps assign new validators for the parachain's sessions.
- After the upgrade, there was an issue with setting initial values, leaving the authorities empty.
- The team talked with Parity developers and created a plan to fix this issue.
- They are asking for the proposal to be approved quickly so they can start distributing token rewards.
- Similar proposals have been approved quickly before, and they hope for the same support.

Contextual information from the Bitgreen team, below:

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

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.

Proposal hash: `0xfc0c33d0c0ae08d940fddadb11e239710da69b8660eaae7f77ea102a331e4ebe`

Preimage is submitted. 



Unbrick Bitgreen Parachain

- Nova Wallet is a mobile app for Polkadot and Kusama that helps users with digital currencies.
- The latest proposal aims to improve the app by adding new features like Agile Delegations and better Staking.
- These updates are based on what the community has asked for.
- Nova Wallet supports many networks and allows users to manage their digital assets easily.
- The team plans to share updates every 1 to 4 weeks and have public demos every 2 weeks.
- The app is designed to be user-friendly and secure while being open source.
- Their goal is to keep improving Nova Wallet for everyone who uses it.

**Nova Wallet 3rd Proposal: OpenGov Agile delegations, Staking improvements, Community requested features:**

[https://docs.google.com/document/d/1eG8xNMVGvTbcXBfOWUN-oxEeXW15y0kofpG0AbihU1E](https://docs.google.com/document/d/1eG8xNMVGvTbcXBfOWUN-oxEeXW15y0kofpG0AbihU1E)

\
![](https://i.postimg.cc/WbDtR1Yb/Nova-Wallet-3rd-proposal.png)

**Feature set of the proposal (see [proposal](https://docs.google.com/document/d/1eG8xNMVGvTbcXBfOWUN-oxEeXW15y0kofpG0AbihU1E))**
- OpenGov Agile Delegations
- Staking improvements
- Community-selected features: Based on requests from community
- Reimbursement for delivered Governance features which were outside the scope of the previous grant

\
**Context of the proposal:**
\
[Nova Wallet](https://novawallet.io/) is the leading **mobile app for the Polkadot and Kusama ecosystem**:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🌌 **65+** Polkadot networks

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🔀 **210+** Cross-chain channels

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🥞 **User-friendly staking**: DOT, KSM, GLMR, MOVR, PDEX, AZERO, TUR, CAPS, KMA

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🙋🏼‍♀️ **OpenGov** & **Governance v1** support

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🌐 **DApp browser** with support for the Polkadot JS & MetaMask protocols 

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🖼 Access to RMRK & Statemine **NFTs**

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 📱 **Hardware wallets** support for Parity Signer & Ledger Nano X

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🚀 Polkadot & Kusama **Crowdloans** 

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 💖 Amazing & Intuitive UX/UI

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ✨ Community-focused

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ⚡️ Fast & Feature-rich

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🦾 Secure & Open source

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🙆 **40 000+ active users** on both iOS/Android

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 🎁 **Funded by the Kusama & Moonbeam Treasuries**, working with **110+ teams** in the eco	



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In May 2022, our previous (2nd) Kusama Treasury proposal was [approved](https://kusama.polkassembly.io/motion/485), and now by November 2022 we have successfully delivered upon all the proposed features. Please refer to [Nova Wallet demo #26](https://www.youtube.com/watch?v=TQxR9wrx524) in order to review the features which we have delivered upon.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Our goal** for [Nova Wallet](https://novawallet.io/) is to build and maintain a high quality, open source, community-focused, and feature rich mobile application, which will have no network biases and can function with no limitations/restrictions.


&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Apart from developing the Nova Wallet mobile application, our team is **consistently contributing to the Polkadot ecosystem** by providing open source SDKs, design assets, knowledge-sharing sessions, and infrastructure. Examples include:

- Substrate SDKs for [iOS](https://github.com/nova-wallet/substrate-sdk-ios) and [Android](https://github.com/nova-wallet/substrate-sdk-android) development
- [Nova Utils GitHub](https://github.com/nova-wallet/nova-utils) — metadata & configs for networks, crowdloans, DApps, cross-chain transfers
- SubQuery API projects [developed](https://github.com/nova-wallet/subquery-nova) and [hosted](https://nova-wallet.github.io/subquery-nova/) by Nova Wallet team
- [Nova Assets Figma](https://www.figma.com/community/file/1039874427311142565) — Polkadot eco tokens, networks, DApps
- [Hosted metadata portal](https://nova-wallet.github.io/metadata-portal/#/polkadot) for Polkadot & Kusama ecosystem networks — metadata portal for [Parity Signer](https://www.parity.io/technologies/signer/), ecosystem hardware wallet

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This proposal covers the further development of Nova Wallet as a mobile application for the Polkadot ecosystem, allowing us to** expand upon the already large set of features** contained within Nova Wallet by introducing **Agile Delegations for OpenGov**, improving** Staking features**, and developing **features suggested by the community**.

\
**The intended outcomes from this proposal:**

- Implementation of this proposal’s feature set for the Nova Wallet iOS and Android apps (as described in [The feature set of the proposal](https://docs.google.com/document/d/1eG8xNMVGvTbcXBfOWUN-oxEeXW15y0kofpG0AbihU1E/edit#heading=h.85ev9ft34nr9) section)
- Public demos: **every 2 weeks** (see [YouTube](https://www.youtube.com/@NovaWallet))
- Updates to AppStore / Google Play: **every 1-4 weeks**
- Open source iOS and Android mobile apps under **Apache 2.0 license**
- Open source iOS and Android Substrate SDKs under **Apache 2.0 license**

\
**Please review the full proposal with a detailed description & costs:**
[https://docs.google.com/document/d/1eG8xNMVGvTbcXBfOWUN-oxEeXW15y0kofpG0AbihU1E](https://docs.google.com/document/d/1eG8xNMVGvTbcXBfOWUN-oxEeXW15y0kofpG0AbihU1E)


Nova Wallet 3rd Proposal: OpenGov Agile delegations, Staking improvements, Community requested features

- A proposal is made to upgrade Polkadot to a new version called v9340.
- This upgrade is only about the software used and does not include a new client.
- The new version will replace older versions, v9320 and v9330.
- The Polkadot Council will decide if the proposal can be voted on by the community.
- If the council agrees, the vote will happen on January 14.
- Some important changes will happen after the upgrade, like stopping certain unfinished tasks.
- Any votes that have passed but not started will not go ahead until after the update.

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

- This is a runtime-only release. 
- No node client is released, also this Polkadot runtime replaces runtime v9320 and v9330.

Proposal hash: `0xace5dccb8eecfab754154a27c370a513d79d4fcda40f5837be1c0f129cdf4726`

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. 

Make sure to vote at your convenience!

### IMPORTANT NOTE ON THIS UPGRADE:

Assuming Referendum 96 passes, Polkadot will upgrade to runtime v9340 on Saturday 14 Jan. This will have several effects: **please read below!**

First, any outstanding multisig calls (ones where one signatory has signed, but not the threshold) will not be able to execute. Please either finish your multisig calls before this upgrade, or wait until after it is completed. [https://github.com/paritytech/substrate/pull/12072](https://github.com/paritytech/substrate/pull/12072).

All preimages and the dispatch queue will be cleared. Any Referenda already passed but not enacted will thus not execute. If the Referendum is ongoing, the preimage can be re-uploaded after the upgrade. [https://github.com/paritytech/substrate/pull/11649](https://github.com/paritytech/substrate/pull/11649).

Runtime Release v9340 for Polkadot

This is a motion to upgrade Statemint to v9330. The release notes can be found in the [Cumulus release page](https://github.com/paritytech/cumulus/releases/tag/parachains-v9330). Like the Statemine upgrade, this adds the new asset destruction interface. It also brings in the ability to pay XCM fees using sufficient assets ([PR 1910](https://github.com/paritytech/cumulus/pull/1910)).

Upgrade Statemint to v9330

- **Rust Syndicate** submitted a treasury proposal for **Uptest**.
- Uptest is a tool to help developers test Pallet functionality.
- It aims to make it easier to find needed runtime migrations.
- The proposal is part of a `batch` call, approving one proposal and rejecting another.
- The full proposal, budget, and technical details are available on Polkassembly.
- The original treasury proposal can be found [here](https://polkadot.polkassembly.io/treasury/186).

Treasury Proposal by Rust Syndicate: Uptest funding proposal

- The proposal is for a project called Kampela, which will design a special device for the dotsama ecosystem.
- Kampela looks like a credit card and has an e-paper screen, making it easy to carry and use.
- It is a signing tool, not a wallet, meaning it can't track money or make transactions on its own.
- The device will use a type of secure technology to keep private keys safe.
- Kampela will cost less than €100, which is cheaper than some other similar devices.
- The project aims to make it easier and safer for users to sign transactions using their phones.
- This proposal covers early development work but not the actual making of the device yet.

This is proposal for Milestones 3&4.

DOT/EUR exchange rate calculated as 5.2334 by EMA7 (EMA with 168 period frame) by [Kraken](https://trade.kraken.com/snapshot/ce84vn6l6f69360p0elg-kraken-dot-eur
)

Our team proposes to design an open source hardware storage for dotsama ecosystem.

[Please see complete proposal on Skiff](https://app.skiff.com/docs/6e1d3e9f-9e2c-4413-9190-9c39cda20763#yJcS2WZZbiuFk4Pe3W5nycQ7vcjEbrXkbfcf2EKIiV4=)

Project name is Kampela, Finnish word for flounder fish. The device is envisioned as flat card mostly consisting of e-paper screen and few controls (and it allows keys to stay safely in depth).

Kampela is a hardware version of Parity Signer. It is a small card-shaped device (ideally comparable to a credit card form factor, to be carried in a wallet when needed) that accepts data through unidirectional NFC port and shows output on a monochrome electronic paper screen. It has cryptographic strongbox with elliptic curves supported by Substrate — which only stores private keys (after initial import) and performs all signing operations on-chip.

Kampela is designed to be a comparatively low-cost (below €100, in contrast to €500+ for a Signer-compatible smartphone) single-purpose device, which would only support a single seed phrase per unit, operated via a drastically simplified user interface. However, it would have all the security features of Parity Signer: a full-featured SURI account derivation system, transactions preview, metadata updates, logging.

As something that supports the same QR code output formats as Signer, it would be able to drop-in replace Signer when providing signatures back to a mobile/desktop wallet. The only challenge would be in transforming the current QR-driven input format of Signer into a suitable NFC payload. Alongside with native support in some apps (which would require software modification) this can also be achieved with a tiny “translator” app for a regular (online, not necessary trusted — one’s usual daily driver) mobile phone: it would snap a QR code with the transaction details and (statelessly, without any extra features or complicated UI) transform that into an NFC payload.

Kampela is a natural (and long-discussed) extension of Parity Signer to leverage the most out of modern hardware-based crypto chips and drastically reduce Signer’s attack surface: no mobile OS, not extra platform features, no unexpected communication methods or airplane mode to take care of.

Kampela is not a wallet! It is a signing tool, it is not able to track on-chain balances, validate things over chain-provided information or generate transactions on itself.

The scope of this proposal does not include actual production, but does result in all preliminary development required for production. Hopefully, many assembly shops would rush in to compete with us and each other!

[Project repository](https://github.com/Alzymologist/Kampela) (check out PRs for more recent WIP)

Project matrix room: #Kampela:matrix.zymologia.fi

[This proposal was prevoiusly posted in Discussions](../post/1227)

[Proposal for milestones 1&2](https://polkadot.polkassembly.io/treasury/163)

[Milestone 1 report](https://app.skiff.com/docs/2b25845a-4a00-4bf4-aaff-3de4a70d4ad7#zSepFgAI0EetUe7eIp2Tlgu/RnhMjnAJRDecVUiVmhQ=)

[Milestone 2 report](https://app.skiff.com/docs/5dcbeadc-e5f3-4f29-8476-e8fcb7786585#ZNnc%2FdmSz3dYkUNc%2BI%2BiarGsZKa0W9uUN25ZqCySPAg%3D)

Edit: [Milestone 3 report](https://app.skiff.com/docs/a0583eb2-1b44-46f1-b921-4dc4aa8abf68#QczSiY%2BGxi93PTv%2BFAd%2BPuNnfBqh%2BCpqBIFdooAufCo%3D)

Edit: [Milestone 4 report](https://app.skiff.com/docs/984d9ed1-9271-4457-be04-a6eca0f25f39#JZdHE9gfXVn%2BtkTl7EBOqCsxCfo%2F2FRjO%2FnnOJoJM6I%3D)

Hardware signer and key storage Kampela: Milestones 3&4

- The Polkadot Alliance was created by seven important projects to set rules and protect open-source development.
- The founding members are Acala, Astar, Interlay, Kilt, Moonbeam, Phala, and Subscan.
- The Alliance has two main ranks: "Fellow" and "Ally."
- Their goals include making rules, managing members, and keeping a list of bad actors.
- Membership shows a group's commitment to quality contributions within the Polkadot community.
- Members must follow rules like respecting each other's work and working together against scams.
- If members break the rules, they can be removed by a vote.

The Seeding of the Polkadot Alliance: Fighting for an open source culture and open collaboration that benefits the Polkadot ecosystem

- This proposal is about an open-source toolset for displaying blockchain data.
- The toolset includes three parts: Editor, Parser, and Management Tools.
- Users can create and manage data widgets easily, even without coding skills.
- It supports many data sources like HTTP API and GraphQL.
- The toolset can help make user-friendly data displays for web projects.
- In the future, there will be free online services based on this toolset.
- The total budget for this project is $201,600, which will be converted into DOT.

This proposal aims to provide ecological users with an open-source toolset, which covers all processes of custom data dashboard and is suitable for mainstream front-end frameworks. Users can use it to conveniently generate, configure, and manage data widgets and inject them into any project that needs to display blockchain data.

The toolset contains three parts: **Editor**, **Parser**, and **Management Tools**. The editor is used to generate and configure data widgets. The parser is used to parse and display widgets. Management Tool is used for widgets management. They all follow the [License apache 2.0](https://www.apache.org/licenses/LICENSE-2.0).

We provide it with a wealth of widgets (covering more than 90% of the [Subscan explorer](https://www.subscan.io/) component library) and support commonly used data sources in the blockchain, such as HTTP API, GraphQL, State, LocalStorage, etc. Any developer (even users without a development background) can use it to customize blockchain data views easily. 

1) Using this toolset, users can easily create a user-friendly explorer UI with any open-source explorer solution (such as [Subscan Essentials](https://github.com/subscan-explorer/subscan-essentials)).

2) Using this toolset, you can customize widgets with custom data sources, such as API / GraphQL([Subquery](https://subquery.network/)), that can be integrated into your websites, Dapps, or any other web views.

In the future, Subscan will develop and deploy free online services based on this toolset.  It will enable users to create and submit widgets to Subscan explorer. Our ideal goal is to create a Dune-like data visualization publishing and collaboration platform.

**Total**

The total amount above is $201,600, and the amount of DOT will be converted based on the EMA7 price on the day of the official submission.

2022-12-08 01:55:42 (+UTC), Block #13260191

DOT EMA7 Price ( USD ): 5.421;

Number of DOT: 37,183.847

> EMA 7 Price: https://polkadot.subscan.io/tools/price_converter?value=201600&type=time&from=USD&to=DOT&time=1670464800

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

> View previous discussion [here](https://polkadot.polkassembly.io/post/1441)



Subscan - Data Dashboard Customization Toolset

- AngelHack is asking for $165,897.49 to help pay for prizes from a hackathon.
- The hackathon took place from May 30, 2022, until July 11, 2022.
- They originally wanted $297,000 to support the prize pool for the hackathon.
- The money for prizes has already been given to the winning teams.
- AngelHack used its own money to cover the difference in costs.
- They are now asking for the remaining amount they need to get back.
- You can find more information in their full proposal linked in the text.

**Proponent:** Tribe/AngelHack 13Ghf2T883ZobjngC1BAgR1BWvK2P7qP37gGxHDVFf3fjbmw

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

**Requested Allocation:** $165,897.49 USD, remaining of $297,000 USD 

*DOT amount calculated via EMA7 on 6 Dec 2022 at GMT+0 0244hrs - 1 DOT ~ 5.508 USD. $165,897.49 USD ~ 30,119.37 DOT

**Short description:**

Referring to the approved proposal [https://polkadot.polkassembly.io/treasury/117](https://polkadot.polkassembly.io/treasury/117), AngelHack has requested for an allocation of $297,000 USD to fund the total prize pool of the Polkadot Hackathon: North America Edition. 

The DOT amount calculated via EMA30 on 17 May 2022 at GMT+0 0721hrs was 1 DOT ~ 14.34, where the requested $297,000 USD had a disbursement of 20,711.2971 DOT.

With the allocated DOT disbursed at the end of the spend period, we have swapped the DOT for USD in order to proceed with prize disbursement. The price was at 1 DOT ~ 6.33 where 20,711.2971 DOT ~ $131,102.51 USD.

Prizes have already been disbursed to all the winning teams with AngelHack covering the current difference. The purpose of the proposal is to seek a bridge of the remaining amount that AngelHack had administered to the winning teams of the Polkadot Hackathon: North America Edition.

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


Polkadot Hackathon: North America prize pool bridging the gap for total amount

- A proposal wants to stop the upgrade of Polkadot to version 9320.
- This is because of changes in the FRAME code that affect how schedules work.
- There is a new check in the code to prevent exceeding weight limits for blocks.
- Most functions will work fine, but the `set_code` function will not pass this check.
- This is due to `set_code` using the maximum block weight, which always fails the check.
- A new proposal will be made with the correct call soon.
- The Council must approve this motion before the community votes on it.

This proposal aims to cancel the upgrade of Polkadot Runtime to v9320, due to a change on FRAME code explained below:

As the dev team works on transforming all FRAME pallets and code to work properly with WeightsV2, they have added the following check to the scheduler pallet: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107)

This piece of code should ensure that we don't execute a scheduled call that would use more weight than we have left for the block. For most calls this isn't any problem as they should be fit easily into a block. However, for `set_code` the dev team currently has annotated it with using the max block weight: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 ](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 )

So, when trying to execute `set_code` with the scheduler it will always fail this check. There will be already some consumed weight when trying to dispatch the call and `some_weight + max_block_weight` will always be bigger than `max_block_weight`. A new proposal will be submitted with the correct call soon.


 - Proposal hash: `0x88998cf7535c1f22d62849be8464fdc38fe46c0a46dc943ec56c91ef6592ec65`

 - Preimage is submitted. 

- Note this motion is an external one: meaning if/after Council approves, the community will vote on this proposal with the final decision.

Cancel the upgrade of Polkadot Runtime to v9320

- RadiumBlock helps build Web3 services for DotSama.
- They started their service at the end of March 2022.
- Their main job is to provide fast and reliable internet connections.
- This proposal is to pay for the services they offer from July to September 2022.
- They make sure their services work well all over the world.
- You can read more about their proposal in a detailed document.

RadiumBlock is a Web3 infrastructure provider for DotSama. We have been active in providing a high performance endpoint service for DotSama since the end of Q1 2022.

This proposal is to cover the ongoing costs(Q3 2022) for the running of our low latency, geo-distributed, high performance, scalable, and reliable public endpoint infrastructure for Polkadot.

Our [detailed proposal can be read here](https://docs.google.com/document/d/15pN1pgbPGVciQYGNYEyCxUelnl25pZsM/edit?usp=sharing&ouid=114172945417100820622&rtpof=true&sd=true).

RadiumBlock Public Endpoint Service for Polkadot (Q3 2022)

### Proposal Summary

- **Proposal Hash:** `0x98b3a8aa425c1e1ca5cd96d1b8f3491233b0745575e648a8c5497e83cec76f16`
- **Objective:** Increase the limit of nomination pools from 64 to 128 in Polkadot.
- **Reason:** Initially set to 64 to prevent risks during the launch, now proposed to be increased since everything is working as expected.
- **Process:** If the Council approves, the community will vote in the referenda queue for the final decision.

Increasing Max Number of Nomination Pools

- There are almost 50,000 nominators involved in a project.
- A new motion is being proposed to improve nomination rules.
- This motion wants to set higher minimum bond limits for nominations.
- There's already a vote for a different proposal called Referendum 86.
- If the new motion is approved, it could replace Referendum 86.
- The goal is to make changes quickly and keep nominations easy.
- More information about why the new limits are important is available online.

As we are almost at 50k nominators and we need to avoid a scenario of no one being able to change or set nominations, this external motion aims to outstrip [Referendum 86](https://polkadot.polkassembly.io/referendum/86) aiming to define slightly higher nomination min bond limits, which is currently up for community vote for next 11 days and with a new motion suggest shorter voting and enactment periods. If approved and later fast-tracked by the TC, making [Referendum 86](https://polkadot.polkassembly.io/referendum/86) redundant; Hence, this proposal, along with updating several staking configurations, would also cancel the [Referendum 86](https://polkadot.polkassembly.io/referendum/86). 

Further information about the importance of the higher nomination min bond limits can be found in the initial discussion post [here](https://polkadot.polkassembly.io/post/1224). 

 ![](https://i.postimg.cc/cJJQF6CT/Screenshot-2022-12-02-at-09-24-23.png)

Redefining Slightly Nomination Minimum Bond Limits and Removing Max Number of Nominators (replacing Referendum 86)

- OneBlock wants money to help run the 2022 Polkadot Winter Hackathon in China.
- They have organized successful Polkadot Hackathons before in 2021 and 2022.
- The hackathon helps teach developers about Substrate, which is a tool for building programs.
- They want to turn learners into builders by encouraging them to create projects.
- The previous hackathons received positive feedback from developers.
- OneBlock believes the winter hackathon is important for promoting Substrate in China. 
- They are asking for financial support to make this event happen.

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

OneBlock, in collaboration with Parity Asia, successfully organized, operated and promoted the three Polkadot Hackathons in March 2021,June 2021 and June 2022. OneBlock propose to continue the Polkadot Hackathon program in winter 2022, an essential part of the Substrate promotion and adoption initiatives in China, to promote Substrate as an open-source framework for developers and convert the Substrate learners from OneBlock’s ongoing Substrate courses to Substrate builders.

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

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

Please feel free to comments!

OneBlock The 2022 Polkadot Winter Hackathon proposal

- DotLeap is starting its third year and has shared 104 weekly editions.
- Bruno Škorvc is increasingly handing day-to-day tasks to gbaci, a professional content writer.
- DotLeap's yearly costs are over $50,000, requiring more funding sources besides personal donations.
- The goal is to keep growing the community and help new participants join easily.
- They have submitted a proposal for funding and are getting positive feedback.
- People are encouraged to participate in discussions about the proposal.
- Thanks were given to the community for two years of DotLeap's success!

DotLeap has officially entered it's third year in production, with 104 weekly editions distributed!

With the growing operations of the RMRK team it has become necessary for Bruno Škorvc to hand day-to-day operations of DotLeap increasingly to gbaci, RMRK's professional content writer and accomplished author of Polkadot for Beginners. 

Additionally, with operating costs in excess of $50,000/year, it has become necessary for DotLeap operating capital to coalesce from sources supplementary to Bruno and gbaci's generous donations of personal financing and time. Production of DotLeap up until this point has been a labor of love.

This proposal serves to secure pro- and retroactive funding for DotLeap so that we may continue to service the growth of our quality community, and so that we may continue to assist the easy entry of new participants in our ecosystem. 

Please review our proposal [here](https://docs.google.com/document/d/1BbpNMmbGU2q-bJlaj8PTscung7h1XUwZwH3hLj2yKwg/edit#) and please view and contribute to discussion in the Discussion forum [here](https://polkadot.polkassembly.io/post/1410)

In the 10 days since we submitted this proposal to Discussions, we have received your positive feedback and will answer your questions and make language adjustments to our proposal as needed!

Thanks so much, Dotsama fam, for two full years of DotLeap success!

Pro- and Retroactive Funding for Continuous Production of DotLeap Newsletter

- A new proposal has been made to cancel an earlier one that is expected to fail.
- The failure is due to recent changes in the code that will not allow the scheduled call to execute properly.
- Developers are working to update the code so that everything functions correctly.
- A new proposal will be submitted soon that should work better.
- The proposal aims to upgrade Polkadot to a new version called v0.9.32.
- There are several minor changes and fixes included in this upgrade.
- After the Council votes on the proposal, the community will also need to vote on it.

This proposal will fail in enactment, so [external motion 306](https://polkadot.polkassembly.io/motion/306) is now opened to cancel this. A change on FRAME code explained below is the reason this will fail: as the dev team works on transforming all FRAME pallets and code to work properly with WeightsV2, they have added the following check to the scheduler pallet: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107)

This piece of code should ensure that we don't execute a scheduled call that would use more weight than we have left for the block. For most calls this isn't any problem as they should be fit easily into a block. However, for `set_code` the dev team currently has annotated it with using the max block weight: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 ](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 )

So, when trying to execute `set_code` with the scheduler it will always fail this check. There will be already some consumed weight when trying to dispatch the call and `some_weight + max_block_weight` will always be bigger than `max_block_weight`. A new proposal will be submitted with the correct call soon.

Please note this proposal should be rejected.

______________________
_______________________
_______________________

The proposal aims to upgrade Polkadot’s runtime to [v9320](https://github.com/paritytech/polkadot/releases/tag/v0.9.32): more information can be found on the release notes.


**Runtime**

- [S] ✅ trivial [#12358](https://github.com/paritytech/substrate/pull/12358) Low - Remove contracts rpcs
- [S] ✅ trivial [#12421](https://github.com/paritytech/substrate/pull/12421) Low - Adapt `pallet-contracts` to weightv2
- [S] ✅ audited [#11649](https://github.com/paritytech/substrate/pull/11649) Low - Bound uses of `call`
- [S] ✅ trivial [#12429](https://github.com/paritytech/substrate/pull/12429) Low - Contracts: adapt dry-run runtime apis to weightv2
- [S] ⏳ pending non-critical audit [#12282](https://github.com/paritytech/substrate/pull/12282) Low - Maximum value for `multiplierupdate`
- [P] ✅ trivial [#6021](https://github.com/paritytech/polkadot/pull/6021) Low - Maximum value for multiplierupdate
- [S] ✅ trivial [#12334](https://github.com/paritytech/substrate/pull/12334) Low - Macro stubs for all pallet:: macros to improve documentation visibility and discovery + revamp of pallet macro documentation
- [S] ✅ audited [#12109](https://github.com/paritytech/substrate/pull/12109) Low - Vesting pallet - make `withdrawreasons` configurable
- [P] ✅ audited [#5451](https://github.com/paritytech/polkadot/pull/5451) Low - Manual para lock
- [P] ✅ trivial [#6155](https://github.com/paritytech/polkadot/pull/6155) Low - Add `force_open_hrmp_channel` call
- [P] ✅ trivial [#6171](https://github.com/paritytech/polkadot/pull/6171) Low - Bump transaction_version (0.9.31)
- [S] ✅ trivial [#12558](https://github.com/paritytech/substrate/pull/12558) Low - Update `pallet-multisig` benches
- [P] ✅ trivial [#6189](https://github.com/paritytech/polkadot/pull/6189) Low - Update weights, attempt two (0.9.31)

This release also contains the changes **from v0.9.31 to v0.9.32**: 
- [Substrate#12630](https://github.com/paritytech/substrate/pull/12630): Make `--database` cli argument case insensitive again.
- [Substrate#12632:](https://github.com/paritytech/substrate/pull/12632): Fixes a bug with the transaction pool after doing a warp sync.
- [Substrate#12633](https://github.com/paritytech/substrate/pull/12633): Fixes the `payment_queryInfo` RPC to be compatible with the latest runtime changes.


Proposal hash: `0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162`

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.

[PLEASE REJECT] Runtime v9320 Upgrade On Polkadot

- Pinknode is a service that helps people use the Polkadot network by providing tools and support.
- They started giving free services in 2021 to make it easier for developers to build on Polkadot.
- Pinknode helps with three main areas: Polkadot, Statemint, and Westend.
- They have many users, with millions of requests to their services every day.
- Pinknode made improvements over three quarters, like adding new tools and fixing problems.
- They had a very high reliability rate in Q3 2022, with only one major issue.
- Pinknode aims to keep getting better at providing these services for everyone.

Proponent: Pinknode

DOT Account: 13EAhGcpe93mqSFZQrQ4P2cfpdAo5txWc5UQVTfEKDoqZjhw

Date: 17/11/2022

Requested allocation: USD$53,243.06 for 3 quarters

Allocation in DOT: 9084.29

**Proposal Summary: Costs for running secure, reliable, and scalable public infrastructure for Polkadot, Statemint, and Westend**

**Project Summary**

Pinknode is a node-as-a-service platform focused on providing shared API endpoint and node operation services catering exclusively to the Polkadot ecosystem. We launched our MVP in June 2021 and have been providing free RPC services to the Polkadot ecosystem’s participants since Q3 2021. Our mission is to aid the Polkadot protocol in achieving its vision of a multi-chain future by providing easy-to-use, reliable, and scalable infrastructure services which remove an entire layer of complexities for developers to start building on Polkadot/Substrate.

Ecosystem participants can access our free API service by creating their own API Key on [Pinknode Portal ](https://portal.pinknode.io/signup)or using our public endpoints (listed at https://polkadot.js.org/apps). In a bid to reduce barriers to entry and attract more developers to the ecosystem, our premium plan, which includes archive data and higher rate limits, is also free for all builders and participants of Polkadot to utilize. 

- https://public-rpc.pinknode.io/polkadot
- wss://public-rpc.pinknode.io/polkadot
- https://public-rpc.pinknode.io/statemint
- wss://public-rpc.pinknode.io/statemint
- https://public-rpc.pinknode.io/westend
- wss://public-rpc.pinknode.io/westend

**Service Details**

**For Q1/22, from 1st January 2022 to 31st March 2022,**

Pinknode’s Polkadot RPC nodes have served an average of 2,737,933 requests per day, for a cumulative total of 246,413,975 requests for the quarter.

Pinknode’s Statemint RPC nodes have served an average of 159,873 requests per day, for a cumulative total of 14,388,568 requests for the quarter.

Pinknode’s Westend RPC nodes have served an average of 189,120 requests per day, for a cumulative total of 17,020,770 requests for the quarter.

**For Q2/22, from 1st April 2022 to 30th June 2022,**

Pinknode’s Polkadot RPC nodes have served an average of 4,849,336 requests per day, for a cumulative total of 441,289,552 requests for the quarter.

Pinknode’s Statemint RPC nodes have served an average of 174,230 requests per day, for a cumulative total of 15,854,972requests for the quarter.

Pinknode’s Westend RPC nodes have served an average of 230,021 requests per day, for a cumulative total of 20,931,893 requests for the quarter.

**For Q3/22, From 1 July 2022 to 30 September 2022,**

Pinknode’s Polkadot RPC nodes have served an average of 8,708,123 requests per day, for a cumulative total of 792,477,238 requests for the quarter.

Pinknode’s Statemint RPC nodes have served an average of 26,7682 requests per day, for a cumulative total of 24,359,125 requests for the quarter.

Pinknode’s Westend RPC nodes have served an average of 350,008 requests per day, for a cumulative total of 31,850,748 requests for the quarter.

**Enhancements for the past 3 quarters:**

- Configuration of our Kubernetes clusters and auto-scaling mechanism
- Automated snapshot scripts
- Setup health check and monitoring tools
- Launch of Pinknode 1.0
- Enhancement of Pinknode’s proxy service and routing protocol.
- Testing and implementation of service recovery scripts
- Introduction of Pinknode’s Status Page for better visibility
- Automated chain upgrade scripts

Pinknode achieved service reliability of 99.94% for Q3 2022 with one major downtime incident on 12 Aug 2022. This major incident was traced to insufficient resource allocation for Pinknode’s proxy service and the fault was promptly resolved. You can view our status page [here](https://pinknode.statuspage.io/).

Pinknode will continue to improve our service reliability by improvement to our automated service recovery scripts and monitoring processes. We are confident of achieving higher service reliability going forward.

Our full report including raw data and graphs can be viewed [here](https://docs.google.com/document/d/1L7uhTEbFpOJ6xQuvoop6EWCLJP7B8uKUQvd4zl1NmXs/edit?usp=sharing).

Pinknode Public Infrastructure for Q1,Q2,Q3 2022

- PolkaWorld is asking for money to help with community education about Polkadot for three months.
- They want to cover costs from December 2022 to February 2023.
- Since June 2021, they have worked on 6 projects very well.
- Their projects are for the Polkadot ecosystem, which is a special technology community.
- You can see more details about their work and plans online.
- They are looking for advice and feedback from the community.

Hi, dotsama community！

This is a follow-up proposal from PolkaWorld to seek to cover the next three months (Dec 2022 to February 2023) of ops and maintenance costs to further promote and support community education for the entail Polkadot ecosystem.

PolkaWorld converted the W3F community grant to an open social contract with Polkadot Treasury in June 2021. Up to now, we have summit 6 [Motions](https://polkadot.polkassembly.io/motion/250), and all works are done in very high quality. You can also learn some of the delivery [here](https://polkadot.polkassembly.io/treasury/160#78ddbc22-acac-4a5f-9883-588928045fce).

Please check all the delivery reports, details for the next 3 months’ milestones, tasks, and the budget [here](https://docs.google.com/document/d/1Z2q3CXSONc01vDFeapAM93C2v8US8gghVKQXnzpDEqw/edit). Love to hear all your advice or any feedback.

PolkaWorld Ops and Maintenance proposal：2022.12 - 2023.2

- A new proposal is for a project called **Snowbridge** that connects Polkadot/Kusama and Ethereum.
- The project is developed by the Snowfork team and aims to be trustless and permissionless.
- It will be launched on a special parachain called the Bridge Hub.
- The proposal requests funding for 28 months to support the Snowbridge team's work.
- This includes 16 months of past work and 12 months for future work.
- If the proposal is approved, both Polkadot and Kusama communities will vote on it.
- More details about the project are available in the full proposal linked in the document.

Original Proposal: [HERE](https://polkadot.polkassembly.io/treasury/192).

The proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Polkadot/Kusama and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. 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 can be reviewed on [the post](https://polkadot.polkassembly.io/treasury/192) 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. Please note that both networks are voting on the project: the Kusama proposal (up for vote by the community on OpenGov) can be found [here](https://kusama.polkassembly.io/referenda/1). 

If approved by Council, this proposal will be up for vote after by the community in referenda queue. @Councillors: please review and vote at your convenience!

Proposal hash: 0xcb7a0584b5d85d6065d2e492d476aa1c1b92b9a0e492aa668b33036671500ddb

Treasury Proposal: Snowbridge Funding Proposal

- OpenZeppelin is a company that started in 2015.
- They are experts in making smart contracts safe.
- There is a proposal for OpenZeppelin to check a smart contract language called ink!
- They will also review something called Substrate’s smart contracts pallet.
- The goal is to make improvements to security and how easy it is to use.
- After their work, OpenZeppelin will give a report about what they found.
- This helps everyone use smart contracts better and keeps them safe.

Since 2015, OpenZeppelin has developed deep expertise and set industry standards for secure smart contract development.

This community proposal is for OpenZeppelin to review and audit the current design of the ink! smart contract language, together with Substrate’s smart contracts pallet, in order to recommend actions to be taken and improve the development experience and security of it.

Upon the conclusion of the engagement, OpenZeppelin will deliver a security assessment report.

[Find full proposal here](https://docs.google.com/document/d/1GzQhvDY1jGeb-7_buNBwO4ppL0Siu-kTDktVQVDCg8g/edit?usp=sharing)

Council Motions