I am very glad to announce DashBoost has launched a public beta. My team has been working very hard to make this work. We have tamed the beast, and here we are for feedback. Giving feedback is the best thing you can do. Thanks a lot. You can access the project at http://test.dashboost.org
Report a Bug!
Read the DashForceNews article!
You can read the Press release here!
Now into the update.
Google Docs Link for formatting.
DashBoost Update
February 28, 2018
Overview
The DashBoost proposal successfully passed at the beginning of February. Escrowed under GreenCandle, DashBoost aims to allow smaller proposals to have a place in the Dash treasury system as well as reintroduce funds leftover from the GreenCandle escrow process. Please read the DashBoost Proposal and the DashBoost Technical Specification to learn more about the project as a whole.
This update will consist of the following parts:
Income
Expenses
Current State of DashBoost Financials
DashBoost, as of the 28th, of February 2018 has the following:
Spending Account: 0.50999313 Dash
Saving Account: 0 Dash
Fee Account: 0 Dash
Achieved
The DashBoost team is very proud of what we have accomplished in the past month. The first thing that was accomplished was the passing of the proposal and our initial meeting with GreenCandle. An MOU was signed by both parties ensuring that GC and the DashBoost team were on the same page. Here and here is the MOU, with information that could be used for personal identification redacted. In the MOU, appendix 1 refers to the technical specification.
DashBoost has had two meetings with GreenCandle. The first meeting’s minutes can be viewed here. That meeting was held on the second of February. The second meeting’s minutes held on the 23rd of February, can be viewed here.
DashBoost’s biggest accomplishment this month was the development that occurred. We have achieved the MVP as defined in the technical specification and more. Starting on the 2nd or 3rd of March, a test cycle will be initiated. All members of the community are invited to participate in the test cycle. This cycle will be one week in duration and will be operated on testnet. The site can be accessed at DashBoost.org. Please recognize the test-site does not have HTTPS, all data sent could be intercepted, as such do not use secure passwords or sensitive information on the test-site.
Next Month
The month of March will be exceptional for DashBoost. Below is a list of what we plan to accomplish in the next month:
Conclusion
DashBoost is satisfied that it reached its initial milestones to create an MVP and is primed to hit the second set of goals. We are satisfied with what we have accomplished and know it will provide an invaluable service allowing micro proposals into the treasury system. Anyone with feedback can send an email to [email protected] or message @Pasta / @TechSquad on Discord. My team and I are excited to continue implementing this project as we head into the test cycle phase. Thank you for your support and time.
Thank you for taking the time to read our February update. Please leave any feedback or questions below. Please report bugs by sending an email to [email protected] or by following the link about.
Report a Bug!
Read the DashForceNews article!
You can read the Press release here!
Now into the update.
Google Docs Link for formatting.
DashBoost Update
February 28, 2018
Overview
The DashBoost proposal successfully passed at the beginning of February. Escrowed under GreenCandle, DashBoost aims to allow smaller proposals to have a place in the Dash treasury system as well as reintroduce funds leftover from the GreenCandle escrow process. Please read the DashBoost Proposal and the DashBoost Technical Specification to learn more about the project as a whole.
This update will consist of the following parts:
- Overview
- A general introduction to the update
- A general introduction to the update
- Financials
- A breakdown of the current finances of DashBoost
- A breakdown of the current finances of DashBoost
- Achieved
- A description of what has been done since the beginning of the project.
- A description of what has been done since the beginning of the project.
- To be Achieved
- A list of the goals that are planned to be completed before the next update.
- A list of the goals that are planned to be completed before the next update.
Income
- 25 Dash from GC as initial payment - 15a871e34c195e41a2e63bda810348f137ca520752dce79b5d826d86ac931431
- 4 Dash from GC as return of proposal fee - bfedac636deb90565eef42b33d25b4d55bd45b884ddc013d09eae3717e902166
Expenses
- 5 Dash paid to “[Redacted at request of reciever]” repaying the dash he put in allowing the project to get started consisting of 3 Dash for proposal fee & 2 Dash for funding the Technical Specification- be62c29396e849c1b49a7ad27a4731f96a639d1e11964e596549fae69967ac57 and 549a186c9cf0d361ec31e5ec5c01304433d347e9be5c1079e61a0d5b11c9adc9
- 1 Dash sent to "Pasta" for reimbursement of proposal fees - 9264e239ded8812f8194263817e1aaa4cbc59df61f98e66f09e377ff90df685f
- 7.5 Dash paid to "Pasta" for administrative services as prescribed in proposal- fe3d57bd48bf567c8b0db4d0e88d7acbac595a423996236a0b9d5e89c706e109
- 15 Dash paid to "TechSquad" for development services as prescribed in proposal- 618f3f25d8b90253fde508fa4309d5f851e7a857ce2275a544a314d5ea8bc172
Current State of DashBoost Financials
DashBoost, as of the 28th, of February 2018 has the following:
Spending Account: 0.50999313 Dash
Saving Account: 0 Dash
Fee Account: 0 Dash
Achieved
The DashBoost team is very proud of what we have accomplished in the past month. The first thing that was accomplished was the passing of the proposal and our initial meeting with GreenCandle. An MOU was signed by both parties ensuring that GC and the DashBoost team were on the same page. Here and here is the MOU, with information that could be used for personal identification redacted. In the MOU, appendix 1 refers to the technical specification.
DashBoost has had two meetings with GreenCandle. The first meeting’s minutes can be viewed here. That meeting was held on the second of February. The second meeting’s minutes held on the 23rd of February, can be viewed here.
DashBoost’s biggest accomplishment this month was the development that occurred. We have achieved the MVP as defined in the technical specification and more. Starting on the 2nd or 3rd of March, a test cycle will be initiated. All members of the community are invited to participate in the test cycle. This cycle will be one week in duration and will be operated on testnet. The site can be accessed at DashBoost.org. Please recognize the test-site does not have HTTPS, all data sent could be intercepted, as such do not use secure passwords or sensitive information on the test-site.
Next Month
The month of March will be exceptional for DashBoost. Below is a list of what we plan to accomplish in the next month:
- Improve user experience and overall design.
- Add in more systems to ensure DashBoost is fully transparent and as decentralized as possible at this point in time.
- Take community feedback and implement features that are very highly desired.
- Launch the first live cycle.
- Start and finish 1 or 2 test cycles.
- Each test cycle will be 1 week long, with the first cycle starting on the 2nd or 3rd of March. A second cycle will be started if additional data and adjusting of the platform is needed.
- The goal of these cycles is to receive feedback from the community about features that are wanted or needed as well as ensure the system is robust and ready for launch.
- Each test cycle will be 1 week long, with the first cycle starting on the 2nd or 3rd of March. A second cycle will be started if additional data and adjusting of the platform is needed.
Conclusion
DashBoost is satisfied that it reached its initial milestones to create an MVP and is primed to hit the second set of goals. We are satisfied with what we have accomplished and know it will provide an invaluable service allowing micro proposals into the treasury system. Anyone with feedback can send an email to [email protected] or message @Pasta / @TechSquad on Discord. My team and I are excited to continue implementing this project as we head into the test cycle phase. Thank you for your support and time.
Thank you for taking the time to read our February update. Please leave any feedback or questions below. Please report bugs by sending an email to [email protected] or by following the link about.