[YieldBay](https://yieldbay.io) started out, about 9 months ago, as an effort to reduce information asymmetry and lower the barrier to entry for liquidity providers and yield farmers within the dotsama ecosystem and make it easier for protocols to acquire liquidity for their token pools.

For details see [Introducing Yield Bay - by Batman](https://blog.yieldbay.io/p/intro).

Dotsama’s multi-chain and interoperable infrastructure enables novel solutions to be built, which were previously not possible. However, this novelty also brings complexity.

Spending time in various community chat servers, we noticed similar questions from community members, stemming from the problem of information asymmetry in finding and participating in liquidity pools and yield farms.

![Information asymmetry in finding and participating in liquidity pools and yield farms](https://i.postimg.cc/nL86ZKgm/collage.png)

This problem affects not only LPs and yield farmers but also protocols, as they suffer from low discoverability and lower conversions, resulting in lower liquidity for their token pools and higher slippage. That’s a big problem if you want people to be able to buy your token. Hence, it is a huge barrier to a new project’s success.

Our goal is to help reduce the time and effort costs of liquidity acquisition and provision for protocols and end-users (LP/yield farmers) respectively, by making it easier to find and list liquidity pools and yield farms in one central location.

In this proposal, we are seeking to fund the development of an aggregation platform for finding and listing liquidity pools and yield farms across the dotsama ecosystem to reduce problem of information asymmetry mentioned above. We believe such a platform will be mutually beneficial for users as well as protocols.

**Progress so far:**

- We've already built a proof-of-concept for this, which is live on [list.yieldbay.io](https://list.yieldbay.io)
- The platform has had 350+ unique visitors who spent an average time of over 4min on the site
- Within a week since we launched YieldBay List (on July 11th, 2022), we’ve received listing requests from over 5 different protocols including Tapio/Taiga, BeamSwap, Darwinia, et al. (**disclaimer:** please note that this **does NOT** imply a partnership or endorsement between YieldBay and these projects)

**NOTE:** This submission is only for the first milestone. We shall make separate submissions for the remaining milestones.

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

Thank you to everyone who contributed during the [community feedback stage](https://polkadot.polkassembly.io/post/1171) of this proposal. We have corresponded with everyone that has provided their inputs in the comment section of the discussion thread.

Awarded

YieldBay Proposal: Listing platform for all dotsama liquidity pools and yield farms

- Discussion: https://polkadot.polkassembly.io/post/1223
- Requested Amount: $25k
- The average price of DOT in the last 7 days: $7.44
- Requested DOT: 3360 DOT

This is Sota Watanabe, founder of Astar Network. On behalf of the following projects, I submit this proposal on Polkassembly. (Astar, Acala, Ajuna, Bifrost, DFG, Efinity, Efficient Frontier, Integritee, Unique, LongHash, Jsquare, Moonbeam, OnFinality, Phala, SubQuery, Equilibrium,Tribe, Web3Go, SubWallet, CESS and Acurast)

Token2049 is the biggest event in Asia this year and more than 3000 people are going to attend. We think that having a great Polkadot presence during this event is important especially to be recognized in Asia. The above 21 projects are going to either participate in token2049 or visit Singapore. These teams have come together to organize a Polkadot event, inviting not only Polkadot team members but also non-Polkadot ecosystem members to help build the Polkadot brand in Asia.

The goal of this event is to make a stronger Polkadot brand and show the unity of the ecosystem. Our KPIs are 1. 300+ registrations and 2. 200+ attendees.

Please see the full proposal [here](https://docs.google.com/document/d/1HyBvtQ1ljW0r6-snUtFmoNDoDRzC1L1oJV3WSsLQ0n8/edit#heading=h.v6is2ta0txr1).

[The event page](https://www.eventbrite.com/e/polkadot-asia-lounge-party-tickets-413358926677
) is already published and more than 300 people already registered. 


Proposal: Polkadot Singapore Event During Token2049

**Requested Allocation:** $40,000 (milestone 2 hackathon for Polkadot)

*DOT amount calculated via EMA on 9 September 2022 at GMT+0 0845hrs: 1 DOT ~ USD$7.55. USD$40,000 ~ 5,298.01 DOT

**Proponent:** EasyA 5FQqvRHgBEUZG17qs9cNFH6ZSSVyAwhb7D6dKjGWb8xgKFkP

**Short Description:**
We’re thrilled to announce our report on the successful completion of the EasyA x Polkadot hackathon (check out the highlight reel [here](https://youtu.be/vo4McHKpchY))! We held the hackathon on 30-31 July in London and are delighted that we exceeded all our targets. Overall, 27 awesome projects were created by 250 students from 30 universities. We educated them on how to build parachains/dApps in Dotsama, and we raised huge awareness of the Polkadot ecosystem amongst thousands of new student developers while we were promoting the hackathon. We have documented the hackathon fully [here](https://docs.google.com/document/d/10GTdZby0vj1qrmmUKrmWpat2XDsB7W38i52gfTdq668/edit?usp=sharing), along with our key successes and learnings for others to draw on when hosting future hackathons. 

As we have completely fulfilled the objectives of the proposal, we are therefore requesting the reimbursement of Milestone 2 (to reward winners and cover final costs). The prizes will be distributed in DOT to the winners. Although the value of DOT has dropped since the Milestone 1 proposal, the participants were aware token prices fluctuate. This is in accordance with our original Milestone 1 proposal which was approved [here](https://polkadot.polkassembly.io/motion/215).

We’re looking forward to building on this momentum and bringing more students to the Polkadot ecosystem soon!

Milestone 2 Proposal: Polkadot Hackathon for 200 Students and Educators

This is proposal for Milestones 1&amp;2.
DOT/EUR exchange rate calculated as 7.3481 by EMA7 (EMA with 168 period frame) by <a href="https://trade.kraken.com/snapshot/ccbh735b5aau6chkob5g-kraken-dot-eur">Kraken</a>
Our team proposes to design an open source hardware storage for dotsama ecosystem.
<a href="https://app.skiff.com/docs/6e1d3e9f-9e2c-4413-9190-9c39cda20763#yJcS2WZZbiuFk4Pe3W5nycQ7vcjEbrXkbfcf2EKIiV4=">Please see complete proposal on Skiff</a>
Project name is Kampela, Finnish word for flounder fish. The device is envisioned as flat card mostly consisting of e-paper screen and few controls (and it allows keys to stay safely in depth).
Kampela is a hardware version of Parity Signer. It is a small card-shaped device (ideally comparable to a credit card form factor, to be carried in a wallet when needed) that accepts data through unidirectional NFC port and shows output on a monochrome electronic paper screen. It has cryptographic strongbox with elliptic curves supported by Substrate &mdash; which only stores private keys (after initial import) and performs all signing operations on-chip.
Kampela is designed to be a comparatively low-cost (below &euro;100, in contrast to &euro;500+ for a Signer-compatible smartphone) single-purpose device, which would only support a single seed phrase per unit, operated via a drastically simplified user interface. However, it would have all the security features of Parity Signer: a full-featured SURI account derivation system, transactions preview, metadata updates, logging.
As something that supports the same QR code output formats as Signer, it would be able to drop-in replace Signer when providing signatures back to a mobile/desktop wallet. The only challenge would be in transforming the current QR-driven input format of Signer into a suitable NFC payload. Alongside with native support in some apps (which would require software modification) this can also be achieved with a tiny &ldquo;translator&rdquo; app for a regular (online, not necessary trusted &mdash; one&rsquo;s usual daily driver) mobile phone: it would snap a QR code with the transaction details and (statelessly, without any extra features or complicated UI) transform that into an NFC payload.
Kampela is a natural (and long-discussed) extension of Parity Signer to leverage the most out of modern hardware-based crypto chips and drastically reduce Signer&rsquo;s attack surface: no mobile OS, not extra platform features, no unexpected communication methods or airplane mode to take care of.
Kampela is not a wallet! It is a signing tool, it is not able to track on-chain balances, validate things over chain-provided information or generate transactions on itself.
The scope of this proposal does not include actual production, but does result in all preliminary development required for production. Hopefully, many assembly shops would rush in to compete with us and each other!
<a href="../post/1227">This proposal was prevoiusly posted in Discussions</a>
Edit: <a href="https://app.skiff.com/docs/2b25845a-4a00-4bf4-aaff-3de4a70d4ad7#zSepFgAI0EetUe7eIp2Tlgu/RnhMjnAJRDecVUiVmhQ=">Milestone 1 report</a>
Edit: <a href="https://app.skiff.com/docs/5dcbeadc-e5f3-4f29-8476-e8fcb7786585#ZNnc%2FdmSz3dYkUNc%2BI%2BiarGsZKa0W9uUN25ZqCySPAg%3D">Milestone 2 report</a>

Hardware signer and key storage Kampela: Milestones 1&2

**SubWallet 2nd proposal:** NFT support on Kusama and Statemine, Cross-chain assets support for Statemine and Statemine, Transactions history, Crowdloan status and Staking information, Custom Networks, XCM Transfer and Integration with Substrate Connect - Light Client.

**Dear Councilors,**

**This is SubWallet's 2nd proposal for Milestone 2 - 12 Weeks: From Mar 2022 to May 2022 (which is completed):**

![](https://lh3.googleusercontent.com/B1THH26yM-lThu2tjrWBWOgwQg_uNZzF_aj55B35mCaQ-0jwPTXZ6l8riCzxCBAsm9VcQ10-H28M8xr8tunGfezm=w640-h400-e365-rj-sc0x00ffffff)

- Full proposal for Milestone 2 with a detailed description & costs: [Link](https://docs.google.com/document/d/1HJ7Jr1BkvyxjBcKZBoKCgmZlcJAXnrW1upJTe7rC0zM/edit#heading=h.v6is2ta0txr1) 
- Community Discussion for Milestone 1 & Milestone 2: [Link](https://polkadot.polkassembly.io/post/1113)
- For full details about all milestones and progress, please refer to this [link](https://github.com/Koniverse/SubWallet-Extension/milestones). (Milestone 1&2 are completed; Milestone 3, 4, and 5 are in progress)
 
**Complete set of the proposal: ([See proposal](https://docs.google.com/document/d/1HJ7Jr1BkvyxjBcKZBoKCgmZlcJAXnrW1upJTe7rC0zM/edit#heading=h.v6is2ta0txr1))**

- Added Donate Button for charity program (Currently, we only support the Ukrainian government according to information Mr. Gavin Wood has published on Twitter, You can see a demo of the feature [here](https://twitter.com/subwalletapp/status/1499786619880341505))
- Added RMRK 2.0: Singular & Kanaria on Kusama
- Send / Receive NFT: Singular & Kanaria on Kusama, Statemine ([Link](https://twitter.com/subwalletapp/status/1506581700775612416) and [Link](https://www.youtube.com/watch?v=fzRbcnafV3M))
- Added cross-chain assets for Statemine, Statemint ([Link](https://twitter.com/subwalletapp/status/1516249395867824130))
- Integrated with SubQuery & Subsquid to show Transactions History, Crowdloan Status, and Staking Information
- Compatible with Metamask and Support EVM Assets ([Link](https://twitter.com/subwalletapp/status/1506581700775612416), [Link](https://twitter.com/subwalletapp/status/1511316471246372874) and [Link](https://twitter.com/subwalletapp/status/1516249395867824130))
- External Security Audit: [Report](https://audit.verichains.io/certifications.html?search=SubWallet)
- Updated new transfer flow for multi-chain assets
- Added Send & Receive cross-chain assets
- Custom Endpoint / Network ([Link](https://twitter.com/subwalletapp/status/1531960712071094273))
- Integrated with Substrate Connect - Light Client ([Link](https://twitter.com/subwalletapp/status/1531960712071094273))
- [And more](https://github.com/Koniverse/SubWallet-Extension/milestone/2?closed=1)
 
**Our tractions as of 15 June 2022**

- 60+ networks supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- 5000+ organic installs and 4000+ weekly active users on Chrome Store & Firefox Store.
- Conversation rate ~ 100%
- Our users come from 70+ countries.
- 5000+ community members on Twitter, Telegram, and Discord
- A member of the Substrate Builders Program
- Working with 70+ teams in the ecosystem with the ultimate goal of bringing the best UI/UX for users. 

**Our tractions as of 31 August 2022**

- 70+ networks supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- 15.000+ organic installs and 12.000+ weekly active users on Chrome Store & Firefox Store.
- Our users come from 80+ countries.
- 6500+ community members on Twitter, Telegram, and Discord
- SubWallet on Polkadot Community Call on August 18, 2022: [Link](https://twitter.com/Polkadot/status/1560234806478356480)

**All the best,**

**SubWallet Team**

Milestone 2: SubWallet Proposes to Build the Web3 Multiverse Gateway for Polkadot & Kusama ecosystem

Dear community and councilors! This is a social contract between PolkaWorld and the Polkadot Treasury. [This proposal](https://docs.google.com/document/d/12o8-i64KsxA2KGnuJg3SUghprqGKUteCAHy8TkqKvNo/edit#) is aimed to cover the community operation costs from Sep 2022 to Nov 2022.

PolkaWorld is the Polkadot community in China and has gathered more than 50,000 followers, we have collaborated with the Polkadot ecosystem and Web3 Foundation to build a strong community since 2019. We received the W3F community grant from 2019 to 2021, then make a social contract with Polkadot Treasury in June 2021, so far we have got 5 times Polkadot Treasury funds. 

Details for **milestones**, **tasks**, and the **budget** for the next 3 months, and all monthly reports can be found [here](https://docs.google.com/document/d/12o8-i64KsxA2KGnuJg3SUghprqGKUteCAHy8TkqKvNo/edit#). Love to hear all your advice or any feedback.

PolkaWorld Ops and Maintenance proposal：2022.9 - 2022.11

Hello Community,

Polkadot, and generally speaking Substrate built block-chains have tremendous potential to deliver decentralized computing, however depending on how they are deployed and operated by the community the resulting system can be more or less centralized/decentralized.

When analyzing the degree of decentralization of the Polkadot Rely chain by the following variables: Region, Computing Network and Node Operator, it turns out that the network is very centralized with most of the public validation activity concentrated and a few Operators, Regions and Computing Networks.

Polkawatch is an analytic tool designed to measure effective decentralization of Polkadot’s Validation process. [Polkawatch](https://polkawatch.app/) entered in production in 2022 Q2.

This proposal aims to fund the 2022 Q3 Continued Operation and implement Software Development and infrastructure improvements.

Our detailed [proposal can be found here](https://docs.google.com/document/d/1Hh1Vjn2tPwx2fAPFoY5WfOeltEJy-B-1HlukPSHLTI0/edit?usp=sharing).

Community feedabck to our proposal can be found in the [Discussion Post](https://polkadot.polkassembly.io/post/1212).


Polkadot decentralization analytics, Continued Operation and Improvements.

**Proponent**: 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf

**Date:** 11th August 2022

**Requested DOT:** 12,471.517 (USD $100,383.24)

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

**Raw Data:** https://docs.google.com/spreadsheets/d/1XwZjMtHVV8OgvqeUZQgMvY45nSL3tD19RFfTyIcRDq8/edit?usp=sharing

**Full Proposal:** https://docs.google.com/document/d/1cpNAYIdSlF9_uofueNHMkmvEtUPExBnJ92zZRgk9Afs/edit?usp=sharing

---

### Service Details

The last quarter showed a number of ups and downs in terms of numbers but still recorded high demand for Polkadot and OnFinality. May had a higher activity than the rest of the quarter which also had our largest daily responses in the quarter of over 224 million in a single day to Polkadot. 

We continued to execute on our efforts to provide unprecedented service stability and reliability to this ecosystem. All supported networks exceeded our 99.9% target, including 99.98% uptime for Polkadot over the last 90 days . At this stage, OnFinality is operationally striving for a minimum of 99.99% availability, which means less than an hour of downtime each year.

Between 2022-04-01 and 2022-06-31 our Polkadot API service has:

- Served a total of 12,264,823,022 (12 billion) responses
- Accumulated over 85 TB of data egress 
- The highest daily total was 224,203,539 responses in a single 24 hour period
- Our rolling 7 day average at the end of this period was over 133 million responses each day.
- Westend had over 609  million API responses in the period
- Statemint had over 353 million API responses in the period
- All time totals for Polkadot is 65,360,914,521 (65 Billion) since November, 2020
- At the end of this period the 90 day uptime for Polkadot, Statemint, and Westend was 99.98%, 99.98%, and 99.99%

**Full Proposal:** [https://docs.google.com/document/d/1cpNAYIdSlF9_uofueNHMkmvEtUPExBnJ92zZRgk9Afs/edit?usp=sharing](https://docs.google.com/document/d/1cpNAYIdSlF9_uofueNHMkmvEtUPExBnJ92zZRgk9Afs/edit?usp=sharing)

OnFinality High Performance Public Infrastructure (Q2 2022)

Blockchain Training Alliance (BTA) has been providing Blockchain training and certification globally since 2017. BTA is seeking to create a Substrate-specific course that will allow developers to learn how to effectively build on Polkadot. The partnership provides new developers from the Web2 space to learn Polkdadot technology and increase developer activity within the Polkadot ecosystem.

Course Overview:

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

This Substrate-specific training course, 20 hours in length, which will be available at no cost on the BTA website for any interested students to enroll into.

Certification

An exam for certification will be available at the end of the training course. Getting certified will demonstrate students have the skills needed to build applications and solutions on Polkadot.

Link to proposal: [https://docs.google.com/document/d/1Q7VdsqyLHFThvv2dTfOSfYovfRkfEj9LIrOGlySmWL8/edit?usp=sharing](https://docs.google.com/document/d/1Q7VdsqyLHFThvv2dTfOSfYovfRkfEj9LIrOGlySmWL8/edit?usp=sharing)

Substrate Training Course and Certification

Beneficiary: OpenSquare(12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4)
Date: 07/20/2022
Requested Allocation: $143,760(18,854 DOT by the EMA30 price of 08.03.2022 on subscan)

---

OpenSquare has been actively developing new features for products including [dotreasury](https://www.dotreasury.com/), [subsquare](https://www.subsquare.io/), [statescan](https://statemine.statescan.io/), [off-chain voting](https://voting.opensquare.io/). This is a proposal for some delivered features and new development plans.

## Delivered

### Child bounties(dotreasury + subsquare)
We implemented child bounties feature for both **dotreasury** and **subsquare**. The supported user stories includes:
1. As a user, I can see all child bounties of one parent bounty.
2. As a user, I can see the list of all child bounties.
3. As a user, I can see the child bounty detail, while it includes the child bounty metadata, timeline.
4. As a user, I can give comments about one child bounty. 
5. As a user, I can go directly from dotreasury to subsquare to view the child bounty context where the child bounty curator can edit the context.

Please check the time we have spent on the development.

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| Design   | 32 | 1 FTE * 4 days |
| Scan scripts   | 60 | 1 FTE * 1.5 weeks |
| Backend server   | 40 | 1 FTE * 1 week |
| Fronted  | 160 | 2 FTE * 2 weeks |

Total: 292 hours.

### Subsquare polkadot integration

Check [here](https://polkadot.subsquare.io/) for the deployment. Generally the work includes:
- Data indexing for historical governance workflow
- Basic stuff design.
- Add code to support polkadot.
- Server setup.

Usually we request $10k for each chain integration and basic setup.

There are also some common features we have delivered since this deployment. The features includes:
- Setting a banner for my post and proposals.
- Adding a poll for my raised discussion.
- Support any of the signatories to edit the proposal context. Previously only the signatory who submits the extrinsic can edit.
- New editor and markdown renderer. We can show the latest polkadot account identity with them after we mention a polkadot account on a post or comment.

We will not request specific fund for above common features. Part of the cost can be covered by the routine maintenance fee we requested from each deployments.

### Statescan on-chain NFT metadata support

Problems: Statescan supports NFT defined by JSON object hosted by IPFS, but there is NFT format whose metadata and image info are defined on chain. We can not recognize it before this feature. Please check the details on this [issue](https://github.com/opensquare-network/statescan/issues/1054).

For development, the main work includes:
- Block business indexing to find the target NFT definition.
- Refactor and add the onchain NFT metadata parsing business to NFT parsing scripts.
- Fronted pages adaption to this onchain NFT format.

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| On-chain NFT metadata   | 60 | 1 FTE * 1.5 weeks |

### Cost

Taking hour rate $80.
|  Item   | Hours  | memo |
|  ----  | ----  |  ----  |  
| Child bounties for dotreasury and subsquare   | 292 | $23,360 |
| Statescan on-chain NFT metadata   | 60 | $4,800 |
| Polkadot subsquare integration and setup   | - | $10,000 |
| Total  | - | $38,160 |

## New features plan

### Dotreasury

#### Problems
Dotreasury serves very well as a treasury dashboard and we received lots of praise for its well designed UX, but it still has following problems:
1. Users have to signup to leave comments, but we should make a web3 oriented product.
2. Subsquare, as another product of OpenSquare, also supports proposals' discussion. It may cause a dispersion problem. So we may remove comments from dotreasury and redirect users to subsquare.
3. It's more like an explorer, but it will be better if we can make it a Dapp where users can interact with chain, like proposing proposals/tips/bounties, closing tips, claiming bounties, etc.
4. Dotreasury should provide more statistic data, like councilor, beneficiary and proposer's behaviors or related data.
5. It's not tracking treasury proposal pipeline through democracy.
6. There are still some polish work we can do, for example, we should show a counting down component for a bounty/child bounty pending payout.

#### Web3 oriented development

Less web2, more web3 🚀.

- Remove interfaces for user signup and login with email or username.
- Add connect with polkadot key. It should support polkadot.js extension, subwallet, talisman and nova wallet.
- Remove comments and redirect users to Subsquare if they want, but the legacy comments will be kept.
- Users can still grade with the connected account while every grade still can have a comment.
- Connected account can manage the proposal title, category, status and urls as an admin if the account is the proposal proposer or beneficiary.

#### Dapp

Dotreasury now has about 8k unique vistors per month on average, and we are sure it could be a good candidate interface for users to do treasury related actions. The planned features includes:

- Treasury proposal
    1. Create new treasury proposal.
    2. Vote a proposal on proposal detail page when there is a motion.
- Tip
    1. Create new tip including `TipNew` and `ReportAwesome` calls
    2. Retract a tip
    3. Endorse a tip
    4. Batch new tips and batch endorsement
- Bounty
    1. New bounty and new child bounty(still no multisig support in this plan)
    2. Accept curator
    3. Claim a bounty/child bounty

#### More statistics

There should be more statistics data besides current data. We want to add more participants' data in this plan.

- A participant list page which each line contains the participant and his/her roles, while the role can be councilor, proposer, beneficiary.
- A participant detail page. Users can switch the role of this participant.
    - As a councilor, we can see the renure, motion/tip attendance.
    - As a proposer, we can all the proposed proposals, bounties and tips.
    - As a beneficiary, we can see all the related proposals, bounties and tips. We can also see the calculated total benefited crypto/fiat value.
- Users can grade any participant on the corresponding detail page.

Please check the design of councilor page and check the figma source file [here](https://www.figma.com/file/zbDvKAgmEPFJOVvUyKzUAu/doTreasury---Preview-Version?node-id=0%3A1).
![](https://i.imgur.com/ClxTpsq.jpg)



#### Enhancement and polishment

- Currently we only track treasury proposal process by council motions, it's not engouth. We will track the process through democracy in this proposal.
- We will polish some counting down components for bounty pending payout and tip closing.

#### Budget

|  Item   | Estimated Hours |
|  ----  | ----  |
| Design   | 40 |
| Web3 oriented development | 40 |
| Dapp  | 160 |
| More statistics | 200 |
| Enhancement and polishment | 120 |
| Total  | 560  |

### Subsquare

#### Problems
Subsquare is a governance platform designed for substrate based chains. It indexs the on-chain governance data and provides interfaces for community to discuss and make calls to propose, second, vote, etc. It works well serving kusama and polkadot, but it can be still improved with following issues:

- It syncs proposal context from polkassembly, but it will better if it can sync comments and discussions, so it will be more convenient for users to view more governance data without leaving subsquare.
- It will be good if we can notify users specific governance proposal timepoint and context with email.
- We need a user profile page to show the basic user information, participated treasury/democracy proposals, raised discussions and list of comments.
- Treasury proposal decided by democracy should be in the proposal timeline.
- Support login with subwallet/talisman.
- Dark mode

#### Sync and load polkassembly

We have plans to create a protocol for governance data decentralization, but it will be big change and we may begin to do it after the implementation of governance 2. Syncing and loading data from polkassembly will be a solution to benefit users better view governance context and discussions. Work includes:

- Load comments for proposals and show them on a specific tab on proposal detail page.
- Sync all discussion topics and load comments on the discussion detail page.

In this proposal we will **not** implement login with polkassembly account on subsquare, while we think data decentralization and web3 should be the correct direction. If users want to leave comments for posts from polkassembly, subsquare will redirect user to the polkassembly page.


#### Subscription and notification

This feature enables user to subscirbe a governance event and subsquare will notify users when it happens. We know some tools like [web3alert](https://web3alert.io/) provides services to subscribe a on-chain event, but solution of subsquare differs in following ways:
- It provides off-chain governance events like a proposal context is provided.
- Notification of on-chain events will provide more related information, for example subsquare will also provide the pipeline info when a referendum started, so users can know this governance proposal full timeline, not just a event with the referendum index.
- Subsquare send the notification by email.

Planned subscription and notification items includes:

- Treasury(proposal, tip, bounties) lifecycle events and related context.
- Motion(Council, Tech. Comm.) lifecycle events and related context.
- Democracy(referendum, public proposals, external proposals) lifecycle events and related context.

#### User profile page

We need this profile page to view users' participation to governance. It will provides:

- Baisc user info address, links to explorers, email(if it's public), username(if registered via email and username).
- All created discussions.
- Proposed treasury/democracy proposals.

#### Enhancement and polishment

There are several improvements similar with those we proposed with dotreasury, but budget of implementation on subsquare will be much lower since it shares part of the logic and code.

- Add democracy process to the treasury proposal timeline.
- Support login with subwallet/talisman.
- Add counting down for bounty pending payout and tip closing. User can claim a bounty or close a tip when the counting down is over.
- Add create new tip interface.
- Dark mode.


#### Budget

|  Item   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Sync and load polkassembly | 112 | 2 FTE * 7 days |
| Subscription and notification | 160 | 2 FTE * 10 days |
| User profile page | 60 | 1 FTE * 7.5 days |
| Enhancement except dark mode | 40 | 1 FTE * 5 days |
| Dark mode | 60 | 1 FTE * 7.5 days |
| Total | 432 |  |

### Off-chain voting

OpenSquare [off-chain voting](https://voting.opensquare.io/) is a common good product which provides off-chain democracy tools for polkadot ecosystem. It has helped projects collecting voting for over 45 proposals. It acts like [snapshot](https://snapshot.org/#/) in the ethereum ecosystem, but it provides different features.

- It supports substrate based chains.
- It supports multiple asset types including substrate native asset, ORML asset, statemine/statemint asset, ERC20 token.
- It supports substrate biased voting strategy.
- It can be configured to support voting from different assets like one proposal vote from $KSM or $DOT.

#### Problems

- Users have to contact OpenSquare team to add a space for them. Check [here](https://github.com/opensquare-network/collaboration/discussions/813) for details.
- Users can not be notified when a new proposal is created.

#### Space creation and configuration

We'd plan to provide users interfaces to seamlessly create spaces for their off-chain voting. 

- User can add a new substrate based chain with multiple endpoints.
- User can add an asset for a chain, choose the asset type, and the backgroud job will check the asset availability.
- User can create a space, while the attributes include id, name, symbol, decimals, threshould to create/vote proposals, vote strategies, log/sns cover, etc.
- User can add/remove supported asset when creating a space.
- A space author can add maintainers for the space. Evenry maintainer has same authority with the author.
- A space maintainer can edit the space configurations.
- A space maintainer can delete the space.

#### In site notifications

- Users have to join a space to receive notifications.
- Users can config the notification types they may want to receive. The first batch of notification types includes new proposal created, new vote, close to a proposal voting end, proposal closed/terminated.
- Users will get in-site notifications when the subscribed events happen.

#### Budget

|  Item   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Space creation and configuration | 288 | 3 FTE * 12 days |
| In site notifications | 40 | 1 FTE * 5 days |
| Total | 328 |  |

## Total budget

Taking hour rate $80, please check the budget list. For details of each item, please check above sections.
|  Item   | Estimated hours  | Fiat cost |
|  ----  | ----  |  ----  |
| Delivered features on dotreasury/subsquare/statescan | 352 + polkadot subsquare integration | $38,160 |
| Dotreasury new features development | 560 | $44,800 |
| Subsquare new features development | 432 | $34,560 |
| Off-chain voting new features development | 328 | $26,240 |
| Total |  | $143,760 |

- Beneficiary: 12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4(identity is OpenSquare)
- We will update the allocated DOT by the price of subscan on the submission date.

## Possible questions

#### Dotreasury and Subsquare shares some business, what's the plan for these 2 products direction?

- Dotreasury will foucus on the treasury mechanism. It will provides more statistics data about treasury income, output and participation.
- We still insist that the treasury need a retrospective mechanism which means there should be ways for community's supervision. We will promote current treasury spend grade method and seek more ways to help the community supervision.
- It will be a dapp besides a treasury dashboard.
- Subsquare is designed to help the whole on-chain governance process. Some treasury details like estimated fiat value and statistics data won't be provided.

#### Is the code of subsquare open source?

Currently still not. We have plans to open it when we have enough deployments and the grant will be closed to our development cost. OpenSquare team has been actively developing subsquare for over 10 months. Though we have gotten grants from dotsama and other para-chains, they are not enough to cover our cost. Requesting treasury from dotsama to cover all the cost sounds not the best idea. We beg the understanding that OpenSquare team has to keep alive before contributing more features.

#### What's your next plans for subsquare?

Gov 2.0 implementation and data decentralization. Data decentralization will be after the implementation of governance 2.0. We may refer to OpenSquare [qa spec](https://github.com/opensquare-network/qa-spec) to make a protocol for governance discussion data decentralization.

#### There are few polkadot/kusama proposals on off-chain voting platform, so how do you make sure this platform will benefit dotsama?

- We're drafting some off-chain proposals with which we aim to collect the community opinions and trigger topics the community may think deeply.
- The ecosystem governance activeness will help the dotsama itself.

OpenSquare treasury proposal for develiered features and new features development for dotreasury, subsquare and statescan

This proposal aims to partially cover the rewards for the 8-week online amsterDOT hackathon.

The hackathon was organized by 8 teams which put up 20 bounties for advancing contributions to the Polkadot and Kusama ecosystems. Furthermore, an Open Category was included to accommodate “anything Dotsama”. The hackathon had a combined rewards mechanism. The first component is rewards provided by the teams which own the bounties (up to $190k). The second component is a $150k prize pool by the Polkadot Treasury (i.e. the subject of this proposal) which was distributed by a jury comprising 7 teams from the ecosystem.

13 out of 14 eligible submissions were given a share of the Polkadot prize pool following the jury vote. The solutions range from full-fledged UIs, dashboards, (command line) tools, a p2e game, to the winner of the hackathon - Morph, an XCM tool for intuitively handling cross-chain transfers.

Please find the full proposal [here](https://docs.google.com/document/d/1iafqqLvsc7w9KEmSiTnp0T2fmMDmOVjfjp1QzAb8KNg)

AmsterDOT Hack

This proposal aims to reimburse the costs associated with the organization of amsterDOT Conf.

amsterDOT Conf was a 4-day event co-organized by 10 Polkadot & Kusama (parachain) teams. The event took place on 4 days (20-23th April 2022) at 3 venues in Amsterdam

With 356 attendees, 32 recorded conference talks, 13 workshops, and countless unforgettable moments spent in each other’s company, we humbly look back at amsterDOT as an organic ecosystem success which established a new bond in our community.

Please find the full proposal [here](https://docs.google.com/document/d/1nXimpXshCYy4hkpAf8m5LvbwMsm_2B4xH3kjmYvWcso)

AmsterDOT Conf

This proposal aims provide funding for the evangelists’ to operate their tasks and motivate them to contribute continuous effort to the Substrate developer community.

Oneblock plans to run a global Substrate evangelist Program to reach a broader group of audience, grow the Substrate developer community and push for the massive adoption of this technology, and at the end will further contribute to develop and grow the Polkadot ecosystem. This program will have a clear growth path and promotion mechanism to motivate the evangelists to contribute for the technology promotion and adoption.

Substrate has gained growing influence in China’s blockchain dev community in the past 24 months. Polkadot outperforms other new L1 chains as the second largest ecosystem in the size of active developers and it clearly has something to do with the continuous promotion and adoption of Substrate as a technology in China and global-wise. Oneblock views the necessity of doubling down the effort of promoting and adopting Substrate which directly contribute to the growth and thrive of the Polkadot ecosystem. Substrate Evangelist Program is a natural extension of Oneblock’s successful effort to promote Substrate and grow the Substrate developer community, from the perspectives of the influential coverage and the geographic market.

Till Mar 5th,a total of 125 applicants come from China, Nigeria, Russia, Minsk, Ukraine, Solomon, Turkey, Togo, Iran, Morocco, Australia, South Africa, New Zealand, America, etc 14 countries.

On April 9th,We hosted the Substrate Evangelist Program kickoff meeting and invited Dr. Radhakrishna @Web3foundation & Parity Asia Pacific Head @helenawang to join the panel and share the latest Polkadot news.

In the past April, May, and June, Substrate evangelists promoted Substrate ecosystem-related content.here you can get all the details [here.](https://docs.google.com/document/d/14o481tQZBxGPr1xBZq-sSVt5HxzbNAItOFGXGt1SLCo/edit?usp=sharing)

Please feel free to leave a comment!

Proposal of Substrate Evangelist Program

> This is a follow up proposal to what we submitted before:

> [#94 Cloudflare Enterprise Plan for Subscan from January 2022 to April 2022](https://polkadot.polkassembly.io/treasury/94)

> [#95 The Infrastructure Costs of Subscan for Polkadot Network from Sep 2021 to Dec 2021](https://polkadot.polkassembly.io/treasury/95)

This proposal is used to pay the infrastructure costs of the Polkadot network and its testnets. The payment involved in this proposal does not include any software development, human resources, etc. 

Previously, every infrastructure cost of Subscan was applied by submitting treasury proposals separately. The application time was asynchronous and the process was complicated, which is easy to cause some confusion to users, and it is inconvenient to clearly obtain the monthly cost. Therefore , this application will count all unpaid infrastructure costs of the polkadot network before June 30, 2022, including:

- GCP: January 1st - June 30th
- Datadog: January 1st - June 30th
- Cloudflare: April 15th - June 30th

In the future, the billing time of all bills will be completely unified, which is more convenient for community management and supervision.

This time, we plan to apply for a total of **50,814 USD in Polkadot**, the amount of DOT will be converted based on the **EMA7 price** on the day of the official submission.  

- 2022-07-27 10:59:42 (+UTC), Block #11343941
- DOT EMA7 Price ( USD ): 7.051;
- Number of DOT: 7,205.831
> https://polkadot.subscan.io/tools/price_converter?value=50814&type=time&from=USD&to=DOT&time=1658919600

**Billing details can be read [here](https://docs.google.com/document/d/1wXSELzfmNH1CP9JbI5Nq1wu8H83vnxJJ22TEjkF2Wgg/edit?usp=sharing).**

Subscan | Infrastructure Costs of Subscan for Polkadot & Westend & Rococo Networks

👋 *Hola* dear community and council! I'm [Daniel](https://github.com/olanod), long time ecosystem builder, senior "king" ambassador and founder of the [Virto Network](https://virto.network), the future hub of sustainable d-commerce and services for Polkadot. 

Earlier this year [with your support](https://polkadot.polkassembly.io/post/825) my team and I built [`libwallet`](https://github.com/virto-network/libwallet), an ultra-light and portable framework for creating fast, secure wallets of all kinds(web apps, extensions, mobile, desktop, hardware, hosted, etc.). It has been an on-going effort of continuous redesign and iteration to get to a point where we are now comfortable with its current architecture to start building real-world and user facing products that accommodate the many interesting use cases of our interconnected ecosystem.

It's our mission to *reeally* bring blockchain to the masses, for more than two years we've been creating solid foundations* and have being learning first hand from regular citizens what might take for people to use blockchain technology without realizing it and how not to compromise decentralization in the process.

*_**Previous work**: Web3 grant for [orml-payments](https://github.com/open-web3-stack/open-runtime-module-library/tree/master/payments), Kusama funded [Sube](https://github.com/virto-network/sube), [Kreivo](https://kusama.polkassembly.io/post/1520) common good parachain for Kusama, [Bloque](https://bloque.app) insta-stores, decentralized on&off ramps._

## Problem

Although a lot of progress has been made all over the place to ease the entry barrier to the Web3, we are still miles away from reaching mass adoption, it's inspiring to see the many efforts the community put in educating new users in the ways of blockchains and decentralization but there's still a long, possibly never ending journey ahead.   

It's great to see how the blockchain industry has one of the highest levels of innovation and technology advancement ever seen, the field moves at incredible speeds that are hard even for seasoned technologists to catch up, trying to reeducate the world in "the new better ways" is a common approach in Web3 however it might not be the best option, we could be neglecting the big majority of the population that won't try to follow the latest and greatest, instead we need to be inclusive and find ways to translate the new revolutionary ideas to a common language that results familiar to the people.

## Solution

We want help newcomers to easily navigate the world of Web3, wallets are the first interaction point of a user but we are starting simple and a bit different, with a set of constraints that I'll call now _the mom rule_, any term or action that would  require me to explain my mom what it is should be avoided, terms like(at least initially) blockchain, private key, hash, staking, NFTs, browser extension, or even wallet don't pass the mom rule so they are not making it in the first cut since they need explanation.

No metaverse-enabled-NFT-capable killer wallet this time, instead let us introduce you what we hope will become your reliable partner in the quest of exploring the sometimes scary Web3.

## [**Fido**](http://fido.sh) 🐶  Your trustworthy Web3 companion
![Logo Fido](https://fido.sh/fido.svg) 

Fido is more than a wallet, it's a development platform. On top of `libwallet` and a plugin runtime we've [prototyped before](https://github.com/virto-network/valor) we are building an ecosystem of wallets for different use cases that can be extended with a variety of services(skills and tricks) developed by the community in their language of preference(JS and WASM). Our target audience being non crypto-native users(including developers) means our product has to feel familiar(e.g. easy login, familiar technologies) yet decentralized.  
The Fido project breaks down mainly in two pieces,

- **Fido bot**: Your companion as hosted wallet that can be interacted with via chat using Matrix, the decentralized communications protocol(bridges to other chats can come later) or other protocols like a traditional HTTP API that gives developers access the different **skills** your Fido has learned. There will be multiple ways to install Fido so it can stay alert 24/7 and give you a hand whenever you need, depending on the platform it will use the most appropriate libwallet vault backend to keep secrets secure, an interesting one being a vault based on Matrix's [SSSS](https://matrix.org/docs/guides/implementing-more-advanced-e-2-ee-features-such-as-cross-signing#3-implementing-ssss) that we have [prototyped](https://github.com/virto-network/summa/pull/9), it allows backing up your wallet securely in your Matrix account to reduce the risk of losing access.

  - **Self-hosted** provided as a binary, docker image, or per-configured OS image that can be burned directly to a linux computer as small as a RaspberryPi Zero.
  - **Embedded Hardware**: Mini-Fido provided as firmware for popular microchips. Initial support for ESP32(-C3) and (future bonus based on what I have available) nrf52840/nrf9160 or the super tiny SAM L11 that could become more of a complementary chewing toy/key-holder/jewellery for Fido that can be powered with just an NFC field.
  - **In browser**_(not yet in scope)_ backed by a combination of service/shared workers(cool web technology) that allows Fido running fully decentralized in your browser without having to install anything. We would also provide an embeddable iframe/web-component that allows third-party applications access the many skills of your Fido. For Virto Marketplaces it will be an important feature that allows executing payments or approve certain transactions.
  - **[Matrix app service](https://matrix.org/docs/guides/application-services)**_(not in scope)_ For communities(like Virto's local communities and marketplaces) with their own Matrix server, this allows non-technical users to have an exclusive companion created for them automatically as soon as they join.
  - **Desktop shell**_(not in scope)_ Embedded in the desktop application.👇

- **Fido Shell**: A decentralized super-app for the Web(not an extension), desktop, mobile and terminal. It's  the graphical interface and Matrix client used to manage your Fido(s), where you can teach it new skills or tricks(mini appplets) and aggregate the many compatible applications created by the community.
_NOTE:  Initiall functionality will be very basic, we will only provide an "accounts skill" with a simple applet for minimal token transfers support and a very simple chat._

  - **Web**: Hosted in [fido.sh](https://fido.sh) and in decentralized form.
  - **Desktop**: As single executable file that works(should) in most platforms(I'll personally only test on Linux but other team members and community will for extended support).
  - **Mobile**(not in scope): Very similar deployment as the desktop application for IOS and Android. 

> ⚠️ To set expectations right, this first delivery of the Fido bot and the Fido shell should be consider experimental software not suitable to for managing large amounts of money that could be lost due to bugs in any of the components of our system. After launch we hope to gather enough feedback from the early adopters in the community before we recommend Fido for production use. 

> 🤔 Hard-core crypto fans might initially find the wallet boring as we are focused more on the real-world use cases of Virto that need to pass the _mom rule_, like buying a t-shirt, ordering food, calling a taxi, etc.

## Development and Milestones

We will divide the work in 3 stages that will last a total of **4-5 months**, after previous experiences developing small pieces of software at a time that are hard to visualize as part of a bigger whole, this time we aim for a longer runway as it has proven difficult to attract/keep talent when working conditions are short term driven and uncertain.

### Stage 1 - Design and architecture
Estimated duration: **1 month**

```
| Task                                         | role  | hours |
|----------------------------------------------|-------|-------|
| Project planning and break-down in GH issues | lead  |  1w   |
| Shell concept design                         | desig |  1w   |
| Brand, logo, web design and components       | desig |  2w   |
| Basic fido.sh with chat for updates          | f-dev |  2w   |
```

### Stage 2 - Wallet backends, Skills API & Shell UI components
Estimated duration: **2 months**

**This is the main stage of development for creating the core building blocks with great emphasis in embedded(no_std) support.**

```
| Task                                         | role  | hours |
|----------------------------------------------|-------|-------|
| Libwallet embedded vault (hardware keys)     | e-dev |  2w   |
| Libwallet Matrix vault with embedded support | b-dev |  2w   |
| Libwallet `pass` vault for hosted Fido       | b-dev |  1w   |
| *Libwallet BLE proxy for Fido->mini-Fido     | e-dev |  3w   |
| APIs design and "Skills SDK" prototype       | lead  |  2w   |
| Web components for shell and tricks/applets  | f-dev |  4w   |
| Fido Skills JS+WASM runtime                  | b-dev |  3w   |
```
_* Bonus with low priority_

### Stage 3 - Integrations and deployments
Estimated duration: **1 month**
``` 
| Task                                         | role  | hours |
|----------------------------------------------|-------|-------|
| Bot and Skills management Skill/API          | b-dev |  1w   |
| Blockchain&Accounts skill with Sube library  | b-dev |  2w   |
| Shell implementation and bot integration     | f-dev |  3w   |
| Accounts applet implementation               | f-dev |  2w   |
| *Bot management applet                       | f-dev |  1w   |
| *Developer applet for debugging              | f-dev |  1w   |
| Shell and Bot packages(image,docker,bin,...) | f-dev |  1w   |
| Testing and QA                               | lead  |  1w   |
| Infrastructure set-up and server deployments | lead  |  1w   |
```
_* Bonus with low priority_

Estimated total hours = `31w * 30h/w = 930h`  
Total USD cost with avg. hourly rate = `930h * USD$75/h = USD$69_750`  
**Total DOT cost** = `USD$69_750 / 7.394 USD/DOT(EMA30) = 9_433 DOT`

Fido Wallet(s)

**I am opening a proposal at the request of the Anti-scan Bounty Curation team to top-up their bounties in order to continue with their initiative for the months to come, after the test period. Reasoning behind the proposal, along with budget, a report on all child-bounties opened and roadmap can be found on their post below.**

_______________________________________________________________________________________________________

Link to the original discussion post: [here](https://polkadot.polkassembly.io/post/1159). 

With this proposal we request a top-up to the [Anti-Scam Bounty](https://polkadot.polkassembly.io/bounty/11) to continue funding the community initiatives that aim to protect users in our ecosystem from falling victim to scams.

The bounty expanded on the previous community initiative targeting scam sites that was ongoing for several months, by adding new tasks that aim to create a holistic solution that addresses the problem from several aspects, while bringing awareness to the community, and educating users of both the problems and the efforts to address them.

The Task to find and take down scam sites is still the flagship of the bounty, taking the lion's share of the rewards, but several others of the tasks are being worked on with good progress and we aim to have all of them completed/active by the end of September 2022.

All the details of the proposal, along with spending analysis, can be found [HERE](https://docs.google.com/document/d/12JAtLuwzQjk5AejR_cxvMgz1xnWGwr90r2L34zBs1v8/edit). 

______________________________________________________________________________________________________

PLEASE NOTE YOU WILL NOT BE ABLE TO SEE THE BENEFICIARY IDENTITY ON-CHAIN (this is the address of the bounty, created once the bounty proposal is accepted) BUT YOU WILL BE ABLE TO CHECK THIS [ON SUBSCAN](https://polkadot.subscan.io/account/13UVJyLnbVp9RBZYFwHYxa6GPKJ2SqkGg4Mo7jG7uLAbPkT8).

![](https://i.ibb.co/2tbzG3H/Screenshot-2022-07-18-at-15-17-31.png)

Treasury Proposal: Anti-Scam Bounty Top-up

**Omni: Polkadot Enterprise desktop app Treasury Proposal - Milestone 2 - Public release:**

[https://docs.google.com/document/d/1TJDK8gqxAI9Q2VjdSEc4Zm8-h0Opv-dbOqSw4aSjNPs/](https://docs.google.com/document/d/1TJDK8gqxAI9Q2VjdSEc4Zm8-h0Opv-dbOqSw4aSjNPs/)

![](https://i.postimg.cc/G3yzmByq/2022-07-12-18-12-07.jpg)

**Feature set of the proposal (see [proposal](https://docs.google.com/document/d/1TJDK8gqxAI9Q2VjdSEc4Zm8-h0Opv-dbOqSw4aSjNPs/))**
- Foundation for Enterprise app:
  - Implementation according to defined [Quality Attributes](https://docs.google.com/document/d/1fVAECuA_6oc6IkCoXu1Hpe1AQDh48d7pFuai1Q0jAv0/edit#heading=h.yqdlcft3mn8k)
  - Light clients integration
  - Data verification for parachain nodes
  - Secure protocol integration for encrypted communication
- Initial Omni Enterprise v1.0 feature set:
  - Easy-to-use multisig accounts
  - Integration with Parity Signer
  - Assets management across all Polkadot eco networks
  - Full set of [features](https://docs.google.com/document/d/1TJDK8gqxAI9Q2VjdSEc4Zm8-h0Opv-dbOqSw4aSjNPs/edit#heading=h.67i7d6qclge2)

\
**Context of the proposal**
\
\
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **Omni Enterprise**
is a desktop application that works around the limitations of Polkadot.js Apps
and can provide a single point-of-view for stakeholders with advanced needs in the entire ecosystem.
It should sync shards (i.e. multi-sig & proxies should not need manual construction for each signatory),
support complex proxy/multi-sig combinations, should amalgamate multiple operations into a
single transaction, and handle staking, asset management, and voting across all shards in a
single user-operation

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; On February 2022,
our previous Polkadot Treasury proposal was [approved](https://polkadot.polkassembly.io/motion/156),
and in July 2022 we have successfully completed the scope of the proposal.
Please refer to the [Omni Enterprise Milestone 1 report](https://docs.google.com/document/d/1EIFH0M8KiveOwxynfAdhcAFnyJW2XIQgylUPFTvqHlw/)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This proposal
covers the first release of the Omni Enterprise **high quality desktop application
for Polkadot & Kusama ecosystem**
that will provide **easy-to-use multisig accounts**,
**light clients nodes** usage and **[Parity Signer](https://www.parity.io/technologies/signer/)** support.
\
\
\
**Please review the full proposal with a detailed description & costs:**
[https://docs.google.com/document/d/1TJDK8gqxAI9Q2VjdSEc4Zm8-h0Opv-dbOqSw4aSjNPs/](https://docs.google.com/document/d/1TJDK8gqxAI9Q2VjdSEc4Zm8-h0Opv-dbOqSw4aSjNPs/)


Omni: Polkadot Enterprise desktop app Treasury Proposal — Milestone 2 — Public releas

[Talisman](https://talisman.xyz) is a community-owned wallet that enables users to “traverse the Paraverse” with ease. We believe in a future where everyone has freedom via true agency over their intentions and finances, and we believe that DotSama will bring this to fruition. 

For more on Talisman, please see the following talks from Polkadot Decoded 2022: Agyle’s [How Talisman is bringing multi-chain to the masses](https://www.youtube.com/watch?v=c7tZjVv70Jk), as well as Jonathan's [introduction to light clients in Talisman](https://www.youtube.com/watch?v=oaidhA5eL_8).

Today, because of its early stage of development and complex multi-chain architecture, both Polkadot and Kusama are changing rapidly and the user experience (UX) can be confusing for end users. It’s our goal to solve that using user experience design and storytelling. We abstract away the complexity of underlying implementation and provide a friendly user experience when using DotSama and a way to discover new applications and services available to end users, while keeping them safe and educated about the actions they are taking.

In this proposal, we are seeking to fund development of a cross-chain transaction history service for the benefit of users, parachains and applications. We believe this will be an advancement in usability and security for end users, as they will be able to more easily understand the actions they have taken across different parachains in DotSama. Parachains and applications that have a presence across multiple parachains will also have an easier way to show users their relevant actions.

We regularly gather customer feedback as we work to uncover difficulties customers have with Talisman and within DotSama. Here are what some users have told us about the need for better cross-chain transaction visibility:

- “Sometimes I don’t even know what assets I have. I do it the hard way, I have them all listed in p.js and I have to cycle through each of the projects to check my balances. When I check on sub.id everything loads, but sometimes locked tokens are missing. So I have to switch parachains, then visit each dapp to keep track.”
- "I would like to see my transaction history all in one place. This would be a huge help for example with my tax filings. Right now it's a real hassle."
- “I want to be able to see multichain assets across multiple parachains.”

Please see the [full description here](https://docs.google.com/document/d/192asiQ13s4EAfXFFDFgKm_W3cqBVPPPxB5VNAig7keE/edit?usp=sharing).

Thank you everyone who has commented during the [community feedback stage](https://polkadot.polkassembly.io/post/1152) of this proposal. We have corresponded with everyone that has provided comment.


Talisman Proposal: Cross-Chain Transaction History Service

This is a follow-up proposal on what we submitted in the beginning of [April](https://polkadot.polkassembly.io/treasury/107), to further fund the development of the RPC services and to cover the maintenance costs of it.

This new proposal includes one Milestone.

**Milestone 1:** Continue to run the Polkadot, Statemint and Westend RPC services on dedicated hardware, located at small independent co-location sites in Sweden.
### Report

During Q2 2022 our Polkadot RPC node served on average **4,176,442** requests per day, and in total we served **375,877,980** requests.

During Q2 2022 our Statemint RPC node served on average **218,805** requests per day, and in total we served **19,692,450** requests.

During Q2 2022 our Westend RPC node served on average **291,186** requests per day, and in total we served **26,216,640** requests.

- Our full proposal can be [read here](https://docs.google.com/document/d/1FE_KBaChASiWQGRV_LoKHooLd691UR4GlMX-yqNpgeg/edit?usp=sharing).

Polkadot RPC services Dwellir Q3 2022

# Background
During the past 1.5 years, We ([Manta.Network](https://www.manta.network/)) developed the on-chain privacy solution for DOT/SAMA eco-systems using zkSNARKs, here are some highlights:

**Dolphin Testnet V1(unincentivized)**

- 60,000 + transactions
- 6,000+ distinct addresses
- send more private transaction powered by zkSNARK in 3 months than Tornado.cash in 1 year

> "The Dolphin Testnet] is really good... The experience is really pleasing, congrats to
  the team.”
>                                                              (Thibaut Sarda, Core Developer, Polkadot.js)

**Dolphin Testnet V2**

- 1/10 ZCash's (Sapling) constraints count in zero-knowledge-proof circuit
- Improved prover performance from 30 sec to 2 sec

As the first project in the substrate space (and very few in the entire Web 3 space) working on zero-knowledge-proof based developed, we experienced a lot of difficulties in terms of ZKP tooling. As a result, we developed a lot of internal tooling that could benefit peer substrate teams deploying zero-knowledge-proof techniques securely and quickly into their project. 

# Potential Applications
- DID projects like KILT can leverage OpenZL to make their KYC/AML process more decentralized
- Cross-chain Bridges can leverage OpenZL to make the bridges high-performance and trust-less
- DAO tooling project can leverage OpenZL to build MACI for governance
- Project like Astar can leverage OpenZL to build ZKRollups 

and many more

# OpenZL Design
![](https://user-images.githubusercontent.com/720571/167014503-10117012-c898-4d54-802a-966eb02dab98.svg)

OpenZL is an open-source library that helps practioners (especially in Web3 space) to develop and deploy secure, high performance zero-knowledge proof code in production. It tries to bridge the gap between low level cryptographic primitives and devlopers' need to build scalable protocols using zero-knowlege proof cryptography securely and quickly. More specifically, many developers today want to leverage zero-knowledge proof systems to build powerful protocols like ZCash/Manta/ZKSync. However, they are facing two less than ideal choices; first, building a protocol using high-level languages like [Circom](https://docs.circom.io/) or [Cairo](https://www.cairo-lang.org/) loses many performance optimization opportunities, and second, building the protocol directly using libraries like [arkworks/groth16](https://github.com/arkworks-rs/groth16), [zk-garage/plonk](https://github.com/zk-garage/plonk), or [microsoft/nova](https://github.com/microsoft/Nova) requires expertise in cryptography and can be very error-prone. Also, zero-knowledge proof systems are a moving target. There have been many new, and "better", proof systems coming out every 2-3 years ([BCTV](https://eprint.iacr.org/2013/879.pdf) -> [Groth16](https://eprint.iacr.org/2016/260.pdf) -> [Plonk](https://eprint.iacr.org/2019/953) -> [Nova](https://eprint.iacr.org/2021/370)). OpenZL tries to solve this problem by building flexible, proof-system agnostic, and extensible libraries for Web3 practitioners.

OpenZL consists of 3 parts:

- Gadget libraries: a library of gadgets that developers can use as building blocks for their protocols. The initial range of the gadgets includes accumulators (merkle tree with zero-knowledge membership proof), zk-friendly hash functions (poseidon hash), and commitment schemes. The gadget libraries are programmed in eclair.
- Embedded Circuit Language And Intermediate Representation (eclair): An embedded DSL in Rust that describes circuit logic. eclair leverages Rust's expressive type system to rule out certain classes of errors during the circuit construction.
- Adaptors to Proof Systems: Adaptors that convert circuit logic in eclair to the constraint systems used in different proof systems. The initial supported proof systems are arkworks/groth16, zk-garage/plonk, and microsoft/nova.


# Interested Users (alphabetical)
* Acala
* Astar
* Interlay
* Mangata 
* Jump Trading Crypto (at ZK Podcast: https://www.youtube.com/watch?v=N-gayIFspno)
* KILT
* Talisman 

# Milestones, Deliveries and  Budgets

## Oversight Committee

Oversight commitee will manage the overall execution and the financial budget of OpenZL:
* **Shumo Chu** (Co-founder, Manta Network), DOT address: `15yUHnjUPumSZUWsAJuDgm794kLyCPFehXrFY4uFUt18jTnV`
* **Luke Pearson** (Research Partner, Polychain Capital), DOT address: `14QPHeVLAvv5EU24mF4LBoqXFPmNg8MpNwsT9e1GSoEKW3Eh`
* **Bryan Chen** (CTO, Acala Network), DOT address: `14DsLzVyTUTDMm2eP3czwPbH53KgqnQRp3CJJZS9GR7yxGDP`

Funding and spendings will be managed in a 2/3 multisig:
`15t6F3Ww4LHy6uw6vYqJzFzWSBqM2gLFDj3mzBFx8qzLeuH7`

## OpenZL Milestones and Deliveries

* Milestone 1 (Product):  Oct, 2022
   * Code complete for all gadget libraries
   * Code complete for `eclair`
   * Code complete for `groth16` adaptor
   * End-to-end example and test using `groth16` backend
   * Spec complete for security audit 
* Milestone 2 (Audit): Nov. 2022
  Potential auditors: ABDK, Least Authority, Trail of Bits
  * Audit complete for all production level support code
  * Substrate based tutorials
  * Trusted-setup toolings 

## Project Budgets:
*  **Developer salary**, `405,000 USD`, (4 cryptographic engineers * 6 months + 1 devop engineer * 0.5 month )  
*  **Security audit**,  `600,000 USD`,  `40,000` LOC (currently, `manta-rs` has about 30,000 LOC) * `15 USD/LOC` (quote from [ABDK](https://www.abdk.consulting/)) |
*  **CI/CD**,  `5,000 USD`,  CI/CD for OpenZL
*  **Misc.** , `500 USD`, DNS, Website Hosting, etc 

Total budget: 1,010,500 USD 

In this proposal, we would like to ask from the milestone 1 funding, 400,500 USD development fund. According to the average DOT price of recent 30 days (https://polkadot.subscan.io/tools/charts?type=price), this equals to 
53149.6 DOT (price 7.62 USD at July 10, 2022).

## Budget and Execution
After the completion of milestone 1, the oversight committee will evaluate the technical merits of the OpenZL and decide whether or not to release the fund to Manta Ray Lab (the dev company of Manta Network).





OpenZL: Common Good Zero-Knowledge-Proof Library for Substrate Builders

Term: 1 April 2022 - 30 June 2022

This Treasury Proposal is an extension of our current maintenance & support contract with the Polkadot Ecosystem. The extension of the maintenance & support contract covers term: 1 April 2022 until 30 June 2022.

* [Current report that account for maintenance & support contract activities](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q2.md)

Polkascan Foundation is a not-for-profit infrastructure service provider and maintainer of Polkadot Ecosystem Python Libraries. The Python libraries are partly funded by Web3 Foundation grants, they have a generalized nature, suitable for adoption by any Python-based project in the broader Polkadot ecosystem. Notable projects/teams using the Python libraries are: LocalCoinSwap, Rotki & Patract Labs.


Previous activity reports can be found here:

* [October 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202010.md)
* [November 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202011.md)
* [December 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202012.md)
* [January 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202101.md)
* [February 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202102.md)
* [March 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202103.md)
* [April 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202104.md)
* [May 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202105.md)
* [June 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202106.md)
* [July 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202107.md)
* [August 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202108.md)
* [September 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202109.md)
* [Quarter 4 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2021Q4.md)
* [Quarter 1 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q1.md)
* [Quarter 2 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q2.md)

Links and further details:

* [The Social Contract Mechanism](https://github.com/polkascan/social-contract/blob/master/README.md)
* [The Social Contract for Maintenance & Support of Python Libraries](https://github.com/polkascan/social-contract/blob/master/polkadot/social-contract-002.md)
* [Business Plan](https://polkascan.org/wp-content/uploads/2022/03/Business-Plan-Polkascan-Foundation-v20220218.1030.pdf)

We will be available to answer the Polkadot Council's questions.

Continuation of Maintenance & Support for Python Libraries

Dear Polkadot community,
We at Crypto APIs are building a robust auto-scalable B2B suite, providing  blockchain- and crypto-related products as a service. With a team of 25 engineers, we have already successfully delivered our development tools to the communities of 12 of the largest blockchains. Now we are looking for funding of  60,000 USD to build three tools that we will provide free of charge to the Polkadot community.

1. An open-source KMS (Key Management System). We will build an open-source SDK, which allows you to create blockchain-agnostic HD Omnibus wallets, derive addresses, prepare and sign transactions, etc. The private keys, mnemonic, etc. (key management) are stored locally and not shared with anyone under any circumstances. Developers can use the other products of Crypto APIs for queries and transactions (read-only data and transact 
locally signed transactions) if they want to. However, there will be no vendor lock-in and the user can switch to another blockchain tooling and infrastructure provider anytime. This open-source product is an alternative to a paid business wallet, providing maximum independence and security to the user.

2. A pool of shared public Polkadot nodes. The default and initial setup will  be for at least 3 nodes. The more demand we have, the more nodes we will add. We will make sure that users always have their needs covered with 
industry-level response times. Crypto APIs will offer a free plan to the Polkadot community and to every organization planning to build on the Polkadot network. The nodes will have a Smart Load Balancer for  improved efficiency and optimal response time. The shared Polkadot nodes will have a response time lower than 20 ms. The bandwidth will be set at 1 GB/sec. The nodes will be hosted on multiple clouds, utilizing the infrastructure of AWS, Azure, and Google Cloud. Crypto APIs will also make sure that the shared RPC nodes are hosted in multiple regions, starting with the EU, USA, and Asia.

3. Block explorer. We want to provide a block explorer to the Polkadot community. We will integrate the Polkadot network into our Blockexplorer.One along with all other protocols that we support. Blockexplorer.One shows on-chain data only and it is completely free to use.

We would also like to share with you our detailed Project Plan for Polkadot with 
milestones, timeline, roles, and budget.

The funding will cover both the development costs and the infrastructure costs that will occur during development. Since we would need to run several nodes before starting the development, we expect payment in two installments: 50% at the beginning and the other 50% after we successfully deliver all three 
products.

We would love to hear your feedback and your thoughts on the project. Feel free to leave a comment below, or reach out via email. My email address is: martin.hrisoskulov@cryptoapis.io

Crypto APIs <> Polkadot - treasury proposal #139

Untitled - treasury proposal #118

**The Polka Haus** team volunteered to cover the organisation and execution of Decoded 2022: Buenos Aires Chapter. Due to the recent volatility in the markets, the Polka Haus team budgeted the total costs of their original treasury proposal to be USD 238,992 but has received the equivalent of 182,902 USD (transferable value). Here's a breakdown of the additional DOT needed to cover the total cost of the event organised for the community:
![](https://i.ibb.co/qr5QSDV/Screenshot-2022-06-21-at-14-04-38.png)

For these purposes, initially, a tip to reimburse PureStake for the extra costs invested was created. However, as the tip process is designed for relatively small amounts, it was agreed by the community that the regular treasury proposal process would be more suitable for reimbursing the team for organising the event in Buenos Aires

Please note that today's DOT rate has been used for calculation: **USD 6.969**. From the initial proposal, the team received the allocation at a price of USD 7.18. They used a 7day avg rate to submit their proposal: USD 9.80.

The original treasury proposal, along with the detailed budget, success metrics and the idea behind the proposal, can be found [here](https://polkadot.polkassembly.io/treasury/125)

Treasury proposal to cover difference in DOT rate from approval to transfer of funds for Decoded 2022: BA Chapter

As we all know, the **PureStake** team volunteered to cover the organisation and execution of Decoded 2022: NY Chapter. Due to the recent market volatility, the PureStake team budgeted the total costs of their original treasury proposal to be **USD 500,000.00** but has received the equivalent of **362,708 USD** (transferable value). Here's a breakdown of the additional DOT needed to cover the total cost of the event:

![](https://i.ibb.co/p1ysyS8/Screenshot-2022-06-20-at-11-28-44.png)

For these purposes, initially, a tip to reimburse **PureStake** for the extra costs invested was initiated. However, as the tip process is streamlined for relatively small amounts, it was agreed by the community that the regular treasury proposal process would be more suitable for reimbursing team for organising the event for the community. 

Please note that for calculation, today's DOT rate has been used: **USD 6.969**. While team received the allocation at a price of USD 7.18 and used a 7day avg rate to submit their proposal: USD 9.90.

The original treasury proposal, along with the detailed budget, success metrics and the idea behind the proposal, can be found [here](https://polkadot.polkassembly.io/treasury/127). 
