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

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

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 )