[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[jk9694]

Seems that my fork and the maternode payments fork is at least the same

Last half our block (18.30 GMT+1)

getblockhash 261725

77bbad43c4ff0232dbd8eb324b332f0331863abc3cd2daa9b86a0ee2baa78ca7

You are on the wrong fork, current block at 13:04 EST is 261716 with the hash of bff7fa213177685cc9fb8da1e5160ae2ce6656208492c065d14a82d9e16ef3bb

[1714030839]

1714030839

[Haunebu81]

Hey everyone,

Here is how to make sure you are on the right chain. Please make sure you have the latest source.

1. Delete everything in your data folder except for:
     darknet.conf
     wallet.dat
     masternode.conf

2. Get the latest chain from here: https://www.dropbox.com/s/k6dax584softm3t/blocks.zip?dl=0

3. Place the chain in your darknet data folder, the zip contains 2 folders.

4. In darknet.conf, have only one node defined.
     connect=coin-server.com

5. Start your wallet and allow it to sync

6. After you have completed the sync, you can add your other nodes back to the darknet.conf file.

Thanks

That seemed to work. But after the wallet updated and resync'd, I entered the "masternode start-missing" command, and the wallet keeps freezing up on me.

Now many masternodes do you have?

100

[berron]

Seems that my fork and the maternode payments fork is at least the same

Last half our block (18.30 GMT+1)

getblockhash 261725

77bbad43c4ff0232dbd8eb324b332f0331863abc3cd2daa9b86a0ee2baa78ca7

You are on the wrong fork, current block at 13:04 EST is 261716 with the hash of bff7fa213177685cc9fb8da1e5160ae2ce6656208492c065d14a82d9e16ef3bb

Seems that I'm on the same fork of all my MN's and of http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

Wrong and rigth fork? For the moment I think there is only a lot of forks. 261716 to 261769 in 26 min??? Well, maybe DN_masternode_payments is also in the wrong fork.

[Balych]

Seems that my fork and the maternode payments fork is at least the same

Last half our block (18.30 GMT+1)

getblockhash 261725

77bbad43c4ff0232dbd8eb324b332f0331863abc3cd2daa9b86a0ee2baa78ca7

You are on the wrong fork, current block at 13:04 EST is 261716 with the hash of bff7fa213177685cc9fb8da1e5160ae2ce6656208492c065d14a82d9e16ef3bb

May be its you on wrong fork. Who decide it? I suppose its network, but looks like it cant find consensus. Anyway this http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html fork have ~355 2.0.2 version masternodes (about 1/3 nodes as before POS) and my wallet show same, have 33 peers connected (all 2.0.2 version too) and no crazy stakes.

[mxnsch]

Hey everyone,

Here is how to make sure you are on the right chain. Please make sure you have the latest source.

1. Delete everything in your data folder except for:
     darknet.conf
     wallet.dat
     masternode.conf

2. Get the latest chain from here: https://www.dropbox.com/s/k6dax584softm3t/blocks.zip?dl=0

3. Place the chain in your darknet data folder, the zip contains 2 folders.

4. In darknet.conf, have only one node defined.
     connect=coin-server.com

5. Start your wallet and allow it to sync

6. After you have completed the sync, you can add your other nodes back to the darknet.conf file.

Thanks

I second this, it's essential you remove all addnode=lines and replace it with a single

Code:

connect=coin-server.com

addnode => add a node to the list of nodes to connect, also connect to other nodes that are discovered
connect => only connect to THIS node.

I am vouching for jk9694 and for the cautious - his systems have been part of the DNET network for a long time.

[Haunebu81]

Is this right:


14:04:43 getblockhash 261825


14:04:43 901eddf161e39c42e675be97c4a723e7c1a3e49d7c8a6370dafb13b474bbd527


?

[Rageee]

Using only the line connect=coin-server.com I am not able to sync at all.

[borris123]

dont see how we can be on 2 different chains if the older nodes are no longer allowed to be connected and everyone downloaded the chain posted?? unless someone has downloaded the new wallet but left it on another chain???

just tried fresh wallet with jk9694 download and only coinserver as a node, it is on and moving along 261847 stuck

done fresh one using s3v3nh4cks zip for controller and nodes suggested by that, it sticks on 261687

masternode is on 261881 and is moving along this was done with s3v3nh4cks zip and nodes as well

[B1tUnl0ck3r]

I tried to reinstall again the wallet... and this time it stopped to sync at 261712. Isn't all point of blockage linked to different forks starting? like in block 260832? because if the wallet refuse to sync further is maybe because there is a fork and it doesn't know which chain to follow  

we definitely have difficulties achieving a concensus and worst for the wallet to maintain it and not always fork. Could it be bad actors trying to undermining our DNET with malicious acts? anyway the code needs to be more robust. Do the others POS coins have this same problem?

edit: I got an interesting event. When syncronizing the masternode (after the block sync) my second node forked itself from the first. during the syncing it was unable to get update from the first one chain and I think created is own chain. I hope it helps.

[jakiman]

Okay. Just woke up.

I just noticed that MN Info page now shows the invaluable block hash!
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

And I can confirm that my controller wallet & my MN's matched the blockhash of the MN page.

getblockhash 262000
2944973b1001b91f6766d4a672b226427460d06741eefe1f32c21d175608e272

[berron]

Okay. Just woke up.

I just noticed that MN Info page now shows the invaluable block hash!
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

And I can confirm that my controller wallet & my MN's matched the blockhash of the MN page.

getblockhash 262000
2944973b1001b91f6766d4a672b226427460d06741eefe1f32c21d175608e272

which nodes in conf file, jakiman?

[B1tUnl0ck3r]

Okay. Just woke up.

I just noticed that MN Info page now shows the invaluable block hash!
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

And I can confirm that my controller wallet & my MN's matched the blockhash of the MN page.

getblockhash 262000
2944973b1001b91f6766d4a672b226427460d06741eefe1f32c21d175608e272

Good morning/afternoon


lastest block from my side on the chain...  

getblockhash 261886

04873e35bd4db6a014c20cc48298c654537bfd3e9258f32220d73bfe97c1a028


edit: wrong chain on my side I stack all blocks... 

[jakiman]

Good morning/afternoon

lastest block from my side on the chain... 

getblockhash 261886
04873e35bd4db6a014c20cc48298c654537bfd3e9258f32220d73bfe97c1a028

Hmm. Doesn't match mine so that would be different to mine & the MN info page. Are you receiving MN payments? (I am)

[Haunebu81]

Mine is:


getblockhash 261886

b534fd9c8ef8314177f8bf7afeef4ced0fd12dd3588acf914bc90217cc54eae2


I'm minting AND receiving MN rewards. Is that normal?

[jakiman]

Mine is:

getblockhash 261886
b534fd9c8ef8314177f8bf7afeef4ced0fd12dd3588acf914bc90217cc54eae2

I'm minting AND receiving MN rewards. Is that normal?

Mine doesn't match yours. (but mine is same as the MN info page)
I'm not sure what's normal. But I think MN page is the correct one.

getblockhash 261886
b600d36e7e371501139e5eb2de2944b95a84070ade173a90248a60e0b6eaf098

[jakiman]

DEV TEAM UPDATE

Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.

As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!

[EcoChavCrypto]

DEV TEAM UPDATE

Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.

As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!

I just logged into my masternode and matched up my confs with the desktop wallet, manually deleted the data files and restarted.  Was just looking for the command to re-sync the masternode blockchain.  Probably best for me to hold out for the solution and rebuild the node.

I was getting well into it for a moment.

[jakiman]

Yeah, I spent hours and hours for past few days with v2.0.0.0, v2.0.1.0 and v2.0.2.0.
Each time updating all my wallets and masternode multiple times. Wasn't fun.

But I did learn a few things to do it quicker using scripts, clustershish etc.
So yeah, new skill earned at least. Now I'm ready for next update.

[mikegi]

The problems syncing could be due to problems with checking the proof of stake, or verifying blocks.

I set up one node to sync using "connect=" from 5 masternodes that are on the same chain.
I assume the masternode would all send the same block updates and there should be no differing headers)
The syncing got stuck about 100 blocks from where the masternodes were. (stuck on block 261687... 9278bbfb89902faee60e0b1a44d6b53616915168aae893b7d8c2ef4e1268aa60 )

