Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

August 2016 Development Update

Discussion in 'Official Announcements' started by eduffield, Aug 2, 2016.

  1. eduffield

    eduffield Core Developer

    Joined:
    Mar 9, 2014
    Messages:
    1,084
    Likes Received:
    5,319
    Trophy Points:
    183
    Hello Everyone!

    I wanted to take some time to update the community about the state of the project and our current work. As you likely know, I recently returned from the d10e conference, where I met a number of volunteers and enthusiasts from the community. We also established many new industry connections. Conferences are incredibly useful, and they remind us that the world has not been exposed to enough information about Dash for it to reach more than a small subset of people even within a community like d10e. Nine of ten people I personally spoke to were completely unaware of what we’re doing, but as they learned about it most became incredibly excited to hear something like this was being created. Dash-only features like self-governance, self-funding, decentralized api access, interest bearing accounts and masternodes were the features these investors were most excited about.

    After returning from the conference, we’re quickly picking up where we left off on 12.1. This is a critical phase of development, far more than at any point we’ve been in the past. This is the phase where we need to anticipate as many use cases as possible for the evolution software, since providing new functionality at a later stage will be more complex. Therefore, this phase is arguably more important than it would be in a centralized company, as we have seen from other projects in the space, due to the complexity of altering decentralized systems after they are in the wild.

    There are currently two separate teams developing the next version of Dash. These are the Evolution team, and dash-core. The Evolution team is tasked with creating a simple user interface to provide a secure, fun, and easy user experience. While this sounds simple, it’s nothing of the sort. The team is building three separate wallets for different audiences. These are going to be the personal-client, merchant-client, and operator-client. The personal-client provides the most simple experience, allowing end-users to engage in social commerce with friends and in transactions with merchants who list their apps and services within a decentralized marketplace in Evolution. The merchant-client will enable the merchants to manage their product and service listings, customer payments, and subscriptions in Evolution. The operator-client enables Masternode operators, moderators, and other incentivized roles to access their functions from a simple client.

    The team is also building the decentralized REST API to be hosted on the Masternode network and a set of SDKs for major platforms. Together, these capabilities will enable merchants to quickly and easily integrate decentralized Dash transactions into any website or app, and without the need to host a Dash node of their own. Integrating Dash into a website or app will be as simple as integrating a few lines of code, similar to what payment gateway providers like Braintree and Stripe provide for online merchants. This will significantly reduce the barriers to digital currency adoption for online merchants, allowing them to integrate Dash within hours and without the need for third-party services, fees, or infrastructure.

    On the dash-core side, the team has been working on general usability/stability of 12.1. We are also integrating a basic version of dashdrive into the system. Dashdrive is the storage mechanism that sentinel+dashd use to store information on the network. At this point it is in a basic state that allows for objects to be created and stored as they will in the future. However the current storage capacity is quite small presently. For now, we will only be storing governance system data, mirroring the system setup for budgets from 12.0.

    After the release of 12.1, utilizing this new technology to build our budgets, we will begin adding additional required pieces of functionality to integrate the two sides of the project. This involves beginning to use dashdrive as it was intended, as a storage mechanism for user data. New functionalities such as creation of users, groups, accounts and the ability to pay-to-url will be next on the development roadmap.

    12.1 is also going to be something of a “pre-alpha” for Evolution. This means it will be able to store some of the basic data structures required for a user to register their Evolution account and be able to use it in basic ways. Many of the more advanced functionalities will first be exposed via CLI, allowing more experienced users access into the system before we implement the features into the evo-client.

    As for current testing process, after d10e we have been busy onboarding some new highly-skilled developers into the core-team, which will be helping us to thoroughly test and refine 12.1 and will continue into 12.2 development. This additional capacity and expertise will accelerate the pace and quality of testing, bug-fixing, and ongoing core development, and allow progress to continue unabated even when my time may be required for events or business-related needs.

    Testing is currently progressing for 12.1, and we are presently working on getting superblocks to be created and accepted on the network. This introduces a lot of new code and needs some work before community-wide public testing would be beneficial. The current one is a process of debugging thousands of new lines of code, and making sure most of the work flows are tested and function on a basic level without critical errors. We should expect to shift to public testing of version 12.1 within the next two weeks.

    Thanks!
     
    • Like x 27
    • Informative x 4
    • Winner x 2
    • Friendly x 1
    • Useful x 1
    • Optimistic x 1
  2. fible1

    fible1 Well-known Member
    Dash Core Team Masternode Owner/Operator

    Joined:
    May 11, 2014
    Messages:
    710
    Likes Received:
    722
    Trophy Points:
    163
    Quick question: Are the new three wallet types being built for evolution going to be electrum based, qt based, or other?

    Thank you,
    Pablo.
     
  3. Solarminer

    Solarminer Well-known Member

    Joined:
    Apr 4, 2015
    Messages:
    762
    Likes Received:
    921
    Trophy Points:
    163
    @eduffield Can you explain the 12.1 budget system? Will this have turing complete programming? If so, this is a really big deal, and it should be the main focus of this release.

    The community would like the opportunity to understand how the code works BEFORE it is released. There could be some changes that severely effect Dash (like multiple month contracts that can never be voted out). How does the minimal Masternode hosting requirements change. Is the REST api going to require more bandwidth? Dashdrive more server space? This release needs a discussion and maybe a vote before it is released.

    Thanks for the update.
     
    • Like Like x 1
    • Agree Agree x 1
  4. flare

    flare Administrator
    Dash Core Team Moderator

    Joined:
    May 18, 2014
    Messages:
    2,287
    Likes Received:
    2,406
    Trophy Points:
    1,183
    The Electrum based Evolution demo was just a prototype/showcase. The actual Evolution wallets are developed from scratch. @AndyDark may chime in if i wrote something wrong :)
     
  5. fible1

    fible1 Well-known Member
    Dash Core Team Masternode Owner/Operator

    Joined:
    May 11, 2014
    Messages:
    710
    Likes Received:
    722
    Trophy Points:
    163
    @flare thank you as always :).

    @AndyDark Hey :),
    Could you please tell me if the wallets will use the electrum codebase at all or be completely new?

    Thank you very much for your help.

    Pablo.
     
  6. TroyDASH

    TroyDASH Well-known Member

    Joined:
    Jul 31, 2015
    Messages:
    1,251
    Likes Received:
    794
    Trophy Points:
    183
    Just wanted to reiterate what solar said above. For Dash users and stakeholders who are not privy to your private development Slack or other private conversations, it really would be nice to have some more information about 12.1 specs. AFAIK, you haven't even officially announced here what sentinel *is* and what these other new features will mean for us in the short term, so you might understand why updating us that you're working on the stability/usability of it (sounds like finishing touches) might make me nervous when it hasn't even been openly discussed.
     
    • Like Like x 2
    • Agree Agree x 2
    • Winner Winner x 1
  7. greensheep

    greensheep New Member

    Joined:
    Jan 3, 2016
    Messages:
    19
    Likes Received:
    19
    Trophy Points:
    3
    +1 I would also like to get more information about how the 12.1 features are implemented. What does Dashdrive mean for the Masternodes? How reliable is their data storage? How did the new budget system end up being implemented? Releasing information early allows for a wider peer review and minimizes the risk that the community will be surprised when the new release comes out and opposes to it.
     
    • Agree Agree x 3
  8. Vedran Yoweri

    Vedran Yoweri Active Member

    Joined:
    Apr 29, 2015
    Messages:
    334
    Likes Received:
    152
    Trophy Points:
    113
    It's not something to vote over. Evan & team build whatever they want. Info would be nice however. But i guess it's better to let the ETH/C storm die down a bit to give our news room to impress.
     
    • Dislike Dislike x 1
    • Funny Funny x 1
  9. Comodore

    Comodore Member

    Joined:
    Nov 8, 2015
    Messages:
    185
    Likes Received:
    97
    Trophy Points:
    88
    So this will be the only protocol version change in comming years?
     
    • Optimistic Optimistic x 1
  10. orangecycle

    orangecycle Well-known Member
    Foundation Member

    Joined:
    Oct 2, 2014
    Messages:
    169
    Likes Received:
    239
    Trophy Points:
    203
    A good place to keep up with all the changes is the official repo https://github.com/dashpay/dash/. You can "watch" a repo and have all updates emailed to you. A lot of updates are packed with valuable and interesting commit comments. Makes for good morning reading with a cup of coffee.
     
    • Like Like x 4
    • Informative Informative x 2
  11. TroyDASH

    TroyDASH Well-known Member

    Joined:
    Jul 31, 2015
    Messages:
    1,251
    Likes Received:
    794
    Trophy Points:
    183
    Yes, info would be nice. Not giving stakeholders a clear picture or even having a discussion with stakeholders prior to dumping a release on us is the kind of thing that exacerbates disunity between core and community. Ultimately, it gets voted on by miners and MNOs when they decide to update or not update. But just leaving it to that sounds like a poor plan if anyone on the dev team cares at all about input from stakeholders or keeping them well informed.
     
    • Agree Agree x 3
    • Like Like x 1
  12. Vedran Yoweri

    Vedran Yoweri Active Member

    Joined:
    Apr 29, 2015
    Messages:
    334
    Likes Received:
    152
    Trophy Points:
    113
    Sorry, don't agree at all. Evan doesn't work for you, he owes you nothing. He builds open source software for everybody to use or not.

    "Demanding" stuff and then starting discussions with big words "disunity between core and community" when your demands are not met is at best illogical. But it also looks like just a tactic to spread FUD. This is something trolls do, not level headed "community" members.
     
    • Dislike Dislike x 1
  13. TroyDASH

    TroyDASH Well-known Member

    Joined:
    Jul 31, 2015
    Messages:
    1,251
    Likes Received:
    794
    Trophy Points:
    183
    Actually he does work for us because we pay him. No one is "demanding" anything. I am simply stating that stakeholders might want to be treated a little differently than this, for good reason. I don't appreciate being labeled by you as a troll, already! Seriously? This is the attitude that alienates people and makes people want to completely withdraw from this place. Anyway, I would appreciate if someone *from core development* ( not you) would be kind enough to weigh in
     
    • Like Like x 1
  14. Vedran Yoweri

    Vedran Yoweri Active Member

    Joined:
    Apr 29, 2015
    Messages:
    334
    Likes Received:
    152
    Trophy Points:
    113
    Not true, the blockchain does.
    I understand, also I didn't do that. I argued from the 'illogical' option.
     
    • Dislike Dislike x 1
  15. TroyDASH

    TroyDASH Well-known Member

    Joined:
    Jul 31, 2015
    Messages:
    1,251
    Likes Received:
    794
    Trophy Points:
    183
    And who decides whether the blockchain pays? Stakeholders. Of which I am a member.

    Saying that my post looks like a tactic to spread FUD which is what trolls do, is a strong enough implication for me.

    From this point forward I will try to keep this *on topic*. A few of us have requested additional information or a response from the op. It's not anything personal. I am happy to hear other people weigh in, both of *us* have already made our opinions known so it's a waste of time for us two to go back and forth anymore.
     
    • Agree Agree x 2
  16. Solarminer

    Solarminer Well-known Member

    Joined:
    Apr 4, 2015
    Messages:
    762
    Likes Received:
    921
    Trophy Points:
    163
    Thanks @orangecycle.

    This budget readme is the one that we want to see before release. It currently says rewrite..
    https://github.com/dashpay/dash/blob/v0.12.1.x/doc/masternode-budget.md

    Why advanced notice on this release? Most releases up to this point just added features. It isn't a big deal to add a feature and shouldn't require any community discussion. This release fundamentally changes the budget system. Users need to know these changes before they are released.

    I see that multiwallet support is listed as a change. This is really cool. (Changes like this don't need a vote, but you do get more ataboys if you can list the cool stuff that is added in the release notes)
    window.setCurrentWallet("~Default");

    If you need someone to write the release notes, ask. I am sure we can help out with this with a little help and direction.
     
    • Like Like x 1
    • Agree Agree x 1
  17. TroyDASH

    TroyDASH Well-known Member

    Joined:
    Jul 31, 2015
    Messages:
    1,251
    Likes Received:
    794
    Trophy Points:
    183
    Just wanted to add this one has a ton of juicy stuff that is nowhere to be found on the official repo...
    https://github.com/evan82/sentinel

    If Evan is not responsive here it's probably because he's committing the hell out of that repository. Documentation on functionality is thin but that might be because there's literally only one person coding all of this. How comfortable is everyone else in our dev team in terms of knowing what this is? I think it is imperative that even though Evan is clearly the lead (if not only) developer for Sentinel, we need to work to get as many people up to speed on what it is and how it is intended to work, as soon as possible. This will speed up testing and also increase the quality of peer review.
     
    • Like Like x 1
    • Informative Informative x 1
  18. bhkien

    bhkien Active Member

    Joined:
    Mar 31, 2014
    Messages:
    454
    Likes Received:
    282
    Trophy Points:
    133
    There is a proposal for technical writing https://www.dashwhale.org/p/crdev-docwiki-201608

    It may help us better view from developer perspective.

    Why don't we vote for it? Evan and his team quite busy to code and that proposal will satisfy us as stakeholders and reduce work load for core developers.
     
    • Like Like x 1
    • Agree Agree x 1
    • Old Old x 1
  19. Solarminer

    Solarminer Well-known Member

    Joined:
    Apr 4, 2015
    Messages:
    762
    Likes Received:
    921
    Trophy Points:
    163
    We are not asking for a 12 page technical paper with drawings and flowcharts! This is a simple 10 item list with some of the important features and how they effect masternode budgets, voting, and operation. Specifically, how the budget contracts are getting implemented and how they can be stopped. Pretty simple. If this takes more than 10 minutes, I would be surprised.

    I suggested that before we ask some technical writing wizard to take money, that we instead ask a few community members to write it. There are many people that want to get involved in Dash and this is a perfect activity to get people to make flow charts, images, or just summarize some text. We already have a gigs list on www.dashnation.com/gigs where slack member participate in bounties and finish projects. That would be a much better solution to get this type of project done.
     
    • Like Like x 1
  20. itscrazybro

    itscrazybro Active Member
    Dash Support Group

    Joined:
    Apr 14, 2014
    Messages:
    137
    Likes Received:
    219
    Trophy Points:
    93
    I love what you guys are doing with your grass roots styled approach @Solarminer, however I do think that the technical writing needs to be done by someone that is experienced at doing that. If there is someone in the community that is experienced then that is great, let them hit up babygiraffe and let him know that they want to apply for the job. However if there is no one that is qualified or experienced at this then the best thing to do is out source and not wait around.
    The grass roots styled approach is great for getting the community involved (hats off to you), however there are two approaches to work getting done and the core seems to be more directive in there approach rather than waiting for someone to do it. It doesn't mean that they wouldn't be open to taking job applications though if someone did step up to the plate.
     
    • Like Like x 3
    • Agree Agree x 1
  21. rustycase

    rustycase Active Member

    Joined:
    Apr 19, 2016
    Messages:
    497
    Likes Received:
    117
    Trophy Points:
    113
    True enough ! Many new presentations with great validity have been overshadowed by distraction.
    Timing is very important to success !
    Best
    rc
     
  22. demo

    demo Well-known Member

    Joined:
    Apr 23, 2016
    Messages:
    3,114
    Likes Received:
    263
    Trophy Points:
    153
    Dash Address:
    XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
    If you are searching a 10 items list, here is a list of 7 rules of sentinel.

    https://github.com/evan82/sentinel/blob/master/docs/rules.md

    Shall we put those rules into a vote?
     
  23. Solarminer

    Solarminer Well-known Member

    Joined:
    Apr 4, 2015
    Messages:
    762
    Likes Received:
    921
    Trophy Points:
    163
    No. This isn't about the set of rules. These rules have changed a few times. This is the not the official repo so it is likely changes will be made until release.

    We are asking how this changes the budget - i.e. are there contracts? How they are voted in/out?
    The other items should also be mentioned like storing user data - are files using encryption? Space needed? Etc.
     
  24. TroyDASH

    TroyDASH Well-known Member

    Joined:
    Jul 31, 2015
    Messages:
    1,251
    Likes Received:
    794
    Trophy Points:
    183
    Well with Evan and some team members agreeing to an interview soon with Amanda, I am happy for now :) Everyone be sure to send your questions to Amanda
     
    • Like Like x 2
  25. qwizzie

    qwizzie Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,544
    Likes Received:
    726
    Trophy Points:
    183
    at least we know they can be stopped :

    https://bitcointalk.org/index.php?topic=421615.msg15659155#msg15659155
     
  26. Comodore

    Comodore Member

    Joined:
    Nov 8, 2015
    Messages:
    185
    Likes Received:
    97
    Trophy Points:
    88
    It will be on youtube on wednesday or are we going to see it live?
     
  27. David

    David Well-known Member
    Dash Support Group

    Joined:
    Jun 21, 2014
    Messages:
    618
    Likes Received:
    628
    Trophy Points:
    163
    Evan receives a payment of 67 DASH per month, the same as all the other Core Team members. Revocation of that payment (approx. $700 per month) is probably not enough to really motivate anyone, one way or the other. Eventually DASH will increase in value to such an extent that the payments will be very motivating, but at the moment they're really a token of appreciation rather than an income.
     
    • Agree Agree x 4
    • Like Like x 1
  28. Solarminer

    Solarminer Well-known Member

    Joined:
    Apr 4, 2015
    Messages:
    762
    Likes Received:
    921
    Trophy Points:
    163
    This not the same thing. The highlight is about proposal owners defunding a proposal. What about defunding a proposal because Dash is now $250 and a webpage designer is suddenly going to be raking in $100,000/mo for 12 months. Or maybe the owner dies(just saying this could happen). The proposal owner isn't going to say no or maybe they can't stop it. The network needs a way to stop a contract without the proposal owners intervention. There have been many threads discussing this.

    https://www.dash.org/forum/threads/budget-system-v2-irrevocable-multi-month-contracts.8174/
    https://www.dash.org/forum/threads/should-budgets-allow-for-irrevocable-contracts.8498/#post-90145
     
    #28 Solarminer, Aug 8, 2016
    Last edited: Aug 9, 2016
    • Agree Agree x 2
  29. Icebucket

    Icebucket Active Member

    Joined:
    Apr 11, 2014
    Messages:
    268
    Likes Received:
    129
    Trophy Points:
    103
    We need something like a monthly videochat debate to settle this kind of matters. The forum is really timeconsuming to follow and maybe 5% of people take the time to go through all of the responds :oops:
     
  30. cryptoshaman

    cryptoshaman New Member

    Joined:
    Aug 9, 2016
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I agree, the information management can be improved. Now, I don't think we need a community manager or some sort that stands in between dev's and the community, but the devs can essentially open up the feature discussion on the blockchain for all the world to see, as it is right now with the masternode proposal votes.

    It's very important that we're not trying to catch our tails as well when no information is certain.

    Looking forward to the dash detailed interview.