Dash Core Group announces first v19 chain halt

To Ledger users : Due to the Dash Blockchain halting Ledger Live could have a problem fetching all Dash transactions through its blockchain explorer part during synchronisation.

According the Ledger Technical team they will update Ledger Live this week. They are aware of Dash Core v19.1
I would avoid making any Ledger transactions (through Ledger Live / Dash Masternode Tool) anyways, untill its clear the Dash network has stabilized.
 
Last edited:
GrandMasterDash said:
Yes we sure did.

Beyond my disdain for HCMNs, the driving factor for me rejecting HCMNs - which I made perfectly clear - was that DCG was introducing too much risk. But everyone rejected it, said it was all going to be okay.

Well look at the fucking mess they made.

Until now, dash could proudly say, not only is it an OG but operated 24/7 without any downtime. No chain halts, ever. Thanks DCG for taking that away from dash. Hope you are proud of yourselves, though I know you will never fully admit and carry the weight of your errors. You will call it the price of progress or claim no one lost money, some pathetic attempt to ignore the reputational damage you have caused that will regurgitate for years.
Click to expand...
Point of clarification, the halt was not related to the HCMN update, it was related to the upgrade of the BLS serialisation. Also, since the voting is done across the P2P network it was never disrupted at all and mnowatch caught every single vote during the freeze. :p

DASH Proposal Analysis for 2023-05-23 08:30:01

Dash DAO voting analysis
mnowatch.org mnowatch.org
 
xkcd said:
Point of clarification, the halt was not related to the HCMN update, it was related to the upgrade of the BLS serialisation. Also, since the voting is done across the P2P network it was never disrupted at all and mnowatch caught every single vote during the freeze. :p

DASH Proposal Analysis for 2023-05-23 08:30:01

Dash DAO voting analysis
mnowatch.org mnowatch.org
Click to expand...
I said "Beyond my disdain for HCMNs", I didn't actually make any attempt to explain technical details.

The actual cause is neither here or there. DCG took on too much risk and took dash's already damaged reputation to a whole new level.
 
At least Dash is getting some news coverage again on tradingview --> https://www.tradingview.com/news/co...-fork-fail-devs-to-try-upgrade-again-june-14/

On a different topic : https://cointelegraph.com/news/ledger-sharded-wallet-keys-shared-if-subpoenaed

Pascal Gauthier, the CEO of Ledger, has confirmed that the private seed phrases of users who opt into Ledger’s controversial new Recover upgrade could, in theory, be handed over to governments if they were to be subpoenaed.

Ledger’s latest firmware update and hardware wallets, in general, have been a touchy subject over the past week.
Click to expand...

People's main concern is that private seed phrases could be extracted from Ledger hardware wallets either through Ledger employees gone rogue, through hackers or through subpoena's from governments or agencies, regardless if people opt in for Ledger Recover service or not. As the firmware update allows extraction of private seed phrases from Ledger wallets (Nano X / Stax, maybe at a later time other older Ledger wallets as well) by Ledger.

See :
 
Last edited:
qwizzie said:
It does come with a visual warning inside the wallet : unknown new rules activated (versionbit 8)
I assume this is related to the postponed v19 activation that Dash Core v19.1 brings with it.
Click to expand...

What does this warning means?
How this message is related to the postponed v19 activation?
Lets search it to the code.

github.com

Warning · Issue #1756 · dashpay/dash

which means the message?: Warning: unknown new rules activated (versionbit 1)
github.com github.com
 
Can someone explain in simple words what a chain halt means and why it is so bad for Dash reputation ?
 
Gass said:
Can someone explain in simple words what a chain halt means and why it is so bad for Dash reputation ?
Click to expand...
the blockchain which is supposed to be extremly powerful stopped working because the network hard forked into buggy software. It is a major reputational blow and it shows the weakness of how dash handles network upgrades
 
I suspect that the problem has not been resolved by passing from v19.0 to v19.1, they just swept it under the rug.
As far as I understand the code, the DCG just delayed the hard fork until june 14, hoping they will discover the bug of 19 version until that date.

github.com

backport: v19.1.0 backports by PastaPastaPasta · Pull Request #5385 · dashpay/dash

Issue being fixed or feature implemented See individual commits, most notably delayed v19 activation What was done? How Has This Been Tested? Breaking Changes This will hard fork mainnet Checklist:...
github.com github.com


ad4767b87942471cef455aec3c35fa9ad48ee2ee.jpg


Sweeping a black cat under the rug, is that ever possible?

maxresdefault.jpg
 
Last edited:
vazaki3 said:
I suspect that the problem has not been resolved by passing from v19.0 to v19.1, they just swept it under the rug.
As far as I understand the code, The DCG just delayed the hard fork until june 14, hoping they will discover the bug of 19 version until that date.

github.com

backport: v19.1.0 backports by PastaPastaPasta · Pull Request #5385 · dashpay/dash

Issue being fixed or feature implemented See individual commits, most notably delayed v19 activation What was done? How Has This Been Tested? Breaking Changes This will hard fork mainnet Checklist:...
github.com github.com


ad4767b87942471cef455aec3c35fa9ad48ee2ee.jpg


Sweeping a black cat under the rug, is that ever possible?

maxresdefault.jpg
Click to expand...
The bug that brought the blockchain to a halt has been discovered. Fixing it is a non-trivial piece of work, so the hardfork has been pushed back to give the Core devs enough time to fix it.
 
AgnewPickens said:
The bug that brought the blockchain to a halt has been discovered. Fixing it is a non-trivial piece of work, so the hardfork has been pushed back to give the Core devs enough time to fix it.
Click to expand...

