12.1 Announcement / Finalized Date / Project Update

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Happy New Year!

It’s been awhile since I’ve done a full announcement about the status of development, both of the core project and Evolution. We have had a lot of positive news in recent months that we’ve been working on, and I thought now would be a good time to update everybody on our progress, which has been quite good. In fact, we are progressing on many fronts simultaneously.

VERSION TWELVE POINT ONE / SENTINEL RELEASE

Launching a new software release on the network requires that all budget proposals be re-submitted into the system. Due to the timing of superblocks, we have a short window to launch, near the beginning of the month. In order to ensure we launch the most stable possible version of the software without interfering with the budget system, we would like to hold off until early February to launch 12.1. Launch date: February 5th, 2017.

CORE DEVELOPMENT

The first area of progress is Dash Core. In addition to running the network at present, Dash Core also serves as the backbone of the Evolution engine. We have done a great deal of work on Sentinel, our large-scale decentralized programmable database solution, which is going to allow us to move radically faster than any other organization in cryptocurrency. Among other things, Sentinel will allow us to push updates to Dash Core much more quickly and easily.

Sentinel can also be re-geared and deployed to operate digital companies that have a built-in workforce, infrastructure to deploy again, and as an engine for storage and retrieval of information. This is the concept we’re working on, which will allow companies to run on the Dash Network and compete with centralized companies that refuse to work with Dash. It’s a simple divide and conquest model.

We have recently moved a good deal of our funding into paying some new hires, who have now integrated into our team and have pushed through many new versions of the software. Among other things, they have fixed various issues with the stability of the daemon, the syncing of governance objects, and the workability of the new Sentinel system. Sentinel uses a complex set of rules and conditions for validation of objects and maintaining the consensus of the network.

STRATEGIC EXECUTION

Ryan Taylor, Dash’s CFO, has coordinated a deal with Arizona State University’s SkySong incubator, allowing us access to their top tier facility in Tempe, Arizona. There are 29 fast-growing, innovative startups sharing this location, and we look forward to talking with many of them. We also look forward to hiring exceptional talent from the University.







NETWORK UPGRADE

Feb. 5 is the date of the launch of our new platform. Enforcement will be turned off for this network upgrade, meaning nodes running the old version of the Dash software (12.0) will quickly stop being paid (contingent on miners upgrading). That means masternode rewards will be shared amongst a much smaller pool of upgraded nodes. This should provide a strong incentive to upgrade quickly; it will be very lucrative to upgrade your nodes as quickly as possible.

EVOLUTION UPDATE

Lead evolution developer Andy Freer has been locked away producing huge amounts of documentation for the various concepts of Evolution. This comes after months of conversations between Andy and myself about how each component of Evolution works, then reimagining it and improving the components and designs systematically. Since the original research phase, documentation, specifications, plans and diagrams have been being drafted, growing into a collection of documents that will be put into a wiki with full documentation for Evolution’s end-to-end design and implementation.

EVOLUTION RESEARCH

In January 2016 we released an early Evolution prototype based on Electrum which enabled basic functions such as registering a username and paying friends by name.

The prototype was pretty basic, with user interaction limited to just paying a few friends and user data stored on a dev server, but at least it proved the concept.

What we set out to do then was to design and prototype all the key technologies that would make these functions work in a purely P2P way, with data secured on the Dash blockchain and accessible from anywhere on any device, with integrated SPV based security and no centralized intermediary services required, and using the most common and censorship resistant protocol available - HTTP(S)

What we have designed and prototyped in various parts is a system that will let people signup to Dash, connect with friends, connect with merchants and buy products and services online with options to refund or pay recurring subscriptions, using just a web browser, without going through any intermediary service or having to integrate their own full node. It’s also a system that lets websites and apps become Dash enabled as easily as signing up for an API key and then cut and pasting a few lines of code into their business application that pops up a payment form and bills the user automatically, with all customers and payments visible to the merchant in DashDrive.

