proposalHash

**Runtime v29 on Polkadot** 

**Motion 70** upgrading Polkadot Runtime to v29 is up for vote.   Release notes, runtime changes and hash can be found [here](https://github.com/paritytech/polkadot/releases/tag/v0.8.29). 

All council members please vote at your earliest convenience!

Upgrade of Polkadot runtime to v29

- Figment wants to use 2380 DOTs to help developers grow in the Polkadot community.
- The DOTs will be given to developers as rewards for their work.
- Figment does not keep any DOTs for itself; all are for developers.
- They have two main platforms: Figment Learn and DataHub.
- Figment Learn helps developers learn about Web 3 development with easy-to-follow tutorials.
- DataHub gives developers access to tools to build their applications for free.
- This proposal aims to make it easier for developers to create and improve their projects.

proposalId

**Proponent:** 142hWpBmGsePS1tSopxg4JWaRirGgVpZubz5h251m31KJXdf

**Date:** 03/09/21

**Requested DOT:** 2380 DOTs for Milestones 1-3 - 100% of the DOTs will be distributed to developers as incentives. Figment retains 0 DOTs for operational costs as part of this proposal.

**Short description:** [Figment](https://figment.io/) is creating a proposal to request DOTs to be used as incentives to grow the Polkadot developer ecosystem via its platforms Figment Learn and DataHub. [Learn](https://learn.figment.io/) is the education and onboarding platform for developers interested in Web 3 development. With Learn, developers gain access to the most comprehensive developer portal which standardizes documentation across networks and offers in-depth practical tutorials to help them get to the next level.

Tutorials can be completed seamlessly with [DataHub](https://datahub.figment.io/sign_up) which provides easy access to the protocols via our highly available full node infrastructure and suite of middleware. Developers then get to build and scale their DApps for free using the DataHub infrastructure.

**Original proposal doc:**

[Visit this link for the full proposal](https://docs.google.com/document/d/1GkgnwLhjVCCrKY43uRgzg6vFI6yN_aoD_TCxBdkNAg8/edit#heading=h.v6is2ta0txr1)

Figment Treasury Proposal: Figment Learn & DataHub Milestone 1-3

- The team is following their original plan but realized they underestimated some parts of it.
- Testing for their project is harder than they thought, especially for the M8.3 part.
- They can't use some tools and have to make extra tests, which makes things complicated.
- The cost to complete M8.3 is higher than expected, now at 48,400 CHF.
- They plan to finish the work within 9 weeks after getting approval.
- The team also mentioned needing to fix a specific issue in their project.
- They provided links to reviews of their earlier work for reference.

We stick to the descriptions of [our initial roadmap](https://polkadot.polkassembly.io/post/111). So far the design is still valid. However, based on our experience after M8.1 and M8.2 we must admit that we underestimated M8.3. Especially the test fixtures are more laborsome than we anticipated. We can still not use `cargo test` for our SGX enclave code, so we have to wrap everything with custom commands and mocking is only partially possible leading to more end2end tests which are harder to debug. Moreover, we became aware of [#208](https://github.com/scs/substraTEE-worker/issues/208) which needs to be fixed.

#### cost and timeline

Our initial estimate for M8.3 was CHF 39'200.- but we have to adjust to **48'400 CHF** (+23%).

We currently have 1.3 FTE reserved for this and intend to **deliver within 9 weeks** after this motion passes.

DOT moving average MA(25)@1day today is 32.0 USDT on binance
USDT is 0.9302 CHF according to coinmarketcap

along previous proposals, we'd add a 10% premium for volatility risk.

We therefore request 48400*1.1/32.0/0.9302 = **1788.59 DOT**

#### reviews 

external reviews of our previous milestones M8.1 and M8.2: [review1](https://docs.google.com/spreadsheets/d/1EZgKLt1SbOsXwGi2NNnEAhjdyTrEUOttC__k4D6dVwg/edit#gid=1901352075), [review2](https://docs.google.com/spreadsheets/d/1sC1Jxy0mKSjUsiPfjc_SO3rwsyjUwV1jT4VCVJbrdrI/edit#gid=1534875011) 

please [tip](https://polkadot.polkassembly.io/tip/0xc5f28e61c17ad452006e6150532a60c95c3936e2046b9b4d38269bd518b2b8f5) & [tip](https://polkadot.polkassembly.io/tip/0xe48b661e5c97caf176e5ac401dc71c01922a3adfb69f6d0378ed103ced0c54c6) the reviewers



SubstraTEE Scalability M8.3

- Proposal 10 is a plan that can't be used anymore because it has the wrong address format.
- It doesn't matter how people vote; the proposal is still invalid.
- The person who made the proposal admitted they used the wrong way to submit it.
- They have created a new proposal, number 11, that people can vote on now.
- Everyone is asked to vote to cancel proposal 10.
- The goal is to clean up the list of proposals.

Proposal 10, a `force_transfer` proposal, cannot be executed: since the Address formats changed, it is now invalid: So it does not matter which way the vote goes, it cannot be applied.

Furthermore, the proposer explains they used the wrong method to submit this proposal, replacing no. 10 with [no. 11](https://polkadot.polkassembly.io/proposal/11) (currently up for vote as Referendum 18). 

Please vote to cancel the proposal and clean the queue. 

Preimage: `democracy > cancelProposal(prop_index) 10`: [HERE](https://drive.google.com/file/d/1W9v7a6LPvO6MzpCy0VahxtRTxv7swcZi/view?usp=sharing).

Cancellation of Proposal 10 on Proposals queue

This is a treasury proposal whose proposer address (12Vv2LsLCvPKiXdoVGa3QSs2FMF8zx2c8CPTWwLAwfYSFVS1) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Untitled Post

**Stylo Proposal Summary**

- **What is Stylo?** Stylo is an offline wallet that makes it easy to store and manage digital money.
- **How does it work?** Users can scan QR codes to make transactions using their phone's camera, keeping their funds safe offline.
- **Development Need:** The proposal requests funding of 159 DOT (about $3180) to help create the app.
- **Developer Background:** Thibaut Sardan, a former Parity employee, is working on Stylo to make it easier for everyone to use.
- **Key Features:** Available on Android, it's designed to support various digital currencies like DOT and ETH, with a focus on user-friendliness. 
- **Future Ideas:** More features may include message signing and fingerprint unlocking.
- **Why Android First?** The app will initially launch on Android due to the developer’s lack of access to Apple devices.

This is the on chain proposal corresponding to the  discussion [https://polkadot.polkassembly.io/post/315](https://polkadot.polkassembly.io/post/315)

### Proposal: Stylo - offline wallet
- Date: 15.02.2021
- Requested DOT: 159 DOTs

## Short description:
Stylo is an offline wallet that brings user friendliness to the front seat. It allows storing funds offline. Any interaction with the online world happens by scanning QR codes. Transactions are scanned, using the phone’s camera. They can then be reviewed and signed offline, and finally transmitted to an online wallet by scanning a QR code displayed on the phone, by a computer webcam. Stylo means pen in french.

## Context of the proposal
Many readers of this proposal will know [Parity Signer](https://github.com/paritytech/parity-signer). The idea of using a spare phone totally offline to store private-keys and scan transactions with QR code is simply great. In the past year however, Parity Signer has become increasingly complex to use. It targets power users, with 10s of accounts and is heavily forcing the hand toward the use of derivation paths. This is a concept that most users do not master. The idea to create a new application came from conversations with external users through the support channel of Parity Signer. Additionally, Parity Signer is currently missing critical features such as the ability to review a transaction, effectively putting its user at risk.

Stylo will be based on Parity Signer, refactoring big parts of the app to make it simple to grasp for its users. The idea is to have a flow similar to the one in Polkadot-js Extension, where all accounts are visible right away (see mocks below). It will be available on Android as an app, and on the Play store for testing. Why not on iOS you may ask? Because I do not have any Mac, or any iOS device. Stylo, just like Parity Signer, will be built using React-Native, therefore, it can be made available on Apple devices in the future, with (hopefully) minimal efforts.

## About the developer
I’m Thibaut Sardan, I have been a Parity employee in the past and worked on Parity Signer. I am dedicated to making this space easier to navigate for new and current users. 

## What this proposal is for
- An app (see mocks below) available as apk (Github) and on the Android Play store
- Support for DOT, KSM, any Substrate chain and ETH. 

## Work to be done
![](https://i.imgur.com/56KcXBq.png)

## Conditions of payment
Amount requested: 159 DOTs
Corresponding to ~3180$, or 60$/h for a developer or designer, and 100$/tester.
Price calculated based on the average price [in the past 1 month](https://polkadot.subscan.io/tools/price_converter?value=1&type=period&from=DOT&to=USD&startDate=2021-01-15&endDate=2021-02-15): 1 DOT = 20$

This is a minimal milestone, aiming at bringing the app live asap and measuring the community’s reaction/adoption. I will build it in my free time. Some features are already implemented, such as the details view.

## Features and ideas that can be added in subsequent milestones:
- support for simple message signing
- support for derivation in a (similar way than Polkadot-js extension)
- unlock with fingerprint instead of pin
- metadata update over QR code

## Mocks
![](https://pix.toile-libre.org/upload/original/1613482893.jpg)

Stylo - an offline wallet based on Parity Signer

- Motion 62 is about upgrading the Polkadot system to version 28.
- Some changes include treasury tip slashes and free participation in Council for newcomers.
- There will be a reorganization of the treasury system.
- Changes will help validators with session keys related to parachains.
- New features will allow checking if accounts exist and a new address format.
- More detailed information can be found in the release notes online.

**Motion 62 upgrading Polkadot Runtime to v28 is up for vote.**

**Some interesting changes:** treasury tip slashes, free participation in Council governance for first-timers, refactor treasury pallet, changes for validators session keys to account for parachains, Introduction of account existence providers reference counting and extensive multiaddress format in all runtimes. 

Release notes, runtime changes and hash can be found [here](https://github.com/paritytech/polkadot/releases/tag/v0.8.28).

Upgrade of Polkadot Runtime to v28

- PolkaBTC is a type of Bitcoin that works on the Polkadot network.
- It uses a bridge called BTC-Parachain created by a company named Interlay.
- PolkaBTC is currently being tested on a special network called Rococo.
- Interlay is launching a Beta testnet to check how well it works, especially some important parts called Vaults and Relayers.
- They are giving rewards to users who help test the system and provide feedback.
- Interlay wants to use some funds from the Polkadot Treasury to support these testnet rewards.
- More information about PolkaBTC and the bridge can be found on their websites.

**PolkaBTC is the trustless wrapped Bitcoin representation on Polkadot,** imported via the Bitcoin bridge (BTC-Parachain) built by Interlay. 

PolkaBTC is live on Rococo and Interlay will be launching a public Beta testnet to test the secure operation of the system, in particular Vaults and Relayers. 

To achieve higher participation during Beta testnet, Interlay designed a campaign for incentivizing users to actively test critical components of the bridge by handing out rewards for specific actions / challenges - with feedback from the Polkadot outreach team.
Since the BTC-Parachain does not have a native token, Interlay would like to put forward a motion to fund the PolkaBTC Beta testnet incentives in DOT from the Polkadot Treasury.

**The detailed proposal is presented [here](https://docs.google.com/document/d/1CBhJros7k7S3dJCjXMINUqw37Xj6JK73dzWfOO9sjOY/edit?usp=sharing):** 



**More details about the bridge can be found here**
- [https://polkabtc.io/ ](https://polkabtc.io/ )
- [https://polkadot.network/bitcoin-is-coming-to-polkadot/ 
](https://polkadot.network/bitcoin-is-coming-to-polkadot/ 
)

**More details on Interlay can be found here**: [https://www.interlay.io/ ](https://www.interlay.io/ )


Proposal: PolkaBTC Beta Testnet Incentives

- This is a proposal for a project milestone called M8.2.
- The project focuses on creating special sidechains that are safe and trustworthy.
- The team originally planned to spend 20,700 Swiss Francs (CHF) for M8.2.
- They had to work harder on the earlier milestone (M8.1) but will still stick to the original budget.
- They have 1.3 full-time workers ready and can finish the project within 3 weeks after approval.
- They are considering the current value of the currency and possible market changes.
- They suggest spending around 1,405 DOT (a cryptocurrency) from their treasury for the project.

This is our proposal for milestone M8.2 of our roadmap towards TEE-validated sidechains.

[Full project description and history](https://polkadot.polkassembly.io/post/111)

[Delivery of M8.1](https://polkadot.polkassembly.io/post/111#33001a84-4f69-4d3f-be6e-bbfad0048854)

According to the original roadmap linked above, we had initially estimated efforts for M8.2 to be 20'700 CHF.

Even though M8.1 has caused more efforts than we had estimated, we will hold true to our initial estimate. We have 1.3 FTE ready to work on this and we expect to deliver within 3 weeks after our proposal has passed approval.

Current exchange rates:

DOT moving average MA(25)@1day today is 18.12 USDT on binance

USDT is 0.8945 CHF according to coinmarketcap

Even though the current market is in our favor, we think a volatility risk margin of 10% is justified. Markets usually crash much faster than they rise.

We therefore propose a treasury spend of 
20'700*1.1/18.12/0.8945 = 1405 DOT

SubstraTEE scalability M8.2

- PolkaStats is a special tool that helps people learn about and track rewards for a type of cryptocurrency called Polkadot.
- It was created by a group called La Colmena, which is based in Sevilla, Spain, and promotes sharing knowledge in Spanish about crypto.
- PolkaStats offers unique features like focusing only on Proof of Stake chains and being built with easy-to-use computer languages.
- In the last month, PolkaStats had 8,100 unique users from 133 countries.
- They are asking for money to cover costs from December 2020 to March 2021 to keep PolkaStats running.
- The money will help pay for the servers they use to operate PolkaStats.
- They want to ask for 37.08 DOT, which is about $700 at the average price they found.

Hi all,

I would like to submit another proposal to cover PolkaStats operation costs for Polkadot for the period 21.12.2020 to 21.03.2021

### MOTIVATION

PolkaStats is a Substrate block explorer aiming to provide the best staking and economic data for both validators and nominators. It helps both types of users by providing comprehensive metrics, charts and utilities to improve their knowledge and performance.
PolkaStats is one of the projects that was born in La Colmena, a crypto community based in Sevilla, southern Spain. The community aims to incentivize content-creation in Spanish for Polkadot, Kusama and other blockchain projects and, as supporters of open source culture, develop software to contribute to the ecosystem. The organization also acts like an incubator that helped create blockchain business models like DragonStake or Delega Networks validators.

One year after starting the project in **La Colmena** it is certain to say that PolkaStats development also helped us learn and understand more about the Substrate framework and substrate-based chains. 

Although there are currently already some very good Substrate explorers in the ecosystem, PolkaStats has a different perspective to offer in order to increase diversity among the existing solutions. PolkaStats differentiates from other explorers in:

1. Focusing on Proof of Stake chains only.
2. Being a Javascript based block explorer (both frontend and backend)
3. Utilising Vue.js / Nuxt.js frameworks used in frontend, with a low learning curve.
4. Allowing Incipient wallet functionalities

### SOME POLKADOT METRICS

Google Analytics metrics of the Polkadot version of PolkaStats in the last month:

- **8.100** unique users
- **13.000** sessions
- Visitors from **133** countries

### PREVIOUS APPROVED PROPOSAL

The details of the last proposal can be found [here](https://docs.google.com/document/d/1eJIyyyl2Asr8tX05zpO-sUOa2aSoeIlCGag030t0vrA/edit?usp=sharing).

Previous proposal discussion can be found [here](https://kusama.polkassembly.io/post/290). 

Last treasury motion, executed at block#1,694,500 (Sep 21, 2020):

- [https://polkadot.polkassembly.io/treasury/12](https://polkadot.polkassembly.io/treasury/12)
- [https://polkadot.polkassembly.io/motion/22](https://polkadot.polkassembly.io/motion/22)


### SPENDING PROPOSAL FOR PERIOD 21.12.2020 to 21.03.2021

PolkaStats aims to submit this spending proposal in the following terms:

- New **3 month period**, covering operational expenses **from 21.12.2020 to 21.03.2021**, which totals to **37,08 DOT**.
- DOT conversion rate of 1 DOT = 18,81 $ (15,70 €) using MA(99) AVG from  [https://www.binance.com/en/trade/DOT_USDT](https://www.binance.com/en/trade/DOT_USDT)
- The funds will be used to pay the servers we rent to Hetzer and Digital Ocean in order to operate PolkaStats for Polkadot and Westend network (shared with Kusama).


### FULL PROPOSAL DETAILS

You can find the full proposal details, including monthly budget [here](https://docs.google.com/document/d/18T0U-dJq_UtmK-K1YbGs4R49wVM1hHWlK1RPf5DibqE).



PolkaStats treasury expense proposal - operation costs for Polkadot, 21.12.2020 to 21.03.2021

bountyId

Motion 59 is **now up for vote**: the bounty proposal seems to be spam, or someone testing the mechanism - since no contextual information has been added to the bounty, I am passing this as a `closeBounty` motion (if your vote is positive, you support closing this bounty) - this is to clean up the queue. 

Bounty proposal #1: spam/testing - passed to council as closeBounty

- A new idea is suggested for increasing the number of validators in the network.
- The plan is to add 1 new validator each day for 100 days.
- The goal is to have 100 more validators by the end of this period.
- This gradual increase helps the community check and review the network's performance.
- If needed, the process can be stopped, and the community can look at the data.
- This method is suggested to avoid sudden big changes in the number of validators.
- The parachains team also supports this idea.

Following up on [this idea](https://polkadot.polkassembly.io/post/283), I am proposing an external motion to be voted by the Council and by the community after. **The motion aims to schedule a gradual increase in the number of validators: 1 slot per day (14,400 blocks) for 100 days. **

We aim for and increase of 100 validators to be able to review metrics after completion. This mechanism can also be canceled, and at that moment the community will be able review network metrics. The proposal aims to avoid an abrupt increase in the number of validators in the network and follows the recommendation of the parachains team as noted [**here**](https://polkadot.polkassembly.io/post/263). 

You can verify preimage [here](https://drive.google.com/file/d/1idocvPtKKMQA36lzG4Upxcb4OXGMUeBW/view?usp=sharing).

Gradual increase in the number of validators

- Fearless Wallet is a mobile app for iOS and Android.
- It was created by SORAMITSU and supports Kusama Treasury.
- This app is special because it is made for Kusama and Polkadot systems.
- Fearless Wallet allows users to connect directly to the blockchain.
- The next stage of development (Stage 3) will focus on making staking easier and improving the app.
- The costs for this project are shared between Polkadot and Kusama.

**Fearless Wallet** is a native mobile app for iOS/Android which is fully supported by Kusama Treasury and developed by SORAMITSU. Fearless Wallet is the first **native mobile application** for Kusama and Polkadot ecosystems with **corresponding libraries** to support the development of native apps for Substrate networks. The mobile application is non-custodial, thus communicates directly with the blockchain without any middlewares in between.

**Stage 3** (this proposal) is planned to be focused on Staking, general app improvements, and native mobile libraries expansion.

Please visit the** full version of the proposal** for more context, budget, milestones, and timeframe:

[Full version of Fearless Wallet Stage 3 Proposal to Kusama & Polkadot treasuries](https://docs.google.com/document/d/13n0VdsXLmMtOvxNmGsKK9RrxeUXFzcHQguxD4r_CedM/edit?usp=sharing)

**Note:** Total cost is divided between Polkadot (this) and Kusama ([link](https://kusama.polkassembly.io/treasury/74)) treasuries, half for each.

Fearless Wallet - Stage 3 Proposal - Staking, Libraries expansion, App Improvements 

**Motion 56 upgrading Polkadot Runtime to v27 is up for vote**.

 After a successful upgrade on Kusama, [motion 56](https://polkadot.polkassembly.io/motion/56) is submitted on Polkadot, aiming to upgrade the network’s runtime to v27. 

  Upgrade priority: **Low** (upgrade at your convenience).

 Release notes, runtime changes and hash can be found [here](https://github.com/paritytech/polkadot/releases/tag/v0.8.27). Please vote at your earliest convenience!

Upgrade to Polkadot runtime v27

- OnFinality is a platform that helps people build on the Polkadot/Substrate blockchain.
- They have launched a beta version of a shared node API Service, which allows developers to access Polkadot nodes easily.
- The service aims to support all blockchain developers by providing them with necessary tools to create their applications.
- On Finality has already handled over 3.2 million requests in one day.
- They are looking for funding to cover the costs of running their free public API service for Polkadot.
- Users can create a free account to access the service, and there will be limits on daily requests.
- Future enhancements and paid options may be available based on how many requests users need.

OnFinality is a SaaS platform providing infrastructure services for the Polkadot/Substrate community. We just launched our beta version of a shared node API Service and are already listed in the Polkadot.js app. This service expands on our core mission - to support all blockchain developers in the world by providing core infrastructure so they can focus on building the next dApp.

Setting up blockchain infrastructure is difficult and time consuming, and requires a level of server development expertise that many don’t have. We're applying for funding for the ongoing costs of our free public API service for Polkadot so that everyone can access a public pool of managed Polkadot nodes.

**This funding grant is for the ongoing running costs of this pool of Polkadot nodes for Q1 2021 (January/February/March) - this will be proposed again every three months. These costs are currently estimated at USD $1,101.60 a month**

**More Info**
- We just served over 3.2 million requests in a single day on the 6th of January 2021 to our free API service
- There is an additional separate funding grant for improvements to the API service that further scale the service. The details of this future grant are here.
- We’ll maintain our free tier for users of 500,000 requests a day while funds to run these nodes remain. This is so we can maintain and ensure that Polkadot is accessible by all, from the largest and most funded development teams, to the many amateurs tinkering away.
- In the future, we may provide additional paid tiers of API Service usage above those 500,000 daily requests at different costs structures
- We’ll maintain the [one click deploy dedicated node](https://onfinality.io/dedicated_nodes) access to Polkadot for customers that need more than what our API service is intended for
- You can access our public API service by[ creating a free account for our admin portal](https://support.onfinality.io/hc/en-us/articles/900004222183), or by connecting to it using [Polkadot.js](https://polkadot.js.org/)

You can read more on this treasury funding proposal at [https://docs.google.com/document/d/10u47lMl_uuDHPL18rzfHn8F3Yt3_mT5B2guqqQUUl04/edit?usp=sharing
](https://docs.google.com/document/d/10u47lMl_uuDHPL18rzfHn8F3Yt3_mT5B2guqqQUUl04/edit?usp=sharing)

You can also read about our funding proposal for the improvements to the scalability of our service [here](https://polkadot.polkassembly.io/post/218).

Additionally, you can talk to us on Telegram at [t.me/onfinality](t.me/onfinality)

Treasury Proposal - High Performance Public Infrastructure (Ongoing Costs for Q1 2021)

- OneBlock wants to organize a Hackathon for Substrate developers in China.
- They are seeking 5786 DOTs from the Polkadot treasury to fund the event.
- The Hackathon will last 30 days online and include 2 days for offline presentations.
- OneBlock is a big community that helps teach people about blockchain technology and has trained many developers.
- The Hackathon aims to help developers turn their ideas into real projects using Substrate and Polkadot technology.
- Different teams can compete, and there will be sharing events to help developers learn more.
- The winning projects will be evaluated based on their business value, completion, innovation, and technical difficulty.

Proponent: 15UkSSYN7pkPSdiHSzjeMZSi1sKmukCkijFrZ8aWaKudCwZV

Proposal date: 29.12.2020

Requested DOT: 5786

OneBlock hopes to organize and host a top-quality Hackathon event for Substrate developers and like to get financial sponsorship from the Polkadot treasury. It plans to attract Substrate technology enthusiasts in China to develop and showcase their cool ideas of the Polkadot ecosystem projects and build more high-quality projects based on Substrate, in order to enrich the Substrate and Polkadot ecosystem.

**We are asking for a one-time payment of 5786 DOTs to hold the Substrate Hackathon（30days online Hackathon + 2days offline Demo Day）for polkadot ecosystem.

We will hold the hackathon in Q1 of 2021.**

### Our plan of the Substrate Hackathon are as below:

**1.Background introduction:**

OneBlock is one of the earliest and largest blockchain developer communities in China. It is a technical education community for Chinese blockchain technology enthusiasts and developer users. It provides systematic technology-related original content, live broadcasts, and professional courses and offline workshops which allow blockchain technology developers to obtain knowledge about blockchain technology in the easiest, most convenient, and nearly zero-cost way. At present, the community has gathered technology enthusiasts from Google, Facebook, UIUC, Oracle, Microsoft, Peking University, Tsinghua University, BAT and other Chinese and American higher institutions and has trained 8,000 international blockchain technology talents for the global blockchain industry.

At the same time, OneBlock is also Parity’s operating partner in China and the exclusive partner of Substrate technology development courses. It is committed to popularizing Substrate technical knowledge and cultivating Substrate ecological developers. OneBlock sent 24 teams to participate in the first official hackathon of Kusama and Polkadot ecology from June to August this year, and one team successfully won the second prize.

Since its establishment in 2018, OneBlock has launched 6 Substrate development courses, and cultivated more than 500 Substrate technology developers. Most of the founders, CTOs, and core developers of the early Polkadot ecological projects are from OneBlock. In the future, OneBlock will continue to support Substrate ecological developers and entrepreneurs, continue to explore and help high-quality Substrate ecological projects, so as to promote the development of China's Substrate technology ecosystem.

**2.What issue will the treasury funds tackle**

Two aspects: 2.1 Regarding the Polkadot ecology, although Polkadot is already a well-known project in China, most developers know little about how to deeply participate in Substrate-related technologies and the Polkadot ecology, what individuals or teams can do and how to do it based on Substrate/Polkadot. In addition, there are not many innovative projects in Polkadot ecology, and the growth rate is not up to speed. 2.2 Regarding developers in the current ecosystem, OneBlock discovered a problem from the existing Substrate technical courses: In each course, OneBlock has nearly 100 developer students who have completed the Substrate development technology course, but they cannot effectively transform the theoretical knowledge learned through the 1-month online course into a practical project that can be implemented. Through feedback from some graduate students, OneBlock hopes to increase the practical competition after the course and encourage the students to form teams for practical projects.

Therefore, OneBlock proposes to hold a Hackthon at the end of the Substrate course in 2020. This would allow the developers to convert the Substrate knowledge learned in the course into creative ideas and ideas, and actually implement these ideas with formed teams through a real Hackathon. This will guide students of Substrate technical courses to actively participate in the development of Substrate ecological projects and gain practical development experience.

OneBlock hopes to combine theoretical knowledge courses with practical challenges to inspire developers to create more innovative and interesting products for the Substrate ecosystem, contribute to the Substrate technology, and ultimately deliver high-quality projects to W3F and Web3 training camps.

**3.What is the proposed solution?**

**3.1 Basic information** about the Hackathon From November 2020 to February 2021, OneBlock will launch Substrate Hackathon through a combination of online and offline forms. The theme of this Hackathon is Substrate and Polkadot related technology. We will allow Substrate developers and Substrate technical course graduates to hack up on their brilliant ideas. This is just the first step: OneBlock plans to continuously organize and host Hackathons in different cities in China to source and promote the coolest Substrate hacker natoin-wide non-stop!

**3.2 Theme: **Substrate Ecological Hackathon Sunrise This is the first hackathon event of Substrate ecology in China. Get ready to build tools, Dapps, etc. based on the Polkadot ecology, and use your unique creative problem-solving skills! At the same time, as the final examination of the Substrate technical course, everyone can fully practice the technical knowledge learned in the course and complete their graduation works. Together, we can contribute to a fair, secure, and adaptive Web3.0. China's largest Substrate developer competition event, Polkadot eco-entrepreneurs and geeks gather in Hangzhou/Shanghai Sufficient preparation time of 30 days online + 48 hours offline hack challenge, there is plenty of room to shine

**3.3** Targeted developer groups Teams who want to create projects based on Substrate and solve real-world problems Teams who want funding, technology, community support and incubation Teams with experience in the development of blockchain projects based on Ethereum / EOS Those who have skills in blockchain development, front-end development, Dapp development, design, operation, business, etc. and are interested in innovation

**3.4 Competition Format:** A team of 1-5 people can participate in the competition, you can form your own team first, or you can register first and form team online later Questions will be announced 30 days before the game to allow for preparation, 48 hours of live Hack 15-minute final results display, score consists of the judges’ votes (80%) + on-site hacker votes (20%)

**3.5 Technology sharing and Q&A:**

SubShare online sharing In order to help Chinese developers and users better understand the ecology of Substrate and Polkadot, OneBlock will carry out a series of related online live sharing activities. Four events will be organized during the competition. Speakers range from KOLs such as the ecological project CTO and the Substrate course ambassador. They are a group of strategists and developers who truly love and hope to contribute to parachains and bridges. They will organize and share what they have learned. In addition, OneBlock will also organize the content into videos and articles after each sharing event and publish them on the public accounts on wechat, bilibili and Top10+ blockchain media platforms, so that more people can understand the Substrate ecology.

Offline Sub Workshop Sub Workshop is a technology sharing column provided by OneBlock and Parity engineers to provide cutting-edge technology introduction and technology concept sharing to developers. Sub Workshop provides developers with professional technical guidance, helping developers to gradually solve the technical difficulties of Substrate in Hackathon, so as to achieve successful project development.

Online Q&A Sub Office Hour The Q&A live broadcast is aimed at the specific questions that developers have during the development process. It collects the problems encountered by the developers during the project development process through the community, and answers them through Sub office Hour.

Technical article output Sub Article In the process of providing technical guidance and sharing to developers, OneBlock will precipitate valuable technical topics and produce technical articles for developers. These articles will be uploaded to social media to attract more Substrate developers.

**3.6 Competition Categories：** This hackathon is open to individuals and teams and is divided into three main categories: Construct tools based on the Polkadot ecology: Use Substrate to build the Polkadot ecological tools, enrich the infrastructure of the Polkadot ecology, and provide a foundation for the construction of DAPP. Build DAPP: Use Substrate to build a creative DAPP based on Polkadot or Polkadot ecological parachain Open Hack: Try everything possible! Be creative and carry out disruptive innovations that will surprise us. Entries can be about test suites, visualization, Wasm interoperability, etc. Anything is possible.

**3.7 Expected recruitment scope Publication viewers: **10,000+ developers Registration link clicks: 6000+ Final successful enrollment: 100 Substrate developers

**3.8 Publicity channels and methods：**

a. Establish multiple channels for simultaneous promotion OneBlock’s own channel promotion China's TOP10 media partners and community assisted promotion Form a team of course ambassadors to assist in the promotion Partnership with China's major university blockchain association

b. Create multiple forms of publicity Course introduction poster Article Online live sharing Offline workshop

c. Expected scope of recruitment Publication viewers: 10,000+ developers Registration link clicks: 6000+ Final successful enrollment: 100 Substrate developers

**3.9 Scoring dimensions：** All entries will be scored in the following four dimensions: Business value (40%): solve problems and have business prospects Completion (20%): The code has implementation logic, not just a concept Innovative (20%): creative and breakthrough Technical difficulty (20%): The technology used has a certain threshold

The specific execution plan must have clearly executable and quantifiable milestones Important process and time node arrangement: Team registration period: January 10th-February 20th Online Co-coding Period: January 10th-February 17th Preliminary selection shortlisted time: February 18th-February 19th Offline Hack and review time (offline): February 20-February 21 Winner announcement time: Based on the judgement of the on-site jury and Hackers’ vote, the winners will be announced on February 21st. The amount of DOT needed from the treasury: propose a reasonable amount of DOT based on your quantifiable milestone

### Here is our budget plan:
https://docs.google.com/document/d/1AilrLogHhsx60mqD_aAhQBUIorkVDsUD5MWqiVYAUkA/edit?usp=sharing

Please contact us if you have any questions: [yaxunchen1995@gmail.com](url)

@Oneblock Substrate Hackathon Proposal

- A group called "16iPbcL3NrdYWNVZ8uYmonmBuVmuSbbQLL5ECBvDxcSNyLPT" wants to be in charge of a new project on Polkadot.
- The team includes four experts: Bette Chen, Katie Butler, Iggy Albero, and Kaye Han.
- They all have a lot of experience in branding and design for technology.
- There is no money reward for this project, just a small fee of 1 DOT.
- This is the first time a bounty is being offered on Polkadot.
- The proposal is open for voting for 6 days.
- The team believes they are the best choice because of their skills and knowledge.

curator

This motion proposes `16iPbcL3NrdYWNVZ8uYmonmBuVmuSbbQLL5ECBvDxcSNyLPT` as curator of the band bounty funded this week.   

The candidacy, a multisig composed by **Bette Chen** (co-founder of Acala and lead of Product design), **Katie Butler** (Marketing director of Moonbeam) **Iggy Albero** (the designer behind the current Polkadot and Kusama’s brand) and **Kaye Han** (head of marqomms division), was proposed by Katie this week based on the parties’ expertise and experience with the brand. 

  While no reward is expected for the effort, the motion is opened with a 1 dot fee for the curator to showcase the bounty mechanism, being this the first bounty on Polkadot. **The motion will be up for vote for 6 days, please everyone vote at your convenience.** The bounty’s scope of work can be found [here](https://polkadot.polkassembly.io/motion/50). 

-------

Katie's msg submitting the multisig candidacy below, shared on Direction Channel in on 30.12.2020:

"Hello Council members!

For Polkadot's first-ever bounty, proposed by Koto Studio, we are excited to present our candidacy as the bounty curator. As outlined in the proposal, the final deliverables must take into consideration the wide-ranging perspectives of the Polkadot community. Thus, we believe this proposal is best served by a multi-sig curator composed of individuals with professional brand development expertise and deep roots in the Polkadot ecosystem. Here is a brief on the individuals that are part of this proposed multi-sig:

**Bette Chen, co-founder of Acala and Laminar**, leads product design and development on token economic models. Bette has decades of experience in product management and has led her teams to much success in the Polkadot ecosystem and blockchain industry at large.

**Katie Butler is the Director of Marketing at PureStake & Moonbeam**. She is responsible for leading her team on marketing and communications for the smart contract parachain. Prior to Moonbeam, Katie gained extensive experience in a wide range of technology companies.

**Iggy Albero, from Web3 Foundation**, is the designer who created Polkadot's beloved logo and many other brand assets. Iggy also designed the Kusama brand and has worked on many design projects with a focus on visualising blockchain concepts, technology, and data.

**Kaye Han, from Parity Technologies**, heads the marcomms division whose design, marketing, and web teams deeply interact with the Polkadot brand on a daily basis. Beyond the blockchain space, Kaye has worked with global brands such as IDEO, Nike, Starbucks, and more.

While no reward is expected for our efforts on this historic bounty proposal, to showcase the power of social coordination on a blockchain network, we propose a symbolic 1 DOT as the curator fee. We believe this bounty is a huge milestone for Polkadot and hope that our expertise, experience and enthusiasm presents us as a great candidate.

**Mutli-sig Address:** 16iPbcL3NrdYWNVZ8uYmonmBuVmuSbbQLL5ECBvDxcSNyLPT" 

-------

The 1st bounty curator: proposing 4 parties multisig as curator for the Polkadot Brand Update Immersion Phase bounty

- A decision is being made about a project on the Polkadot Network.
- Koto Studio proposed a plan to help rebrand Polkadot.
- The rebranding aims to meet the changing needs of Polkadot.
- Koto worked with W3F to make the proposal better.
- They want to use new ways to make business on a decentralized internet.
- The first step of the project is called "Immersion".
- More details about the project can be found in a document linked in the proposal.

This motion approves/rejects the first bounty on Polkadot Network. 

[Koto Studio](https://koto.studio/) submitted the proposal to develop the first phase (immersion) for a Polkadot rebrand strategy, aiming to meet the network’s evolving needs by leveraging the input and insights from various stakeholders across the ecosystem. Koto consulted W3F before structuring the proposal, and decided to use on-chain governance, treasury, tokens, and the blockchain network as a novel approach that sparks imagination of how business can be conducted on a decentralised internet. 

The scope of the bounty covers the first phase of the strategy: **Immersion** (more info on tasks to be developed can be found in the document below). A full description of the bounty by Koto can be found [here](https://www.dropbox.com/sh/7nwymn0rs42tjtp/AACSntxUFdJdOoRQl9GTJA2Oa?dl=0&lst=).



The First Polkadot Bounty: Polkadot Brand Update Immersion Phase For a Rebrand Strategy

- Europa is a special environment for developers to test and improve a program called Substrate Runtime.
- It helps in finding mistakes in a type of contract called the `ink!` contract.
- Europa makes it easier to run and check certain operations by offering important services.
- The team is working on improvements for more helpful error messages and better debugging tools.
- They plan to create better ways to see what happens when a contract runs, like tracking errors and execution steps.
- Their future updates will make the debugging experience smoother and connect better with other tools.

This is copy from https://polkadot.polkassembly.io/post/189
 
Github: https://github.com/patractlabs/europa

Europa is a sandbox environment that runs `FRAME Contracts pallet`, and it is also a framework that provides a sandbox environment for Substrate Runtime. Therefore, developers can use the executable files compiled by Europa to debug the `ink!` contract, and they can also use the library provided by Europa as a framework to implement a sandbox environment for the Runtime in their Substrate project.

Europa provides the minimal service components that support Runtime to package and execute transactions normally. Therefore, although Europa can be regarded as a chain node, this node has no consensus system, no network connection, and only retains the Runtime executor, RPC and some other necessary services. In addition, as a WASM contract running sandbox, we modified `FRAME Contracts pallet` to provide more detailed debugging information, including contract execution process information (in `FRAME Contracts` layer) and WASM execution information (in WASMI execution layer).

In order to facilitate debugging and add new features, Europa removed all WASM components in Substrate, so any `std` code can be added to the entire system of Europa to meet experimental requirements.

## Europa's Future development plans

~~v0.1: Have an independent runtime environment to facilitate more subsequent expansion directions.~~

v0.2: Modify at `FRAME Contracts pallet` level to provide more information。

v0.3: Improve the development experience, strengthen collaboration with other tools, and extend the sandbox to be compatible with other runtime modules。

We submitted a proposal for [Europa v0.1](https://polkadot.polkassembly.io/post/102) two months ago, and wrote the [treasury report](https://polkadot.polkassembly.io/post/166). In v0.1, Europa has completed the basic framework of the Runtime sandbox, removed unnecessary modules related to the chain, removed the functional components of WASM, and provided many necessary tool components as a sandbox.

## Detailed design of Europa v0.2

### 1. Fork `FRAME Contracts Pallet` to provide more debug information

Although `FRAME Contracts pallet` has been iterative, its error messages are not friendly to contract development. Although in Substrate's [Commit #6773](https://github.com/paritytech/substrate/pull/6773) and [Commit #7017](https://github.com/paritytech/substrate/pull/7017), the error handling of contracts has been improved a lot, but these error messages are mainly concentrated in the `FRAME Contracts pallet` layer, missing a lot of error information about WASM execution layer. For example, WASM execution crash errors or out-of-bounds errors do not have detailed information. For example, this part of the code in Substrate [`frame/contracts/src/wasm/runtime.rs:LL367`](https://github.com/paritytech/ substrate/blob/master/frame/contracts/src/wasm/runtime.rs#L367)

```rust
		// Any other kind of a trap should result in a failure.
		Err(sp_sandbox::Error::Execution) | Err(sp_sandbox::Error::OutOfBounds) =>
			Err(Error::<E::T>::ContractTrapped)?
	}
}
```

As shown above, because `sp_sandbox::Error` only provides three types of errors, and these error types do not contain more detailed reasons for this error. For example, developers only know that it is an execution error of `Execution` and an out of bounds error of `OutOfBounds`, And all have been converted into `ContractTrapped`. Therefore, the reason for the internal crash of the contract cannot be known to the outside world. In our fork development of `FRAME Contracts pallet`, we will supplement and perfect this short board.

In the execution environment of the contract `wasmi`, all error messages are discarded. For example, in this part of the code in Substrate [`primitives/sandbox/with_std.rs:L287`](https://github.com/paritytech/substrate/blob/master/primitives/sandbox/with_std.rs#L284), The information of `_err` of `Err(_err)` is discarded.

```rust
match result {
    Ok(None) => Ok(ReturnValue::Unit),
    Ok(Some(val)) => Ok(ReturnValue::Value(val.into())),
    Err(_err) => Err(Error::Execution),
}
```

Although the `debug_message` field is provided in the contract RPC call `contracts_call` to provide the function of returning more information before the formal execution in the future, more detailed information still needs some customized development to provide. For details, please refer to the discussion in [ink! issue #589](https://github.com/paritytech/ink/issues/589#issuecomment-731745755). Therefore, the developers cannot well know the error information in the current `FRAME Contracts` layer and the `wasmi` interpretor during the execution of the contract.

On the other hand, when a contract calls a contract, the current `FRAME Contracts pallet` cannot tell the developer which layer of the contracts has a problem. In other words, there is no `Contract Stack trace` information about the execution process of the contract in the `FRAME Contracts pallet`.

In addition, as a tool for contract debugging, the contract module lacks a lot of display for internal execution information, such as displaying the value of the `selector` called by the current contract and the parameters passed by the contract. On the other hand, we can count the gas consumption of the contract calling the contract (not the gas consumption of a single contract, but the gas consumption during the execution), and the number of times of reading, writing, storing, and accessing other interfaces.

### 2. 2. Provide log printing during contract execution

Developers need to know some variables or information during the execution of the contract. The easiest way is to print logs during the contract execution. 

For printing logs information, currently `seal_println(_ctx, _ptr: u32, _len: u32)` is provided in `FRAME Contracts pallet`, and `::ink_env::debug_println()` is provided in `ink!`. This group of functions plus `ink_prelude::format!` can be combined into a feature similar to the `println!` macro in rust to print information to the console. Therefore, after the debugging switch (flag) of the contract is turned on, the following printing can be provided:

```rust
let s = ::ink_prelude::format!("print in contract:{}", 1_u32);
::ink_env::debug_println(&s); // == println!
```

Set `log=runtime=debug`, then start the node, You can see the logs:

```bash
Dec 01 20:02:13.307 DEBUG execute_block:apply_extrinsic: print in contract:1    {ext}
```

The logs printed  in the node by this method are all DEBUG level, and the `target` of the logs are all `runtime`. But compared with `println!`, the existing `log` crate in Rust provides the function of printing logs at different levels (like DEBUG|INFO...), and can use the `target` to filter the log, so the usage of `log` in debugging contracts is more powerful than `println!`.

We hope to provide the following functions in the contract by modifying `FRAME contract pallet` and `ink!` or providing other additional libraries:


```rust
impl Erc20 {
	/// Creates a new ERC-20 contract with the specified initial supply.
    #[ink(constructor)]
    pub fn new(initial_supply: Balance) -> Self {
        use log::{info, trace};
        info!(target: "contract1", "it's info log: {}", initial_supply);
        trace!(target: "contract1", "it's trace log: {}", initial_supply);
        // ...
    }
}
```

After you executed the contract, you can see the logs in node:

```bash
Dec 01 20:02:13.307 INFO contract1: it's info log:123    {ext}
Dec 01 20:02:13.307 TRACE contract2: it's trace log:123    {ext}
```

### 3. Fork `wasmi` interpreter to provide `Backtrace` functions etc.

As a WASM interpreter built by parity, `wasmi` has implemented all the standard functions of WASM. But for contract developers, the execution process of `wasmi` is similar to a black box. The contract developer only knows that the contract is executed by the `wasmi` interpreter after deployment, but cannot know the execution status of the contract in `wasmi`. If you encounter a crash such as `panic`, `wasmi` does not retain the current context and cannot report back the situation in the `function stack`. On the other hand, WASM does not currently provide a good breakpoint debugging and Single-step debugging method, so it is not possible to interrupt during WASM execution to view the information during execution.

Therefore, we plan to fork `wasmi` and provide functions similar to `Backtrace` information. **We may also add Breakpoint Debugging in the future**

In the customized `HardHat EVM`, abnormal [`stack traces`](https://hardhat.org/hardhat-network/#solidity-stack-traces) will be printed during the execution of the Solidity code:

> ```text
> Error: Transaction reverted: function selector was not recognized and there's no fallback function
>   at ERC721Mock.<unrecognized-selector> (contracts/mocks/ERC721Mock.sol:9)
>   at ERC721Mock._checkOnERC721Received (contracts/token/ERC721/ERC721.sol:334)
>   at ERC721Mock._safeTransferFrom (contracts/token/ERC721/ERC721.sol:196)
>   at ERC721Mock.safeTransferFrom (contracts/token/ERC721/ERC721.sol:179)
>   at ERC721Mock.safeTransferFrom (contracts/token/ERC721/ERC721.sol:162)
>   at TruffleContract.safeTransferFrom (node_modules/@nomiclabs/truffle-contract/lib/execute.js:157:24)
>   at Context.<anonymous> (test/token/ERC721/ERC721.behavior.js:321:26)
> ```

In `wasmtime`, when the inside execution of `panic` appears, similar output will be printed:

```text
Error: failed to run main module `target/wasm32-unknown-unknown/debug/bt.wasm`

Caused by:
    0: failed to invoke command default
    1: wasm trap: unreachable
       wasm backtrace:
         0: 0x1cda - <unknown>!__rust_start_panic
         1: 0x1cce - <unknown>!rust_panic
         2: 0x1c9e - <unknown>!std::panicking::rust_panic_with_hook::hc5713da015ebaa19
         3:  0x26e - <unknown>!std::panicking::begin_panic::{{closure}}::h8e62ab0ea555186f
         4:  0xfba - <unknown>!std::sys_common::backtrace::__rust_end_short_backtrace::h34a944558df1326a
         5:  0x15c - <unknown>!std::panicking::begin_panic::h03c636dac2b8fb70
         6: 0x1a65 - <unknown>!_start
```

In `wasmer`, when the inside execution of `panic` appears, similar output will be printed:

```text
error: failed to run `target/wasm32-unknown-unknown/debug/bt.wasm`
│   1: RuntimeError: unreachable
           at __rust_start_panic (bt.wasm[67]:0x1cda)
           at rust_panic (bt.wasm[66]:0x1cce)
           at std::panicking::rust_panic_with_hook::hc5713da015ebaa19 (bt.wasm[65]:0x1c9e)
           at std::panicking::begin_panic::{{closure}}::h8e62ab0ea555186f (bt.wasm[2]:0x26e)
           at std::sys_common::backtrace::__rust_end_short_backtrace::h34a944558df1326a (bt.wasm[36]:0xfba)
           at std::panicking::begin_panic::h03c636dac2b8fb70 (bt.wasm[0]:0x15c)
           at _start (bt.wasm[55]:0x1a65)
╰─> 2: unreachable
```

In `wasmi`, when the inside execution of `panic` appears , only the following output will be printed:

```text
thread 'main' panicked at ': Trap(Trap { kind: Unreachable })', src/bin/instantiate.rs:87:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

Learning from the `HardHat EVM`, `wasmer` and `wasmtime`, we will make similar modifications to `wasmi` to achieve similar functions. We will migrate the relevant code of [`wasmer`](https://github.com/wasmerio/wasmer) and [`wasmtime`](https://github.com/bytecodealliance/wasmtime) to develop similar functions into `wasmi`.

We estimate that we should at least implement the following two parts in `wasmi` in order to provide a printing function similar to `BackTrace` information in `wasmi`:

1. Keep the stack information of the WASM execution stack.
2. Parse the `Name Section` in the `*.wasm` source file with compilation information to provide corresponding debugging information.

## Detailed plan of v0.2 （6 weeks, 30 Nov ~ 11 Jan）：
   
* M1: Fork `FRAME Contracts pallet`. (3 developers \* 2 weeks) *
    1. Enrich the error types of the module, associate more error messages related to the internal `wasmi` interpreter, and attach some context information to the error and print it in the log.
    2. Provide the function of tracking the contract call stack.
    3. Add Event Tracking to the function defined in the `define_env!` macro to provide statistics on contract execution information.
    4. Provide a function to print statistical data of a period of contract execution to the log.
   
* M2: Provide `log` tools and function/macro in contracts. (3 developers \* 1 weeks) *
    1. Provide components similar to `RuntimeLogger` in Substrate Runtime
    2. Provide the corresponding method in `define_env!` of `FRAME Contracts Pallet`
    3. Provide wrapper functions and other functions for `RuntimeLogger` in `ink!`

* M3: Fork `wasmi`. (3 developers \* 2 weeks) *
    1. Investigate the design of `wasmer`, `wasmtime` and `wasmi`
    2. Design and implement functions similar to `Backtrace` for `wasmi`
   
* M4 : Integration and testing  (3 developers \* 1 weeks) *

The above-mentioned forked repos are independent of Europa repo, and the corresponding functions will not be submitted to the original repo. If there are similar functions in the original repo plan, the corresponding functions will be merged after discussion with the original repo author.

## Cost of v0.2 (18 developers \* weeks)

* Operating activities: $3600 ( Rent and Devices: $200 per developer * week )
* Employee payments: $36000 ($1900 per developer * week)
* —————————— +
* Total Cost: $37800
* Exchange Rate: $5.0 / DOT
* Treasury Proposal: 7560 DOT

## Verification : Github source & Treasury Report

1. Construct incorrect contracts and execute logs printing to determine whether it meets expectations
   1. Can trigger all wrong contracts in `wasmi`
   1. Can trigger all wrong contracts in `FRAME Contracts Pallet`
   1. Construct a contract to call a contract example and crash in it
1. Display the call statistics of the `define_env!` interface during contract execution
1. Execute the log printing function, provide formatted printing examples of different data, and judge whether it meets expectations
1. Construct a contract that crashes under different conditions and record the log after execution. Then judge whether the backtrace information of the contract execution is completely printed, and check whether it matches the actual execution of the collapsed contract.


Patract Hub's treasury proposal for Europa (sandbox) v0.2

- This proposal is about creating a mobile app for voting and governance in Polkadot and Kusama networks.
- The app aims to make it easier for users to participate in on-chain governance activities.
- The team led by Hanwen Cheng has experience in building mobile apps and is working with Litentry Technologies.
- The app will allow users to verify their identity, receive notifications about governance updates, and see their voting statistics.
- It will improve participation rates by providing a user-friendly design and relevant information.
- The proposal is divided into four milestones, starting with identity registration and ending with more features like lottery integration.
- The total cost for the first phase is approximately $28,210, requesting 6,132 DOT.

> Note: This treasury proposal is only for **milestone 1**, we list all milestones here only to provide an holistic overview of our vision and better context for understanding our proposed solution.

Proposer: (Hanwen/Litentry) `14zExx2SkY7j9HLeBmuz91o3KfSroSAFRFGNtBnEkYNC492U`

Date: 17.12.2020

Requested DOT: 6132

[Original proposal on GitHub](https://github.com/hanwencheng/gists/blob/master/Litentry/governance-app.md)

[Discussion on Polkassembly](https://polkadot.polkassembly.io/post/217)


**Short description**: Governance-focused Mobile App for substrate-based networks

---

In this proposal, we raise the idea of building a governance-focused app with cross-wallet support, which could encourage the user to take part in various on-chain governance actions and be able to interact with on-chain governance activities in a low friction manner, thus improving the on-chain governance engagement.

## 1. Context of Proposal

Hanwen Cheng was the former product owner of [Parity Signer](https://github.com/paritytech/parity-signer). He has rich experience in building mobile and web applications, also very familiar with Substrate-based tools. Now he is working for [Litentry Technologies GmbH](https://www.litentry.com/), a technology company focusing on building a [cross-chain identity aggregator](https://litentry.medium.com/why-we-need-cross-chain-identity-on-polkadot-d59a90c9329c), which includes the substrate-based networks and related tools. The team has solid substrate development experience and specialization in mobile engineering.

Aggregated identity means an identity linked with accounts from different blockchains and off-chain applications/services, which represent the owner behind the accounts, and further present the owner's credibility and reputation in various aspects. 

In this proposal, we present a governance app. It could 

* facilitate the governance process by lowering the participation friction
* increase user engagement by providing clear UI/UX for interactions 
* allow users to subscribe to remote **Push Notifications** for relevant topics
* provide richer information related to the identity across different substrate-based chains
* serve as a basis for more incentive mechanisms

*Polkadot* currently employs *Phragmén Method* to equalize stake holder's voting power in elections. In our eyes, we see a future where the reputation of identity also plays a vital role in calculating the voting power of elections.

## 2. Problem statement:

There are currently a few issues when it comes to on-chain governance on *Polkadot* and *Kusama*:

1. Low Voting Participation Rate: Currently, the on-chain governance participation rate is quite low, even in the case of controversial decisions (such as  *Kusama* redenomination, in which only about 10% of stakeholders participate in the vote).

2. Missing Identity Governance Stats: When voting for the council members, it is hard to know who, from all councilors, has made the most contributions to the ecosystem and who has participated the most in the discussions. Currently, there is no dashboard to show on-chain governance stats of identity. Also, on [Polkadot.js Apps](http://polkadot.js.org/apps/) and [Polkassembly](https://polkadot.polkassembly.io/), the identity tooltip is limited to certain fields. Therefore richer information is needed to be shown when users browse and participate in governance. Opensquare has made a [proposal](https://kusama.polkassembly.io/post/352) on *Kusama* about the treasury reputation recording system, and this system is currently in the web app side.

3. After investigating the wallets listed on https://wiki.polkadot.network/docs/en/build-wallets, currently only [Polkawallet](https://polkawallet.io/) natively supports for governance module. The rest wallets either use integrated governance DApp in a WebView, or do not even have governance module integration at the moment. Furthermore, each mobile app has its own governance UI. The engineering power is wasted and lacks interoperability.

Imtoken |  Math Wallet | Polkawallet
:-------------------------:|:-------------------------:|:---|
![imtoken](https://raw.githubusercontent.com/hanwencheng/gists/master/Litentry/imgs/GovernanceImtoken.jpeg)  |  ![mathwallet](https://raw.githubusercontent.com/hanwencheng/gists/master/Litentry/imgs/GovernanceMath.jpeg)| ![polkawallet](https://raw.githubusercontent.com/hanwencheng/gists/master/Litentry/imgs/GovernancePolkawallet.jpeg)

4. Current state of *Polkadot.js Apps* is mostly catered for experienced users or developers. Besides, it exposes low-level APIs to interact with substrate-based blockchains, which introduces frictions for end-users to interact. 

5. There is no mobile application that could relay the transactions from other wallets on the *Polkadot* ecosystem. And only a few mobile wallets like *Parity Signer* and [Math Wallet](https://mathwallet.org/) could sign the transactions from *Polkadot.js Apps*. The wallet ecosystems are relatively closed.

6. When Council submits emergency proposals, councilors must view and react to the proposals in a timely fashion, but there is currently no efficient way to notify the councilors in case of emergency proposals. This is especially challenging since councilors are in different time zones.

## 3. Proposal Objective/solution/s:

### Objective

We want to create a governance mobile application that could:

1. Offer native governance support integration and Polkassembly off-chain discussion.
2. Improve user engagement by allowing them to receive and customize **Push Notification** of governance-related updates.
3. Provide participants with good governance statistics and gamification scores to incentivize users to join governance.
4. Provide the option to notify App users (in the form of **Push Notification**) for emergency proposals. The notification itself can be customized with a basic ruleset (e.g., users who logged in as Councilors or Technical Councilors members in case of a proposal have to be processed urgently)

|Current Governance Ecosystem| Targeting Governance Ecosystem|
|-------------------------|-------------------------|
|![imtoken](https://raw.githubusercontent.com/hanwencheng/gists/master/Litentry/imgs/governanceBefore.png)|![mathwallet](https://raw.githubusercontent.com/hanwencheng/gists/master/Litentry/imgs/governanceNow.png)|

### Solutions / Milestones

#### Milestone 1: Integrate identity registration
1.1 Offer user the capability to verify Identity (e.g., email, riot) in App.
1.2 Provide a registrar service to verify the submitted identity automatically.
1.3 Display a basic dashboard of governance-related activities for this identity
1.4 Display Identity registration Status on *Polkadot*/*Kusama*.

#### Milestone 2: On-chain governance basic support
2.1 Support native governance actions on *Polkadot*/*Kusama* with good information hierarchy and UX/UI.
2.2 Allow users to subscribe to governance-related updates via Push Notification to improve engagement. (e.g., when a new proposal is up, or it is either being accepted or rejected.)
2.3 Build further on a governance dashboard, allowing the user to see governance-related statistics of any Account. (e.g., if a user is browsing a proposal and wants to learn more about the **proposer**)
2.4 Support role-based Push Notification subscription of a certain type of on-chain events.


#### Milestone 3: Identity Dashboard and customization
3.1 Allow users to customize further **Push Notification** settings to receive the tailored governance-related digest.
3.2 Show identity on-chain governance states on *Polkadot*/*Kusama*.(Extends on Openquare's treasury [reputation data](https://kusama.polkassembly.io/post/352))
3.3 Allow users to participate in discussions from Polkassemby natively in app.
3.4 Further enrich governance dashboard's data of an Identity from different chains.
3.5 Interact with other wallet app and sign the transactions with inter-app communication (work together with WalletConnect [Specification v2](https://docs.walletconnect.org/v/v2.0.0-alpha/tech-spec)).


#### Milestone 4 Governance Score and Lottery integration
4.1 Be able to do on-chain governance actions on different networks.
4.2 Build further on Push notification touchpoint to increase engagement
4.3 Build further on the main dashboard to highlight important proposal or event for the community
4.4 Integrate substrate [lottery](https://hackmd.io/68rduBydTEy4X-ULevd90g) support.

### Network Benefit

* Have more users share their voice on important elections. (`vote`)
* Encourage users to register on-chain identity. (`identity`, `setIdentity`, `requestJudgement`)
* Have users change/update their validator nominations on a regular schedule. (`nominate`)
* Encourage brainstorming of ideas in future updates and changes (`propose_bounty`)
* Encourage user to use tipping system (`tip`, `reportAwesome`)
* Have more users (change their) backing of (candidate) council members (`electionPhragmen`, `vote`)
* Encourage users to use lottery modules and join vote (`buy_tickets`, `vote`)
* Encourage users to join the off-chain discussion on Polkassembly.

## 4. Why Polkadot Network.

The governance on *Polkadot* affects most users, and it is of the most important features among all substrate-based networks.

The technical implementation does not have much difference when we compare *Polkadot*/*Kusama* or Substrate-based networks. So we are doing the work firstly on *Polkadot* and *Kusama*, and then it will be further extended to all the substrate-based networks.

 ## 5. Payments and Conditions
 
 The total estimate time is 438 hours, estimated with 1 designer and 2 developers in mind. In the case of discrepancies of our time estimate (either over or underestimate), we will be revising it in future milestones.
 
 It is calculated with an hourly rate of 70 USD/hour and using DOT 5 USD/Unit as a reference for the total dollar value of 28210 USD.
 
There are 4 milestones in total, and the detailed information of each milestone is listed in the table below,

| Milestone | Task                                                                                                                                           | Research/Design (Hours) | Development (Hours) | Total (Hours) | DOT (Unit) | Dollar Value |
|-----------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|---------------|------------|--------------|
| 1.1       | Design Register Backend (BE) to be able to verify Email, riot, and Twitter data                                                                | 6                       | 16                  | 22            | 308        | 1540         |
| 1.1       | Implement in BE of chain monitoring on identity events                                                                                          | 4                       | 4                   | 8             | 112        | 560          |
| 1.2       | Implementation of submission of judgment based on the verified result                                                                           | 5                       | 16                  | 21            | 294        | 1470         |
| 1.2       | Add database layer to BE to persist processed verification                                                                                     | 0                       | 12                  | 12            | 168        | 840          |
| 1.3       | Able to scan address from different source and display its Identity data (e.g. Judgment status)                                                | 6                       | 10                  | 16            | 224        | 1120         |
| 1.3       | Support signing Tx with QR code (integration with Parity Signer and other offline wallets)                                                     | 3                       | 12                  | 15            | 210        | 1050         |
| 1.4       | Design UI/UX to allow user submit identity Info (via forms)                                                                                    | 2                       | 8                   | 10            | 140        | 700          |
| 1.4       | Allow user to request judgment and display its status                                                                                          | 6                       | 12                  | 18            | 252        | 1260         |
|           |                                                                                                                                                |                         |                     |               |            |              |
| 2.1       | Design Information hierarchy of governance and implement corresponding UI/UX                                                                   | 6                       | 16                  | 22            | 308        | 1540         |
| 2.2       | Implement BE infrastructure to be able to send Push notification to device                                                                     | 4                       | 12                  | 16            | 224        | 1120         |
| 2.2       | Implement in App to receive and process Push notification content                                                                              | 6                       | 16                  | 22            | 308        | 1540         |
| 2.3       | Build further on governance dashboard with more information                                                                                    | 8                       | 16                  | 24            | 336        | 1680         |
| 2.3       | Provide detailed screen of the certain proposal and user can see in app directly more identity-related information of *Proposer*               | 4                       | 16                  | 20            | 280        | 1400         |
| 2.4       | Design and implement Setting pages for Push notification based on user roles.                                                                  | 6                       | 16                  | 22            | 308        | 1540         |
| 2.4       | Handle remote navigation when remote Push Notification came in App (Navigate to proper screen)                                                 | 3                       | 10                  | 13            | 182        | 910          |
|           |                                                                                                                                                |                         |                     |               |            |              |
| 3.1       | Design more granular level of Push notification for user to receive, e.g, only receive when a proposal is proposed                             | 5                       | 16                  | 21            | 294        | 1470         |
| 3.1       | Build UI/UX in app to allow the user to customize which Push notification should be received                                                   | 2                       | 12                  | 14            | 196        | 980          |
| 3.2       | Integrate on-chain governance state (Extends from Opensqares proposal)                                                                         | 3                       | 8                   | 11            | 154        | 770          |
| 3.3       | Build UI/UX to integrate Polkassembly functionalities in App                                                                                   | 6                       | 12                  | 18            | 252        | 1260         |
| 3.4       | Connect different sources of on-chain governance data from different chains                                                                    | 6                       | 10                  | 16            | 224        | 1120         |
| 3.5       | Support WalletConnect protocol as a signing method                                                                                             | 3                       | 12                  | 15            | 210        | 1050         |
|           |                                                                                                                                                |                         |                     |               |            |              |
| 4.1       | Support more native on chain governance related actions                                                                                        | 6                       | 20                  | 26            | 364        | 1820         |
| 4.2       | Build further on Push notification touchpoint with a clear and quick call to action button to participate                                      | 4                       | 12                  | 16            | 224        | 1120         |
| 4.3       | Design main dashboard to be able to highlight on-chain governance-related event by showing countdown or teaser with a prominent call to action | 6                       | 18                  | 24            | 336        | 1680         |
| 4.4       | Design and integrate substrate lottery function in to app                                                                                      | 4                       | 12                  | 16            | 224        | 1120         |
|           | Sum                                                                                                                                            | 114                     | 324                 | 438           | 6132       | 30660        |


Here is the summary of the 4 milestones.

| Milestone   | Research/Design (Hours) | Development (Hours) | Total (Hours) | DOT (Unit) | Dollar Value |
|-------------|-------------------------|---------------------|---------------|------------|--------------|
| milestone 1 | 32                      | 90                  | 122           | 1708       | 8540         |
| milestone 2 | 28                      | 102                 | 139           | 1946       | 9730         |
| milestone 3 | 25                      | 70                  | 95            | 1330       | 6650         |
| milestone 4 | 20                      | 62                  | 82            | 1148       | 5740         |
| Sum         | 114                     | 324                 | 438           | 6132       | 30660        |

**Payment suggestion:**

As the proposal will benefit both Polkadot and Kusama network, we could split the proposal with the payment of both DOT and KSM. For example, we accept payments of milestone 1 and 2 in DOT, and accept payments of milestone 3 and 4 in KSM.


Governance-focused Mobile App for all Substrate-based networks

- The Substrate Developer Academy helps developers learn how to create projects using Substrate and the Polkadot ecosystem.
- The program lasts 6 weeks and includes online lessons, a project internship, and a certification.
- Students will learn to build and launch their own blockchain and decentralized applications (DApps).
- Mentors include experienced professionals from the Polkadot community.
- Scholarships are available for those who can't afford the course fees.
- The academy will track the success of its students and provide reports on their progress.
- Future plans include improvements to the program and offering more scholarships.

**Problem: **There are not enough resources available to developers wanting a more hands-on approach to learning Substrate. In order to see a vibrant Polkadot ecosystem, we must first address education so that developers have the tools to build. 

**Goal: **Create a hands-on and affordable educational environment where developers can learn first hand from existing developers in the Polkadot ecosystem. We want to give developers the tools (education and mentorship) to build the next great DApp or Parachain on Polkadot. While Acala has created the educational framework, we need help ensuring that any qualified developer who cannot afford the Academy will have access to it through a scholarship. 


**How we’ll get there… **

The Substrate Blockchain Developer Academy brings together the best in industry expertise, interactive learning, and a recognized certification program to help developers learn to program and build on Substrate and Polkadot in just 6 weeks. Here’s what developers can expect: 


Hands-on Start a Project from Scratch
Understand the Polkadot ecosystem and Substrate codebase. Use Substrate to develop a product-ready blockchain project.

Code & Launch Your First Blockchain & DApp
Learn blockchain design principles. Learn Polkadot.js SDK. Launch your first blockchain, and build a web3 front-end DApp.

Connect with Global Polkadot/Substrate Developers
Connect with the most passionate, accomplished developers in the Polkadot and Substrate ecosystem, and have access to resources and opportunities from ecosystem projects.


**Mentors/Instructors:**
Bryan Chen -- Co-Founder of Acala and CTO of Laminar
Joe Petrowski - Technical Integrations at Parity Technologies
Ricardo Ruis - Runtime Engineer at Parity Technologies 

**Course Details: **
6 weeks of online, video-based content + 4 weeks of project-based internship
The course is $492 -- this fee covers costs and ensures active participation from students. Crypto is accepted as a method of payment. 

Lecture 0 Preparation
1. Why learning Substrate
2. Intro of Lecturer & Tutors
3. Course overview and how to be successful in this Course
4. Prerequisites & Preparation

Lecture 1 Introduction to Polkadot/Substrate
1. What is Substrate
2. Introduction of Polkadot Ecosystem
3. Setup development environment for Substrate
4. Start testnet and send a transaction
5. Substrate Kitties demo

Lecture 2 Substrate Basics
1. Create multi-nodes network
2. Commonly used Substrate command-line arguments
3. Substrate Architecture Overview
4. Substrate Pallet
5. Project file structure

Lecture 3 Writing Substrate Pallets
1. How to create a Substrate Pallet
2. Substrate macros
cargo expand
decl_module
decl_storage
3. Implement Substrate Kitties
4. Code walkthrough: pallet-assets

Lecture 4 Onchain Upgrade
1. Implement Substrate Kitties Version 2
2. Onchain runtime upgrade
3. Code walkthrough: pallet-sudo
4. pallet-member and pallet-collective

Lecture 5 Data Structures, Testing & Debugging
1. Linked-list data structure
2. Unit test
3. Storage comparison: map / double_map
4. Code walkthrough: pallet-balances

Lecture 6 Install & Integrate with Pallets
1. Use pallet-balances pallet
2. Dependency Injection
3. Events
4. Introduce ORML
5. Integrate with orml-nft

Lecture 7 Advanced Topics
1. Weights mechanism
2. Metadata system
3. SCALE codec
4. Offchain worker
5. Code walkthrough: pallet-im-online

Lecture 8 Production Ready, Cross-chain, Parachain
1. Before go live
Security
Transaction fees
Governance
Compatibility
2. Cross-chain message passing
3. Become a parachain


For more information on the program, visit: https://www.industryconnect.org/substrate-runtime-developer-academy/


**Substrate Developer Scholarships:**
There are developers interested in attending who require financial aid in order to participate. We would like for the Polkadot Treasury to provide scholarships to students so that they can learn the skills it takes to build the next great application or parachain on Polkadot. 

**Financial Commitment: **
643 DOTs

**Your commitment provides:**
Full sponsorship of 6 students into the Substrate Developer Academy

**Scholarship Evaluation Process:**
The Acala team will act as a stand in for evaluating scholarship applicants for this Substrate Developer Academy course and will work with other organizations in the ecosystem to identify developers who are in need of financial support. 

**Criteria for scholarship will be based on: **
Applicant has mastered at least 1 programming language
Applicant has a minimum of one year professional coding experience
Applicant has demonstrated financial need. 

**Payment Conditions:**
A one-time payment of 643 DOTs (monthly average of $4.36 per DOT) 
Should there be any funds that are unused, Acala will roll them over into the next Developer Academy for scholarship purposes. At the request of Council, Acala will return any remaining funds to the treasury. 

**Measuring Success: **
At the end of the program, Acala will report back on the amount of participating developers, graduation rate, projects started/completed, and other unforeseen success metrics (e.g., hires into the Polkadot ecosystem, etc). It is our goal to give developers the tools to build -- and then help them integrate into the ecosystem for collaboration and funding opportunities. 

**Future Plans:**
Acala intends to continue refining and improving upon the Substrate Developer Academy. In 2021, we plan to roll out an updated version of the Substrate Developer Academy -- students will be able to apply for a scholarship directly via a Substrate Academy Bounty Program. 

Substrate Developer Academy Scholarships

slashIndices

This is a motion whose proposer address (12mP4sjCfKbDyMRAEyLpkeHeoYtS5USY4x34n9NMwQrcEyoh) 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