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

[mxnsch]

I would not rush to do every one of your masternodes, do a few and lets see how the night goes

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111
connect=185.86.151.173
connect=185.86.149.212


~/Darknet/src# ./darknet-cli getblockhash 259280
d363a8592e5391df7b9a9b2c62012724f3c22c0bebfdf3dae27a34f997f7ab66

confirmed, i am on the same chain with 10+ masternodes and increasing.

[1713869989]

1713869989

[1713869989]

1713869989

[DRPD]

I would not rush to do every one of your masternodes, do a few and lets see how the night goes

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111
connect=185.86.151.173
connect=185.86.149.212


~/Darknet/src# ./darknet-cli getblockhash 259280
d363a8592e5391df7b9a9b2c62012724f3c22c0bebfdf3dae27a34f997f7ab66

confirmed, i am on the same chain with 10+ masternodes and increasing.

yup me too 15 mn's done so far
waiting for the windows controller wallet on version 2.0.3.0

thanks for all your work

[mxnsch]

waiting for the windows controller wallet on version 2.0.3.0

Is's already online: https://github.com/Darknet-Crypto/Darknet/releases/download/v2.0.3.0/Darknet-Qt-Windows32.64-Wallet-v2.0.3.0.zip

[DRPD]

waiting for the windows controller wallet on version 2.0.3.0

Is's already online: https://github.com/Darknet-Crypto/Darknet/releases/download/v2.0.3.0/Darknet-Qt-Windows32.64-Wallet-v2.0.3.0.zip

ohh ty!

[BitcoinFX]

Forked at:

~/Darknet/src# ./darknet-cli getblockhash 261082
8a28c95758d5604d82e9e5069dc7bd48f423cfd219f32e13bd8bf1bd622e7120

~/Darknet/src# ./darknet-cli getblockhash 261082
018f7d90a69e51382bbdb92bb6027bacb8212925625f98ab6e30d431d2395c23


Ignore the above. Consensus block;

~/Darknet/src# ./darknet-cli getblockhash 261088
5b090e96924dae0fd0ad6e67fbc4bcc85d31e6f9792c6d3c2d14dc1942a2c5ce

- http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

[BitcoinFX]

Forked at:

~/Darknet/src# ./darknet-cli getblockhash 261082
8a28c95758d5604d82e9e5069dc7bd48f423cfd219f32e13bd8bf1bd622e7120

~/Darknet/src# ./darknet-cli getblockhash 261082
018f7d90a69e51382bbdb92bb6027bacb8212925625f98ab6e30d431d2395c23


Ignore the above. Consensus block;

~/Darknet/src# ./darknet-cli getblockhash 261088
5b090e96924dae0fd0ad6e67fbc4bcc85d31e6f9792c6d3c2d14dc1942a2c5ce

- http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

~/Darknet/src# ./darknet-cli getblockhash 261101
1c926399e6610a25b027955ab0e272fdc7fc2affcf51916226c0322fbbdd1c37

- http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

Last Block: 261101
Hash: d0c0d3857010e574047a8f658f3d533fa104d34cfbe655712e644c5b63eefd32

[jakiman]

New source is up, building wallets now, v2.0.3.0

Bring all your wallets, lets see if we can break it again.

delete the chain you have...

use the same nodes in your config file as before

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111

delete your peers file just in case..

Do Not use any other chain than this one...

https://www.dropbox.com/s/njdjxmsvhwh6njf/.darknet.zip?dl=0

Restart your wallet, and sync up before enabling staking..

Note to everyone, if you enter getblockhash 259280 and don't get d363a8592e5391df7b9a9b2c62012724f3c22c0bebfdf3dae27a34f997f7ab66 you are on the wrong chain. sync from scratch.

To all, it could be missed so I just wanted to mention that that it's "connect=" and not "addnode=".

[BitcoinFX]

New source is up, building wallets now, v2.0.3.0

Bring all your wallets, lets see if we can break it again.

delete the chain you have...

use the same nodes in your config file as before

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111

delete your peers file just in case..

Do Not use any other chain than this one...

https://www.dropbox.com/s/njdjxmsvhwh6njf/.darknet.zip?dl=0

Restart your wallet, and sync up before enabling staking..

Note to everyone, if you enter getblockhash 259280 and don't get d363a8592e5391df7b9a9b2c62012724f3c22c0bebfdf3dae27a34f997f7ab66 you are on the wrong chain. sync from scratch.