So the bug has been discovered, the fix has not been discovered.
Thats not a good thing, it reminds me of my pathetic self.
I can discover too many bugs in my everyday life, but I am unable to discover their fix, or discover their fix the correct time.
 
Last edited:
TheNetworkIsBiggerThanYou said:
the blockchain which is supposed to be extremly powerful stopped working because the network hard forked into buggy software. It is a major reputational blow and it shows the weakness of how dash handles network upgrades
Click to expand...
Thank You.
And what are the negative consequences of that ? What happened with transactions been done during this stopped period ? Did some people lose money ?
 
Gass said:
Thank You.
And what are the negative consequences of that ? What happened with transactions been done during this stopped period ? Did some people lose money ?
Click to expand...

I think they didnt lose money (correct me if wrong). They were just unable to do transactions during the halt time.

But the issue is , this is the FIRST time such an incident occurs in Dash cryptocurrency, since its initial start up 9 years ago.

The High Colateral Masternodes, introduced in v19 in order to support the stupid Dash Platform, are a piece of shit. The masternodes are paying the consequences of their stupid HCMN decision, and if they insist in their HCMN idea, they will pay even more severe consequences.
 
Last edited:
While fuckup is undeniable, and changes are necessary in order to mitigate such risks in the future, I don't think talking about "major reputational blow" makes any sense. This is only emotional rethorics.
What reputation?
In the world outside, there was no impact on the markets and the problem went almost unnoticed. Ask yourself why.
And this is a problem to address, if we want Dash to be relevant in the modern crypto world.
 
kot said:
While fuckup is undeniable, and changes are necessary in order to mitigate such risks in the future, I don't think talking about "major reputational blow" makes any sense. This is only emotional rethorics.
What reputation?
In the world outside, there was no impact on the markets and the problem went almost unnoticed. Ask yourself why.
And this is a problem to address, if we want Dash to be relevant in the modern crypto world.
Click to expand...

No impact on the markets?

The stupid Evo decision about 4K High Collateral Masternodes=HCMN (stupidly named by DCG as HPMN=High Performance Masternodes) is taken, 9 Jan 2023
https://www.dashcentral.org/p/EVO-DECISION-4K-HPMN

15 Jan 2023, Dash is coin number 70
https://coinmarketcap.com/en/historical/20230115/

26 Mar 23, Dash is number 70
https://coinmarketcap.com/en/historical/20230326/

14 April 23, Announcing Dash is going to v19 in order to implement the stupid idea of HCMN.

16 April 23, Dash is coin number 76
https://coinmarketcap.com/en/historical/20230416/

23 April 23, Dash is coin 80.
https://coinmarketcap.com/en/historical/20230423/

7 May 23, Dash is coin 84
https://coinmarketcap.com/en/historical/20230507/

14 May 23, Dash is coin 88
https://coinmarketcap.com/en/historical/20230514/

22 May 23, Dash chain halts for the first time in history, due to a bug caused by the complexities that the HCMN idea adds to the Dash network. And all this in order to feed a parallel project (dashplatform) by draining the masternodes' rewards because the afforementioned project is unable to stand alone in the free market.

Lets take our popcorn, and watch the rank of Dash in coinmarketcap in the future, due to the stupid decision of the masternodes.

vazaki3 said:
I believe that the correct vote/pray (for the branch of the Dash knowledge tree we are discussing in this thread) is:
1) Dashplatform should be launched initially by the discovered individualities of mnowatch.org , one node each. <--real decentralization, incentivizes the increase of the voters
2) Let the DashPlatform launch standalone in the free market, without asking any masternode rewards. <--NO to a Dashplatform fed by MN rewards, this is statism.
3) Offer Dashplatform shares to all the masternodes, allowing them to be paid in case the Dashplatform becomes profitable in the free market. <-- unify the dash community, in contrast to the "divide and conquer" method of DCG
4) Turn the Dashplatform profitable by creating an app that will support the creation of a Dash knowledge tree. This decision tree will be replicated everywhere in the platform and people will vote/pray on it, add or delete branches of it, and comment on it (by paying the relevant platform fee). <-- governance without amanda's chief
5) Make the tree an absolute commitment for all the developers of DCG, so that no DCG development is allowed in case there is not a relevant branch of the tree that allows it. <-- accountable developers
Click to expand...
 
Last edited:
vazaki3 said:
No impact on the markets?

The stupid Evo decision about 4K High Collateral MAsternodes (stupidly named by DCG as High Performance Masternodes) is taken, 9 Jan 2023
https://www.dashcentral.org/p/EVO-DECISION-4K-HPMN

15 Jan 2023, Dash is coin number 70
https://coinmarketcap.com/en/historical/20230115/

26 Mar 23, Dash is number 70
https://coinmarketcap.com/en/historical/20230326/

14 April 23, Announcing Dash is going to v19 in order to implement the stupid idea of HCMN.

16 April 23, Dash is coin number 76
https://coinmarketcap.com/en/historical/20230416/

23 April 23, Dash is coin 80.
https://coinmarketcap.com/en/historical/20230423/

7 May 23, Dash is coin 84
https://coinmarketcap.com/en/historical/20230507/

14 May 23, Dash is coin 88
https://coinmarketcap.com/en/historical/20230514/

22 May 23, Dash chain halts for the first time in history, due to a bug caused by the complexities that the HCMN idea adds to the Dash network. And all this in order to feed a parallel project (dashplatform) by draining the masternodes' rewards because the afforementioned project is unable to stand alone in the free market.

Lets take our popcorn, and watch the rank of Dash in coinmarketcap in the future, due to the stupid decision of the masternodes.
Click to expand...
It was not 4K MNs that caused the chain halt, stop spreading misinfo, it was the BLS signatures.
 
You must log in or register to reply here.
Back
Top