Dash Core v0.14 on Mainnet

Status
Not open for further replies.

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,729
1,283
https://blog.dash.org/dash-core-v0-14-on-mainnet-ef2d0e49e29a





Dash Core Group is pleased to share that Dash Core v0.14.0 binaries are released and ready for deployment on mainnet by node operators.

This software release focuses on improving the user experience while increasing network security. Highlights of this release include:

Long-Living Masternode Quorums (“LLMQs”), which will increase scalability through improved consensus and expand the universe of potential use cases of the network;

⛓ LLMQ-Based ChainLocks, which leverage LLMQs to improve network security by mitigating 51% mining attacks; and

⏩♂ LLMQ-Based InstantSend, using LLMQs to not only improve network scalability, but in combination with ChainLocks will allow for secure, real-time payments.

This release represents a major step towards making Dash the most user-friendly blockchain based payment system in the world. Long wait times make it hard for today’s crypto networks to truly compete with traditional payment methods like credit and debit cards. For a user trying to purchase groceries, for example, waiting more than a minute for a transaction to process simply isn’t acceptable. Beyond this, once a payment is received, users accustomed to traditional payment methods expect to be able to re-spend that received money immediately.

Other networks that have managed to reduce wait times have typically done so at the cost of network security by overly centralizing the authority over which transactions go through and which don’t, creating greater opportunity for manipulation and attack. Dash, on the other hand, will provide users with the real-time payments they expect at an extremely high level of security through the second layer masternode network. Someone who wanted to try to manipulate or attack the system would need to spend hundreds of millions in USD to do so.

Read more about these features in the "); background-size: 1px 1px; background-position: 0px calc(1em + 1px);">Dash Core v0.14.0 Product Brief and download the binaries from the "); background-size: 1px 1px; background-position: 0px calc(1em + 1px);">Dash Core Group website.

Network Operators: Rollout Procedure and Upgrade Instructions
We ask partners, network operators, and other stakeholders to please begin upgrading as soon as possible.

Rollout Procedure
Below please find a diagram explaining the currently planned rollout procedure for Dash Core v0.14. Please note that this may change as we proceed and learn more — if this occurs, communications will be distributed to alert the community.



Current Dash Core v0.14 Rollout Plan — May 21, 2019
The next 4032-block window will begin sometime this coming weekend, at block 1,076,544.

Upgrade Instructions
Please find instructions on how to upgrade here:
https://docs.dash.org/en/stable/developers/dip8-upgrade.html.
The procedure is fairly straightforward this time. Masternode owners do not need to wait for their next payment before upgrading. As always if you have any questions or need assistance with the upgrade, please contact the
https://support.dash.org/en/support/home
 

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Looks like this will also require a sentinel update, something that is not mentioned i think in the installation notes ?

cd .dashcore
cd sentinel
git pull

I assume it needs a sentinel update because when i did a git pull it showed 4 changed files
and a number of additions and deletions, suggesting to me Sentinel indeed updated itself.
 
Last edited:

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,765
1,005
1,183
Very impressed with the CPU usage. I've seen a few spikes but overall the CPU usage is really low!

Also, after updating sentinel, you can check the version like so:

Code:
grep sentinel_version lib/config.py
 
  • Like
Reactions: qwizzie

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Why is dash-qt missing from the bin directory?
the dash-qt.exe is both in the windows 32 & 64 bit version ZIP file. Maybe your anti-virus scanner deleted the
dash-qt.exe during extraction ? My anti-virus scanner bitched a bit about the exe file (it bitch about any exe file), but i could surpress the warning and extract it.

I downloaded it from official site (https://www.dash.org/downloads/)
 
Last edited:

strophy

Administrator
Dash Core Team
Moderator
Dash Support Group
Feb 13, 2016
723
426
133
  • Like
Reactions: qwizzie

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,284
1,283
Great and smooth update guys. Gratz, Indeed CPU usage is very low. Top!
 

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
The 0.14 DIPs haven't enabled yet, so this doesn't really mean anything...

How's RAM usage? Bandwidth? Frankly, those two are more important than CPU...
I think the activation of the spork that handles LLMQ InstandSend (spork 20), could have the most impact.
Will be interesting to see what happens when that particular one activates.
 

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Last edited:

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,729
1,283
"Dash Core v0.14 Rollout Plan" image in that blog is not loading for me, i hope you dont need to be signed in to see it.
only seems to work on a not private browser
(does not work for me ether ; ) pinged liz already)
check this:
 
  • Like
Reactions: qwizzie

masternube

Member
Nov 9, 2017
81
14
48
How can I see if a specific block is voting for activation?
If I look at Blockchair, all blocks only seem to be voting for BIP9.
 

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Looks like the first window of 4032 blocks did not achieve the 80% of miners signalling support, which means we are now entering the second window of 4032 blocks.
Hopefully DIP8 will lock-in during this second window, which will end with block 1,084,608
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Showing "Unlisted (0%) in the color red on Dashninja for all my masternodes almost gave me a heartattack. I'm not a fan of this specific status indication / active score.
I like the "Valid" or "Active" (100%) indication in color green much more.

Link : https://www.dashninja.pl/deterministic-masternodes.html

Sample of some random active masternodes on first page :

 
Last edited:

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,906
6,729
1,283
Showing "Unlisted (0%) in the color red on Dashninja for all my masternodes almost gave me a heartattack. I'm not a fan of this specific status indication / active score.
I like the "Valid" or "Active" (100%) indication in color green much more.

Link : https://www.dashninja.pl/deterministic-masternodes.html

Sample of some random active masternodes on first page :
dashninja just updated to 14.0.1
there must have gone something wrong , not loading propper for me , pinged elberth already

Edit:
Fixed Now
 
Last edited:
  • Like
Reactions: qwizzie

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Looks like the conditions for activating spork 17 (QUORUM_DKG_ENABLED) are met :

DKG Spork Activation Criteria

Once at least 50% of masternode owners have updated to Dash Core v0.14.0.1 and 80% of masternode owners have updated to at least the Dash Core v0.14.0.0 version,
we plan to activate the DKG spork. At that time, LLMQs will begin forming and PoSe scoring will occur.



v0.14.0.1 > 50%
v0.14.0.1 + v0.14.0 > 80%
 
Last edited:
  • Like
Reactions: JGCMiner

masternube

Member
Nov 9, 2017
81
14
48
Isn't 80% miner signaling also a condition for the sprok?

And to answer my own question from earlier, I'm guessing that the signaling can be seen as version 0x20000010 instead of 0x20000000.
 

qwizzie

Well-known Member
Aug 6, 2014
1,602
754
183
Isn't 80% miner signaling also a condition for the sprok?
I suspect this specific spork (QUORUM_DKG_ENABLED) is more depending on a broad masternodes support and less on a broad miners support.
While a spork like ChainLocks not only need broad masternodes support for activation, but also need broad miners support to have the enforcement of it switched on.

Please have someone correct me, if my assumption is incorrect or incomplete and we do need to wait for DIP8 activation for this DKG spork to activate.

The way i see it :

* Spork 17 (DKG) can now be manually activated
* After short time Spork 19 (ChainLocks) can be manually activated
* Once DIP8 activates in a few weeks, Chainlocks gets automatically enforced
* After ChainLocks enforcement, Spork 20 (LLMQ-based InstandSend) can be manually activated and monitored for impact

Edit : Spork 17 has been activated : http://178.254.23.111/~pub/Dash/Dash_Info.html (SPORKS)



Which means LLMQs will begin forming and PoSe scoring will occur.
 
Last edited:
Status
Not open for further replies.