To all, it could be missed so I just wanted to mention that that it's "connect=" and not "addnode=".

Indeed. Also, "listen=0" whilst syncing with the correct chain wouldn't go a miss. The revert to listen=1 when we have consensus.

[boy2k]

To clarify...

we should replace

addnode=72.49.184.206
addnode=68.227.30.210
addnode=74.118.192.18
addnode=68.227.23.166
addnode=138.68.50.249
addnode=173.245.157.244
addnode=173.245.158.8
addnode=coin-server.com

with

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111
connect=185.86.151.173
connect=185.86.149.212

yes or no?

Is this for wallet and masternodes?

[BitcoinFX]

Forked at:

~/Darknet/src# ./darknet-cli getblockhash 261082
8a28c95758d5604d82e9e5069dc7bd48f423cfd219f32e13bd8bf1bd622e7120

~/Darknet/src# ./darknet-cli getblockhash 261082
018f7d90a69e51382bbdb92bb6027bacb8212925625f98ab6e30d431d2395c23


Ignore the above. Consensus block;

~/Darknet/src# ./darknet-cli getblockhash 261088
5b090e96924dae0fd0ad6e67fbc4bcc85d31e6f9792c6d3c2d14dc1942a2c5ce

- http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

~/Darknet/src# ./darknet-cli getblockhash 261101
1c926399e6610a25b027955ab0e272fdc7fc2affcf51916226c0322fbbdd1c37

- http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

Last Block: 261101
Hash: d0c0d3857010e574047a8f658f3d533fa104d34cfbe655712e644c5b63eefd32

Again, ignore the above. Consensus block;

~/Darknet/src# ./darknet-cli getblockhash 261122
f4ac41feb83ff64ac649d637571534d81d416b480bd41011a67a25ab8e160c73

[BitcoinFX]

To clarify...

we should replace

addnode=72.49.184.206
addnode=68.227.30.210
addnode=74.118.192.18
addnode=68.227.23.166
addnode=138.68.50.249
addnode=173.245.157.244
addnode=173.245.158.8
addnode=coin-server.com

with

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111
connect=185.86.151.173
connect=185.86.149.212

yes or no?

Is this for wallet and masternodes?

Yes. ONLY use connect=

It is the sync. v2.0.3.0 darknet.conf for ALL nodes - masternodes or otherwise. For now anyway.

[BitcoinFX]

connect=72.49.184.206
connect=68.227.30.210
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111
connect=185.86.151.173
connect=185.86.149.212
connect=104.218.120.209

[BitcoinFX]

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

[borris123]

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

so this update hasnt worked and no point updating nodes?

[Rumhurius]

aaaaaaaaaaaaand we have a 51%+ fork that needs another fork here.

Hardcoded good nodes, blacklisting old clients, a valid checkpoint and a forced sync from scratch should do the trick over the next update.

Patience or dump in my low orders pls.

[borris123]

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

one node i have done is stuck there as well. meh!!

controller stuck there as well. followed instructions exactly.

[werwortmann]

All my nodes forked, can we get the latest blockchain to try and resync?

[B1tUnl0ck3r]

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

one node i have done is stuck there as well. meh!!

me too. I tried to reinstall all the wallet, with the file, multiple time, differents peers. only coin-server... what ever. impossible to get past it.  

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

effectively I can confirm this... many are stuck there.

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

so this update hasnt worked and no point updating nodes?

yep. better no waste your time. this one isn't the update your looking for.

aaaaaaaaaaaaand we have a 51%+ fork that needs another fork here.

Hardcoded good nodes, blacklisting old clients, a valid checkpoint and a forced sync from scratch should do the trick over the next update.

Patience or dump in my low orders pls.

I don't think that hardcoding "good nodes" is the way to go. the problem we have right now is that the blockchain for most doesn't move past 261107.

Futhermore in the list given

connect=68.227.30.210
connect=173.245.157.244
connect=173.245.158.8

have been behaving badly. not on sync. and specially 68.227 was starting to sync from block 0...

It would be cool to double check the list of recommended node before publishing it...

However I strongly agree with you... patience.

[jakiman]

Yeah, I'm having issues also with my MNs. Back to the drawing board is needed I would say.

[mikegi]

Yeah, I'm having issues also with my MNs. Back to the drawing board is needed I would say.

Have you checked you masternode transactions?  Some of mine had staked to I needed to make a new address and and change the masternode.conf and the private key in the masternode's darknet.conf.