- Rinke Hendriksen |
- Blockchain developer and consultant |
- MSc. Digital currencies (expected January 2018) |
- Background in Economics and Finance |
- First release of my code to the public |
- Call for help |
- Open discussion |
- Rules are both in wet-code (plain language) and dry-code (source: unenumerated)
- Wet-code is enforced by voting |
- 'Correct' voting is incentivized by game-theory (aka token-economics) |
- Dry code:
Setting a budget for maximum spending (of Ether), per period per address (who was given the authority to spend by voting)
- Wet code:
When an authorized address spends from the balance of the DAO, the spender must publish details of every transaction, explaining the reason of the spending
- Rules are both in wet-code (plain language) and dry-code (source: unenumerated)
- Wet-code is enforced by voting
- 'Correct' voting is incentivized by game-theory (aka token-economics)
- Which allows changing all parameters (for example: default budget / budget period) |
- Which makes the contract itself fully upgradable, both on-chain and across blockchains |
I need:
- Critical people, to discuss my initial set-up |
- Web-developers, to help creating my user-interface |
- Lawyers, or other people capable of creating my wet-code |
- Experienced Solidity developers, to audit my dry-code |
- Supporters! :) |
- Please reach out to me on Github |
Ask me Anything!