If one is not able to sync from 0 blocks (without downloading a blockfile), reliably, then something is seriously broken.

It would be interesting to know if master nodes are paying on the chain that the are on only, or both chains. I haven't looked into how masternodes work in detail,I suppose they check, sign and send transactions based on the fork that they are on, and these are verified by other masternodes based on their version of the chain. Also, it's possible that a masternode can exist on one fork and not the other if it's transaction has been spent on one chain and not on the other or if the masternode transaction only exists on one fork (created after forking). 
So we end up with masternodes disagreeing.

DarkCoin / Dash has had at least this fork:
https://www.dash.org/forum/threads/issues-with-masternode-payments-fork.858/

I noticed that these messages stop appearing in the logs when the syncing freezes:

Code:

2016-08-11 23:13:54 UpdateTip: new best=55e6a5b9629e9a8bb8c00e43079857d6db2f832b5fdcf0a69e060c4dadadf564  height=260824  log2_work=55.897618  tx=370493  date=2016-08-11 02:55:27 progress=0.978356  cache=108387

My  guess is that at some point there are too many orphan blocks to sort out and it becomes impossible to proceed.  

DEV TEAM UPDATE

Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.

As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!

Good to hear! I think a roll back to 259200 would be fair. (At least, it would prevent having to choose a chain and associated disappointments)

I'll stop digging through git and sleep.

[NotMyFarm]

(stuck on block 261687... 9278bbfb89902faee60e0b1a44d6b53616915168aae893b7d8c2ef4e1268aa60 )

same here