Proposal “dash-platform-incubator-phase-4“ (Completed)Back
Title: | Dash Platform Incubator - Phase 4 |
Owner: | andyfreer2020 |
Monthly amount: | 275 DASH (15280 USD) |
Completed payments: | 3 totaling in 825 DASH (0 month remaining) |
Payment start/end: | 2020-11-13 / 2021-02-10 (added on 2020-11-18) |
Votes: | 1070 Yes / 11 No / 4 Abstain |
Proposal description
Dash Proposal: Dash Platform Incubator - Phase 4
1. Summary
This proposal provides a “Phase 4” to the Dash Platform Incubator Phase 3 proposal (https://www.dashcentral.org/p/dash-platform-incubator-phase-3) to extend bounty funding for the development of tools, resources, Dapps and Protocol enhancements for Dash Platform on EvoNet and leading to Testnet for a further 3 months.
2. Phase 3 Review
As per Phase 3 goals to improve Dev onboarding, as well as continuing and expanding existing bounty work, we’ve completed a set of bounties to upgrade the Incubator itself as a standalone open-source / open-data App, to make it more effective in onboarding devs and flesh out the incentive structure to help us scale, with all existing funds and bounties migrated to the new system:
https://dashincubator.app
How this will work going forward is that my series of proposals will provide funds into the App (its input) and a group of Admins will create and manage Bounties that provide incentives to users to produce work via the App (its output).
This is V1 of the App and still uses Trello on the backend for Bounty management and a Gdoc for accounting so its far from fully automated, but work will be ongoing now on V2 to implement our own (public) backend wired to the site ASAP, followed by a Dapp version once Platform is on mainnet (and ultimately i’d like to Dappify the funding side too using smart code if our protocol allows).
The goal of the App is to provide an optimal way to translate blockchain funds into valuable human labor for Dash (with a focus on Dapp development), built on the principles that maximizing transparency in decision making and operations can also maximize productivity, accountability and ROI to the Dash network, with the right tools and incentive structures in place.
The App is essentially governed by a set of Rules implemented by both the App’s code and the Admins governing it, who i’m appointing today as we soft launch the App. Each Admin has the ability to create, manage, and earn commission from their own set of Bounties within the App and operate within their own budget. These rules represent the full terms of how these Proposals and the App itself will be implemented as of today:
https://dashincubator.app/rules
Whilst eventually we’ll move to full decentralized control by Admins (via quorum based decision, election, review and removal mechanisms), for the time being as Proposal Owner I will retain overall control/veto on decisions until I’m happy that the system is mature enough to decentralize completely.
List of the Admins i’m appointing is as follows:
I’ve selected this group to have a wide range of skills / experience / interests and with positive reputations within the Incubator already, including some DCG devs to give them access to help expedite or flesh out some peripheral parts of their work that might help Community devs get what they need faster.
3. Phase 3 Highlights
Instead of manually listing all the progress this past Phase, we’ve created a page now that shows the Bounties produced by Incubator users in realtime:
https://dashincubator.app/output
4. Phase 4 Strategy
Now that we have a group of Admins, each will have their own strategy for the output they want to incentivize within the context of the overall Incubator strategy which is stated in the rules as follows:
https://dashincubator.app/rules#14-strategy
My own strategy as an Admin during this Phase is:
In terms of funding, I've increased the ask slightly to factor in the additional work we are taking on to develop and improve the Incubator App itself (referred to in the App as Meta Bounties). This being said, there are some upcoming Bounty projects that could easily accelerate our burn rate beyond these levels (for example, some new work connecting ETH to Dash in the form of externalizing smart contract storage, providing Oracles to the ETH network and wrapped-Dash on ETH, which are larger projects than we usually take on and involving Ethereum developers). In such cases, from some discussions with the Admins, I or another Admin could raise some supplemental ‘top-up’ proposals to ask the Network to provide more funding for specific projects and let those stand on their own merit; In either case I will continue to raise my proposals as a baseline to keep the core Incubator strategy funded on a quarterly (ie. 3 superblock cycle) basis.
5. Terms
You can read the full Rules aka ‘protocol’ for the App here, these are comprehensive and supercede the rules from my previous proposals:
https://dashincubator.app/rules
6. Auditing
All resources required to publicly audit all information, source and output of the Incubator are available here:
https://dashincubator.app/rules#6-resources
Thanks
Andy Freer
Dash Developer
1. Summary
This proposal provides a “Phase 4” to the Dash Platform Incubator Phase 3 proposal (https://www.dashcentral.org/p/dash-platform-incubator-phase-3) to extend bounty funding for the development of tools, resources, Dapps and Protocol enhancements for Dash Platform on EvoNet and leading to Testnet for a further 3 months.
2. Phase 3 Review
As per Phase 3 goals to improve Dev onboarding, as well as continuing and expanding existing bounty work, we’ve completed a set of bounties to upgrade the Incubator itself as a standalone open-source / open-data App, to make it more effective in onboarding devs and flesh out the incentive structure to help us scale, with all existing funds and bounties migrated to the new system:
https://dashincubator.app
How this will work going forward is that my series of proposals will provide funds into the App (its input) and a group of Admins will create and manage Bounties that provide incentives to users to produce work via the App (its output).
This is V1 of the App and still uses Trello on the backend for Bounty management and a Gdoc for accounting so its far from fully automated, but work will be ongoing now on V2 to implement our own (public) backend wired to the site ASAP, followed by a Dapp version once Platform is on mainnet (and ultimately i’d like to Dappify the funding side too using smart code if our protocol allows).
The goal of the App is to provide an optimal way to translate blockchain funds into valuable human labor for Dash (with a focus on Dapp development), built on the principles that maximizing transparency in decision making and operations can also maximize productivity, accountability and ROI to the Dash network, with the right tools and incentive structures in place.
The App is essentially governed by a set of Rules implemented by both the App’s code and the Admins governing it, who i’m appointing today as we soft launch the App. Each Admin has the ability to create, manage, and earn commission from their own set of Bounties within the App and operate within their own budget. These rules represent the full terms of how these Proposals and the App itself will be implemented as of today:
https://dashincubator.app/rules
Whilst eventually we’ll move to full decentralized control by Admins (via quorum based decision, election, review and removal mechanisms), for the time being as Proposal Owner I will retain overall control/veto on decisions until I’m happy that the system is mature enough to decentralize completely.
List of the Admins i’m appointing is as follows:
- Andy Freer (Proposal Owner)
- Cloudwheels (Community Dev)
- Rion Gull (Community Dev)
- Readme (Community Dev)
- Pasta (DCG Dev, L1)
- Ivan Shumkov (DCG Dev, L2)
I’ve selected this group to have a wide range of skills / experience / interests and with positive reputations within the Incubator already, including some DCG devs to give them access to help expedite or flesh out some peripheral parts of their work that might help Community devs get what they need faster.
3. Phase 3 Highlights
Instead of manually listing all the progress this past Phase, we’ve created a page now that shows the Bounties produced by Incubator users in realtime:
https://dashincubator.app/output
4. Phase 4 Strategy
Now that we have a group of Admins, each will have their own strategy for the output they want to incentivize within the context of the overall Incubator strategy which is stated in the rules as follows:
https://dashincubator.app/rules#14-strategy
My own strategy as an Admin during this Phase is:
- Continue to work with other Admins and devs to improve processes within the Incubator App itself, as laid out in the roadmap https://dashincubator.app/rules#7-roadmap
- Focus on completing current high-value Dapps into a fully demoable state ready for Testnet, such as our first Social Media Dapp (Jembe, the Twitter alternative), including surrounding work needed to easily on-board users to Dash (Evolution) and get them using these Dapps with minimal friction and the best UX. I’ll be working with Dashameter and TheDesertLynx to achieve this.
- Continue to raise proposals and represent the Incubator, providing the baseline funding and strategy as we grow, and mentor and guide the Admins and developers involved.
In terms of funding, I've increased the ask slightly to factor in the additional work we are taking on to develop and improve the Incubator App itself (referred to in the App as Meta Bounties). This being said, there are some upcoming Bounty projects that could easily accelerate our burn rate beyond these levels (for example, some new work connecting ETH to Dash in the form of externalizing smart contract storage, providing Oracles to the ETH network and wrapped-Dash on ETH, which are larger projects than we usually take on and involving Ethereum developers). In such cases, from some discussions with the Admins, I or another Admin could raise some supplemental ‘top-up’ proposals to ask the Network to provide more funding for specific projects and let those stand on their own merit; In either case I will continue to raise my proposals as a baseline to keep the core Incubator strategy funded on a quarterly (ie. 3 superblock cycle) basis.
5. Terms
You can read the full Rules aka ‘protocol’ for the App here, these are comprehensive and supercede the rules from my previous proposals:
https://dashincubator.app/rules
6. Auditing
All resources required to publicly audit all information, source and output of the Incubator are available here:
https://dashincubator.app/rules#6-resources
Thanks
Andy Freer
Dash Developer
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
No comments so far?
Be the first to start the discussion! |
https://pastebin.com/wgJuEwww
Bob is awesome and he's visited my place many times during my handover of CTO role to him, along with lot of the devs. The role I took from Evan was protocol design dev manager, so I was very happy to hand this to Bob once we could find the right person and also see him really get implementation work organized in DCG and the fruits of that are coming now as we can all see.
In terms of how we agree protocol changes, that's a collaborative process in Dash via DIPs, which I introduced specifically for that purpose. Bob has a role, as do lot of the devs and Ryan who leads DCG, but also any external stakeholders with the knowledge / interest in how we improve Dash, such as myself.
It's worked great up until now so I don't see any reason to change that.
BTW this proposal isn't proposing any protocol changes - I just mention an (obvious) addition that could be done later given the protocol we have today and now addition of L2.
I don't understand why this is necessary. We already have a system whereby proposals such as this one gets funded by the Dash block reward if the DAO deems them worthy. How do you envision "smart funding" working and why is it needed?
What i'm proposing is ti add the option that the superblock pays to a contract (a Dapp) and smart code in the dapp spends those funds autonomously not dependant on an intermediary private key holder.
It's similar to how Dash as a whole pays proposals - superblocks are autonomous, the miner doesn't hold the private key to proposal funds and we trust them to pay proposals manually, they get paid automatically (qualifying Dash as a DAO) without a centralized intermediary. It's just extending that trustless execution down to proposal organizations.
If superblocks paid to Dapps autonomously each proposal organization would be a DAO in it's own right and spending could be conditional and trustless and no individual private key holder would be responsible for the funds.
For example I could make a proposal to say my Dapp will get 1 Dash per 1000 user signups for 3 months, and that could be implemented in smart code. Or in the case of Dash Incubator, you could distribute control to the 6 admins, and condition payments based on a majority vote from them, instead of trusting a centralized intermediary PO (myself) to enact the reward payouts to make the operation of the organization truly decentralized (at the end of the day each PO can always decide what they do with the proposal funds as they hold the private key giving POs a lot of centralized control within their organizations).
It's not something we can do today anyway, i'm just floating it as something I think is a good feature we should add in the future.
Andy for the future please consider submitting the proposal earlier and not 5 days before the voting cycle end.
Anyway you have my support man! :)