What this enables is the first usable digital cash built for the digital economy, because rather than having to integrate an esoteric P2P system into existing digital applications and services using complex infrastructure and interoperation or a centralized intermediary, Dash Evolution can be accessed by an HTTPS API that works more like a decentralized cloud, using familiar data structures such as Users, Accounts and Orders instead of transactions, blocks and crypto addresses, secures user information like a cloud service, but behind the API functions as a purely P2p, decentralized service. We believe this will be the key to gaining mainstream traction for users and businesses on P2P cryptocurrencies, i.e. they won’t even know it’s a P2P cryptocurrency they are using, because it’s as quick, familiar and easy to use / integrate as any existing payment systems used in the mainstream digital economy, all of which are API service based.

EVOLUTION FRONTEND

The 3 main areas of frontend design and development have been to design a secure, SPV based Web Wallet, merchant tools to enable drag-and-drop checkout on a website, and an SDK that connects web clients to DAPI.

The Web Wallet has taken the form of an SPA (single page application) that web users can download as a single HTML page and hashcheck to use securely from their desktop, that enables users to login and manage their accounts, contacts and merchant relationships, including an integrated marketplace for products and services. Users hold their account password and account HD seed on the client side, and on the network side, all of their account meta data is encrypted and stored on the network. After designing the UI / UX in July, ongoing work has been to develop the web wallet platform and soon work is starting to port the work to Android and iOS Evolution wallets. A revamped Dash.org is also being designed (following from the upcoming launch of dash.org v2) to provide a signup to Evolution call-to-action on the homepage and a download or hosted link to the Web Wallet code (and mobile versions).

The merchant tools have taken the form of code that can be cut and pasted into their web page and server to instantly enable Dash payments by user’s name against products the merchant is listing, including a Dash Checkout modal that can handle the payment automatically on the client side. The merchant can also list the products directly in DashDrive to enable Users to make one-time payments, moderated refunds or recurring auto-payments within any DAPI enabled client (such as the Web Wallet) and access full CRM information for their sales / product listings in DashDrive via DAPI.

The SDK (Dash.js) is a single library that web clients and servers include to easily access all wallet and merchant functions using their user accounts or API keys for merchants. This has been based initially on BitPay’s BitCore API and ongoing work has included a variable SPV implementation for the library which enables clients to specify the level of security they wish to balance this between performance and amount of data that needs to be downloaded.

EVOLUTION BACKEND

Evolution Backend Development has leveraged two strategies this year. The first has been to port BitPay’s Bitcore Platform to Dash including merging Bitcore Node to DashCore 12.1 for native API support.

