• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Inconsistency in Masternode - Upate to 0.12.0.58 asap !

43.6 % are behind please bump this thread + post in other slack and let's get this going please !!!
;)
 
90% of my mnodes look like this:
Note listed only errors.

Code: 
72207:2016-08-21 04:52:54 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
72208:2016-08-21 04:52:54 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
73788:2016-08-21 05:03:44 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
73789:2016-08-21 05:03:44 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
75431:2016-08-21 05:16:14 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
75432:2016-08-21 05:16:14 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
78413:2016-08-21 05:41:27 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
78414:2016-08-21 05:41:27 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
83540:2016-08-21 06:13:52 socket recv error Connection reset by peer (104)
84330:2016-08-21 06:19:44 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
84331:2016-08-21 06:19:44 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
85597:2016-08-21 06:28:42 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
85598:2016-08-21 06:28:42 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
86184:2016-08-21 06:32:20 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
86185:2016-08-21 06:32:20 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
86805:2016-08-21 06:37:06 socket recv error Connection reset by peer (104)
87040:2016-08-21 06:47:09 socket recv error Connection reset by peer (104)
87109:2016-08-21 06:48:37 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
87110:2016-08-21 06:48:37 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
87873:2016-08-21 07:00:58 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
87874:2016-08-21 07:00:58 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
88013:2016-08-21 07:04:23 socket recv error Connection reset by peer (104)
88255:2016-08-21 07:16:23 socket recv error Connection reset by peer (104)
88714:2016-08-21 07:23:19 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
88715:2016-08-21 07:23:19 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
88773:2016-08-21 07:23:24 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight
88774:2016-08-21 07:23:24 CBudgetManager::CheckAndRemove - pfinalizedBudget->IsValid - strError: Older than current blockHeight

----------------------------------
Masternode 7 - Menu v1.28 by AjM
----------------------------------
Your Version . . . . v0.12.0.58
Latest Version . . . v0.12.0.58
----------------------------------
Masternode Section
----------------------------------
1 - Mn Update
2 - Mn Getinfo
3 - Mn Status . . . . . Running
4 - Mn Stop
5 - Mn Start
6 - Mn Debug.log errors
7 - Mn Purge debug.log . . 12M
----------------------------------
Linux Section
----------------------------------
m - Memory Status
d - Disk Status
f - Firewall Status
p - Processes (Q - Exit)
u - Linux Update
r - Reboot VPS Server
----------------------------------
Enter - Exit Menu     C - Clear
----------------------------------
>>
 
in case there are any confusions
this is it:

block 523412 - 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d
 
i dont understand ? what happened ? maybe we should make instantx mandatory, maybe by making normal tx fee more expensive ???
 
So, there the nodes on the old version have forked off now which many gets mined on by zpool. I hope exchanges were already running the newest version of Dash... Noticed that poloniex has temporarily disabled deposits and withdrawals.
 
I am sending the following message to all interested parties - feel free to re-use it in your communication:

During the last hours we have experienced some inconsistency in our blockchain. This was caused by the fact that block 523412 was mined (almost) simultaneously by 2 different miners and some parts of network agreed on one version of the vote outcome, while the other agreed on another version. As a result there is another, shorter chain in the network.

