Hi Yongfeng! Thank you for submitting and pushing this for vote. With regards to the site for collaborations in a bounty and child bounty way: can you give us more info about userbase and some metrics? Also, do you publicize this site anywhere? how attractive is it por developers? 

[@RTTI-5220](GLVeryFRbg5hEKvQZcAnLvXZEXhiYaBjzSDwrXBXrfPF7wj-kusama) , thank you for the question. Following chart is about visitors and requests to opensquare.io. However, I think most visitors are for off-chain voting: https://voting.opensquare.io . The bounties site is in a very early stage since now there are very few child bounties, but we believe child bounty collaboration should be a feasible way for public goods development. Future work should includes talking with bounty curators and do promotion to external developers.

BTW, we haven't publicized this site through medias or social network. Publicization work includes:
1. We created a post on polkadot forum to call for developers.
2. Announce it in kusama governance channel.
3. We broadcast developer enrollment information in wechat groups we know.

We got 2 developers for our child bounties in upper ways. We didn't take ways which will charge fees due to there is not enough fund, and we don't think it will be effective.

![](https://ipfs.opensquare.io/164cdea3-2276-4d48-a55a-7895921198f0-bucket/others/20230608-160713.jpeg)

Hi Yongfeng. We'd like to invite you to join AAG on Monday at 3:30pm UTC to share your proposal and take questions from the audience.

Please reach out on Matrix @jay-chrawnna:matrix.org

Thanks! 🙏

Participating in Subsquare bounty program was a great experience. Good learning experience and pro-active guidance/mentorship from Yongfeng LI | OpenSquare.

Good documentation, modular and clean code made it even seamless to contribute. 💯

Ethereum also has a similar platform, Gitcoin. I'm hopeful we can use opensquare bounty platform to such extent.

[@Joe](GcDZZCVPwkPqoWxx8vfLb4Yfpz9yQ1f4XEyqngSH8ygsL9p-kusama) Hey, the beneficiary the address of the [bounty #11](https://kusama.subsquare.io/treasury/bounty/11).

[@Anaelle | Parity](/user/FABqdo6XpBEFY6taVDa9GKKdSxPWWwpZAtJgjAKM7t2ah6h) Thanks for your reminder. This proposal is a topup for [bounty #11](https://kusama.subsquare.io/treasury/bounties/11), so we updated our process there.

What we have achieved:
1. Implemented identity business and released on polkadot/kusama statescan. We can see how identity pallet works by this work and understand the business by delivered UIs. We also give update on [polkadot forum](https://forum.polkadot.network/t/subsquare-feature-updates/2985/14?u=wliyongfeng).
2. Implemented multisig pallet business. The delivered work includes multisig related UI on [statescan](https://polkadot.statescan.io/#/multisigs?page=1), multisig graphql API which is also used by subsquare for related multisig UIs, updates on forum [here](https://forum.polkadot.network/t/subsquare-feature-updates/2985/17?u=wliyongfeng).
3. Implemented 1st version of [vesting-scan](https://github.com/opensquare-network/statescan-v2/tree/main/backend/packages/vesting-scan), but we need more refactor work for final delivery.
4. We finished 2 child bounties collaboration through the built bounty collaboration site [#245](https://bounties.opensquare.io/#/network/kusama/bounty/11/child-bounty/245) and [#335](https://bounties.opensquare.io/#/network/kusama/bounty/11/child-bounty/335). The assumed workflow in bounty #11 is proven workable, but there are still much work can be done for improvements, like not all kinds of work is appropriate for external developers bounty, best bounty size for different work(backend, fronted, scan, etc), communication workflow with bounty hunters.

Future work plans:
- Refactor vesting scan and scan blocks for polkadot/kusama.
- Create graphql API for vesting business.
- Vesting business related UI.
- Improve child bounty workflow and try to make it more efficient.

We plan to finish upper planned work in the first half year of 2024.

- Date: 08.06.2023
- Proponent: OpenSquare(ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb)
- Bounty address: F3opxRbN5ZbjJNU513biNd7gHacZD1K3wU4M6Yiq3MZxZgf
- KSM requested: 3,100 KSM
---

Please check [Bounty #11](https://kusama.subsquare.io/treasury/bounty/11) or [full proposal](https://hackmd.io/@WIq3uV0rRwS6W3GGj2pmyA/Sy9-nCF9t) for details of polkadot visualization bounty program. Its targets includes:
- Implement a group of UI to show business of kusama/polkadot.
- Engage more developers to dotsama developing in the way of child bounties.
- Seek ways to facilitate collaborations between projects and external developers in the dotsama ecosystem.

Current achivements:
- Developed and released [a site](https://bounties.opensquare.io/) for collaborations in a bounty and child bounty way. Bounty curators can import bounties or child bounties on chain to this site, and external developers can apply them. This bounty site support basic collaboration flows between curators and external developers. Funded by [child bounty #34](https://kusama.subsquare.io/treasury/child-bounty/11_34).
- [Statescan-v2](https://github.com/opensquare-network/statescan-v2) is developed and released. Now it support polkadot, kusama and several other common good para chains. It's 100% open source. Compared to statescan v1, v2 is more modularized and friendly for collaboration between developers. V2 development work is still not paid due to the market condition.
- [Bounty #245](https://bounties.opensquare.io/#/network/kusama/bounty/11/child-bounty/245) and [bounty #335](https://bounties.opensquare.io/#/network/kusama/bounty/11/child-bounty/335) are created for identity and vesting pallet business scan. Identity scan child bounty has been awarded, while vesting pallet child bounty is still under developing. 2 external developers are enrolled.

## Budget

Already spend:

|  Item   | Spend  | Fiat | Status |
|  ----  | ----  | ---- | ---- |
| [child bounty #34](https://kusama.subsquare.io/treasury/child-bounty/11_34)  | 281.7KSM | ≈$10,000 | Awarded |
| [Child bounty #245](https://bounties.opensquare.io/#/network/kusama/bounty/11/child-bounty/245)  | 100KSM | ≈$3,000 | Awarded |
| [Child bounty #335](https://bounties.opensquare.io/#/network/kusama/bounty/11/child-bounty/335)   | 80KSM | ≈$2,000 | Developing |

Current remaining: 262.77KSM, ≈$6,500.

The final request is $80,000 considering the request of the bounty [proposal](https://hackmd.io/@WIq3uV0rRwS6W3GGj2pmyA/Sy9-nCF9t) and the cost already been spent.

## Possible questions

### Can the bounty site be used by other bounties?

Of course. Any dotsama onchain bounties can be imported and seek collaborations with hunters.

### OpenSquare requested maintenance cost for statescan, is it been double paid?

We usually separated public goods maintenance proposal and new features development proposal. Though maintenance proposal includes some small amount for development, in most cases it's bug fixes, UI tweaks and code refactor. Beg the understand it's a complex process to develop, maintain and collaborate with external developers for a robust and 100% open source explor.

### Why a bounty instead of a dedicated team?
1. OpenSquare is dedicated to dotsama ecosystem development, but our capacity is limited.
2. Bounty and child bounty will make these jobs open to all developers.
3. Bounty provide a price discovery mechanism between dotsama development and labors.

### OpenSquare Bounty Proposal Summary

- **Date:** 08.06.2023
- **Proponent:** OpenSquare
- **Bounty Address:** F3opxRbN5ZbjJNU513biNd7gHacZD1K3wU4M6Yiq3MZxZgf
- **KSM Requested:** 3,100 KSM

**Goals:**
- Create UI for Kusama/Polkadot business visualization.
- Engage more developers through child bounties.
- Facilitate collaboration within the Dotsama ecosystem.

**Achievements:**
- Developed a bounty site for collaboration.
- Released Statescan-v2, supporting multiple chains.
- Created child bounties for identity and vesting pallet scans.

**Budget:**
- Spent: 461.7 KSM (≈$15,000)
- Remaining: 262.77 KSM (≈$6,500)
- Final request: $80,000

**Questions:**
- Bounty site can be used by other bounties.
- Maintenance and development costs are separate.
- Bounties allow open participation and price discovery.

Awarded

medium_spender

WHO: OpenSquare

WHAT: Implement UI, engage developers, facilitate collaborations in Polkadot ecosystem

PRICE: 3,100 KSM (requested), $80,000 (final request)

TIMEFRAME: N/A

RESOURCES: [Bounty #11](https://kusama.subsquare.io/treasury/bounty/11), [full proposal](https://hackmd.io/@WIq3uV0rRwS6W3GGj2pmyA/Sy9-nCF9t)

Item	Spend	Fiat	Status
child bounty #34	281.7KSM	≈$10,000	Awarded
Child bounty #245	100KSM	≈$3,000	Awarded
Child bounty #335	80KSM	≈$2,000	Developing

Visualize polkadot program phase1 bounty top up

Budget

Possible questions

Can the bounty site be used by other bounties?

OpenSquare requested maintenance cost for statescan, is it been double paid?

Why a bounty instead of a dedicated team?

OpenSquare Bounty Proposal Summary