The second ongoing strategy is to leverage this platform to fulfill long-term Evolution requirements while filling more immediate needs. Through this approach we’re now positioned to leverage the entire BitPay ecosystem, most notably Copay (https://copay.io) and the new Insight API. We anticipate having a Dash variant of the Copay wallet available on testnet by the end of January 2017.

In support of the v0.12.1.x Dash Core release, we’ve integrated the Governance Object model into the Bitcore platform (e.g. Budget Proposals). This integration has led to the development of a client-side budget generator as well as an extension of Insight API which returns active budget proposal objects. Moving forward this type of close integration between Bitcore and the Governance Object system will be a huge asset and a foundational piece for continued innovation in v0.12.2.x and beyond.

Work has also included with ProtonMail and Sean Ryan (Node40.com) has also delivered a Payment Processing API which is capable of connecting directly to the Bitcore Wallet Service. A compatible WooCommerce plugin has been developed and is intended to act as both a Proof of Concept for this API as well as a Prototype for future eCommerce integrations. More information on this plugin and related API will be released in early January 2017.

EVOLUTION CORE

Evolution Core work has been focused on first providing a basis to the new system in the form of Sentinel and improving DashCore to be implementation-agnostic to governance functions and objects.

Additional work has been the design / prototype of several key technologies needed at the core level, ranging from the RPC/ZMQ interface to DAPI, a generic Object system governed by a shared Schema protocol that enables Users to secure Object state transitions on the Dash Blockchain and store Object Data sharded across Masternodes (DashDrive). This work has also included upgrading the existing Masternode design to retain proposals, votes, and rewards in DashDrive to provide blockchain consensus. After 12.1 release, work will focus on implementing these designs in conjunction with the frontend and backend work.

Thanks to everyone involved!
 

fible1

Well-known Member
Dash Core Team
Masternode Owner/Operator
May 11, 2014
710
722
163
@eduffield Two quick questions:

1. Do you have an updated timeline of Evolution delivery past V12.1?
2. Will any of these new wallets, including the one based off copay, have native Trezor support for masternodes? Or how will this continue to be handled in the future as it seems Electrum-Dash is abandoned?

Thank you,
Pablo.
 

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,335
571
283
Finland
Great devteam!

I just hope we get a detailed instructions to setup new masternode / sentinel system before 12.1 launch.

EDIT: and what is new recommended masternode server specs, memory, cpu, hd space and monthly bandwidth?
 
Last edited:
  • Like
Reactions: pille and bhkien

MasternodeX

New Member
Jan 2, 2017
3
0
1
36
Curious if ill be able to continue the raspberry pi use of a new masternode, and as above, wonder about the requirements for the new masternode protocols ? ie just download a built dashd/dash-cli and copy paste it in, or more things needed (space, processing power, ram)
 

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,891
6,719
1,283
@eduffield Two quick questions:

1. Do you have an updated timeline of Evolution delivery past V12.1?
2. Will any of these new wallets, including the one based off copay, have native Trezor support for masternodes? Or how will this continue to be handled in the future as it seems Electrum-Dash is abandoned?

Thank you,
Pablo.
as far as i know
nothing is abondened - they are all based / waiting on 12.1
with that launched electrum is back on track and so will be trezor with mns and the rest
@flare can propably clarify this
 
  • Like
Reactions: daf and Raico

fible1

Well-known Member
Dash Core Team
Masternode Owner/Operator
May 11, 2014
710
722
163
@tungfa Ok, I'm not one to split hairs, so lets say that electrum is "un-maintained". Still, the gist of my question goes to how Trezor will be integrated into the Evolution ecosystem.

@eduffield look forward to the info.

Pablo.
 
  • Like
Reactions: halso and tungfa

daf

Active Member
Oct 18, 2015
176
133
103
Very exciting announcement! Thanks to anyone involved for their hard work.
 
  • Like
Reactions: bhkien

GrandMasterDash

Well-known Member
Masternode Owner/Operator
Jul 12, 2015
2,735
973
183
And thus the long term failure is clear to see.. governance... who's governing?

Feb. 5 is the date of the launch of our new platform. Enforcement will be turned off for this network upgrade, meaning nodes running the old version of the Dash software (12.0) will quickly stop being paid (contingent on miners upgrading). That means masternode rewards will be shared amongst a much smaller pool of upgraded nodes. This should provide a strong incentive to upgrade quickly; it will be very lucrative to upgrade your nodes as quickly as possible.​

That's right folks, MNOs aren't in control, they are being coerced - oh sorry "incentivized" - into running a binary without a single attempt to using the voting system that dash holds in high esteem. Tell us, what are the key applications of blockchain tech? - ah yes, supply chain... but we'll ignore that when it comes to version control, right? Unable, unwilling, to eat it's own dog food.

This is absolute proof that core see themselves as The New Geek Bankers and totally unwilling to hand over source and binary version control to MNOs or other independent body (let alone the voice of end-users). Why people hate bankers? - because they changed the rules.. who's changing the rules now huh?

Let me guess, when The New Geek Bankers change the rules, the little people (MNOs and end-users) must blindly accept those changes or fork? How about when core want to do something against the will of the people, that they are the ones that have to initiate the fork? How about the code supply chain being audited and approved, that end-users can maintain faith in dash's security and stability?

The day will come when the most important blockchains will require solid code governance that uses blockchain tech itself to govern... that's never going to happen with dash, and thus dash will not survive in the long term.
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Feb. 5 is the date of the launch of our new platform. Enforcement will be turned off for this network upgrade, meaning nodes running the old version of the Dash software (12.0) will quickly stop being paid (contingent on miners upgrading). That means masternode rewards will be shared amongst a much smaller pool of upgraded nodes. This should provide a strong incentive to upgrade quickly; it will be very lucrative to upgrade your nodes as quickly as possible.​
why dont you add a question into the budget, asking whether the masternodes want to accept this update or not?

Add it like like this:

Do you want the Feb. 5 update? (yes/no)
In case of a yes, your 5 dash will be reinbursed.
In case of a no, you will lose your 5 dash but you will be the winner.

So in case of a no, the field will be open for a more specific proposal to follow, that will solve the problem.

The day will come when the most important blockchains will require solid code governance that uses blockchain tech itself to govern... that's never going to happen with dash, and thus dash will not survive in the long term.
It will never going to happen, until you or any other Dash community member makes it to happen.
 
Last edited:

GrandMasterDash

Well-known Member
Masternode Owner/Operator
Jul 12, 2015
2,735
973
183
why dont you add a question into the budget, asking whether the masternodes want to accept the update or not?

Add like like this:
Do you want the update? (yes/no)
In case of a yes, your 5 dash will be reinbursed.
Well, that's entirely possible and I fully expect it to be accepted.. but that's not the point. Crypto is offering a golden opportunity to end-users that the governance of it's coin can be handled and trusted in a fair way. And we're not just talking about one big update but rather all the updates that have gone into this. For example, the cost of Instant Send was reduced 10x... imo a good move, but it wasn't widely and transparently accepted.. other than my initial request for it to happen.
 

GrandMasterDash

Well-known Member
Masternode Owner/Operator
Jul 12, 2015
2,735
973
183
Bwah ha ha -- there are forces out there that are quite terrified of Dash. We're winning!
I have no doubt dash will see success in the short-medium term, but long term, not a chance, it's way too insular.
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Well, that's entirely possible and I fully expect it to be accepted.. but that's not the point. Crypto is offering a golden opportunity to end-users that the governance of it's coin can be handled and trusted in a fair way. And we're not just talking about one big update but rather all the updates that have gone into this. For example, the cost of Instant Send was reduced 10x... imo a good move, but it wasn't widely and transparently accepted.. other than my initial request for it to happen.
In that case why dont you follow this procedure in order to define a bounty for whoever developer manages to code for Dash something similar to what you have just described?

1) Do you want the masternode software updates to be governed by a blockchain? (yes/no) (in case of a yes result, the 5 dash proposal fee is reimbursed)
2) In case of a yes in the proposal 1, do you agree to pay 50 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
3) In case of a yes in the proposal 2, do you agree to pay another 100 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
4) In case of a yes in the proposal 3, do you agree to pay another 200 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
e.t.c.

