mirror of https://github.com/status-im/swarms.git
81 lines
1.6 KiB
Markdown
81 lines
1.6 KiB
Markdown
---
|
|
id: #317-dapps-store
|
|
title: DApps Store
|
|
status: research
|
|
lead-contributor: Andy
|
|
contributors:
|
|
- Andy
|
|
- Julien
|
|
- Andrei
|
|
budget:
|
|
- actual: xxx
|
|
- estimate: yyy
|
|
- currency: ETH
|
|
---
|
|
|
|
|
|
DApps Store Swarm Proposal
|
|
=
|
|
|
|
## Summary and Goals
|
|
|
|
The DApps Store swarm will deliver SNT based curation mechanisms in accordance with the white paper.
|
|
|
|
It allows individuals to curate DApps by staking SNT and have access to this list within Status.
|
|
|
|
## Contributors
|
|
|
|
- Andy
|
|
- Julien
|
|
- Andrei
|
|
|
|
(+ Janitor swarm)
|
|
|
|
## Communication
|
|
|
|
`status channel`: #317-dapps-store
|
|
`sync schedule`: weekly
|
|
|
|
`Meeting notes`:
|
|
|
|
## Research
|
|
|
|
`Timebox`: wrap by 28/12
|
|
|
|
`Previous work`:
|
|
|
|
DApps are currently exposed as a static catalog hardcoded in Status client.
|
|
Previous versions of Status relied on a basic discovery protocol to discover new DApps.
|
|
[State of the DApps](https://www.stateofthedapps.com/) is an existing curated list of DApps.
|
|
|
|
Andy [proposed](https://discuss.status.im/t/how-to-curate-dapps-simply/759) a bonded curve based curation mechanism.
|
|
|
|
`Potential user stories for MVP`:
|
|
- As a Status user:
|
|
- I want to easily browse interesting DApps
|
|
- I want to see new DApps frequently.
|
|
- I want to see old unusable DApps removed.
|
|
- I want to be confident a DApp is usable / not a scam.
|
|
- I want to be able to propose a DApp for inclusion.
|
|
- I want to vote for a DApp inclusion.
|
|
--
|
|
- As a DApp developer:
|
|
- I want to be able to propose my DApp for inclusion.
|
|
- I want to vote for my DApp inclusion.
|
|
|
|
|
|
`Research questions`:
|
|
|
|
- Is it possible to
|
|
|
|
|
|
## Specification
|
|
|
|
## Implementation
|
|
|
|
## Maintenance
|
|
|
|
## Copyright
|
|
|
|
Copyright and related rights waived via CC0.
|