- PolkaWorld wants to make a plan called a **Social Contract** with the Polkadot Treasury.
- PolkaWorld is the first Polkadot community in China and has been running for two years.
- They have helped the community by writing articles and organizing events to teach people about Polkadot.
- Now, they want financial support from the Polkadot Treasury to keep helping the community.
- They are asking for about **1885.98 DOT** for the months of June, July, and August.
- This funding will help them build a strong and fair Polkadot community in China.
- Everyone is welcome to share their thoughts or comments on this proposal!

Awarded

This proposal aims to establish a **Social Contract** between PolkaWorld and the Polkadot Treasury. PolkaWorld is the first Polkadot Chinese community in China. For the past two years, PolkaWorld was running as an independent Polkadot Chinese community funded by Web3 Foundation. We contribute to the Polkadot community by publishing Polkadot related articles (translated from Polkadot Blog/wiki or produce the original content), interviewing Polkadot eco-constructors, and organizing Meetup/Polkadot China Tour /Substrate Workshop and Substrate Hackathon in different cities in China to help people learn Polkadot well and build a strong Polkadot Chinese community!

As Polkadot became a decentralized, on-chain governance network, PolkaWorld would like to apply for funding from the Polkadot Treasury to continue to contribute to the Polkadot community and help build and maintain a strong, decent, and neutral Chinese community!