With this method, an amount of money will be allocated and given to the people that will finish the job. If nobody is interested to code it, then more money can be allocated, until the motivation is strong enough for the competent developers to start coding it.

If there is a no at the first proposal, this means that the masternodes dont like to decide about the updates, and that they blindly believe and trust to whatever the core team authority does.
 
Last edited:

GrandMasterDash

Well-known Member
Masternode Owner/Operator
Jul 12, 2015
2,735
973
183
In that case why dont you follow this procedure in order to define a bounty for whoever developer manages to code for Dash something similar to what you have just described?

1) Do you want the masternode software updates to be governed by a blockchain? (yes/no) (in case of a yes result, the 5 dash proposal fee is reimbursed)
2) In case of a yes in the proposal 1, do you agree to pay 50 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
3) In case of a yes in the proposal 2, do you agree to pay another 100 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
4) In case of a yes in the proposal 3, do you agree to pay another 200 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
e.t.c.

With this method, an amount of money will be allocated and given to the people that will finish the job. If nobody is interested to code it, then more money can be allocated, until the motivation is strong enough for the competent developers to start coding it.

If there is a no at the first proposal, this means that the masternodes dont like to decide about the updates, and that they blindly believe and trust to whatever the core team authority does.
Except that this code governance is just one of several core beliefs in the attributes of a long term stable crypto.. privacy-first is one of the other requirements and I'm currently making enquiring to analyse and uncover MNOs... well, they did vote for transparency-first...
 

Geert

