status-im/swarms
2
0
Fork 0
mirror of https://github.com/status-im/swarms.git synced 2025-02-26 08:35:22 +00:00
Code Issues Projects Releases Wiki Activity

Review pt. 1

Browse Source
This commit is contained in:
Richard Ramos 2019-01-04 12:57:30 -04:00
parent ac0290d3c2
commit a74a85eba2
No known key found for this signature in database
GPG Key ID: 5660EFE0444098A8
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
ideas/322-dao.md
View File

@ -23,6 +23,9 @@ DAO
One major drawback in legacy social networks is the lack of influence their users possess over the networks themselves. They are often powerless in having a say on how the platform evolves. We aim to democratise this power, giving stakeholders a direct influence over all decisions within the network, including how the software is developed with voting and allocation of funds via liquid pledging One major drawback in legacy social networks is the lack of influence their users possess over the networks themselves. They are often powerless in having a say on how the platform evolves. We aim to democratise this power, giving stakeholders a direct influence over all decisions within the network, including how the software is developed with voting and allocation of funds via liquid pledging
#### Goals
- Funding done on the mainnet. A goal is to have funds currently in the multisig of the GMBH to start moving to DAO’s for allocation to projects.
## Contributors ## Contributors
@ -50,11 +53,15 @@ One major drawback in legacy social networks is the lack of influence their user
- Liquid Pledge uses Solidity < `0.5.0`. Migrating to 0.5.0 would make debugging easier thanks to revert exceptions including an error message. However, the project uses OpenZeppelin and Aragon's contracts which would make the migration to `0.5.0` more complicated. - Liquid Pledge uses Solidity < `0.5.0`. Migrating to 0.5.0 would make debugging easier thanks to revert exceptions including an error message. However, the project uses OpenZeppelin and Aragon's contracts which would make the migration to `0.5.0` more complicated.
- What information is important to be displayed to funders, delegates and projects?
- What is the ideal specification for a "Pledge"?
#### Key assumption to test: #### Key assumption to test:
- Funding done on the mainnet. A goal is to have funds currently in the multisig of the GMBH to start moving to DAO’s for allocation to projects.
- Voting is described as part of governance in the Status whitepaper. The voting dapp is currently used as a signaling tool, and it does not have in-chain consequences. Will voting be used also for project funding? (via topic democracy or other mechanism) - Voting is described as part of governance in the Status whitepaper. The voting dapp is currently used as a signaling tool, and it does not have in-chain consequences. Will voting be used also for project funding? (via topic democracy or other mechanism)
- Principles signing should be required in order to access the funds. A plugin could be made for this, or in case identities are implemented, maybe a Claim could be created for an identity once the principles are signed. - Principles signing should be required in order to access the funds. A plugin could be made for this, or in case identities are implemented, maybe a Claim could be created for an identity once the principles are signed.
- Are delegates needed?
- Is directly funding a specific purpose Aragon DAOs from the primary multisig easier to manage?
## Specification ## Specification
TODO TODO