proposalId

See details on [the discussion here](https://polkadot.polkassembly.io/post/797)

Value used from the proposal document of:

EUR 104000 = USD 118061.84

2022-01-23 23:04:48 (+UTC), Block #8712309

DOT Price ( USD ): 18.2248;

Number of DOT: 6,478.0791

DOT EMA30 Price ( USD ): 25.7591;

Number of DOT: 4,583.2988

DatDot.org 

ZKValidator is asking for money to host an online event about privacy and zero knowledge proofs in the Polkadot ecosystem. Here are some important points about their proposal:

- They want to use €8000 from the treasury to pay for the event.
- The goal is to make more people aware of why privacy is important in blockchain.
- The event will help people connect and share ideas.
- ZKValidator has held similar events before, including a workshop in 2019 and a virtual event in 2021.
- They are looking for support and welcome feedback on their proposal.

ZKValidator is submitting a treasury proposal to fund a virtual event to raise the profile of privacy and the use of zero knowledge proofs in the Polkadot ecosystem. We are a mission driven validator with the goal of promoting more extensive adoption of privacy and zkp tech in the blockchain space.

The proposal would use €8000 in DOT from the treasury to fund the event. The full proposal is viewable through the link [here](https://docs.google.com/document/d/1qKy8-dGO8w2GUMDW6qiEalhB0iTUKJsYBYUErnOx28w/edit#heading=h.v6is2ta0txr1). The key points and motivation for the profile are as follows:

- Privacy is a blocker to more extensive adoption of blockchain technology.
- Hosting an event raises awareness of the importance of privacy on Polkadot and encourages discussion in this subject area.
- An event also provides a platform for networking - new connections can be made and ideas shared.
- We previously hosted a privacy focused workshop for Polkadot in the Summer of 2019, the write up is here and a virtual event in April 2021, with the recordings of the event viewable here. We hope that you will support our proposal and welcome any feedback.

Thank you for your consideration!

ZKValidator virtual event for Polkadot

- The proposal is to fund the Bright Treasury app's maintenance costs.
- Bright Treasury is a web app that helps users work with the Treasury on Polkadot and Kusama networks.
- The app makes it easier to submit proposals and see Treasury actions.
- It uses a special method called CI/CD for updates and testing.
- The project aims to attract more people to contribute who might not be experts in blockchain. 
- There are links to learn more about the app and its documentation.

**This proposal was added through BrightTreasury. For more info & discussion, check [BrightTreasury](https://stage.treasury.bright.dev/proposals/85?networkId=polkadot)**

## About the project

The goal of the proposal is to fund the Bright Treasury app maintenance costs. We have automated tests and deployment of infrastructure templates with continuous integration and delivery (CI/CD). The infrastructure as code approach lets us have an easy run and update of the environment.

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

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

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


Bright Treasury maintenance 01.2022 - 03.2022 (t)

- A proposal is made to upgrade Polkadot's system to a new version called v9151.
- This upgrade fixes some issues, including one about council voters and their deposits.
- People can check the details and changes about the upgrade online.
- There is a special code called a hash that identifies the proposal.
- It is important for everyone to vote on this upgrade soon.
- The upgrade is needed to get ready for the next improvements in the system.

proposalHash

The proposal aims to upgrade Polkadot’s runtime to [v9151](https://github.com/paritytech/polkadot/releases/tag/v0.9.15-1): Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.15-1). This release contains some runtime cleanup, like kianenigma’s fix locked deposit of council voters.

Hash: `0xc0d644131338cbf809cdb03afe0f7e1660b228e18011087858828ced4365d82e`

Please feel free to use srtool yourself to check the proposal hash. Make sure to vote at your convenience, it should be upgraded asap to prepare for the next runtime.

Polkadot Runtime Upgrade to v9151

Polkadot India is working to educate people in India about Polkadot and Substrate. Here are the main points:

- They started two programs: DotFriday (a webinar series) and Substrate Saturdays (a bootcamp series).
- These programs began in September 2021.
- They have been successful and the community is growing quickly.
- They want to reach 1500 crypto fans and 1000 developers by February 2022.
- More information about their events is available online.

Polkadot India aims to sensitize the Indian crypto community about Polkadot and Indian developers about Substrate. 

To this effect we have created two properties DotFriday(A Guest Webinar Series), and Substrate Saturdays(A Bootcamp Series) and have been running them since September 2021. 

Our properties have been seeing glimpses of success and the community has been growing rapidly since September, and we propose to continue hosting such events with an aim of impacting 1500 crypto enthusiasts and 1000 developers by Feb 2022. 

Link to Polkassembly [post](https://polkadot.polkassembly.io/post/764). 

Detailed proposal along with relevant links/ metrics from previous events + details of upcoming events are shared [here](https://drive.google.com/drive/folders/1FhydhPMUzO9Kh5yi-axS1TumCPkNH9e8?usp=sharing). 

6 Polkadot Webinars + 3 Substrate Bootcamps in India 

- A conference called "Smart Contracts on Polkadot - WASM" is being organized.
- The aim is to bring people together to discuss WASM and its importance for building apps.
- The organizers are Supercolony, who have helped improve WASM and related projects.
- The conference will be virtual and only last one day.
- They plan to use a platform called Hopin for streaming the event.
- They want to organize 3-4 events next year, including a Polkadot Hackathon.
- Feedback is welcomed on marketing and ideas for the event.

Hi there!

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

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

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

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

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

Smart Contracts on Polkadot - WASM conference (Virtual)

- A proposal is being voted on to upgrade Polkadot to version v9150.
- This upgrade includes fixes for some issues in the system.
- The proposal has a special code called a hash for reference.
- Voting is important and should happen soon to get ready for future updates.
- There is an update suggesting to vote “Nay” on Referendum 49 because of potential problems.
- Some people might see errors in Kusama nodes because of the upgrade.
- An additional upgrade may be needed to fix these issues later.

The proposal, upgrading Polkadot Runtime to **v9150**, is up for vote. 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.15). This release contains some runtime cleanup, like kianenigma’s fix locked deposit of council voters but also the locked deposits of Nicks pallet.

Hash: `0x960d3ad3f42eb41ab2131e1561dd8cc20f87585e37d2d1b02525578204f11d4b`

Please feel free to use srtool yourself to check the proposal hash. Make sure to vote at your convenience, it should be upgraded asap to prepare for the next runtime.

-------------------------


**UPDATE**

It is advisable to vote `Nay` on Referendum 49. It looks like the runtime upgrade lacked a corresponding Polkadot companion change for #10043, as a result some people may see some errors in the logs of Kusama nodes.

For Kusama an additional runtime upgrade will likely be proposed reverting the issue. Until it is resolved we don't want to risk anything happening on mainnet, so only after we will move to a new upgrade.

Runtime v9150 on Polkadot Network

- Polkassembly helps with the governance of Polkadot and Kusama networks.
- This proposal is asking for money to pay for running and maintaining Polkassembly.
- The payment will happen every three months (quarterly).
- Funds are requested for the first three months of 2022 (January, February, March).
- The maintenance costs include upgrades and infrastructure.
- The proposal will alternate between Polkadot and Kusama for funding every three months.
- More information about the proposal can be found in a linked document and discussion.

[Polkassembly](https://polkadot.polkassembly.io/) 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 January, February, March of 2022. We are requesting the Polkadot treasury to provide funds this time.

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

Social Contract between Polkassembly and Polkadot Treasury

- Many clients need special nodes called RPC nodes to connect to the Polkadot network.
- If the current RPC nodes aren't available, users can't access the Polkadot chain.
- A new RPC service is being created to help with this problem.
- The new service is located in Scandinavia and will make the network stronger and safer.
- There is already a request submitted for this new service, and it's now available online.
- More details about this proposal can be found in a linked document.
- Information about the DOT rate can be checked using a specific tool.

Most clients that need to connect to the Polkadot network are dependent on RPC nodes to interact with the network. Should the set of existing registered RPC nodes be unavailable, many users will not be able to access the Polkadot chain.

This proposal is about covering the maintenance costs of running a new RPC service for the community. The services is hosted in Scandinavia and will help to further decentralize the network.

- We have already submitted a [Pull Request](https://github.com/polkadot-js/apps/pull/6116) for our RPC service, and the service is now publicly available online.
- Our full proposal can be [read here](https://docs.google.com/document/d/1fHGFJfPmssOzS3u0JCXHvaYsMe5yHbcx4rgOCkRJScQ/edit).
- DOT rate based on 30 day avg tool by [Subscan](https://polkadot.subscan.io/tools/charts?type=price).

 Proposal: Polkadot RPC node Dwellir

- This proposal is between the Polkadot Council and MIDLDEV OÜ, a company from Estonia.
- MIDL.dev wants to provide daily blockchain snapshots for the Polkadot network to help node operators and validators.
- These snapshots are special file backups that help quickly recover or set up systems.
- They will also create a website, polkashots.io, for users to easily access these snapshots.
- MIDL.dev has been taking these snapshots for a year and has a reliable system for doing so.
- The project costs about 1200 EUR each month for two engineers, plus additional cloud service costs.
- Downloading a snapshot costs around $2, and they expect costs to rise as more parachains go live.
- This service helps the Polkadot network be stronger and recover from storage problems efficiently.

This treasury proposal is Between the Polkadot Council and MIDLDEV OÜ, a company registered in Estonia with registry number 14973249, commonly known as MIDL.dev.

## Service description

- A functioning infrastructure to provide usable blockchain database snapshots for the Polkadot network, to the benefit of node operators and validators,

- New snapshots at least once per day. Snapshots are filesystem dumps of the Polkadot node storage backend files, of variety RocksDb, of type pruned, with a depth of 1000 blocks, compressed in 7z format, that can be used by validators to quickly spin up or restore their infrastructure,

- A website frontend at polkashots.io with relevant metadata and download links, including a permanent link that always redirects to the most recent snapshot,

- Best effort incident and problem management,

- Redundant implementation setup which allows for continuity, seamless upgrades and basic disaster recovery & contingency management.

## Context

Node operators must have a contingency plan for loss of storage. For us at MIDL.dev, it consists of regularly taking snapshots of the node filesystem and backing it up for recovery if needed. We regularly generate these archives for our own benefit as well as the community. All cloud automation code used for generation of snapshots is [open-source](https://github.com/midl-dev/polkadot-snapshot-generator) so node operators can easily replicate the setup in order to be in full control of the generated snapshots.

The website polkashots.io has been operational for a year now. It has had excellent uptime. It is very frequently mentioned in the Validator Lounge Matrix channels and there are youtube videos referencing them. It is beneficial to the ecosystem by providing a path for validators to quickly and safely recover from a storage failure or migrate their operations.

## Alternatives

The warp sync feature has been implemented in Polkadot 0.9.9, however it still requires several hours for a full sync.

A unique snapshot service that many independent validators relies on constitues a centralization risk. It remains our hope that other ecosystem participants will step in and offer an alternative service.

## Operational expenses

The labor cost is 1200 EUR/month including 2 engineers in 2 geographical locations (Western US and Western Europe).

In addition, we pass along the cloud costs with a 50% markup.

Polkashots is hosted on google cloud. Google cloud has the concept of "projects" which allows for segregation of costs. The cloud cost is determined as follows:

- from June 1 to October 10, 2021, polkashots was hosted in a google cloud project shared with other MIDL.dev services named "MIDLUS" for which we estimate about 30% of the costs were incurred by generation and download of Polkadot snapshots.

- from October 11, 2021 to November 30, 2021, we moved polkashots to a dedicated google cloud project named "MIDLPS", allowing for the most precise cost calculation. We arbitrarily allocate 50% of these costs to Polkadot and 50% to Kusama. A dedicated project for each network would incur overhead costs that we do not feel are necessary.

A majority of these costs are network egress. Google cloud egress costs are in the higher range, similar to Azure and Amazon. Google cloud has two tiers, premium ($0.12/Gb for most regions) and standard ($0.85/Gb for most regions). The premium tier is using google private network across the globe. Polkashots uses the premium tier.

The costs have gone upwards after the introduction of parachains. This is due to the increased storage requirement of the relay chain node in the presence of parachains: as of this writing, a pruned polkadot node with 1000 blocks uses 18Gi of storage (7z compressed). In other terms, it costs the treasury $2 each time someone downloads a Polkadot snapshot. We expect this cost to go up again soon as more parachain slots become active.

The usage of the best cloud platform money can buy is justified by the benefits: a faster download speed and better reliability means that the nodes are more apt to recover quickly in case of accidental loss of storage, making the entire network more resilient.

Screenshots of the billing console are attached for reference.

## Usage

From the MIDLPS billing screenshot, we can see 17,262 Gibibytes of download from the period Oct 10-Nov 31 from all regions excluding Asia and Australia. Polkadot snapshot size is 17Gi and Kusama snapshot size is 50Gi, so assuming a medium download file size of 34Gi, there were 500 downloads during the period, or 10 downloads per day. This is a combined figure for Polkadot and Kusama networks.

## Note

This proposal is for the Polkadot portion of polkashots. We already submitted a [similar proposal](https://kusama.polkassembly.io/motion/412) to the Kusama council, who accepted it.

## Budget

![](https://i.ibb.co/rb2GC2j/Screenshot-2021-12-30-at-07-43-05.png)

More info on usage can be found on [THIS LINK](https://polkadot.polkassembly.io/treasury/80).

Polkashots.io maintenance

- Shell updated Statemint and started block production with collators.
- There was a problem because two types of keys were used: sr25519 and ed25519.
- Aura needed sr25519 keys but was using ed25519 keys from the start.
- A temporary fix was made to use ed25519 keys in Aura for Statemint.
- This change will help validators check the signatures on blocks.
- After resolving the issue, a further upgrade will switch back to sr25519 keys.
- A special call hash was created for this update.

After Shell successfully processed the runtime upgrade to Statemint and handed over block production to the Statemint collators, they were not able to produce blocks due to a mismatch in key types. Specifically, Aura uses sr25519 keys to sign blocks, but the keys in the genesis chain spec were generated using ed25519.

A new runtime was created as a temporary fix. This runtime enables ed25519 in Aura for Statemint. This will be enacted on the Relay Chain so that validators will be able to validate the collator signatures. After the chain is producing blocks again, a follow up runtime upgrade will migrate Aura back to using sr25519 keys.

Call hash: `0x0e21b5233c7591ee89eca0cae71cf9a9a4c45fe2393075ab33361a673f5d322d`

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

Fix Statemint - Aura Key Scheme

- This is about a vote called a referendum related to Polkadot.
- The previous referendum didn’t pass because Polkadot needed a default setting for messages.
- This setting helps keep Polkadot safe by making sure messages are sent with a safe version first.
- Since Polkadot is using a new feature called cross-chain interaction, they had not set a version before.
- The new proposal includes the same two calls from the last vote plus a new call to set a safe version to "2".

This is a follow up to [Referendum 46](https://polkadot.polkassembly.io/referendum/46), which failed because Polkadot did not have a default XCM version set. This protection, that the Relay Chain will not dispatch messages without a minimum safe version, was put in place after a previous vulnerability. Since this is the first cross-chain interaction that Polkadot has had, the version was not initialized.

The batch of calls contains the same two calls as Referendum 46, with an additional call to set the default XCM version of Polkadot to 2.

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

Upgrade Shell to Statemint (with XCM Fix)

- Messari wants Polkadot to join their Messari Hub. 
- The Hub is a place for independent research made by expert analysts. 
- It helps people like users and investors learn about Polkadot and its ecosystem. 
- Reports will be free and shared through newsletters and social media. 
- Messari is asking for $125,000 in DOT to fund an initial report and 4 more reports each year. 
- This money includes a 10% extra amount to handle price changes. 
- The goal is to give more information about Polkadot regularly.

Messari is proposing Polkadot to join the Messari Hub, a community-driven marketplace for independent research written by qualified contributing analysts and funded by crypto organizations. This enables quality research to be freely available to various stakeholders including users, developers, and investors looking to stay adequately informed about Polkadot and its broader ecosystem. Reports will live as free resources on Messari and distributed through our newsletter (~200k subscribers) and various social channels.

We are requesting $125k payable in DOT with a 10% premium to account for market volatility. This will go towards funding an initial "ecosystem report" and then 4 quarterly reports to provide more ongoing coverage.

You can find further details in the [full proposal](https://docs.google.com/document/d/1Mkurr4HK0UEiI4aDs6bDWYM7CwycKW8tTHA95dotwcU/edit#).

Commission research through the Messari Hub

- Patract made a proposal to cover costs for Polkadot projects in 2021.
- They create tools and services for a special technology called Wasm.
- With help from Polkadot Treasury, they finished important projects like Redspot and Europa.
- The proposal is about paying for the maintenance of these projects.
- The projects had many changes throughout the year.
- More details about the money and tasks are available in the treasury submission.

The proposal, by Patract, aims to cover maintenance costs for all related Polkadot projects for the year 2021: The team provides dev tools and services for Polkadot’s Wasm contract tech stack. With the support of Polkadot Treasury, they have completed the development, report, and external review of **Redspot, Europa, Elara, zkMega, Metis**. This proposal aims to cover maintenance costs of the projects, given the breaking changes throughout the year. 

Budget, tasks and more context for the proposal can be found on [the treasury submission](https://polkadot.polkassembly.io/treasury/78).

Patract Labs' maintenance cost for Polkadot of 2021

- There are two important actions planned for upgrading a system called Statemint.
- The first action will set certain storage settings to prepare for the upgrade.
- This includes important items like setting the first Aura collators and updating a safety feature.
- The second action will authorize the actual upgrade to Statemint.
- These actions need to be carefully scheduled to ensure they happen in the right order.
- The proposal involves sending messages from a main network called Polkadot to Statemint.
- Each action is given a lot of importance to make sure they are completed properly.
- After the upgrade is authorized, it will take about an hour for the changes to take effect.

This will be a batch of two scheduled transactions. They would probably work fine at once, but will schedule to be safe and ensure that the `set_storage` takes place prior to authorizing the upgrade.

The first will set some storage keys in Shell for Statemint's "genesis". The second will authorize the upgrade to Statemint. Both calls need to be constructed on Shell and then dispatched from the Relay Chain in an XCM.

See the [release notes](https://github.com/paritytech/cumulus/releases/tag/statemint-v6.0.1) to review the assets, reproduce the `set_storage` call, and generate the runtime.

## Shell Constructions

### Set Storage

The `set_storage` call can be generated with the `build-spec` command from a collator node, using `statemint_genesis.json` as input. See the release notes for more info. Notable storage items include:

- Setting the first set of Aura collators.
- Setting the `SafeXcmVersion` to `2` to protect against older XCM formats.

Call data (statemint_genesis_values.scale):

```
0x0006908015464cac3378d46f113cd5b7a4d71c84476f594316a7dfe49c1f352d95abdaf110000000008015464cac3378d46f113cd5b7a4d71c844e7b9012096b41c4eb3aaf947f6ea4290800008015464cac3378d46f113cd5b7a4d71c845579297f4dfb9609e7e4c2ebab9ce40a0502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b38015464cac3378d46f113cd5b7a4d71c84579f5a43435b04a98d64da0cefe185054000a0acb9030000000000000000000000801809d78346727a0ef58c0fa03bafa3234e7b9012096b41c4eb3aaf947f6ea42908000080267ada16405529c2f7ef2727d71edbde4e7b9012096b41c4eb3aaf947f6ea429080000083a6300803c311d57d4daf52904616cf69648081e4e7b9012096b41c4eb3aaf947f6ea429080000803c311d57d4daf52904616cf69648081e5e0621c4869aa60c02be9adcc98a0d1d0502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3803f1467a096bcd71a5b6a0c8155e208104e7b9012096b41c4eb3aaf947f6ea4290800008057f8dc2f5ab09467896f47300f0424384e7b9012096b41c4eb3aaf947f6ea4290800008057f8dc2f5ab09467896f47300f0424385e0621c4869aa60c02be9adcc98a0d1d0502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3805e8a19e3cd1b7c148b33880c479c02814e7b9012096b41c4eb3aaf947f6ea42908000080682a59d51ab9e48a8c8cc418ff9708d24e7b9012096b41c4eb3aaf947f6ea429080000807474449cca95dc5d0c00e71735a6d17d4e7b9012096b41c4eb3aaf947f6ea429080000807b3237373ffdfeb1cab4222e3b520d6b4e7b9012096b41c4eb3aaf947f6ea42908000080c2261276cc9d1f8598ea4b6a74b15c2f308ce9615de0775a82f8a94dc3d285a1040180c2261276cc9d1f8598ea4b6a74b15c2f4e7b9012096b41c4eb3aaf947f6ea42908000080c2261276cc9d1f8598ea4b6a74b15c2f57c875e4cff74148e4628f264b974c80400000000000000000000000000000000080cd5c1f6df63bc97f4a8ce37f14a50ca74e7b9012096b41c4eb3aaf947f6ea4290800002101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb30b1aeeca675702f24c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421804c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d54212101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb314f6a7e973c2c34dc5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b76280c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7622101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb34cb6fa5260704ee40b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3800b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b32101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb35242002c980f9df1c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d781180c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d781180cec5070d609dd3497f72bde07fc96ba04e7b9012096b41c4eb3aaf947f6ea4290800003501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa19502fe5f80e8854f64761757261804c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421804c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d54213501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa1950a3f059d7e690a34f6175726180c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d781180c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d78113501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa1950c41649dd3c9d26696175726180c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b76280c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7623501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa1950fa571e62466b970561757261800b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3800b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b380cec5070d609dd3497f72bde07fc96ba088dcde934c658227ee1dfafcd6e169030502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b380cec5070d609dd3497f72bde07fc96ba0e0cdd062e6eaf24295ad4ccfc41d46090504104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d54214c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b762c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b30b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b380d57bce545fb382c34570e5dfbf338f5e4e7b9012096b41c4eb3aaf947f6ea42908000080d5e1a2fa16732ce6906189438c0a82c64e7b9012096b41c4eb3aaf947f6ea42908000080e38f185207498abb5c213d0fb059b3d84e7b9012096b41c4eb3aaf947f6ea42908000080e38f185207498abb5c213d0fb059b3d86323ae84c43568be0d1394d5d0d522c4100200000080f0c365c3cf59d671eb72da0e7a4113c44e7b9012096b41c4eb3aaf947f6ea429080000
```

### Authorize Upgrade

This message authorizes the upgrade of Shell to a runtime with a given hash (statemint_runtime-v601.compact.compressed.wasm). Once the upgrade is authorized, anyone can submit the runtime via `parachain_system.enact_authorized_upgrade`, and it will upgrade 600 blocks (approximately 1 hour) later.

Call data: `0x0103af49687b93d91fc08c1fcea1001d724a95c533a949019645d3e4179beedbf67e`

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

## Polkadot Proposal

This proposal is to schedule these messages to dispatch from Polkadot to Shell. They will dispatch 5 and 20 blocks after enactment to ensure each is processed separately. We give them plenty of weight (100 billion and 1 billion, respectively) to ensure they execute.

Call hash: `0xa6830793b6a3473f66fbd7305a9e330dd2dd688df0e8fcbd0c9ff08d28040a34`

![](https://i.imgur.com/5D8syF9.png)
![](https://i.imgur.com/YmVC8o3.png)


Upgrade Shell to Statemint

- A new update called Polkadot Runtime v9140 is being proposed.
- It will disable xcm teleports and reserve transfers.
- This change is needed to upgrade Shell to Statemint.
- You can find more information in the release notes online.
- There's a special code called a proposal hash for this update.
- It's important to vote on this proposal when you can.

The proposal, upgrading Polkadot Runtime to **v9140**, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.14). This runtime only executes a single change: disabling xcm teleports and reserve transfers as a prerequisite to upgrading Shell to Statemint on the network.

- Hash: `0x317c7862dc523bd083e4dd6545079bdc18058f561bada9e5e5646935b1cc04af`

Please feel free to use srtool yourself to check the proposal hash. Please not this is a runtime-only release. Please vote at your convenience!


Runtime v9140 on Polkadot Network

- The university is asking for $27,000 for hackathon prizes.
- They want to convert this amount to 658.30 DOT.
- The calculation is based on the average price of DOT.
- This is part of their university engagement program.
- They have a report and list of prizewinners from the hackathon.
- The prize money is for the winners of the hackathon.

As part of our university engagement programme (see [here](https://docs.google.com/presentation/d/1LLFxCpO7y1fyIfcdTpDQGkbuPoGy2mFvlusYb1tTe74/edit#slide=id.gc2bb29227c_0_1294)), we would like to request our third phase of funding ($27,000) to pay hackathon prizes.

The amount we are therefore requesting is 658.30 DOT (based on the 30 day moving average of 41.015 according to [Subscan](https://polkadot.subscan.io/tools/charts?type=price)) to pay the prizewinners in the hackathon.

Please find a report of the hackathon and list of prizewinners in the tranche 2 report [here](https://polkadot.polkassembly.io/post/574).

Encode Polkadot Tranche 3 (hackathon payments)

- A proposal was made to help the Spanish community understand Polkadot better.
- The goal is to create an Educational Hub for Spanish-speaking members and ambassadors.
- There are many requests for Spanish information about Polkadot on social networks and chats.
- The proposal wants to provide easy explanations of Polkadot in Spanish.
- Steps planned include creating guidelines, tutorials, blog posts, and translating important documents.
- A Spanish Polkadot webpage has already been completed.
- The budget for this proposal includes 494.35 DOTs.

**Proponent**: 1ndvErzA6F2gHFXwEqjcPd7qtGnsZDiStpSj4A8LytDJRhf

**Date**: 24.11.2021

**Short description**: This proposal is focused on increasing the Polkadot Spanish community with the development of an Educational Hub for Spanish community and ambassadors.

As ambassadors we need information about the Polkadot ecosystem, we have been searching and translating documentation to participate in events since last year. We also notice requests for this kind of information in social networks, official and unofficial chats, frequently. We have seen the limitations of English communication in the community. The complexity of the protocols and the ecosystem requires additional information and an easy way to explain the system.

To solve the necessity of the community, we believe that it is important to explain the ecosystem in an easy way, and in Spanish, to give tools to the community to participate in the Polkadot ecosystem.

As we know, some people are working on tutorials, translations, or blog posts but there is not an integrated, compiled, and organized information system for this community, and we aim to establish one for the Spanish and Latin American communities.

We consider that development of the Spanish community (Spanish language) should be through different actions and activities, building content in communication channels:

a.- **COMPLETED** - Development of a Spanish community Polkadot webpage.

**Milestone 2 (covered by this proposal) includes:**

b.- Guidelines and Tutorials about Polkadot Ecosystem.

c.- Spanish content as blog posts, guidelines, papers and more about Polkadot.

e.- Translations of Polkadot Wiki and official documents and research of important information in the ecosystem.

For milestones, budget, and reasoning behind Milestone 2 of this proposal please visit [THIS DOCUMENT](https://docs.google.com/document/d/1vj95yKquBI_qzoejMvljfmShqLvoE8p6S0gDwGt2-nY/edit#heading=h.v6is2ta0txr1).

Please note:

- This allocation covers Milestone 2 of the original proposal
- DOT Rate: 39,43 USD/DOT (24.11.2021) based on subcan EMA30 tool
- Allocation: 494.35 DOTs
- The team will follow up with a report on development.

POLKADOT EDUCATIONAL HUB IN SPANISH (Milestone 2)

**CryptoLab Overview**

- CryptoLab helps people manage their money in the cryptocurrency world.
- It focuses on making staking like an investment for non-technical users.
- Users can create and manage portfolios to control their risks and earnings.
- The website offers a Portfolio Benchmark to choose the best validators for staking.
- It also provides Portfolio Management to track earnings and alert users of important changes.
- CryptoLab supports the Polkadot and Kusama networks.
- They plan to complete three stages of development to improve their services.

**Short description**

The [CryptoLab](https://www.cryptolab.network/) aims to help non-technical nominators build stable and risk-controlled cash flows via well-designed and financial tools. The core idea is that we want to make staking the same as an investment. Therefore, we help nominators to build good portfolios and to manage their portfolios to control risk and revenue. Portfolio management is challenging in Polkadot/Kusama system because they are NPoS consensus.

We design the CryptoLab website to help users to do their cryptocurrency financial management. Our goal is to make staking comprehensive to people who may not be yet familiar with blockchain, from basic wordings to data representation. We plan to provide the following features in this stage,

- Portfolio Benchmark

- Portfolio Management

Portfolio Benchmark helps nominators to evaluate which validators they should stake on. They can simply choose and nominate from our pre-built strategies or set their conditions on different criteria to get a list of validators. And it is just the first step.

The real difference that makes CryptoLab outstanding is Portfolio Management. We want to help nominators track their revenue and suggest new sets of validators according to the criteria they set. In addition, we want to maintain nominators make adjustments in time to prevent profit loss by notifying them when a validator increased its commission or when a validator is being slashed.

The CryptoLab staking website supports both Polkadot and Kusama networks. Please note that this proposal is only for milestone 1 on Kusama. We will submit the milestone 2 & 3 to the Polkadot Treasury once we finish the milestone 1.

Please look at our [full proposal](https://github.com/cryptolab-network/cryptolab-staking-treasury-proposal) for more detailed information. Feedback would be greatly appreciated. Thank you.

After completing milestone one and launching the CryptoLab Staking website, the team submitted the second and final treasury proposal to achieve the website.

- The report for milestone one can be found [here](https://kusama.polkassembly.io/treasury/97#c6d6a68b-4b23-4580-8cdb-71e9faf6b51e).
- Please see the details of the 2nd and 3rd milestones on the [full proposal](https://github.com/cryptolab-network/cryptolab-staking-treasury-proposal).
- This second proposal also includes another half the operating costs (3000 USD) to maintain the website on AWS.
- The total amount would be 14,250 (2nd) + 7,500 (3rd) + 3,000 (operation) = 24,750 USD
- DOT rate: 43.39 USD based on EMA30 by Subscan on 11.24.2021

Treasury Proposal - CryptoLab Staking Website (milestone 2&3)

calls

This motion is a bit of housekeeping and cleans the bounty proposal queue: closing 6 bounty proposals with no contextual information about their purpose. This proposal includes the closing of bounty proposals 3, 4, 5, 6, 7 and 8. Please note bounty proposers will lose their bond.

Rejecting Bounty Proposals with No contextual Information

- A new plan is made to help people who got scammed in the Polkadot community.
- Merkle Science will help by tracking scams using special tools.
- The team has worked for more than two months with other groups to make this plan.
- The project will start monitoring and investigating by December 2021.
- People can check for scams on a specific website for Polkadot.
- They will create different phases of development to make monitoring better.

This Proposal aims to provide a solution for cases of scam victims and other illicit activities in the Polkadot community. As a blockchain analytics provider, we understand the urgency for such a solution so, from our side, we are placing the Polkadot protocol on the top of our roadmap of blockchains to onboard in our monitoring and investigations solution. With the funds provided, we’ll not only be able to prioritize the launch in production (December 2021) but the ecosystem will have priority access to start monitoring all addresses under https://polkadot.js.org/phishing/.

Merkle Science has been working closely with Michalis (Web 3 Foundation) and RTTI-5220 (Polkadot Council) for over 2 months in shaping this proposal in the best way possible to meet the current and future needs for continuous monitoring and blockchain investigations by the Anti-Scam Response Team.

Proposal - [HERE](https://docs.google.com/document/d/1wR2hYa20PfBXjntTywm6vp179OL0HzJZYK0afDGy1vg/edit?usp=sharing).

- This proposal includes the development of phase 1 (a & b) + the monitoring services subscriptions.

- DOT rate is calculated based on 30day avg tool by Subscan on 05.11.2021: [https://polkadot.subscan.io/tools/charts?type=price](https://polkadot.subscan.io/tools/charts?type=price)

Merkle Science - Proposal: Polkadot Transaction Monitoring

- This is a proposal for money to help run a Polkadot community called PolkaWorld in China.
- The proposal covers costs from December 2021 to February 2022.
- PolkaWorld has over 40,000 followers and works with other Polkadot groups.
- They published 785 articles and had between 70,000 to 100,000 readers every month in 2021.
- They interviewed more than 50 projects and developers in the Polkadot community.
- PolkaWorld holds monthly meetups where about 150 people come to learn and share.
- They have also hosted 27 online events for the community to connect with projects.
- The proposal includes plans for activities over the next three months.

This is a treasury proposal for ops and maintenance of a Polkadot community in China, and it's aimed to cover the community operation costs from December 2021 to February 2022. PolkaWorld is a Polkadot community in China and has gathered more than 40,000 followers, they have collaborated with the Polkadot ecosystem and Web3 Foundation in the following ways：

- published a total of 785 Polkadot /Kusama/ Substrate articles（Wechat official account can't share a link).
reached total readings of 70k - 100k each month in 2021

- Interviewed 50+ eco-projects/Substrate developers

- host [monthly meetups](https://www.huodongxing.com/people/7602091781099?type=pub) in different cities from January 2021, an average of 150+ people come and meet in each meetup

- host 2 - 4 online broadcasts each month to let the community meet eco-projects/parachains online, so far we have hosted 27 online broadcasts on Wechat Channel（Wechat Channel can't share a link).

You can find more in their [monthly reports](https://polkadot.polkassembly.io/treasury/63). And all milestones and tasks for the next 3 months here.

- DOT Rate: calculated on 08.11.2021 based on [30day avg rate](https://polkadot.subscan.io/tools/charts?type=price).

PolkaWorld Ops and Maintenance proposal for 12/2021 - 2/2022

- A person named 12WarfbFeUm5L9Fs5zkTaQQH7L5hqaGPEgM9vQ1UFK8kiUSK wants $25,000 to write a book.
- The book will be about Polkadot, a network, and will be easy to understand for everyone.
- There are many books on Ethereum but hardly any on Polkadot.
- The person already has a first draft that is almost finished.
- They want feedback to make the book better.
- The book will be published for everyone to use and share for free.

**Proponent**: 12WarfbFeUm5L9Fs5zkTaQQH7L5hqaGPEgM9vQ1UFK8kiUSK

**Date**: 03 Nov 2021

**Requested allocation**:  ~$25,000 (in three installments).

**Short description**: Although Ethereum is a much less complicated system, google ‘books on Ethereum’, then google ‘books on Polkadot’. You’ll notice that while there are more than 10 books on Ethereum, Polkadot (the network) has nothing. Of course, this is more a sign of age than anything, but I’m proposing a way to start our journey.

This proposal brings to light the lack of a holistic and easy-to-understand explanation of Polkadot in a book form. It outlines the importance of a book and proposes a solution to create one. But not just another book about blockchains but one focused on Polkadot and written from a totally non-technical perspective.

Please visit [this link](https://docs.google.com/document/d/11NT6BzM8nOcbXR7wD1C2IJlsi0XyeJaS5Hv50Wy4rJ0/edit) to read the full proposal

A first draft has already been drafted (90% finished). You can view the first draft [here](https://docs.google.com/document/d/15p4Xy-I6_44zexCsPcZXHHlCj7L3Jcddle_8567B3x8/edit). Please leave your feedback to help shape the second draft.

The book will be published under a Creative Commons License (CC BY).

Previous discussion can be followed [here](https://polkadot.polkassembly.io/treasury/52).

Proposal to expand the Polkadot ecosystem with a book for blockchain beginners

- A proposal to upgrade Polkadot Runtime to version v9122 is open for voting.
- This upgrade will help with the first auctions and crowdloans on the Polkadot Network.
- You can find more details in the release notes online.
- The proposal has a special code called a hash: 0x0f598b97de6adfb2c5edffb7e8e5aed6408d29382a9de372ed229391a20c4a86.
- This change is only about the runtime, so node operators don’t need to update anything.
- No new installation files have been created for this release.
- Everyone is encouraged to cast their vote when they can!

The proposal, upgrading Polkadot Runtime to v9122, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.12-1). If enacted, this runtime will be the one supporting the first auctions and crowdloans on Polkadot Network.

- Hash: `0x0f598b97de6adfb2c5edffb7e8e5aed6408d29382a9de372ed229391a20c4a86`.

Please feel free to use srtool yourself to check the proposal hash. This is a **runtime-only** release. Node operators do not need to upgrade. As such, no binaries, package files or docker images have been created for this release.
 
Please vote at your convenience!


Runtime v9122 on Polkadot Network

This is a Proposal whose proposer address (12NLgzqfhuJkc9mZ5XUTTG85N8yhhzfptwqF1xVhtK3ZX7f6) 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.

Council Motions