Member
Aug 26, 2015
46
21
48
I have no doubt dash will see success in the short-medium term, but long term, not a chance, it's way too insular.
Dash is a complex, innovative software product in early stage development. The roadmap for that development cannot be formulated democratically by the potentially thousands of people who own masternodes. That would be a disaster.
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Except that this code governance is just one of several core beliefs in the attributes of a long term stable crypto.. privacy-first is one of the other requirements and I'm currently making enquiring to analyse and uncover MNOs... well, they did vote for transparency-first...
Ok, your first core belief was denied by the masternodes.

Shouldnt you try to ask the masternodes about your second core belief?
They may accept this second one, and in that case a bounty to the developer who will code it will be defined. And if it is a good bounty then, who knows, maybe a competent developer will decide and code it.

And as long as the code is opensource and everyone can use it or fork it, you will be one step closer to the long term stable crypto.
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
The roadmap for that development cannot be formulated democratically by the potentially thousands of people who own masternodes.
Of course it can be formulated.
 
Last edited:

Geert

Member
Aug 26, 2015
46
21
48
Of course it can be formulated.
Let's assume for the moment that you are intelligent enough, knowledgeable enough, and wise enough to have good ideas about where Dash should go from here. What about all the other masternode owners? They have a vote too, and they might be swayed by people who are stupid or malevolent.
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Let's assume for the moment that you are intelligent enough, knowledgeable enough, and wise enough to have good ideas about where Dash should go from here. What about all the other masternode owners? They have a vote too, and they might be swayed by people who are stupid or malevolent.
The masternodes cannot be more than 10000 and the people who operate the masternodes may be even less than 10000.

I doubt if there are more than 535 operators of masternodes currently.
535 operate the US congress, and the roadmap of the US is much more complicated than Dash.

If the masternodes operators are all stupids or malevolent and they dont know what their interest is, you should not have created the budget system in the very first place.
 
Last edited:

GrandMasterDash

Well-known Member
Masternode Owner/Operator
Jul 12, 2015
2,735
973
183
Dash is a complex, innovative software product in early stage development. The roadmap for that development cannot be formulated democratically by the potentially thousands of people who own masternodes. That would be a disaster.
True. And I'm not just knocking dash, there is yet to be a crypto with all the essential qualities... but we are seeing individual cryptos emerge that are embracing such things.. dash for issuing grants, monero for privacy, tezos for the governance, synereo (and others) for formal verification.. and so on. Will dash embrace such ideas? - not impossible but based on previous experience, very unlikely. Is it technically possible that a single crypto can cover all these key bases? - yes, I believe so.
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
No Improvement in Congress Approval, at 13%

http://www.gallup.com/poll/189848/no-improvement-congress-approval.aspx

I rest my case :)
Anyway, what I wanted to say is that the masternodes should start mimic the parliement, they should vote laws, and the core team and the developers should respect these laws when they do their updates. And in case their code is against the laws then they should be judged by an independant Dash jury and they should pay dash as a penalty. The more severe the crime is, the more the dash paid.

This is how the roadmap of a community can be formulated democratically, and this is how the software updates can be controlled.
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
True. And I'm not just knocking dash, there is yet to be a crypto with all the essential qualities... but we are seeing individual cryptos emerge that are embracing such things.. dash for issuing grants, monero for privacy, trezos for the governance, synereo (and others) for formal verification.. and so on. Will dash embrace such ideas? - not impossible but based on previous experience, very unlikely. Is it technically possible that a single crypto can cover all these key bases? - yes, I believe so.

So you think that the code is already written, and the only thing needed is someone to start puting all of it together? In that case why dont you ask the masternodes if they want someone to do this assemblage. And if the masternodes desire the assemblage, then a bounty can be defined in order to incentivize potential developers.

I dont think that the code is already written. So someone has to ask the masternodes for each one core value separately. In order to get the masternodes' initial approval and then start the negotiations about the bounty given to the one who will succesfully code the core value.

You asked the masternodes about privacy, and the masternodes deny it. But this is not the end of the world. Au contraire, asking the maternodes about their core values is only the beginning of the journey. Someone has to ask the masternodes for other values as well. Someone may also ask the masternods about privacy, once again. Asking the masternodes, and asking them again, this is the road.
 
Last edited: