View All Bounty

Bounty proposal: Visualize polkadot bounty program phase 1

4 years ago
Claimed

Dotsama has more rich features compared to 1st generation state transition blockchains like Ethereum and UTXO based chains like Bitcoin, but at the same time it's more complicated for people to understand them. We propose to implement a group of business oriented explorers and Dapps to help users better understand and work with dotsama.

The implementation will be done through bounties and child bounties, and we propose ourself OpenSquare to be the curator. We will split the work into child bounties, build a site for curator and external developers to collaborate on child bounties, and report back the development progress to the council.

So this proposal has following motivations:

  1. Implement a group of business oriented explorers and dapps.
  2. Educate more developers by implementing the explorers and dapps features with child bounties.
  3. Seek ways to facilitate collaborations between projects and external developers in the polkadot ecosystem. We will experiment the way bounty -> curator(OpenSquare) -> child bounties -> developers in this proposal.

Problems statement

Rich features need visualization

No doubt polkadot has more rich features compared to 1st generation state transition blockchains like Ethereum and UTXO based chains like Bitcoin，such as forkless upgrade, on-chain governance mechanism, treasury, para-chains, etc. But to be honest it’s more complex too, which means it will cost more for people to understand them. We need better UIs to demonstrate them. They should show the participating roles, workflows, business life cycles, and to a user, it should tell the steps to complete a business.

Dapps with more contextual info

Polkadot/Substrate portal is great, but it has problems too.

  1. Most shown data is on-chain, while we have to check the contextual info from a explorer to complete some operations.
  2. Too advanced to some non-technical users, while they expect simpler ones.

The proposed business oriented explorers can provide the contextual data, and it will be perfect if we can complete our business just on these business explorer pages.

More builders, more collaborations

We need more developers, designers, educators and other roles to build web3 based on substrate/kusama/polkadot. The best way to enroll more builders is collaboration. Bounty & child bounties will be good ways to start collaborations, between curators, child bounty curators and implementers.

Solutions & Implementations

OpenSquare proposes the big bounty, becomes the curator and then creates child bounties, assigning them to external developers. Deliveries will include:

  • Identity pallet business explorer and user interfaces to register and request judgement.
  • Vesting pallet business explorer and user interfaces to vest_transfer and vest.
  • Basic block/extrinsic/event pages for relay chain.
  • A bounty collaboration site where curator can collaborate with child bounty hunters.

There will also be other business implementations in the future plan, including governance, society, para-chains, etc. For more detailed proposal context, milestones, budget, deliverables and plans, please check the full proposal.

We are OpenSquare team, dedicated to facilitate the collaboration between projects and developers.

Comments (7)

4 years ago

Please check OpenSquare's candidacy request here.

Generally we are qualified to be the curator because:

  1. OpenSquare is the initial proposer and implementer of statescan. Considering most of the work will be done based on statescan, no one is more suitable to curate the work.
  2. OpenSquare has rich experience in developing explorers with good UIs for substrate based chains which can be verified by the previous delivery of dotreasury and statescan. You can also check our work off-chain voting and SubSquare.
  3. To facilitate collaborations between projects and developers is one of the main businesses OpenSquare is dedicated to, so we have a great passion to connect projects and developers.
  4. Though we don’t have a big developer community, we know enough developers who are qualified enough to finish the child bounties.

And our work will be:

  1. Divide the big bounty into child ones, the find developers and allocate child bounties
  2. Do some child bounties by ourselves to keep efficiency and make sure the delivery.
  3. Educate developers who are not so experienced with polkadot/blockchain.

About child bounties:

  • Please check the possible child bounties here in the full proposal.
  • Implementers can apply these child bounties on the site promised to be built by OpenSquare.
    1. OpenSquare will post child bounties info to the site.
    2. Hunters can apply with their application signed by their polkadot key.
    3. Assignment and other collaboration behaviors will happen on this site.

3 years ago

We'd like to report our work till now for this bounty, and that's we've finished the design for planned bounty collaboration site.

Generally it will enable curators and hunters to collaborate with bounties. The supported user stories includes:

  1. As a curator, I can import a on-chain bounty and edit description for it. So I can import child bounties for it to attract hunters.
  2. As a curator, I can import a on-chain child bounty and edit description, so hunters can apply.
  3. As a hunter, I can apply a child bounty only with my polkadot key.
  4. As a curator, I can assign/unassign a child bounty to one of the applicants.
  5. As a assignee, I can submit my work with description and a link.
  6. As a curator, I can award the bounty assignee.
  7. As a user with a polkadot key, I can have a discussion with others under a bounty or child bounty.

Some screenshots:

Home page with a bounty list
Image

Bounty import page
Image

Child bounty detail page(hunter's view)
Image

PleaseLogin to comment

Child Bounties