In order to ensure that your wallets are on the longest chain (which is https://explorer.dash.org/chain/Dash ), please upgrade all of your wallets to version 0.12.0.58 available at our website: https://www.dash.org/downloads/
In case you can't upgrade the wallet or prefer to use lower version, we strongly recommend you to re-index, bootstrap or sync your wallet from scratch.

To verify if you are on the right chain, please check the hash for the block 523412 - it should be 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d

Our team continuously monitors the network and is ready to respond to any of your questions.

Thank you
 
Last edited:
tungfa said:
all exchanges are informed

https://explorer.dash.org/chain/Dash
is up to date
Click to expand...

Not what I see.........................................



From: https://chainz.cryptoid.info/dash/search.dws?q=523412

Dash Blockchain Explorer

up to block 523694


Search Results
block.png
Block 523412 00000000000047e6e7aebb3fa1a0565a283f05d11d9324c23252424fb6e6518d




And:
Quote from: UdjinM6 on Today at 04:34:35 AM on BTCtalk
Please check the hash for the block 523412 - should be 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d
Code:
$ dash-cli getblockhash 523412
000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d





So - according to UdjinM6 chainz is not on the correct chain

Please correct me if I'm wrong
 
corrcy
MangledBlue said:
Not what I see.........................................



From: https://chainz.cryptoid.info/dash/search.dws?q=523412

Dash Blockchain Explorer

up to block 523694


Search Results
block.png
Block 523412 00000000000047e6e7aebb3fa1a0565a283f05d11d9324c23252424fb6e6518d




And:
Quote from: UdjinM6 on Today at 04:34:35 AM on BTCtalk
Please check the hash for the block 523412 - should be 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d
Code:
$ dash-cli getblockhash 523412
000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d





So - according to UdjinM6 chainz is not on the correct chain

Please correct me if I'm wrong
Click to expand...

correct
that's why is said :
https://explorer.dash.org/chain/Dash
is on the correct .... :rolleyes:
 
sorry
am on a bus in Vietnam !
(I better be quiet now)
 
tungfa said:
sorry
am on a bus in Vietnam !
(I better be quiet now)
Click to expand...

Is it a chicken bus?
Those are fun - lol - bit scary at times, but fun none-the-less - lol
[wait - I'm thinking of Guatemala again :p]
 
kot said:
I am sending the following message to all interested parties - feel free to re-use it in your communication:

During the last hours we have experienced some inconsistency in our blockchain. This was caused by the fact that block 523412 was mined (almost) simultaneously by 2 different miners and some parts of network agreed on one version of the vote outcome, while the other agreed on another version. As a result there is another, shorter chain in the network.

In order to ensure that your wallets are on the longest chain (which is https://explorer.dash.org/chain/Dash ), please upgrade all of your wallets to version 0.12.0.58 available at our website: https://www.dash.org/downloads/
In case you can't upgrade the wallet or prefer to use lower version, we strongly recommend you to re-index, bootstrap or sync your wallet from scratch.

To verify if you are on the right chain, please check the hash for the block 523412 - it should be 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d

Our team continuously monitors the network and is ready to respond to any of your questions.

Thank you
Click to expand...

If this inconsistency (fork) was caused by simultaneous block discovery then why does the version matter?
 
If we run the risk of having blockchain splits when running several Dash versions on our network (all on the same protocol version) then we really need to address this in the future,
force every masternode / pool / miner to be on the last version or stop payments to them / reject their mined blocks.

Right now nobody was aware there was a mandatory need for masternodes / pools / miners to upgrade to 0.12.0.58 as it was never announced like that...

New procedure suggestion : give masternodes / pools / miners a week the time to upgrade towards a newer version and then just block all the older versions so we avoid below situation :

kOdZHVn.jpg
 
Last edited:
Pretty sure it's been posted for a while.....

https://www.dash.org/downloads/


Minimum Version Requirements
Users should ensure that they are using the version listed below (or newer) to ensure optimal performance and compliance with the network. Depending on usage, the minimum version requirement may not always be the latest release, although updating is recommended.

General Users
0.12.0.58

Masternode Operators
0.12.0.58

Pool Operators
0.12.0.58



Just say'n :p
 
MangledBlue said:
Pretty sure it's been posted for a while.....

https://www.dash.org/downloads/


Minimum Version Requirements
Users should ensure that they are using the version listed below (or newer) to ensure optimal performance and compliance with the network. Depending on usage, the minimum version requirement may not always be the latest release, although updating is recommended.

General Users
0.12.0.58

Masternode Operators
0.12.0.58

Pool Operators
0.12.0.58



Just say'n :p
Click to expand...

Then they should have communicated that more clearly to all of us. By the way every new version is labeled "mandatory" on dashninja, eventhough it may well not be mandatory (in case of no protocolversion changes).
All i ever heard about .058 was that people should try it if they had stability problems with their masternodes, it was never officially announced.
I think in the end it served more as a prelude to 12.1 .. prepping the way for it.
 
You must log in or register to reply here.
Back
Top