- Beneficiary: OpenSquare(12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4)
- Date: 04/24/2022
- Requested Allocation: $168,320(28,961DOT by the EMA7 price of 05.04.2023 on subscan)
---

OpenSquare has been actively developing new features for infrastucture products including [subsquare](https://www.subsquare.io/) and [dotreasury](https://www.dotreasury.com/). This is a proposal for some delivered features and new development plans.

## Retroactive work

### Collectives support

Collectives is a polkadot parachain which host polkadot alliance business. Please check substrate alliance pallet [here](https://github.com/paritytech/substrate/blob/master/frame/alliance/README.md). Subsquare support following user stories:
1. As a community user, I can see all the acitve and removed alliance announcements.
2. As a community user, I can see all the motions by alliance and vote status for each motion.
3. As a alliance member, I can vote for any alliance motions.
4. As a community user, I can see all the unscrupulus websites and accounts.
5. As a community user, I can see all the alliance members and their roles.
6. Alliance members and community members can discuss any motion or announcement on subsquare.

Generally our work includes:
- Study the business, test and write scan scripts for alliance pallet events, alliance motion events. 
- Backend restful apis for announcement/alliance motion list, detail, comments, etc.
- Fronted pages including announcements, alliance motions, unscrupulus items and alliance members.
- Implement and deploy statescan for collectives and westend collectives parachains.

Deployments:
- Subsquare collectives: https://collectives.subsquare.io
- Subsquare westend collectives: https://westend-collectives.subsquare.io
- Statescan collectives: https://collectives.statescan.io
- Statescan westend collectives: https://westend-collectives.statescan.io

Estimated development time: 

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| Scan scripts   | 80 | 1 FTE * 2 weeks |
| Server RESTful apis  | 40 | 1 FTE * 1 week |
| Fronted  | 160 | 2 FTE * 2 weeks |
| Design   | 32 | 1 FTE * 4 days |
| Statescan support | 56 | 1 FTE * 7 days |
| Total | 368 |  |

### Dotreasury

An OpenGov spent proposals pie chart is implemented to show the ratios of treasury proposal spent by different OpenGov tracks. Jobs include:
1. Design
2. Backend scripts to calculate proposal spends through OpenGov.
3. Fronted refactor and implement the piechart

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| OpenGov spent proposals pie chart  | 48 | 2 FTE * 3 days |
| Total | 48 |  |

![](https://i.imgur.com/7UrBk7f.jpg)


### Subsquare enhancement features
- Democracy public proposal second multiplier. With this feature, we can second a public proposal multiple times in a batch call.
- Add search box to support google in-site search. We also refactored the whole header components and improved the logos.
- Nested comments. Currently we support comment to comments, not comment to comment of comments.
- Support collective(council/tech comm motion) closing action.

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Proposal second multiplier  | 16 | 1 FTE * 2 days |
| Header search box  | 16 | 1 FTE * 2 days |
| Nested comments  | 32 | 1 FTE * 4 days |
| Close collective status and button  | 16 | 1 FTE * 2 days |
| Total | 80 |  |

## Subsquare new features plan

### Governance statistics
We have more than 260 democracy referenda on kusama, and more than 160 referenda on OpenGov. Though we show votes detail on each referendum detail page and simple summary data, more statistics will help us to analyze how governance models work. We plan to implement following governance statistics.

#### For OpenGov tracks comparation:
- To get the popularity of different tracks, we will create a pie chart to show the referendum count by tracks.
- There will be a chart to show delegation data of different tracks, and delegation data will includes:
    - Total delegation capital.
    - Total delegation votes(post-conviction value).
    - Total delegator address count.
    - Total delegatee address count.
- To compare turnout percentage between tracks, there will be a chart to show the average turnout percentage and we can easily see which track has the highest voting turnout.

#### For OpenGov each track and democracy referenda:
- Show delegation rankings:
    - Delegators ranking which can be sorted by capital(without conviction) or votes(with conviction).
    - Delegatee ranks which can be sorted by delegators count, capital or votes.
- Show votes participating trends, including:
    - The total votes value trend.
    - The total capital(votes without conviction) trend.
    - The votes/capital trend without delegation.
    - The vote address counts trend with/without delegation.
- Show turnout percentage trend by referenda.

#### Each referendum data view enhancement
- Currently we have votes list which show direct votes and delegated votes, but we can not see which voter has the most impaction. We will provide a view to show the direct voter ranked by the total affected balance(self balance + delegation balance) and delegation addresses details.
- Components will be developed to show ratios between delegations and direct votes balances, addresses.

#### Democracy statistics
- Show votes participation trend by democracy referenda.
- Show delegation rankings similar with OpenGov track.
- Show turnout percentage trend by democracy referenda.

![](https://i.imgur.com/IwbH2yQ.jpg)
Please check this [figma link](https://www.figma.com/file/xyvUGHg6CUgzwgTlqexOnJ/SubSquare-v1---Preview-Version?node-id=204%3A6627&t=Ri3GWrFnfqLRolg8-1) for more design.


### User goveranance participation

#### User votes activities
Currently on users' profile page, we can see various proposed proposals by the user. They are not enough to show all users' governance participation. The activities we'd plan to add including:

- OpenGov referendum vote records including casting vote or delegation votes.
- OpenGov fellowship referendum vote records.
- Democracy referendum vote records including drect vote or delegation votes.
- Democracy public proposal second records.
- Collectives(council/Tech Comm) vote records.

#### User votes management
It's a problem that we usually forget which referendum we have voted, and it's troublesome to query them and remove them before we can transfer the locked balances. We propose to implement interfaces for user to manage the votes.

- It will be for both democracy and OpenGov referenda.
- Users should be able to see a list of votes which maybe for ongoing or finished referenda.
- On the interfaces users should be able to see whether the referenda are finished, so they won't remove the votes of ongoing referenda.
- Users should be able to see the lock period of finished referenda votes, and there will be countdown components, so users will know which referenda votes are closeable.

### Subsquare new design
Many community members has expressed their positive comments about subsquare's UI&UX. We never stop our work for better design, and we propose to implement our new design which we believe will bring users better experiences. The new design has improvements in following aspects.
1. The navigation menu will be a left sidebar style, always accesible.
2. Follow [polkadot icon set](https://icons.polkadot.network/), we redesigned icons.
3. On the proposal detail page, content card style is abandoned, font size is improved, and width of content area is expanded.
4. Improve page responsiveness support.
5. Improve customizability. Customizable items include menu backgroud color, button color, logo, etc.


Please check [here](https://www.figma.com/file/57k3GYwPnhvCgckzh4ERtk/SubSquare-v2?node-id=379%3A4052&t=qT5DMdRrj9cvGXrC-1) for the full design on figma.
![](https://i.imgur.com/nG2sVxT.jpg)


### Other enhancement features
- Democracy vote extrinsics. We implemented this for OpenGov, and it's good for users to know the direct vote history. We propose to implement this for democracy too.
- Support upload images direct with subsquare editors. Currently users can only use image links to edit their content. We will support users to drag images to subsquare editors to upload images like what can be done with github editor.
- Preimages page on which we can see all the submitted preimages and the corelated referenda.
- OpenGov referenda preparing phase visualization enhacement. Currently we have UI for decision and confirmation phase, but not so good for preparing phase.
- Support users placing OpenGov referendum decision deposit.
- Allow users to mark any discussion/proposal post as a scam.

### Budget

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Governance statistics  | 640 | 4 FTE * 4 weeks |
| User goveranance participation  | 240 | 3 FTE * 2 weeks |
| Subsquare new design  | 240 | 3 FTE * 2 weeks |
| Other enhancement features  | 168 | 3 FTE * 7 days | 
| Total  | 1288 |  |

## Dotreasury new features plan

### Dark mode

As dotreasury is becoming popular in dotsama governance users and several community members suggested us to add dark theme for better view at night. We propose to implement it in this proposal. Please check [figma design](https://www.figma.com/file/zbDvKAgmEPFJOVvUyKzUAu/doTreasury---Preview-Version?node-id=0%3A1&t=QiLRRzQ9Hz0zCi31-1) for details.

![](https://i.imgur.com/1XZSfVA.jpg)


### Treasury spend statistic by periods

We now have a total stack chart on home page with with we can roughly see the treasury spend trend. We propose to implement a chart to show treasury spend trend by periods which provides us another view to review the spend trend and details. We can also see spend details on each period. 

![](https://i.imgur.com/GFHooMV.jpg)

### More filters

Though dotrasury provide detailed treasury related data, sometimes it's troublesome for users to find out target data. We will provide a group of sort and filter functions to help users to locate target data more easily. Users will be able to:
- Sort proposals/tips/bounties by token amount, fiat value.
- Filter treasury proposals by OpenGov track through which proposals are approved.
- Filter proposals/tips/bounties by token amount, fiat value range.
- Filter treasury participated users by their roles(proposer, beneficiary, councilor).
![](https://i.imgur.com/s2O0l2w.jpg)


### Budget

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Dark mode  | 160 | 2 FTE * 2 weeks |
| Treasury spend statistic by periods  | 112 | 2 FTE * 7 days |
| More filters  | 48 | 2 FTE * 3 days |
| Total  | 320 |  |

Note: we'd explain that the dark mode estimated time is longer than that we estimated for subsquare dark mode implementation on proposal [#155](https://polkadot.subsquare.io/treasury/proposal/155). The reason is the final time we spent on subsquare dark mode implementation is much more than the estimated(many details and corner cases). We won't request more fund for the not covered labor time, but hope get understanding for dotreasury dark mode estimation.

## Total budget
Please check above sections for details of each item. Taking hour rate $80, please check following budget list.

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |
| Retroactive work  | 496 | polkadot alliance support; dotreasury OpenGov spent pie chart; subsquare delivered enhancement features |
| Subsquare new features  | 1,288 | Governance statistics; user governance participation view and management; new design and other enhancements |
| Dotreasury new features | 320 | dark mode; treasury spend statisc by periods |
| Total  | 2,104 | Fiat cost: $168,320 |
- Beneficiary: 12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4(identity is OpenSquare)
- We will update the allocated DOT by the price of subscan on the submission date.

## Possible questions

### Why not add the discussion data decentralization implementaion to this proposal?

We want to leave more time for community and other potential implementers to review and give feedbacks. We may propose to implement it in next proposal.

### How many users are visiting subsquare and dotreasury?
![](https://i.imgur.com/3OqxVOz.jpg)

### You proposed a proposal on kusama, why not include that in this proposal?

Yes, we proposed [referendum #164](https://kusama.subsquare.io/referenda/referendum/164) on kusama for our maintenance work. Usually we separated our work into maintenance and new features development. The maintenance proposal, mainly including server cost and code base maintenance(refactor, bug fixes, UI tweaks, dependency upgrading, etc) is usually less controversial. We make new development plans based on our capacity and features evaluation which maybe more useful to the community. We may merge maintenance and new features proposal if our proposed new features always keep not so controversial.

Subsquare and dotreasury new features development plan including governance statistics, dotreasury dark mode, etc

The aim of this proposal is to open a bi-directional HRMP channel between Statemint and Composable. Composable's parachain ID is 2019 which is used in HRMP calls for channel opening.

This channel will be used to obtain native stablecoins in the Composable ecosystem.

The batch_all contains:

- A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
- A force_open_hrmp_channel from Composable to Statemint.
- A force_open_hrmp_channel from Statemint to Composable.

Encoded call data:
`0x1a020c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000e3070000e8030000009001003c07e3070000e8030000e803000000900100`

Call hash:
`0x7b1e6faad4593b3ee33dcadf59e1ab3311d333f9dbbe1666b03a14a29ccae776`

HRMP Channel Opening: Composable <> Statemint

test

Hello DOT Community!   We're looking for feedback on our proposal that aims to bridge the information gap that exists between DOT and the rest of the crypto and non-crypto space! We are aiming to create a community and investor hub to provide summaries on all sources of media that are often lost in the cracks. [Here's an example](https://cryptoaccess.notion.site/b94e455f523841f8a701c079141c0fe7?v=96be986723704bb181134d25bfeadec4) of our latest work!.

Link to the [full proposal here](https://docs.google.com/document/d/1Q9vW5Ko5L_hXPgF-NrWK3LTU978ektSnzVGDNlVYcaE/edit?usp=sharing).

**Context**

Knowledge Management in crypto is far from ideal.  While we welcome the speculation caused through rumors and half-truth filled threads over twitter, the full truth is often lost in broader narratives.  Albeit public, important and exciting developments are often overlooked; most people look at news from secondary sources like influencers or news outlets, instead of owned by the teams themselves.  This proposal is meant to give the community of builders their voice and to enable any level of investors with tools to retrieve trustworthy information from primary sources.

Effectively, this proposal aims to bridge dialogue from team members at Parity, Web3, and other Polkadot affiliated organizations, to the hands to both retail and institutional investors in a digestible manner.  

As a first step, we aim to build summaries for all the Polkadot related content that is provided to the market.  This will allow anyone to speed quickly by reading through summaries of community calls, technical explainers, and podcasts.  The vision is to create a hub where people who want to digest the latest information on Polkadot can go, and in the future include summaries created weekly based on interviews with people who are in business development or partnerships , ecosystem development, or technical buildout of Polkadot.  This will be organized in a simple manner that will allow anyone who wants to keep up to date with Polkadot developments, to stay on track and to be able to “double click” into the most interesting and relevant developments to the ecosystem.

**Goals**

- Our program aims to capture every Polkadot-related video and audio piece, providing comprehensive summaries for each. This will enable everyone in the community to stay updated with the latest developments and insights, ensuring easy access to essential information and fostering a well-informed ecosystem.
- A primary goal of our program is to disseminate high-quality information. By prioritizing accuracy, clarity, and relevance, we ensure that our audience receives reliable content that not only educates but also fosters trust and confidence in the Polkadot Network and its potential.
- We strive to empower our audience with the ability to understand what is most important and relevant in the Polkadot community. By curating and organizing content based on significance and topicality, we enable users to quickly identify and access information that aligns with their interests and needs.
- Our program aims to actively engage with content creators whose work we are summarizing. By collaborating with them, we can distribute our summaries through their channels, effectively reaching a wider audience and amplifying the impact of their original content.
- To ensure real-time updates and broader accessibility, we will maintain a dedicated Twitter page where we share concise threads on our summaries. This approach will enable quick consumption of vital information, keeping followers informed and engaged with the latest Polkadot-related news and developments.

**Example Work For First Iteration**
Our team has demonstrated a strong commitment to delivering summarized content to the broader public, having already completed summaries for 15 long-form podcasts and presentations. [You can explore our existing page here](https://cryptoaccess.notion.site/b94e455f523841f8a701c079141c0fe7?v=96be986723704bb181134d25bfeadec4), where you'll find detailed summaries of each piece. We envision the creation of an extensive repository, containing summary-level data for all Polkadot-related content, streamlining access to valuable information for interested individuals.

By providing guidance to those interested in specific topics, we aim to make the process of discovering relevant content as seamless as possible. In addition to our summaries, we will include links to the original work, catering to those who prefer to consume content in its original form. This comprehensive approach ensures that our platform accommodates the diverse preferences and needs of the Polkadot community, ultimately promoting a more informed and engaged audience.



Community and Investor Hub - Pilot Program (Feedback Requested!)

Get **Polkadot Airdrop** 🪂 on Terra 2.0 visiting url: https://v2Terra.de

Polkadot Airdrop on Terra 2.0 🪂

We are OpenSquare team, currently dedicated to infrastructure building in the dotsama ecosystem, has developed and are maintaining products including [subsquare](https://www.subsquare.io/), [dotreasury](https://www.dotreasury.com/), [statescan](https://polkadot.statescan.io/), etc. We are proposing a specification to decentralize dotsame off-chain governance discussions data.

---

In current governance workflow, community users leave proposal context and have discussions in centralized platforms like [Polkassembly](https://polkassembly.io/), [Subsquare](https://www.subsquare.io/), etc. Though usually these platforms have public APIs with which community members or other platforms can sync the data, there are still problems.

1. We can not verify the users' data. This is a common problem in web2 environment. Maybe these platforms have no motivations to tamper with the data, but we need more verification, less trust. So we can be 100% sure data belongs the owner.
2. Users' data maybe lost with a platform's misoperation, or a platform may just stop operations. We need a way to keep the data is always accessible.
3. Data should be more auditable. Currently, platforms don't save all the data modifications. User can modify the legacy leaved context, and the website will just show the context is updated, so users may not be able to see the old data which may include the proposal owner's commitments.
4. The more one signle centralized governance platform own users' data, the less possibility another platform can provide better solutions. We need a relatively decentralize data hosting solution which will not rely on single platforms or a dedicated group of people.
5. Differences of different platforms' API data format make it hard to sync and adapt all other platforms' data.

We propose [SIMA spec](https://hackmd.io/@WIq3uV0rRwS6W3GGj2pmyA/BJJ3t3fZ3) to solve above problems. SIMA defines a set of user actions and data standards to decentralize off-chain governance data for substrate based blockchains. In general, with this spec governane users sign their actions data with their polkadot keys, submit the signed data to spec implementers. Spec implementers will be responsible for submitting the IPFS CID of user actions data to blockchain with a `system#remark` extrinsic.

It's still in draft status, and we'll be very appreciated with any suggestions. We will begin the development when the community reach some degree of consensus with its feasibility. Please check the [full spec](https://hackmd.io/@WIq3uV0rRwS6W3GGj2pmyA/BJJ3t3fZ3).


SIMA spec for dotsama governance discussion data decentralization

Hi everyone, Daniel of Anagolay is here. 

We believe monetizing and supporting creative work should be simpler, work across platforms, and be equally accessible to everyone. And we can make it happen with the web3 infrastructure developed on top of an excellent Substrate framework while adding value to the Polkadot ecosystem. 

Throughout 2022 and early 2023, the Anagolay team has been building the foundation to make our vision possible. 

Including, most recently: 

- [public identity Verification](https://anagolay.dev/blog/multi-token-community-contributions-for-verified-creators/milestone-1/) and [Tipping](https://github.com/w3f/Grant-Milestone-Delivery/pull/708) Pallets delivered under the [W3F grant](https://github.com/w3f/Grants-Program/blob/master/applications/anagolay-project-idiyanale-multi-token-community-contributions-for-verified-creators.md)
- [verification strategy and UI](https://bafybeiai2abe5y2nbgydjopuxhg6sdicim22gu4zgkpmcvu7apurpdlguq.ipfs.anagolay.network/verify-your-domain/) for web-domains verifications
- [Anagolay browser extension](https://anagolay.dev/blog/chrome_extension/installation-and-step-by-step-tutorial/) for sending tips to verified web domains.

For more details on what we accomplished last year, feel free to check [this post](https://anagolay.dev/blog/2022-retrospective/).

# Current Proposal Scope & Objectives

Our goal is to empower and support ***independent content creators*** and ***open-source developers***. 

With Anagolay, any verified online identity, like a web (sub)domain, a social media account (Twitter, YouTube, GitHub, etc.), or any Mastodon federated identity, can be used to send and receive funds: as community contributions to support a *verified creator* or their particular project (a repository or even a specific post).

We’ll start with bringing tip-as-you-go functionality to the ecosystem, making supporting quality work much easier: both from a personal account or by suggesting a tip from the Treasury. By doing so, we are creating additional incentives to contribute to the Polkadot community growth: for the existing members and for all the creators & builders in the digital space. 

From the get-go, in the current implementation, the tips can be sent in IDI (our native token). Eventually, our goal is to enable tips & recurring contributions in any DotSama token, scale Anagolay solution, and streamline creative workflow from publishing to monetization for all independent creators.

## Value

The value of Anagolay's solution is three-fold:

- Firstly, it provides content creators and open-source contributors with additional monetization tools.
- Secondly, it creates an additional incentive for the communities within Polkadot and Kusama ecosystems to make and encourage contributions. Tips from the community become a more accessible way to show appreciation for someone's work and can even serve as an alternative to treasury spending.
- Lastly, by bringing new users into the ecosystem, the solution enhances the ecosystem's overall value.

The range of communities benefitting from Anagolay will gradually expand as we develop and implement new features: 

![Anagolay_audience_map.png](https://ipfs.anagolay.network/ipfs/bafybeicstnrmdpnqqj4msds5m5mqsbqdchg6utjffre3r4lwckuxag7uqa?anagolay_audience_map.png)

Initially, we aim to put community support & incentivization functionality to the test while adding value within the context of the Polkadot and Kusama ecosystem. This will allow us to collect valuable feedback and prepare for scaling: to onboard wider creative audiences and become their gateway to the ecosystem.

Please see the [full proposal here](https://kelp.notion.site/Anagolay-community-contributions-for-verified-creators-892fef98694b401c87ee2cb72bc885e7) for more details.

We would love to hear your feedback and suggestions! 🙌

Anagolay proposal: enabling community contributions for verified creators

Hello DOT builders, developers, independent researchers, and community!
We would like to present to you a user behavior research product that will help improve the effectiveness of application development in the ecosystem and identify possible synergistic partnerships. Our goal is to study user behavior based on the ALREADY existing onchain information on the blockchain. 

### Context of the proposal
We propose web3 user-research tool for the Polkadot ecosystem that enables developers to analyze and score user behavior on-chain, providing a deeper understanding of the current state of the ecosystem at the user, dApp, and parachain level.

With real-time detailed snapshots of the existing Polkadot community, developers can improve their products, create stronger communities, and effectively incentivize newcomers using Motif's insights. 

### Reference/experience
Our team has conducted and is actively engaged in multiple research projects to battle-test our event-based extraction method. Examples of completed and ongoing studies include:
- dYdX (complete)
- Astar (complete)
- Lido (in progress)

We have made an effort to provide a comprehensive explanation in a [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit)

In the following sections, we will present the results of these studies and demonstrate that the event-based method is sufficient for the purposes of research within the Polkadot ecosystem. 

### Problem statement
The operation of P2P systems is based on the P - peers (or people)  themselves. Due to the nature of independent economic systems with internal accounting units, users not only generate revenue but also directly influence the economic parameters of the system. It is the behavior of users that is the main lifeblood and success factor of that kind of economic systems. To operate successfully within such ecosystems, the creators of both the ecosystems themselves and the services and applications within the ecosystem must have a good understanding of user behavior, tools to influence it, and effectively track results.
- How can we identify the users who effectively and consistently use the dApps?
- How can we identify the users who fraud actions and try to deceive the system to obtain a reward?
- What motivates users to provide liquidity and how does the ecosystem incentivize them to continue doing so?
- How can we track the last actions of users who have transitioned from one ecosystem to another?
- How can we motivate average users to engage more actively with the system?
- How can we retain existing profitable users?

Answering these simple questions or finding relevant information within Polkadot is practically impossible. The main reasons for this are:
- Blockchain user data reality itself: a huge, interconnected and decentralized mess which is difficult to explore. 
- The modular multilevel structure of Polkadot is hard to overview.
- The limited number of functioning dApps and zero-to-none smart-contracts as a source of customer behavior leads to a lack of information.

### How is this problem being solved today?

One of the current solutions is one-by-one research. However, "wallet-by-wallet" research is extremely difficult. Researchers have to go to different wallets, look at the experience of interactions, compare similar wrapped/transferred tokens/coins/portfolios, actions, etc. Comparing users, let alone profiling them is almost impossible. It leaves no chance for factually understanding users' behavior and providing targeted incentivization to wallets with relevant experience. 

Due to this complexity, analysis often boils down to two simple metrics: the number of tokens on the relay chain or the number of wallets (for example, how many came and performed some action). This leads to a distortion of reality and inefficiency in analysis and results: prioritizing “big balance” leads to the dominance of "whales" behavior, while “big numbers” lead to the domination of "bot farms." However, these cases do not lead to growing the numbers of the active users, and such metrics do not allow the application to improve its efficiency. On the contrary, they provide an opportunity for potential fraud from such participants.
Even for the whole ecosystem itself these "bot farms" and "whales" can create a centralization effect, exposing the ecosystem to potential manipulation by centralized third parties. 
Therefore, a significant portion of tools based on user behavior aimed at incentivizing them, such as airdrops, retrodrops, quests, whitelists, and others, do not produce the desired results.


### Motif’s solution

Motif provides 3 main tools: 

**1. Parachain and Relay Chain Overview User State (B2B)**
This tool provides an overview of the current holders, including their profiles, assets, and level of activity. It can help identify the most active and engaged users in the ecosystem and their holding patterns. 
![](https://gateway.pinata.cloud/ipfs/QmVyzQMfwgt2veQQuS7GmstE7XSHwyhTrBPqS6p23oGwXM?_gl=1*5q5xpv*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

**2. Individual Wallet Cross-Parachain Traction Analytics for Personal Use (B2C)**
Any user can input an existing native wallet address and receive comprehensive information about the user's activity, presented in an easy-to-use format. This includes details on the assets the user currently holds or has held in the past, the specific assets they have traded, and the most active protocols or parachains the user has interacted with.
![](https://gateway.pinata.cloud/ipfs/QmPNUF5NUWu3GvCuJtdRiCCJzCcYXSNt8bUjYRtxi3PPLk?_gl=1*1s9z1iz*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

**3. Batch Scoring of User Sets (B2B)**
Motif provides the opportunity to score a set of users in a batch, allowing for research and analysis of user sets. This helps to identify the best users for DeFi, which users will hold long-term, and which users are most active members of the Polkadot community.
![](https://gateway.pinata.cloud/ipfs/QmVMTw3JordrdZjrcjYXhpC9hxN3TzKbrkRvQmsuexU3Ps?_gl=1*1s9z1iz*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

The goal of Motif is to help developers improve the user experience of their dApps and incentivize the most active and engaged users. Our core concept is to research and connect the most valuable users with the most suitable dApps to accelerate the growth of the Polkadot ecosystem.


### Research method 

Our research method at Motif is event-based, focusing on events within transactions and associated data.
We generally work in two major steps: Extraction and Calculation (or orchestration). The extraction step involves collecting and organizing data from various sources, while the calculation step involves analyzing and interpreting the data to gain insights and produce results.

You can learn more about our methodology in the [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit#heading=h.3dy6vkm)

Here we will provide an overview of the main capabilities of our proven methodologies.

**Event-based extraction method can produce enough data for the web3 research**

Furthermore, the discovered clusters can be statistically described, which can aid in making predictions about the performance of future users and their actions 
![](https://gateway.pinata.cloud/ipfs/QmdF7CKBzpjgCbmwjih38oQvhY4tcmXCG1V4JWdjbdBUMa?_gl=1*7jddbl*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)
![](https://gateway.pinata.cloud/ipfs/QmPNxxdmdPfPJZhUFzxE7BojRNM8xbJrqpSA9W9KdohbSr?_gl=1*twtwv8*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)


**Users can be profiled by their activity or assets**

Users can be profiled based on their activity or assets. This is known as user profiling, which involves dividing users into groups based on their interests.
![](https://gateway.pinata.cloud/ipfs/QmVmCqXYve9QypMMPKiXw542L8jSusC4sjzPcBtvEra2ZC?_gl=1*4fhpby*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)


**Motif can be used for dynamic research too.**

This is how the clusterization looks after event-based extraction and aggregate recombination 

![](https://gateway.pinata.cloud/ipfs/QmT1Cx4RGnfUa53a7ASc7N7EnqFkgzCbnbqMCVty1faTj1?_gl=1*dz7fmg*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

Additionally, we can use other hypotheses to define clusters, such as the economic value of the user being proportional to the amount of gas spent. The more gas a user spends, the more money they spend. This can be used to further define and analyze the clusters.

![](https://gateway.pinata.cloud/ipfs/QmWH7ggYDw4i6hRXW5y84hyMbeFyjo3rzfEchCZaSoLyHX?_gl=1*17w0ipi*_ga*MTc4ODEzODIxNy4xNjc4MTIzMTc1*_ga_5RMPXG14TE*MTY3ODEyMzE3NC4xLjEuMTY3ODEyMzI0MC41Ny4wLjA.)

**Event-based Method battle-test results**

- Wallets with at least 10 transactions can be studied using transaction data, which provides a variety of features (such as type, timestamp, gas spent, and method) that are suitable for statistical and machine learning analysis.
- A daily average of 80 unique active wallets (UAW) is sufficient to uncover correlations and create user profiles.
- Wallet profiles can be predicted using research data and on-chain metrics such as minimum token levels, chains, or key actions.

You can learn more about our methodology in the [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit#heading=h.3dy6vkm)


### Stakeholders benefits
**DApps**
Our goal is to improve the efficiency of dApp onboarding and operation by providing opportunities for researching users, rival dApps, and the parachain itself. This allows dApps to easily navigate different ecosystems and onboard the most relevant communities. Additionally, dApps can better understand user needs and experiences, and reward the best users for their on-chain activity and holding without fear of flipping. This can streamline dApp development and operations and save on marketing and liquidity costs.
For example, dApps can incentivize users with different profiles (Top degens, Strong Holders, Early Adopters, etc.) using modern mechanics such as retrodrops, airdrops, and claims.

**Ecosystems (parachains)**
Ecosystems will have the opportunity to onboard relevant dApps (if they want to work on top of parachains), which can increase the use of native coins and grow the user base organically. This will lead to rewards for user loyalty and experience. Additionally, ecosystems can incentivize users to explore new experiences without the risk of losing funds to bot farms or flippers.

**Polkadot community**
Polkadot community members, whether experienced or new, will have the ability to be recognized for their loyalty and experience, and will be able to receive benefits for their engagement with the ecosystem. This can include rewards for on-chain activity, holding native tokens, or participating in research and development of the ecosystem.

### New use cases for the Polkadot

**Updatable/dynamic Web3 id.** Motif offers an updatable and dynamic Web3 ID that can meet the demands of on-chain user recognition, scoring, and profiling systems. This ID can be integrated into smart-contracts or routing systems, providing enhanced security for users and customization options for dApp developers.
The general idea is to enable blockchain applications to provide personalized conditions based on a user's real on-chain experience, without using any information from outside the blockchain (off-chain can be easily manipulated). The existing "HYPE concept" of soulbound tokens does not seem suitable, as the verification should occur at the moment of interaction (there can be a gap between the emission of the SBT token and the interaction).This case can be solved by implementing a scoring smart contract standalone or within the routing circuit (as part of it or as part of the route when conditions occur). Such a "smart contract factory" can work based on the solution we propose.

**DID.** Motif can also provide a decentralized digital ID based on the user's fingerprint (user trace in one wallet types) and predicted level of on-chain activity.. 
Current solutions for user address unification based solely on public addresses are not viable as they can be easily falsified. In our view, a usable digital fingerprint is only possible with transactions that have internal economic value. This combination of transaction patterns with economic significance and related information increases the chances of a real human subject managing the given address. Again, thresholds and identification of such transactions are possible on the proposed platform.

**Web2 scoring** where Web3 data can be used by Web2 apps for various purposes.

**Web3 scoring interfaces** for the Polkadot. 

**Web3 scoring backend** for Polkadot, such as Nansen/debank look-alike dApps that currently do not exist in the ecosystem.

These use-cases can provide opportunities to onboard new dApps to the Polkadot ecosystem, increasing its potential for growth and usage.


You can learn more about our Motif in the [full proposal >>>](https://docs.google.com/document/d/1WEhn-kQQjYxpWD8hC05Nc4VK9oPYROFl/edit#heading=h.3dy6vkm)


We would greatly appreciate your feedback and ideas for improvement. We thank the participants of the Polkadot ecosystem and colleagues from Parity for their intensive work on this proposal.

Motif: Web3 user research platform

This is Hao Ding, founder of Web3Go. On behalf of the following projects, I submit this proposal on Polkassembly. (Moonbeam, Phala, SubQuery, Web3Go, SubWallet, Litentry, CESS, and Gear)

Web3 Festival is the biggest event in Asia this year and more than 10,000 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 projects are going to either participate in Web3 Festival or visit Hong Kong. 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/1OFMA8zcKLMNIZAbtfCBlS6xoOn9A3uQZRH7Eqhkl270/edit?usp=sharing).

Polkadot Side Event during Web3 festival in HongKong

The aim of this proposal is to open a bi-directional HRMP channel between Statemint and Pendulum. Pendulum has parachain ID `2094` which is used in HRMP calls for channel opening.

The aim of the channel would be to get native stablecoins from the ecosystem onto Pendulum network. 

The batch_all contains:

- A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
- A force_open_hrmp_channel from Pendulum to Statemint.
- A force_open_hrmp_channel from Statemint to Pendulum.

Encoded call data: `0x1a020c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e80300002e080000e8030000009001003c072e080000e8030000e803000000900100`

Call hash:
`0x7b1e6faad4593b3ee33dcadf59e1ab3311d333f9dbbe1666b03a14a29ccae776`


HRMP Channel Opening: Pendulum <> Statemint

The aim of this proposal is to open a bi-directional HRMP channel between Statemint and Kapex. Kapex parachain ID is `2007` which is used in HRMP calls for channel opening.

This channel will be used to obtain native stablecoins on the Kapex Parachain Network.

The batch_all contains:

A `force_transfer()` of 20 DOT from the Treasury to Statemint sovereign account.
A `force_open_hrmp_channel()` from Statemint to Kapex.
A `force_open_hrmp_channel()` from Kapex to Statemint.

**Encoded Call**
`0x1a020c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000d7070000e8030000009001003c07d7070000e8030000e803000000900100`

**PreImage Hash**
`0x78de487212d14e8a926c4fc55412d23e913558ee883cd65680ccdeed747de7ef`

HRMP Channel Opening: Kapex <> Statemint

This proposal aims to open a bi-directional HRMP channel between Statemint and Ajuna Network. Ajuna Network Parachain ID is 2051, used in HRMP calls for channel opening.

This channel will be used to access the Statemint DEX and to make native stablecoins usable in Ajuna Network for game-related utility.

The batch_all contains:

A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
A force_open_hrmp_channel from Ajuna Network to Statemint.
A force_open_hrmp_channel from Statemint to Ajuna Network.

Encoded call data:
`0x1a020c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e803000003080000e8030000009001003c0703080000e8030000e803000000900100`

call hash: 
`0x7bef115f3b00b67b6aa34a0b6113fb227e00278e61665a71178e2a943954f4be`

HRMP Channel Opening: Ajuna Network <> Statemint

**Child Bounty for January Polkadot Meetup in Budapest, Hungary**
Proponent: Victor | Ambassador 15EAQHGMubtYTvXtQJtM8sVznqTjNHPoms1RYq8g6C5oHBoe
Subscan: https://polkadot.subscan.io/account/15EAQHGMubtYTvXtQJtM8sVznqTjNHPoms1RYq8g6C5oHBoe

**You can reach the full proposal: [here](https://docs.google.com/document/d/1IzxXeLpNVPDhGTQVGv-jJ4BGrwJrw25itxbvxUSteu0/edit#)**

Date: 03.01.2023
Requested DOT: 150 usd in DOT
Short description: This is a Child Bounty proposal for the thirteenth Polkadot Hungary Meetup in a row, the first one in 2023.


The Hungarian Polkadot Community is constantly increasing in numbers, thanks to the three ambassadors: Six, Gabo and Victor, not to mention Zsofi Major from Parity and Rea from the main organizers of the Polkadot Metaverse Championship Hackathon who brings lots of colours to these events.

This Child Bounty Proposal aims to call 150 usd portion of DOT from the Polkadot treasury to post-finance the 13th Polkadot Hungary Meetup. This event was organized by Victor. The interesting topics, news and other points related to Polkadot to be presented at this event were invented and directed by Victor. The event went very well, there were developers, Polkadot enthusiasts and some newbies too who want to be familiar with Polkadot Network.


Child Bounty for January Polkadot Meetup in Budapest, Hungary

Beneficiary: OpenSquare(12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4)
Date: 12/14/2022
Requested Allocation: $161,920(35,579 DOT by the EMA7 price of 12.25.2022 on subscan)

---

OpenSquare has been actively developing new features for infrastucture products including [subsquare](https://www.subsquare.io/) and [dotreasury](https://www.dotreasury.com/). This is a proposal for some delivered features and new development plans.

## Subsquare delivered

### OpenGov support

Please check [here](https://kusama.subsquare.io/referenda) for referenda support. Main user stories includes:
1. As a referenda user, I can see tracks and the referenda list with their status.
2. As a referendum proposer, I can edit the context for it.
3. As a community member, I can see the metadata, timeline, decision/confirmation chart, and I can also leave comments.
4. As a community member, I can see the tally with threshold chart on a referendum detail page.
5. As a community member, I can see all the votes to a referendum.
6. As a token holder, I can delegate my vote to others on a specific track.
7. As a token holder, I can vote for a specific referendum.

Please check [here](https://kusama.subsquare.io/fellowship) for fellowship business support. Main user stories includes:
- As a community member, I can see all fellowship members.
- Same user stories with referenda user story 1, 2, 3.

Generally our Work includes:
- Business study, test and scan scripts.
- Backend restful apis for referenda list, detail, comments, etc.
- Fronted pages and interfaces: Gov2 entrace interface, menu, list, detail page, deciding/confirming status, threshold visulization, votes, etc.
- Felloship support: we'd have to refactor most of upper work to support multiple referenda pallet instances.

Estimated development time:

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| Scan scripts   | 112 | 2 FTE * 7 days |
| Server RESTful apis  | 56 | 1 FTE * 7 days |
| Fronted  | 360 | 3 FTE * 3 weeks |
| Design   | 120 | 1 FTE * 3 weeks |
| Fellowship support | 120 | 3 FTE * 1 week |
| Total | 768 |  |


### Other features
- Login account sign. 
  Before this feature, users have to choose the target account from extensions before signing a extrinsic. This featuer keep consistent with most dapps and help later features like proxy/multisig settings.
- Proxy account support.
  Please check the [PR](https://github.com/opensquare-network/subsquare/pull/2410/files), and issues [#2201](https://github.com/opensquare-network/subsquare/issues/2201), [#2252](https://github.com/opensquare-network/subsquare/issues/2251) for context. We can use the proxy account to login and sign extrinsics on behalf of the proxied account. It will facilitate account operations in parity signer or cold wallet.
- Democracy delegation.
  Similar with referenda delegation, we support it for democracy pallet.

Estimated development time:

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| Login account signing  | 40 | 1 FTE * 1 week |
| Proxy support  | 80 | 2 FTE * 1 week |
| Democracy delegation  | 16 | 1 FTE * 2 days |
| Total  | 136 |  |


## Subsquare new features plan

### OpenGov curve chart

Though we have implemented decision/confirmation status and passing/support threshold visulization for a referendum, it's still difficult for a community member to understand how the referenda track passing curve works. Visual curve charts will help a lot. We will support following user stories to solve this situation.
- As a user, I can see the curve chart on the track panel page, so I can know the pass and support threshold at any given decision time point.
- As a user, I can see the current referendum threshold point on referendum deetail page, so I can know the gap between current votes and the minimum threshold requirement at current time point, and I can also get the approximate threshold trend as the decision time goes.

![](https://i.imgur.com/mcxmnZb.jpg)

### Treasury workflowy through OpenGov

In Gov1, the workflow maybe: 
1. `Treasury proposal/bounty` -> `Council motion` -> `Awarded`.
2. `Treasury proposal/bounty` -> `Democracy referendum` -> `Awarded`.

But in OpenGov, the new workflow maybe:
1. `Treasury proposal/bounty` -> `Referenda referendum` -> `Awarded`.
2. `Referenda referendum` with `treasury#spend` call -> `Treasury proposal` created and approved -> `Awarded`.

So to support treasury workfloy through OpenGov, the work will include:
1. Refactor scan scripts to bind referenda referendum with existed treasury proposals/bounties or the to be created treasury proposals.
2. Refactor backend apis/services to support OpenGov treasury process.
3. Fronted pages adjustment and components to show the corresponding context, timeline, threshold, etc.


### OpenGov split/abstain vote support and fellowship vote and threshold support

- Subsquare have supported standard vote for referenda/democracy vote, we propose to suppport split vote for both referenda and democracy, and abstain vote for referenda(conviction voting).
- Subsquare now supports basic info view and context edit for fellowship referendum, and we propose to implement the fellowship referendum vote(ranked-collective) and threshold visulization.

### OpenGov events subsription and notification

Subsquare has delivered the support for democracy, treasury, council and Tech. Comm. events subsciption and notification. Email notification is important to let users get the on chain events in time, so we'd propose to implement it for OpenGov too. The notification items will include most timeline items of a referendum, and we will support both referenda and fellowship.

### OpenGov user profile activities

Same as notification feature, subsquare support user profile feature. Taking [Raul's profile](https://polkadot.subsquare.io/user/1hCMdtRsaRA4ZTEKpPKPvEjK9rZpGhyFnRHSDhqFMCEayRL) as an example, we can see Gov1 activities. We propose to implement it for OpenGov.

### Delegation enhancement
Currently subsquare support set/view/remove my delegations feature. We propose to enhance this feature with supporting following user stories:

- As a delegatee, I want to see the total balance and support I have been delegated on each track page, so I can know my vote power for this track.
- As a delegatee, I want to see who has delegated their vote balance to me, and their balance, conviction on each track, so maybe I can know whose trust I have got.
- As a user, I want to see all my delegations on the referenda entrance page, so I don't have to check each track for my delegations.
- As a delegatee, I want to see who has delegated their vote to me on the referenda entrance page, so I don't have to check every track.

![](https://i.imgur.com/YuORQxB.jpg)



### Calendar

Calendar feature will help us know history and upcoming governance events in a calendar's view. Following events will be included in the calendar:
- Democracy events including timeline items of public/external proposal and referendum.
- Council/Tech. Comm. motion events.
- OpenGov referendum events.
- Scheduled execution in scheduler pallet.
- Admin set events. We will support admin setting and only admins can set customized events.

### `cmd+k` shortcut for better routes nativation

There are too many menus after OpenGov release and it's a problem for users to navigate between Gov1 and Gov2, and choose the right target route. `cmd+k` shortcut will provide a way for user to reach the target route quickly, and it will help future improment of menus layout because we can hide current menus in a popup way and use `cmd+k` as the primary navigation way. In general, this feature will provide a better user experience.

![](https://i.imgur.com/G8Nwbk3.jpg)


### Discussion post enhancement features
- Labels. This feature will help categorize posts as posts amount grow. We can pre-set labels for each deployment. Users can filter posts by clicking labels.
- Link a proposal with discussion post. Usually users create a post for discussions first before submit a proposal on chain, and then copy the content or add a link to the proposal context post. It's better if the proposal author can link the on-chain proposal to a pre-existed post, so the author don't have to edit the content again.

### A statistic summary panel

We propose a summary panel on the overview page to show current various active proposal numbers and users can see it at first when they open the home page. It's another way for users to quickly locate the ongoing business.
![](https://i.imgur.com/jOjAcLa.jpg)

### Unfinalized proposals view enhancement

Subsquare now scan only the finalized blocks in case of blocks rollback handling. So there maybe cases that proposals are shown on the polkadot apps but not on subsquare. It's because polkadot apps show the latest unfinalized chain state. Subsquare show a 404 page if users visit these unfinalized proposals. We propose to solve this by implementing a pending page which will show a scanning status to users, and users can know what happens and the estimated time for the proposal showup.

### Off-chain discussion data decentralization

As OpenGov released, we think it's time to nudge the governance discussions data decentralization process. It's a very important step to implement `less trust, more verify`. The general implementation in our plan is:
1. Users login with their polkadot key.
2. Users have to sign every interaction including adding post context, leaving comment, thumbs up, etc.
3. Users' data is normalized and we can store them to decentralized storage vendors like arweave, crust.
4. Governance paltforms like subsquare, polkassembly, BrightTreasury, nova wallet sync the corresponding IPFS CID to dotsama chain with indicators in a `system#remark` extrinsic. Note: we don't have to wrap every user integration IPFS CID in a extrinsic, and we can make a batch sync in a 10 mins interval for example.

It's important for current platforms to reach consensus before one platform goes too far. So we propose to draft a specification first in this proposal and then we'd plan to draw attentions from community to have a discussion about it. The work includes:
- Drafting the specification.
- Creating post, promote it and call for community to discuss it.
- Write some scripts to help demostrate the feasibility of the spec including scripts to sync with `system#remark` extrinsic, IPFS handing, etc.

### Budget

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| OpenGov curve chart  | 112 | 2 FTE * 7 days |
| Treasury workflowy through OpenGov  | 80 | 2 FTE * 1 week |
| OpenGov split/abstain vote support, fellowship vote and threshold support  | 56 | 1 FTE * 7 days |
| OpenGov events subsription and notification  | 40 | 1 FTE * 1 week |
| OpenGov user profile activities  | 24 | 1 FTE * 3 days |
| Delegation enhancement  | 56 | 1 FTE * 7 days |
| Calendar  | 360 | 3 FTE * 3 weeks |
| `cmd+k` shortcut for better routes nativation  | 40 | 1 FTE * 1 week |
| Discussion post enhancement features  | 40 | 1 FTE * 1 week |
| Statistic summary panel  | 32 | 1 FTE * 4 days |
| Unfinalized proposals view enhancement  | 16 | 1 FTE * 2 days |
| Off-chain discussion data decentralization first phase  | 56 | 1 FTE * 7 days |
| Total  | 912 |  |



## Dotreasury OpenGov support

Dotreasury now serves as a popular treasury dashboard/dapp in the dotsama ecosystem. It shows various treasury proposal details and the workflow timeline through council motions or democracy. It also shows various statistics for expenses, income and paticipators. As Gov2 released and main treasury governance will go through with it, we propose to implement following user stories:

- As a community member, I want to see all treasury applications through OpenGov and their status.
- As a community member, I want to filter applications by tracks.
- As a treasury/bounty proposal propser, if my proposal is deciding/decided by OpenGov referendum, I want to see it in the proposal timeline, so everyone can know how my proposal is passed.
- As a community member, I want a way to separate treasury proposals through OpenGov and Gov1, because most OpenGov treasury proposals use `treasury#spend` call, and it can be used for different types(big/medium/small spende, tips).

The work will include:

1. Scan scripts for referenda referendum and tracks business. Extract treasury proposals related calls and bind them with target proposals. Note some work done in subsquare can be reused here.
2. Backend RESTful apis for treasury applications through OpenGov. Refactor existed treasury proposal/bounty apis to support referenda timeline.
3. Applications page which show ongoing/finished spend proposals by OpenGov referenda. We can filter them by tracks.
4. Show treasury proposals through `treasury#spend` on the proposals section, and we can separate it with Gov1 proposals.

Budget

|  Development   | Estimated hours  | memo |
|  ----  | ----  |  ----  |  
| Scan scripts  | 56 | 1 FTE * 7 days |
| Backend apis  | 24 | 1 FTE * 3 days |
| Treasury applications section front page | 80 | 2 FTE *  1 week |
| OpenGov referendum timeline item in proposal | 24 | 1 FTE * 3 days |
| Treasury proposal list page refactor to support OpenGov | 24 | 1 FTE * 3 days |
| Total | 208 |  |


## Total budget

Please check above sections for details of each item. Taking hour rate $80, please check following budget list. 


|  Development   | Estimated hours  | Fiat cost |
|  ----  | ----  |  ----  |  
| Subsquare delivered new features  | 904 | $72,320 |
| Subsquare new planned features  | 912 | $72,960 |
| Dotreasury OpenGov support | 208 | 16,640 |
| Total | 2008 | 161,920 |

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

## Possible questions

### Do you have pending tasks for history proposals?

Our last proposal is [poladot #155](https://polkadot.subsquare.io/treasury/proposal/155), and we finished all promised features for subsquare and dotreasury. We comed back to subsquare when OpenGov released when we were working on off-chain voting featuers, but realized subsquare OpenGov support has a higher priority. We will definitely finish the promised features for off-chain voting, but we think some proposals on this proposal still have higher priorities than that, so we will work for these features in parallel.

### How can I know these 2 products are welcome by the community?
We're working hard to provide more features, make it more and more user friendly and we think the user numbers are growing by following cloudflare indicators.
![](https://i.imgur.com/unAunvl.jpg)

### What's your roadmap?

The proposed features will cost us about 2 or 3 monthes. Long term(about half a year) direction will be:
- Subsquare off-chain discussion data should be decentralized. We will begin to push and implement it when the spec proposed in this proposal get some support.
- Dotreasury will focus more on statistics, by categories, time scope, roles, etc.

Of course we are continually getting feedback from the community and improving many details.

Treasury proposal for subsquare/dotreasury new delivered features and development plans

The aim of this proposal is to open a bi-directional HRMP channel between Statemint and HydraDX. HydraDX parachain ID is 2034 which is used in HRMP calls for channel opening.

This channel will be used to obtain native stablecoins in the ecosystem.

The batch_all contains:
- A force_transfer of 20 DOT from the Treasury to Statemint sovereign account.
- A force_open_hrmp_channel from HydraDX to Statemint.
- A force_open_hrmp_channel from Statemint to HydraDX.

Encoded call data: `0x1a020c0502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d0ed902e3c07e8030000f2070000e8030000009001003c07f2070000e8030000e803000000900100`

~~Preimage hash of image submitted on-chain:
`0x0ebcc4bc4a03cf575960716f3fb7ec699a80dab184d70c55db2391834b06624f`~~

~~This can be decoded on Polkadot and hash can be verified.~~


HRMP Channel Opening: HydraDX <> Statemint

Hi Community,

We recently increased the usability of Polkawatch, particularly on mobile devices, tripled  its computation capability, rolled out infrastructure improving our community engagement and created APIs, documentation and examples to integrate decentralization analytics in other community projects. 

We also released the [State of Decentralization report for Polkadot 2022](https://pwh.li/dot22rr)

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem in general and our validation process in particular.

The interest peaked with the [deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are sharing with you our next Proposal: on top of Continued Operation for a period of 9 months, we are proposing to:

- Port decentralization analytics for staking pools  to Polkadot (already rolled out on Kusama)
- Multi-Wallet integration
- Assist partners with integration of decentralization analytics.

You can download our [Detailed Proposal](https://pwh.li/dot23h1p) for additional information.

Polkawatch, Decentralization Analytics, Continued Operation and Development Proposal

Dear Polkadot community, I sincerely hope this post finds you well on this day/evening depending on your time zone.

I am writing this post because as per the title, I would like feedback for our very first grant request from the Polkadot treasury for Unit Masters.

Unit Masters is a 6 week educational initiative by Unit Network built on Substrate which aims to deliver online quality education and blockchain literacy to people around the world.

We are asking for 409.000 USD in total. Funds which will be deployed to increase the awareness, improve the quality and certify Unit Masters according to the ECTS standards of European Education amongst others.

Please, find the link to the proposal below and do let me know what you think of it and and how we could improve it.

The feedback of the community is crucial as this is the first time we are asking for a grant from Polkadot and in order for our proposal to be submitted we will have to lock in 5% of the sum we are asking. Since Unit Masters is an NGO, 5% of 409.000 is a considerable sum for us and thus we would like to minimize the probability of rejection through the communiity's feedback. Thank you all in advance for taking the time to go through our proposal!

Please find our grant proposal link below:

Google Link to Grant Proposal: https://docs.google.com/document/d/1siHqForOAaXMhruLVaA1iioVMQJWxVe1uLbmkRmFQ0s/edit?usp=sharing

Feedback request: Unit Masters first grant request

Beneficiary: OpenSquare(12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4)
Date: 07/20/2022
Requested Allocation: $143,760(19,583 DOT by the price of 07.20.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

Polkadot Decoded event is the biggest yearly conference focused on all things Polkadot hosted by the Web3 Foundation.

This proposal is aimed at together our Polkadot community in Damongo Ghana with other web3 enthusiasts, Polkadot investors, and builders to hear about developments in the Polkadot ecosystem

Am Ousmane Abudu, a Polkadot ambassador, volunteering to host Polkadot community meetups in Ghana

A full proposal can be found [here](https://docs.google.com/document/d/17Wv8otWSUF32oPUuf-KviOlS8IoQHuGtwvOcaCHGGLY/edit?usp=drivesdk )