Inconsistency in Masternode - Upate to 0.12.0.58 asap !

qwizzie said:
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.
Click to expand...
Yep, .58 was kind of recommended and "let's slightly prepare for 12.1 migration" type of build - it was meant to fix some bugs, add some compatibility to future changes and, huh, resolve some inconsistencies in mn list... No protocol bumping or smth. And it turned out that, probably, 0.58 did way too well to achieve more consistency... That fact alone wouldn't cause any issues imo but then there is "chance" . We still have to see if greater number of MNs on .58 will help to make winners list more robust but so far it looks like it's stabilizing imo (though it's still far from being perfect for some blocks).
 
The Future of Finance and the Continuation of an Interest Based System:
http://dashmasternode.org/the-future-of-finance/

A Masternode can be thought of as a computer that runs a dash wallet. This computer and wallet make decisions, such as locking transactions with InstantX (instant transaction protocol), coordinating mixing of coins (PrivacyProtect protocol), and voting on budget funding. Masternodes are required to have 1000 Dash collateral, a dedicated IP address, and be able to run 24 hours a day without a more than a 1 hr connection loss. Masternodes get paid 45% of the block reward on every block, this is distributed to masternodes one at a time. Typically, around 2 dash is paid to each masternode every 7 days.
 
we are NOT done yet !!!

please update !! 58 is your number !!
 
*** Earth calling Masternode owners, come in please ***

Masternode Enforcement is off currently !! Please all upgrade to latest version, so it can be activated again !!
As long as masternode enforcement is off, masternode payments will not get paid out when they are mined by pools like zpool.ca ..
who are unwilling to pay the masternode fees !!

Please upgrade your masternodes immediately to latest version 0.12.0.58 !!
Please download from official source : https://www.dash.org/downloads/

Current masternode versions % on the Dash network dd 25-aug-2016 : https://www.dashninja.pl/masternodes.html
w6QwjaR.jpg
 
I downloaded my Dash Core (0.12.0.58) after June 9th, 2016. Is everything okay with this config?
 
Last edited:
qwizzie said:
Masternode Enforcement is off currently !! Please all upgrade to latest version, so it can be activated again !!
As long as masternode enforcement is off, masternode payments will not get paid out when they are mined by pools like zpool.ca ..
Click to expand...

Is that why my MN shows as being paid 3 days ago but the dash balance did not increese?
 
Does it matter if MN is remotely hosted? I mean will the host ensure that the latest version is running?
 
Dear All,
Here is the incident root cause analysis done by @UdjinM6 (many thanks for that!)

Forked Blocks:
Hash: 00000000000047e6e7aebb3fa1a0565a283f05d11d9324c23252424fb6e6518d
Previous Block: 000000000002dc1c76bbac26dede4791e11565f8bed8030652d8823afd1443c8
Height: 523412 <-------------
Transaction Merkle Root: d106445cd5dc1bff22b37fc4fabcea78593a19aa9e93307231ab90355a5faf2a
Time: 1471728542 (2016-08-20 21:29:02)
Difficulty: 20 351.533 (Bits: 1b03385f)
Nonce: 2929999341
Payee: Xoi3AgTmuBGR2beRJsXKrLtsX8WAtZweZP <-------------

Hash: 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d
Previous Block: 000000000002dc1c76bbac26dede4791e11565f8bed8030652d8823afd1443c8
Height: 523412 <-------------
Transaction Merkle Root: 9f8f2556ad9e488596adb21fb3fc161b9b10b744a68920806b72908ea49b7b01
Time: 1471728541 (2016-08-20 21:29:01)
Difficulty: 20 351.533 (Bits: 1b03385f)
Nonce: 1110724282
Payee: XtCicpfofmiPUzDQzAmdy6Sf5zCmr3cXhi <-------------

What happened :
1. We had an inconsistency in masternode list between pre-0.12.0.58 (57?) and 0.12.0.58 nodes, _probably_ due to a bug in ipv6 MN signatures itself or due to its fixes #847 and #858 (improved in #860) /facepalm here/ or both. Anyway there must be some inconsistency to trigger (2).
2. Masternode list inconsistency was the reason why results of voting for a winning masternode could look like this: { "523412": "XtCicpfofmiPUzDQzAmdy6Sf5zCmr3cXhi:5, Xoi3AgTmuBGR2beRJsXKrLtsX8WAtZweZP:5" } Note, that neither one of masternodes received enough votes (6+) to be declared a clear winner.
3. We have a rule which says that if there are not enough votes to declare a clear winner, network should accept a block with any of nodes (which were voted for) included as valid (https://github.com/dashpay/dash/blob/master/src/masternode-payments.cpp#L519)
4. However there probably was large enough number of nodes who had vote results like { "523412": "XtCicpfofmiPUzDQzAmdy6Sf5zCmr3cXhi:4, Xoi3AgTmuBGR2beRJsXKrLtsX8WAtZweZP:6" } or { "523412": "XtCicpfofmiPUzDQzAmdy6Sf5zCmr3cXhi:6, Xoi3AgTmuBGR2beRJsXKrLtsX8WAtZweZP:4" } and they thought that there was a clear winner but it was different for each side.
5. So when two large miners solved block with different winner every node which had a clear winner recieved a block it liked, rejected another block and later continued with choosen branch.
6. Miner who solved 00000000000047e6e7aebb3fa1a0565a283f05d11d9324c23252424fb6e6518d was minnig on pre-0.12.0.58 node and like probably most of pre-0.12.0.58 nodes had a clear winner, so he also rejected another block and continued minig on his chain.
7. Nodes that had no clear winner probably accepted both blocks they received but later just continued with the longest chain.

Temporary solution:
If suggestion about masternode list inconsistency (1) above is right then having most nodes on 0.12.0.58 should reduce inconsistency i.e. it will be much more unlikely to have a situation when there are two different winners with 6+ votes for different parts of network.

Current known issues:
We can't get rid of masternode list inconsistency completely right now due to the way it's implemented.

Thoughts on future solutions:
Since masternode winner list is actually a part of the consensus, we need to implement a deterministic solution to avoid any inconsistency. This can be either some on-chain solution or off-chain protocol enhancement like another round of voting or some kind of vote synchronization among top10 masternodes.

Final thoughts:
Having most of masternodes and all (or at least all major) miners on 0.12.0.58 should be enough for now. In long-term a solution must be provided to address inconsistency issue.
 
Thanks to all the devoted humans who are right on top of discrepancies that may occur !
Much appreciation !!!
rc
 
I noticed an oddity where dashninja says I got a payment, but it shows an even 1000 balance. Only happened twice... Related?
 
We are "nearly" there but still .... these last % of old Mn's .....
PLEASE UPDATE !

qGce7ai.png
 
tungfa said:
We are "nearly" there but still .... these last % of old Mn's .....
PLEASE UPDATE !

qGce7ai.png
Click to expand...

Couple of questions :

* how much is nearly there ? 85% or 90% or higher ?
* zpool.ca is currently paying MN fees so i assumed enforcement was "on" by now .. is it still "off" ?
* why are we not using more official channels like Twitter / Facebook / Slack to reach more masternodes owners and explain to them why exactly they need to upgrade ?

I cant help but feel if we still need 6.7% or more to switch to latest version it could actually take awhile, as those 0.12.0.55 owners dont seem to be aware of the enforcement problem
(which may have resulted to not much decline in the 0.12.0.55 %)
 
Last edited:
qwizzie said:
so i assumed enforcement was "on" by now .. is it still "off" ?
Click to expand...

Code: 
$ ./dash-cli spork show
{
    "SPORK_2_INSTANTX" : 978307200,
    "SPORK_3_INSTANTX_BLOCK_FILTERING" : 0,
    "SPORK_5_MAX_VALUE" : 2000,
    "SPORK_7_MASTERNODE_SCANNING" : 978307200,
    "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : 1472238675,
    "SPORK_9_MASTERNODE_BUDGET_ENFORCEMENT" : 0,
    "SPORK_10_MASTERNODE_PAY_UPDATED_NODES" : 0,
    "SPORK_11_RESET_BUDGET" : 0,
    "SPORK_12_RECONSIDER_BLOCKS" : 0,
    "SPORK_13_ENABLE_SUPERBLOCKS" : 0
}
$ date -d @1472238675
Fri Aug 26 19:11:15 UTC 2016
 
Balych said:
Code: 
$ ./dash-cli spork show
{
    "SPORK_2_INSTANTX" : 978307200,
    "SPORK_3_INSTANTX_BLOCK_FILTERING" : 0,
    "SPORK_5_MAX_VALUE" : 2000,
    "SPORK_7_MASTERNODE_SCANNING" : 978307200,
    "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : 1472238675,
    "SPORK_9_MASTERNODE_BUDGET_ENFORCEMENT" : 0,
    "SPORK_10_MASTERNODE_PAY_UPDATED_NODES" : 0,
    "SPORK_11_RESET_BUDGET" : 0,
    "SPORK_12_RECONSIDER_BLOCKS" : 0,
    "SPORK_13_ENABLE_SUPERBLOCKS" : 0
}
$ date -d @1472238675
Fri Aug 26 19:11:15 UTC 2016
Click to expand...


okay, so this is not about enforcement anymore but its more about the masternode selection winners ? the higher % on 0.12.0.58
the less chance on accidental split offs due to multiple winners ?

Also crowning site needs updating i think with regards to enforcement, it still shows :
Payment Enforcement Status: 'On' since 2015-08-22-12:00
Click to expand...
 
Last edited:
qwizzie said:
Couple of questions :

* how much is nearly there ? 85% or 90% or higher ?
* why are we not using more official channels like Twitter / Facebook / Slack to reach more masternodes owners and explain to them why exactly they need to upgrade ?

I cant help but feel if we still need 6.7% or more to switch to latest version it could actually take awhile, as those 0.12.0.55 owners dont seem to be aware of the enforcement problem
(which may have resulted to not much decline in the 0.12.0.55 %)
Click to expand...

- we are using all channels !
- 85-90% is nearly 100% - correct ?
(and better than the initial 67 or whatever it was)

we can survive without the last couple of % but it would be 'nice' to finally get these old nodes updated
so i keep pushing this a bit longer :rolleyes:
 
I noticed that the masternode payment enforcement number changed. Does that mean that enforcement is back on?

I thought a screen shot here, but I'm having some serious upload problems. Anyway:

0.12.0.58: 83.8%
0.12.0.59: 0.5%
 
yes enforcement is back on
59 ? might be a testrun by some devs :rolleyes:
 
You must log in or register to reply here.
Back
Top