So this is an open social contract for a 3 months OKR and we apply approx **1885.98 DOT** total allocation for **June**, **July**, **August** depending on EMA(30) AVG rate（DOT = 36.04 usdt） [here](https://polkadot.subscan.io/tools/charts?type=price) and you can get all OKR details [here](https://docs.google.com/document/d/1ocWQuGWJ50JW3y00DG5pZhhZA3_eoIgZnmt07kkEfR8/edit?ts=6062dd8e&pli=1) 

Please feel free to comments!


A Social Contract between PolkaWorld and Polkadot Treasury - Ops and Maintenance proposal

Encode Club helps students learn about blockchain technology. Here are some important points:

- They work with 75 universities around the world.
- Encode Club organizes events like educational programs and hackathons.
- They want to start a new program to involve students in the Polkadot ecosystem.
- The program includes learning series, a special hackathon, and an accelerator.
- They are asking for money in five steps to support their projects.
- The first step needs about £30,000 to help 50 universities and 1000-2000 students.

[Encode Club](https://www.encode.club/) educates, supports and backs the next-generation of university and hacker talent coming into blockchain. We work across 75 universities worldwide. We mainly organise educational programmes, hackathons and accelerators.

After the success of Polkadot's involvement in a recent [Encode Club hackathon](https://medium.com/encode-club/encode-hack-club-polkadot-overview-5689abfa62d0), we would like to extend our work, bring more adoption and new talent to the ecosystem.

We propose a year-long programme to build student involvement in the Polkadot ecosystem, including:

- An education series and curriculum
- A dedicated hackathon
- A dedicated accelerator

Please find more details in our proposal deck, attached [here](https://docs.google.com/presentation/d/1eMwwFDkJS1FrKN1IBD6fuXHrO-bBXpxVrUNOAqt0R4A/edit?usp=sharing).

**Our proposal is split across 5 tranches:**

**For the first tranche, we are asking for 1087.90 DOT** (roughly £30,000) to cover the education series and curriculum. With this first tranche funding, we aim to achieve the milestone of delivering 8 events, with 50 universities participating and 1000-2000 students attending.

There are five tranches in total, these are:

- **Now**: £30k to pay for the education series and curriculum

- **August 2021**: £30k once the education series and curriculum is over to pay for hackathon

- **December 2021**: £30k once the hackathon is over to pay for the accelerator.

- **December 2021** :up to £20k to reward hackers and pay prizes

- **April 2021**: up to £30k to pay grants to the accelerator teams.

All milestone info is in the [deck.](https://docs.google.com/presentation/d/1eMwwFDkJS1FrKN1IBD6fuXHrO-bBXpxVrUNOAqt0R4A/edit#slide=id.gc4baf28d3e_0_847)

Encode Club - university engagement programme - Phase 1 (out of 5)

- OnFinality is a platform that helps people build on the Polkadot blockchain.
- They have a new service called a shared node API, which was recently launched.
- The service helps developers by providing important tools they need.
- OnFinality has recorded over 1 billion requests for this service.
- They offer a free plan allowing 500,000 requests each day for users.
- You can create a free account to use their public API service.
- Their goal is to support all types of developers, from beginners to big teams.

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.

**This funding grant is for the ongoing running costs of two pools of Polkadot nodes for Q2 2021 (April, May, June) - this will be proposed again every three months.**
- These costs are currently estimated at USD $9,714.86 each quarter
- In Q1 2021 we served ([see previous proposal report](https://polkadot.polkassembly.io/treasury/31)):
    - A grand total of 666,946,005 requests over the quarter.
    - A record 31,447,298 daily requests
    - A rolling 7 day average at the end of the Q1 period of 9,441,503 requests each day
- Earlier today (21st April) we just passed 1 Billion requests to this service so usage is only accelerating
- We’ll maintain our free tier for users of 500,000 requests a day. 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.
- 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 about this proposal, including detailed itemised costing here](https://docs.google.com/document/d/1VbNyiJ1az_4khvG0yCuf2vof-yxivplgBN5rfs_OKes/edit?usp=sharing)

High Performance Public Infrastructure (Ongoing Costs for Q2 2021)

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

M1-1: Private Assets

Redspot is a tool that helps people create special contracts using something called Wasm. Here are some important points about it:

- Redspot makes contract development easier by hiding complicated technical details.
- Several teams, like Acala and Plasm, are already using Redspot to build applications.
- Redspot has finished different versions, with the latest one being v0.3 which helps more developers join.
- In the upcoming version (v0.4), Redspot plans to support multiple contracts and create a user-friendly web interface.
- It will also allow users to compile contracts using Docker, making it easier for different computer systems to work together.
- There will be new features like plugins that make coding easier, such as using easy-to-read amounts for transactions.
- The goal is to make Redspot helpful for both new and experienced developers in building contracts smoothly.

[Redspot](https://redspot.patract.io/) is one of [Patract](https://patract.io)'s Wasm contract development tool suite. Redspot's goal is to standardize the contract development process, hide the underlying compilation details of the contract, and combine the sandbox, library, API, SDK and other plugins to create a one-stop smooth contract development process. Patract had finished 3 proposals for Redspot at 4 months ago, the latest one is for v0.3 at [treasury #23](https://polkadot.polkassembly.io/treasury/23), and the report is at [post #207](https://polkadot.polkassembly.io/post/207) . We also had followed up the changes of Pallet-Contracts and ink! during the last 4 months.

There are also many parachain teams already in use of Redspot, including [Acala](https://acala.network/), [Plasm](https://www.plasmnet.io/), [Litentry](https://www.litentry.com/), [OpenSquare](http://opensquare.network/) etc. At the ParityAsia Hackathon, the [inkBridge](https://github.com/ParityAsia/hackathon-2021-spring/blob/main/teams/26-InkBridge/docs/project.md) and [SkyePass](https://github.com/ParityAsia/hackathon-2021-spring/blob/main/teams/30-SkyePass/docs/project.md) all used Patract suite (Redspot, Europa, PatraStore, etc.) to develop Wasm contract DApps from zero and win the 2nd and 3rd prizes.

## Summary of Redspot’s Future Plan (old)：

* v0.1(finished): Build core functions based on Truffle framework
* v0.2(finished): Migrate to Hardhat framework to enhance the extensibility of plugins and add some features to provide a smoother development workflow
* v0.3(finished): Promote Redspot and allow more contract developers to participate. Combine the features of Substrate to add various plug-ins, such as Waffle, Jupiter, Gas report.
* v0.4: Provide Typescript type support for contracts (similar to Typechain), integrate multi-language SDK, etc.

In the old design of the v0.4, the plan we expected is no longer suitable for the recent situation:

1. Typescript support for contracts: After discussing with Jacob (`api-contract` in `polkadot.js` is going to support Typescript), we believe that its importance is not high and does not affect the current use, so the support for contract Typescript is placed after `api-contract` supports this function.

2. Integrate multi-language SDK: Since `pallet-contracts` changed the interfaces in 3.0.0 and the recent changes are huge, the Himalia project of Patract’s multi-lang SDKs currently has only the Go version to catch up with the latest changes, and the python version is not updated in time. Moreover, the java version and .NET version have not been launched yet, so the multi-lang SDKs are not yet fully prepared, so they are temporarily unable to be integrated into Redspot in this version.

## Summary of Redspot’s v0.4 Plan (new)：

1. Support multi-contract: In the recent updates of ink! and cargo-contracts, multi-contracts can finally be compiled normally. Therefore, Redspot will revise its support system for multiple contracts.
2. Support docker compilation: Because of the current different environments, Wasm compilation results will be inconsistent (for example, Substrate's Runtime uses [srtool](https://github.com/paritytech/srtool) to solve this problem). On the other hand, It may be difficult to build a compilation environment under different operating systems (such as Windows), so supporting docker can solve many environmental problems.
3. Support web interface: Although Redspot is basically a command line tool, it is not very attractive to programmers who are just getting started. Therefore, Redspot plans to introduce a contract deployment and operation interface similar to Canvas-UI, and add rich functions to this interface, strengthen the contract-related attributes in product design, and visualize some Redspot functions. And this interface can also add additional functions such as calling the polkadot{.js} extension for transaction signing (the browser extension cannot be called in the Redspot command line).
4. Add some other plugins to enrich the Redspot ecosystem, such as support for chain types, plugins for monitoring file changes, and so on.

## Detailed design of v0.4:

### 1. Multi-contract support

The problem of ink! and cargo-contracts compiling multiple contracts has been corrected after the submission of [Cargo-contract PR#199](https://github.com/paritytech/cargo-contract/pull/199). Therefore, Redspot can restart the supports for multi-contract compilation (Redspot once supported the multi-contract organization structure to a certain extent, but was stopped due to the inability to compile)

Redspot's multi-contract support will start from the following aspects:

1. Multi-contract indexing and identification of document structure.
2. `redspot.config.ts` supports configuration by file index.
3. Judgment and sorting of compilation results (including the processing of compilation result of the contracts with same name)
4. Support the use of multiple languages for mixed compile

Redspot will automatically find all contract files in this directory through the configured search directory. Then compile through the configured compile tool, and finally all compile results will be output to the `artifacts` directory. At the same time, a `buildInfo` file will be generated, which records the project directory structure before compilation.

### 2. docker compilation support

Supporting the invocation of docker in Redspot can solve many problems related to environment setup. For related discussions, see [cargo-contract issue #188](https://github.com/paritytech/cargo-contract/issues/188) and [cargo-contract issue #184](https://github.com/paritytech/cargo-contract/issues/184), submitted by us. Therefore, when we noticed that the cargo-contracts `dockerfile` appeared in the [CI of scripts](https://github.com/paritytech/scripts/tree/master/dockerfiles/contracts-ci-linux ), we can add related functions for Redspot about calling docker.

Redspot will detect whether there is an existing docker environment. And automatically pull the docker image of the specified version. On the other hand, Redspot will maintain a docker image as the default testnet.

### 3. Web interface support

Since the main functions of Redspot have been relatively complete, the follow-up of Redspot will do more easy-to-use development on the product. For example, providing a contract-related UI interface to Redspot can make it easier for beginners to get started with the contract development process. On the other hand, there are some functions in Redspot that need to evoke the browser to participate in the corresponding operation (for example, call the polkadot{.js} extension to sign).

Although parity has provided [Canvas UI](https://paritytech.github.io/canvas-ui/#/) and Developer-Contracts in [https://polkadot.js.org/apps](https://polkadot.js.org/apps) , these two cannot reach our demand in terms of the specialization of the contract part. For example, Canvas-ui provides a more intuitive contract operation interface, but it does not has chain-related display information. Although apps has a more comprehensive information display, the contract call part is stronger than canvas-ui, but regardless of canvas-ui or apps are still lacking in contract-related functions, such as scanning and recording existing contracts, parsing contract parameters, and associating with the secret key in the Redspot configuration, and so on.

On the other hand, like Truffle, Redspot will also be designed to be used in a production environment to deploy contracts, so Redspot needs to provide a secure way to sign transactions. For example, hardware wallets such as ledger and parity-signer can be used in the future to deploy and call contract transaction signing. In this way, developers can firstly uses a configuration similar to `development`, configures the test key to test the contract in the test environment, then switches to production environment, configures the key of the production environment to deploy the contract. In order to take care of all environments, we think that calling the browser to interact is a better method. So this time we try to integrate the call of polkadot{.js} extension.

In summary, Redspot's web interface will provide beginners with a wealth of information to start contract operations, and also integrate some operations that cannot be handled in the cli environment:

1. The interface will contain basic information such as chain blocks, transactions, events, etc., and the contract operation interface is similar to Canvas-UI.
2. The web will scan or record (different strategies according to different chains) existing contracts, and read the Redspot config environment to associate with the existing keys
3. The web interface will display detailed information related to contract operations on the contract interface, such as gas, selector, parameter content, etc. in a contract call
4. The web interface will visualize some operations of Redspot, such as introducing Redspot's console interface to display the log of the executed operation, or it can display test and script information, and call and execute it through the interface.
5. When the security key is configured in Redspot's config, the web interface will need to call polkadot{.js} to sign the transaction.
6. Support the storage query of the contract.
7. The latest local compilation result will be uploaded automatically. It is convenient to deploy and call contracts manually.

### 4. Add some other plugins

4.1. Redspot-watcher

Currently Redspot executes commands such as `redspot test`, `redspot console`, etc. to check whether the contract file is modified when it is executed. Therefore, the developer needs to judge whether the contract needs to be compiled and add the `--no-compiled` command to inform redspot that the contract does not need to be compiled for this execution. Therefore, after the introduction of `redspot-watcher`, before calling the redspot runtime to execute, the `redspot-watcher` can determine whether there are file changes, so as to determine whether the compilation process needs to be invoked.

redspot-watcher will modify redspot's test, run and console commands. Before each run, the file hash will be calculated and stored in the buildinfo file, and then compared with the previous file hash. If there is no change, the compilation will be skipped.

4.2. Balances decimal plugin

In `web3.js`, you can use methods such as `1 ETH` to replace inputs like `10000...000`. This human-readable approach can greatly reduce the probability of making mistakes when developer write scripts and tests. However, because the precision of Ethereum is fixed, and when Substrate introduces `pallet-contracts`, the precision is determined by this chain, so the plug-in is not a static conversion, but needs to get the relevant information of the chain (decimal, symbol ) to be converted.

Therefore, the plug-in will eventually achieve functions similar to the following:

* '1 DOT' = '10000000000'
* '1 KSM' = '1000000000000'
* '1 nano’ = ’10^-9 DOT'

4.3. default blockchain types plugin

Since Substrate has not yet integrated `scale-info`, each chain provides `types` to support the parsing of polkadot.js. Currently, Redspot requires developers to fill in the type information in `redspot.config.ts`, which causes some troubles for developers. This plug-in obtains the types of different chains that already exist in apps, provides it to polkadot.js by default, and allows developers to override the form in `redspot.config.ts`, so that in most cases, developers do not need to worry about the need of providing polkadot.js the types.

We will discuss with polkadot apps and hope to release the @polkadot/apps-config package. Then all types provided in this package will be registered. We will also process the known contract chains with wasm functions. Maintain the types of their test chain. In this way, as long as the chain’s specversion is correctly set, there is no need to worry about the version.

## Detailed timeline of v0.4（5 weeks, 4 Apr ~ 10 May）

- Week 1: Implement docker support (3 developers)
   - can specify docker image as a node.
   - can specify docker image as the contract compiler.

- Week 2: Support multi-contract compilation and redspot-watcher plugin (3 developers)
   - Multi-contract compilation is possible
   - The compiled product can maintain the directory structure
   - Can detect whether the contract file has been modified, and skip the compilation if there is no modification

- Week 3-4: Web interface design and development (3 developers \* 2 weeks + 1 designer \* 1 week)
   - can browse to view contract events
   - You can query the storage of the contract
   - Can automatically upload local wasm and metadata files
   - Automatically inject locally configured accounts
   - Can call contracts and deploy contracts

- week 5: Develop balances decimal plugin and default blockchain types plugin (3 developers)
   - The amount can be passed in in a human-readable way.
   - In most cases, there is no need for developers to pass in types.

## Cost of v0.4 (1 designer \* week + 15 developers \* weeks)
* Operating activities: $3200 ( Rent and Devices: $200 per developer * week )
* Employee payments: $30000 ($1500/$1900 per designer/developer * week)
* Total Cost: $33200 and monthly average: $36 / DOT
* Treasury Proposal: 922 DOT

## How to verify v0.4:  Github library

* Multi-contract support: able to compile the delegator contract in ink/example and the multi-contracts contract project provided by redspot
* Support docker compilation: redspot can automatically pull and run the docker image containing cargo-contract component under the user's choice to compile the contract. The compiled structure can be moved to the `artifacts` directory, and the file permissions are correct.
* Redspot's web interface:
  1. Display the information and contract interface of the connected node
  2. When a contract is deployed, the contract information and related transactions will be recorded. And can be associated with the deployer. For Europa, it can directly scan the deployed contracts and associate relevant information.
  3. Display detailed contract operation information
  4. The information that Redspot originally displayed on the command line can be displayed in the web interface, and redspot test cases can be called and executed from the web interface.
  5. Able to call the polkadot.js extension to sign Redspot transactions.
* Other plug-ins
  * redspot-watcher: When the file is not edited, the contract will not be compiled if the relevant commands are re-executed. When the file is compiled, the compilation process will be called when re-executed
  * Balances decimal plug-in: Use canvas, Jupiter and Europa to test, respectively test `1 Unit`, `1 DOT`, etc.
  * default blockchain types: Connect Canvas-node and Jupiter. You no longer need to fill in types and you can send transactions normally.

Patract’s treasury proposal for Redspot v0.4 (Wasm contract scaffold)

- The project has finished the first part (M1) and it was approved.
- They will now work on the second part (M2).
- M2 has five main tasks to do.
- The first task is to let users manage multiple accounts.
- The second task adds notifications for important events.
- The third task customizes notifications based on user roles.
- The fourth task allows users to customize notification details.
- The fifth task improves the governance dashboard with new views.

Followed by the completion of M1 of our [proposal](https://polkadot.polkassembly.io/motion/49) and its successful [review](https://polkadot.polkassembly.io/motion/49#d617672a-1999-442f-94df-3a150cb8a176), we want to proceed the development as outlined in M2.

The tasks in M2 mainly focus on:

1. Offer user the interface to interact with multiple accounts under each network.
2. Basic support on Push Notification to subscribe important event.
3. Support different Push Notification type based on user roles
4. Basic customization support on the granularity of the Push notification
5. Further support of the governance dashboard by implementing missing views, e.g. Referendum list and detail view, treasury detail view.

Detail breakdown and its estimate can be found under the proposal [here](https://docs.google.com/document/d/1kZoYFv6hVodf-hTYZofNZ37ShkcNU97LXDaFlg0ouSs/edit?usp=sharing)


----
Reference links:

- M1 Review form: [here](https://docs.google.com/spreadsheets/d/17PRwueKUVH5NuJl7xItaURnAKFtxfLWgnGSPdo4wYQY/edit?usp=sharing)

- M1 Intake review report: [here](https://docs.google.com/document/d/1fwhb8rnitTNx_GuRX4-Ou4EIxJv3RhgzrCxYSTs8pUs/edit?usp=sharing)

- Original proposal: [here](https://polkadot.polkassembly.io/motion/49)


Milestone 2 of Governance-focused Mobile App for all Substrate-based networks 

- Dotreasury is a project funded by Kusama that provides accounting information and allows community comments on expenses.
- The team plans to integrate Polkadot into Dotreasury and make improvements, like better code for supporting multiple chains and a price tracker.
- They will show fiat values of tokens instead of just amounts and will deploy a Polkadot archive sync node for better performance.
- The total cost for the project is $11,300, which includes expenses for developers and server fees.
- The team expects to deliver the updates within a month.
- They want to discuss the credit model for future work and have plans to share a draft document for it soon.

Copied from [post 368](https://polkadot.polkassembly.io/post/368)

---

As you may know we developed [dotreasury](https://www.dotreasury.com/) with 2 milestones funded by Kusama. Generally now dotreasury provide a detailed accounting info and a place for community members to comment the expense. Please check following links for more details.
- The initial post and discussions: [link](https://kusama.polkassembly.io/post/352)
- 1st milestone work report: [link](https://kusama.polkassembly.io/post/352#870d76ca-0cf3-4f87-8c94-012fccc939ea)
- 2nd milestone proposal page: [link](https://kusama.polkassembly.io/treasury/75)
- 2nd milestone work report: [link](https://www.dotreasury.com/proposals/75#60489b5e98f65074c4c9036a)

Or just check [here](https://www.dotreasury.com/projects/dotreasury) for the dotreasury project page on dotreasury. We propose to integrate polkadot to dotreasury.

## Work 
### Code refactor
Now the code is highly coupled with Kusama, and we need to refactor all the packages(scan, restful server, react app) to support multiple chains.
- We don't plan to use 2 subdomains for kusama and polkadot separately, so the front page url may become from `/proposals `to `/[ksm|dot]/proposals`. Benefit is user don't have to login again after switching chains.

### Price tracker
Some metrics now in dotreasury are ranked by the token amount, while it will be better if we can rank them with the fiat cost. Generally we will create a price ticker and call the api of some exchanges(maybe binance, huobi, ok) maybe every minute. Finally we may show the fiat value with the proposed time price and we don't have to make it so accurate to reduce development cost.

### Others
- A polkadot archive sync node will be deployed on our server to better scan performance
- Expense related links will be collected to show on the corresponding pages.
- Collect the funded projects, show the list the detailed page with the timeline.
- Listen the direct transfers to treasury address.
- Polish. For example, we may provide a link to the staking remaining explanation pages to user to better understand the inflation. Some UX tips will also be improved.

## Cost and delivery

Cost details
- 3 developers * 2 weeks equivalent work = $3500 * 3 = $10500
- Server fee for 2021.03 and 2021.04:  (8vCPU + 16GiB + 500GiB SSD + 10Mbps) * 2 = $800
- Auxiliary work from 1 designer and 1 executive intern = $0

So the final price is $11300. Taking dot price as $30, the request dot amount is 376. 

We will deliver it as soon as possible, but since we are developing other products as well, we hope deliver it no later than one month. Output will be:
Output: 
- Polkadot shown on [dotreasury.com](https://www.dotreasury.com/)
- [Code repo](https://github.com/opensquare-network/dotreasury) better support multiple chains.

## Possible questions

1. Why not develop the M3(credit model) first, and the polkadot?
    - We want the credit building rules are fully discussed before we finally build it. Even so, we may build it by steps. But the work of M1 and M2 is meaningful to polkadot too.
    - Though polkadot integrated, M3 work will be done for kusama, and then polkadot when no big disputes.
    - Better to adjust code structure first before add big new features from the view of development.

2. How to discuss the credit model?  
  We have a draft doc for it and will create a post soon for discussion. But it may be posted in the kusama polkassembly first.

---
We are [OpenSquare](https://www.opensquare.network/) team, dedicated to facilitate the collaboration between projects and developers.

OpenSquare's treasury proposal for doTreasury polkadot integration

- PolkaWorld is asking for help to improve their website for the Polkadot Chinese community.
- They are the biggest Chinese community on WeChat but can only share one article each day.
- Many important articles are not shared quickly because of this limit.
- Currently, their information is only available on WeChat, which makes it hard for more people to learn about Polkadot.
- They want to add new features like real-time news and videos to their website to share content better.
- They are requesting 647.07 DOT to support the changes for the first three milestones.
- More details about the project and budget are in a provided link.

Hi, all councilors,

PolkaWorld is submitting a proposal for polkaworld.org website development and enhancement for the Polkadot Chinese community. PolkaWorld is the largest Chinese community in China, based solely on wechat so far.

Problem Description As Polkadot ecology flourishes, more content is produced by PolkaWorld. Due to the WeChat official account platform restrictions, we can only publish one article per day. As a result, we have accumulated a lot of useful content that cannot be released in time.

At present, PolkaWorld information can only be displayed on the mobile terminal of WeChat ecosystem, not on a public website, which to some extent affects more people who learn Polkadot.

With the growth and development of the community, the current content form is too restricting: we need more forms (Real-time News/live streams) to spread the content of Polkadot and Substrate.

The deliverable of this proposal is the enhancement of the website on polkaworld.pro, which will allow us to post content at any time and add a section of Real-time News and videos to enrich the form of content, providing the community with real-time information.

We requested 647.07 DOT (Rate: 34.37 USD/DOT based on a EMA30 rate on [subscan](https://polkadot.subscan.io/tools/charts?type=price)) for milestone 1 ~ milestone 3.

You can get more details about the milestones and budget [here](https://docs.google.com/document/d/1nxJNfGgLoiZcbmqpTCDD5TstCxAPUlgnX1a28Byd3pE/edit#)

Pls feel free to feedback me if you have any confuse/questions!

Many thanks!

PolkaWorld treasury proposal: a website development for Chinese Community

- 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.

**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

**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

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

- 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

- **Proposal Overview**: This is a proposal to verify the completion of Milestone 1 (M1) for the Polkawallet Treasury Proposal.
- **Milestone 1 Goals**:
  - **Social Recovery Pallet**: Supports observer mode, account recovery settings, and agent operations.
  - **Offline Signature**: Implements QR code functions, direct transaction sending, and compatibility with Polkadot-js web wallet.
- **Verification Methods**:
  - Download the beta version of the app from the official website.
  - Follow guides to verify Social Recovery and Offline Signature features.
- **Funding Request**: The proposal seeks Kusama treasury funding, with the receiving address identified as `POLKAWALLET`.
- **Project Links**: Includes links to the project's GitHub, official website, Twitter, and contact email.

Polkawallet Treasury Proposal - M1

- 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.

Rejected

**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 

- 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

- 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

- 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

- LocalCoinSwap is a platform for trading cryptocurrencies directly between people (P2P).
- It helps people in many places access cryptocurrencies, especially where banks are not available.
- They finished the first part of a project and are now working on the second and last part.
- In the first part, they created tools to help with trading on a special system called Polkadot.
- For the second part, these tools will help users trade Polkadot on LocalCoinSwap.
- Users will have features like wallet access, direct trading, and swapping different kinds of cryptocurrencies.
- They invite people to ask questions or give feedback on their plans.

After successful completion of the first milestone, we are pleased to submit our proposal for the second and final milestone of the LocalCoinSwap non-custodial trading implementation for Polkadot.

**Github:** https://github.com/LocalCoinSwap/

**Homepage:** https://localcoinswap.com/

**Intro:**

LocalCoinSwap is a P2P cryptocurrency exchange which focuses on providing trustless fiat on-ramp solutions, enabling global accessibility for cryptocurrencies. We bridge the gap between users and crypto where centralized exchanges fail, in particular across developing regions of the world where access to mainstream finance is limited.

In the first milestone of this project we extended the kusama-utils library that we previously built to create a generic substrate-utils library. We also extended the Kusama-api to create a generic Substrate-API. These packages are now generically useful for any number of substrate parachains and tokens.

For the second milestone, we will be utilizing these libraries to allow Polkadot to be fully tradable on the LocalCoinSwap API as well as through the LocalCoinSwap front-end application. This includes end-user wallet functionality, non-custodial P2P trading, basic and advanced pricing mechanisms as well as allowing crypto-to-crypto swaps.

Please check out our detailed proposal below and we welcome any questions or feedback: https://docs.google.com/document/d/1vP54xXbJxPC1nJQ0RA7TC4S16mFAuNvSP6iDxfFFcPc/edit

LocalCoinSwap Treasury Proposal - Python Substrate libraries upgrade & Polkadot integration: Milestone 2

- DoraHacks is hosting a Substrate Hackathon in Hangzhou, China on December 19-20, 2020.
- The event will bring together 80-100 people including developers, designers, and blockchain fans.
- There are 10 online workshops about Substrate and Polkadot leading up to the hackathon.
- The hackathon has 20 judges who will review the projects based on their technical and business ideas.
- They are asking for 3000 DOT as prizes and to cover costs of the event.
- Hacker projects will be shared on a specific website and bounties will also be posted there.
- DoraHacks is a big global hacker community known for organizing many hackathons.

**DoraHacks** is running a Substrate Hackathon in Hangzhou, China on December 19th-20th, 2020.

**Venue**: Future Science City, Hangzhou, China

**Time**: 19th-20th, December, 2020

There will be approximately 80-100 Substrate Devs, PMs, designers and other cypherpunks and blockchain enthusiasts joining this event and exploring the fun of hacking with Substrate. We currently received 50+ hacker registrations and are expecting a dev crowd of 80-100 during the weekend of the Hackathon.

This will be the **one and only** Substrate Hackathon taking place in China in the year of 2020, where all Chinese Substrate Developers will gather in Hangzhou to learn, explore, social and create.

We have 10 online workshops about Substrate and Polkadot Ecosystem Intro prior to this event, which will be livestreaming on Bilibili(dev's fav online video and live streaming platform) and recorded. The videos will also be displayed on DoraHacks's official account on Bilibili.

- 12.9 Litentry(John, core dev) : Connect Ethereum identity with offchain worker
- 12.10 Parity(Maggie Dong, Engineer): Introduction to Substrate and Polkadot
- 12.11 Parity(Maggie Dong, Engineer): Parachain and Cross-chain
- 12.12 OpenSquare(Yongfeng Li): How Substrate Treasury Pallet Works
- 12.13 Web 3 Foundation(Qinwen Wang) : Governance and Grants of Web 3 Foundation
- 12.14 Bandot(Feng Chen): Defi 2.0
- 12.15 Rust China Community(Bin Guo, core member): Rust Introduction
- 12.16 Rust China Community(Mike Tang, Founder): Rust in Depth-Future
- 12.17 Polkaworld(Xioajie Pang, Founder): The Development of Polkadot Ecosystem

We have 20 judges and mentors for this Hackathon. They will be commenting on hacker's projects' based on technical and business potential.

- Yaoqi Jia, Parity Technologies
- Maggie Dong, Parity Technologies
- Qinwen Wang, Web 3 Foundation
- Yin Cao, Digital Renaissance Foundation
- Fuyao Jiang, Acala Netwok
- Hanwen Cheng, Litentry
- Denny, Darwinia Network
- Marvin Tong, Phala Network
- Xiaojie Pang, PolkaWorld
- Lipeng Yue, Patract Labs
- Feng Chen, Bandot
- Kamie, Stafi
- Lurpis, Bifrost
- Charlie Hu, CANDAQ Group
- Kyrie Li, Delin Capital
- Jocy Lin, IOSG Capital
- Haiguang Huang, Cabin VC
- Stephanie Lu, Fenbushi Capital
- Mable Jiang, Multicoin Capital

**Our Ask:**

3000 DOT as Hackathon prizes(1500 DOT) and operational costs coverage(1500 DOT)

Hackathon prizes will be distributed to hacker team based on the number of votes they receive from judges and other teams.

Operation costs are mainly the cost of logistics of this Hackathon and our teams effort to make this Hackathon great.

**Hacker Projects** will be uploaded here: https://hackerlink.io/buidl 

**Hackathon Bounties** will be posted here: https://hackerlink.io/bounty

**About DoraHacks(DoraHacks.com): **

DoraHacks is an active global hacker community. We're Hackathon enthusiasts, and did 31 blockchain Hackathons in 2018 in 8 countries, 15 cities. We're also the organizer of the largest Hackathon in China history: the 4th Industrial Revolution Hackathon. We're also the largest blockchain developer community in China.

**About HackerLink(Hackerlink.io): **

Hackerlink has bounty, grant, BUIDL and Hackathon features catering to the needs of Chinese developers when they want to engage with blockchain projects.

**About DoraHacks Global Hackathon Series: **

DoraHacks GHS 2021 is coming back! We're running 15-20 offline hackathons in China, US and Europe in 2020-2021 despite the craziness of Covid-19. We're actively running offline blockchain hackathons in China recently. Our first Hackathon was DoraHacks x Binance Smart Chain Defi Hackathon in Beijing, November 14th-15th where 91 hackers created 17 new Defi Projects. You can find all their contributions here: https://www.theblockbeats.com/news/20748

The initial proposal can be found here: https://polkadot.polkassembly.io/post/193

Substrate Hackathon @ Hangzhou, China on Dec.19-20, 2020

- **Project Name**: Megaclite  
- **Goal**: Add zero-knowledge proof (ZK) support to Polkadot for better privacy and performance.  
- **Key Features**:  
  - Supports four cryptographic curves: alt_bn128, bls12_381, BLS12-377, and BW6_761.  
  - Provides basic math operations (ADD, MUL, Pairing) for these curves in both Native and WASM layers.  
  - Helps developers build privacy-focused apps using ZK Rollup technology.  
- **Future Plans**:  
  - Create tools for developers to use ZK proofs in smart contracts.  
  - Build a sample payment app using ZK Rollup for fast and secure transactions.  
- **Cost**: $31,500 for the first phase (v0.1).  
- **Verification**: Test on Jupiter Testnet, watch YouTube demos, and check GitHub libraries.

**The original post is https://polkadot.polkassembly.io/post/167, after the feedbacks from the group, we have decided to modify our proposal into this, and we have highlighted the difference (bond and deletion)**

## Suggestions from W3F and Parity

> [Arkworks](http://github.com/arkworks-rs/)' library is better than Zcash's old library
> 
> Ethereum's alt_bn128 is too old, we originally decided only add bls12_381, W3F suggests to add another two curves: BLS12-377, BW6_761
> 
> The native layer's design (Runtime interface or WASM boundary) for final complete crypto curves support is TBD, so we will not try to merge our code into Substrate about the crypto units in native layer. We will change this project as the POC and show the real benchmark difference of native and WASM implementation. So, we have decided to deliver two version of the crypto units (ADD, MUL, Pairing) of those four curves in native layer and in Runtime WASM layer.

Among the current Layer 2 solutions to the privacy and throughput problems of blockchains, zero-knowledge proof is considered the most powerful solution. Compared with Channels, Mixers, and Ring Signature, zero-knowledge proof is the most difficult to implement, but the effect is the best, and it can be applied to almost all scenarios on the blockchain. With the development of some technologies around the Ethereum community in recent years, the efficiency of zero-knowledge generation and verification has been greatly improved, and the upper layer abstract has become more and more mature, and the development difficulty has been greatly reduced. Recently, some related projects have appeared in the Polkadot community, such as [Matter Labs](https://matter-labs.io/), [Starks Network](http://www.gbctech.cn/), etc., but for WASM smart contract and Runtime development, the Substrate framework still lacks some underlying technical support.

Patract Hub https://patract.io develops local open source tool suite and a one-stop cloud smart IDE, and is committed to providing free development tools and infrastructure services for Polkadot's WASM smart contract ecosystem. Megaclite is the 5th project of Patract Hub. In the process of developing this project, we will also launch the 6th project at the same time: Metis, a WASM smart contract library. The Megaclite project will be dedicated to introducing basic zero-knowledge proof underlying support for the Polkadot ecology, so that developers can easily develop applications at the upper level through WASM smart contracts or Runtime. Megaclite will  support the more mature zkSNARK-related technologies firstly, and may also support zkSTARK-related underlying technologies later.

## ZK Rollup Introduction

Compared with the privacy function, the performance improvement brought by Rollup is the early application direction of zero-knowledge proof. At present, the Layer 2 expansion plan of the blockchain is to transfer a considerable part of the on-chain workload to off-chain to complete, and the most watched one is ZK Rollup. The essence of ZK Rollup is to compress the application on-chain state and store it in a Merkle tree, and move the state transition funtions to off-chain. At the same time, the correctness of the off-chain state transition process is guaranteed through the proof of zkSNARK. Compared with the high cost of directly processing state changes on the chain, the ZK Proof's on-chain smart contract verification is extremely cost low. At the same time, the compressed information will also be submitted to the chain together with the proof, which ensures data availability and obtains the same level of security as Layer 1.

The Ethereum Layer 2 protocols related to ZK Rollup are: [zkSync](https://zksync.io/), [aztec](https://aztec.network/), etc. Their contract verification modules share a part of the elliptic curve's basic algorithms. In 2017, Ethereum integrated three basic cryptographic calculation units of the alt_bn128 curve in the form of pre-compiled contracts, which are [EIP196](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-196.md)’s ADD and Scalar_MUL algorithms, and [EIP197](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-197.md)’s Pairing algorithm. On top of this, due to the lack of rapid upgrade capabilities of Ethereum, the community can only encapsulate some tool libraries through costly Solidity contracts. On top of these basic contract libraries, many DApps can combine ZK Rollup technology to achieve some innovations, such as [loopring](https://loopring.org/), [gitcoin](https://gitcoin.co/) and [uniswap](https://uniswap.org/) etc. However, in the past 3 years, ZK technology has further developed, such as the more practical [BLS curve](https://electriccoin.co/blog/new-snark-curve/), and [PLONK algorithm](https://eprint.iacr.org/2019/953/20190827:165656) etc. Ethereum has not yet supported it.

## Megaclite's Future Development Plan （v0.1 ~ v0.3）

Github：https://github.com/patractlabs/megaclite

Megaclite will firstly provide the following functions on our Jupiter smart contract testnet. ~~After full verification, we will apply to Parity to merge this into the Substrate framework.~~

- Provide more on-chain underlying cryptography support than Ethereum. The current stage includes two curves : [alt_bn128](https://github.com/zcash-hackworks/bn) and [bls12_381](https://github.com/zkcrypto/bls12_381) , **and two more: BLS12-377, BW6_761**

- Integrate ADD, MUL, Paring units in Native layer, and provide them to Runtime applications through Runtime-Interface, and further provide them to WASM contract applications through Contract-Seal

- **Integrate ADD, MUL, Paring units in Runtime WASM layer, and provide them to WASM contract applications through Contract-Seal**

- Through Pallet and Ink! contract libraries, providing more higher-level verification and crypto tools than Ethereum, improving execution efficiency and reducing development costs

- Provide off-chain cryptography toolbox through Rust SDK

- Provide typical sample applications through Ink! sample contracts

### v0.1: Provide on-chain support for elliptic curve alt_bn128 and bls12_381 **and BLS12-377, BW6_761**(5 weeks)

- Integrate addition (ADD), scalar multiplication (MUL) and Pairing functions of the curves in Native layer **and Runtime WASM layer**.

- Provide these three functions to the upper Runtime Pallets and Contracts to call.

- In the Runtime layer and the Ink! contract layer, provide two zkSNARK Verify upper-layer interfaces ( verification function of groth16, similar to the Verifier library of [ethsnarks](https://github.com/HarryR/ethsnarks)).

- Start the Metis project and implement EdDSA, MerkleTree, MiMC Hash, etc. contract library on the Ink! contract layer.

### v0.2: Provide off-chain toolbox support for Ink! contract (5 weeks)

[ZoKrates](https://github.com/Zokrates/ZoKrates) is the zkSNARKs toolbox on Ethereum. It helps developers generate computable proofs using high-level languages and verify the proofs in the Solidity environment. We will transform this toolbox based on ZoKrates to adapts to the Ink! smart contract environment.

-  Support the complete commands supporting the zkSNARKs protocol, including the use of Compile, Setup, Compute-witness, Generate-proof, Export-verifier and other commands in the Ink! smart contract environment

- Provide Javascript toolkit, support API interface, including compile, computeWitness, setup, generateProof, exportSolidityVerifier, etc.

### v0.3: Create a sample payment DApp based on Megaclite (6 weeks)

Payment is one of the typical scenarios for the large-scale popularization of blockchain applications. However, due to the performance, cost and scalability of the Layer 1 basic chain, low-latency and high-throughput payment applications cannot be implemented on the Layer 1 chain. Now benefiting from the basic capabilities of zkSNARKs provided by the previous two versions, we will implement a highly scalable payment application based on Layer 2 ZK Rollup technology for the community. 

The application has the following characteristics: completely trust-free, anti-censorship, high security, fast real-time, high throughput. Developers can reuse the application code with very few changes and directly apply it to the Polkadot WASM smart contract ecosystem to serve large-scale community users, and it will also bring great scalability to the Polkadot parachain.

- Provide a Metis smart contract library that supports deposit, withdrawal, transfer and verification of off-chain ZK proof
- Provide ZKP engine including transaction pool, Merkel state tree, circuit, and proof generation
- Provide state management module and transaction pool module

## Detailed Design of v0.1: 5 weeks (16 Nov - 21 Dec)

### M1: Integrate the basic units of alt_bn128 & bls12_381 & **and BLS12-377, BW6_761** (3 developer * 1 weeks)
1. ~~Prepare the 3 basic algorithm codes (Add, Scalar_Mul, and Pairing) of alt_bn128 elliptic curve from zcash's official library [bn](https://github.com/zcash-hackworks/bn)~~ 
2. ~~Prepare the same 3  basic algorithm codes of bls12_381 from zcash's official library [bls12_381](https://github.com/zkcrypto/bls12_381)~~
3. **Prepare the basic algorithm codes (Add, Scalar_Mul, and Pairing) for 4 curves from arkworks' library** 
4. Integrate the above algorithms into the under layer of Substrate Runtime **and Runtime WASM layer**.

### M2: Provide to upper runtime and smart contract applications (3 developers * 1 weeks)
1. Add Runtime_interface to the Jupiter testnet and provide it to Runtime applications.
2. Add Contract_Seal to the contract module of the Jupiter testnet and provide it to the WASM contract application.

### M3: Integrate upper-level verification and tool functions (3 developers * 1 week)
1. The runtime pallet that implements the zkSNARK verification algorithm.
2. The Metis contract library that implements the zkSNARK verification algorithm.
3. The Metis contract library that implements other commonly used algorithms, such as EdDSA, MerkleTree, MiMC Hash, etc. and other commonly used algorithms.

### M4: Test (3 developers * 1 week)
1. Test six basic elliptic curve algorithms
2. Test the zkSNARK verification algorithm of the Runtime layer
3. Test the zkSNARK verification algorithm implemented in the contract layer
4. Test EdDSA, MerkleTree, MiMC, etc. and other commonly used algorithm contract templates.

### M5: Benchmark (3 developers * 1 week)
1. Provide benchmark results of all the above functions and develop them for the community as a reference for transaction weight and pricing.

## Cost of v0.1 (15 developers * weeks)
* Operating activities: $3000 ( Rent and Devices: $200 per employee \* week )
* Developer payments: $28500 ($1900 per developer \* week)
* —————————— +
* Total Cost: $31500
* Exchange Rate: $5.8 / DOT
* Treasury Proposal: 5431 DOT

## How to verify v0.1: Jupiter Testnet & Youtube demo & Github library

1. The cryptographic units can be verified through the Runtime and Metis contract modules that we deploy on Jupiter.
2. The upper-level Verification function can be verified through the Runtime and Metis contract modules deployed on Jupiter.
3. The functions of the upper-level tools can be verified through the Metis contract module deployed on Jupiter.
4. You can view and reproduce our Benchmark results.


Treasury Proposals