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

[coinwider]

anyone not past block 325101 needs to reboot their wallet and masternodes. everything should be good with masternode payments, we just found and patched a little speed bump..

Yes rebooting wallets did it, can you verify    "getblockhash"  with   "dce9bdfafcbe139e9e193e12134beaf0ff2383ffe2ff9bf740cddfe5e7cadc0a"   ?
Cause MN Pay + presstab BE are behind


thx in advance

[1713946247]

1713946247

[1713946247]

1713946247

[DRPD]

anyone not past block 325101 needs to reboot their wallet and masternodes. everything should be good with masternode payments, we just found and patched a little speed bump..

all of my wallets and all nodes are stuck at block 324999.
if i restart a wallet it will sync again a little further an than stuck again. this happens on windows wallet and on nodes ....

Darknet Masternode Payments is also stuck on 324999  

edit: tested this on 10 nodes now and all nodes will stuck again after few blocks, 325394, 325391, 325398, and so on

will leave most nodes on 324999 now until have a proper way to fix this

edit 2 : shure i run the newest version everywhere!

[coinwider]

anyone not past block 325101 needs to reboot their wallet and masternodes. everything should be good with masternode payments, we just found and patched a little speed bump..

all of my wallets and all nodes are stuck at block 324999.
if i restart a wallet it will sync again a little further an than stuck again. thais happens on windows wallet and on nodes ....

Darknet Masternode Payments is also stuck on 324999  

Do you run the latest version 2.1.3  ?

edit:   I am now at 325390  and counting but not sure if this is the right chain -  my hash is 0c887bdd47eaac119e33d3f709a307413522bc7b76df32de29c2e95e47843db8

edit 2:  Looking into connected Masternodes via Wallet-Tools i have 4xMN running v 2.1.3 and 4xMN running v 2.1.2.3    
            I am not sure, but is connection probs relying to the protcol 70705   +   70701  mixing?   If so, is there a command for .conf file like  the bantime?

edit 3: After another wallet restart i have 6x 70705 protocol MN and 2x 70701 (just consider if protocol is for IPv4/Tor connections?)

edit 4: now i have the same hash as yours for block 325390 - c84469e88d2736aa9d4ea3c703e51b75b4960dc557f949a5d161ca74ef4d6d63

edit 3 is obsolete - after running from last restart - now i have 7 connections to MN with 70705 - i think bantime worked them out

edit 5   THX DRPD - i deleted complete blockchain-data and rest - copied a blockchain form 23.9. into    and   put 2 Masternodes with wallet 2.1.3 (!!!) into my darknet.conf
addnode=164.132.238.67
addnode=193.124.129.189
ATM all connections are with version 2.1.3 -  bantime kicks every other MN away  and 325390 hash is c84469e88d2736aa9d4ea3c703e51b75b4960dc557f949a5d161ca74ef4d6d63   

[DRPD]

anyone not past block 325101 needs to reboot their wallet and masternodes. everything should be good with masternode payments, we just found and patched a little speed bump..

all of my wallets and all nodes are stuck at block 324999.
if i restart a wallet it will sync again a little further an than stuck again. thais happens on windows wallet and on nodes ....

Darknet Masternode Payments is also stuck on 324999  

Do you run the latest version 2.1.3  ?

edit:   I am now at 325390  and counting but not sure if this is the right chain -  my hash is 0c887bdd47eaac119e33d3f709a307413522bc7b76df32de29c2e95e47843db8

ohh man dnet is forking again after restarting my windows wallet again and again im on 325401 and getblockhash 325390
05c512ca7ccaa4381bf69c564da641fb91b85bfda2de97941ca0fb22fe98df4d

...... not good

edit

 and from one of my nodes:

./darknet-cli getblockhash 325390
c84469e88d2736aa9d4ea3c703e51b75b4960dc557f949a5d161ca74ef4d6d63

crap tons of forks!

edit 2: after restarting now more than 20 node wallets 90% of them are on the chain with getblockhash 325390 05c512ca7ccaa4381bf69c564da641fb91b85bfda2de97941ca0fb22fe98df4d
so at least i hope this is the right one ....

[NotMyFarm]

anyone not past block 325101 needs to reboot their wallet and masternodes. everything should be good with masternode payments, we just found and patched a little speed bump..

getblockhash 325390 05c512ca7ccaa4381bf69c564da641fb91b85bfda2de97941ca0fb22fe98df4d
so at least i hope this is the right one ....

restarted wallet
same hash here

[jakiman]

Okay. Just got back from work and noticed mine is stuck also. Here are some hashes after restart.

getblockhash 325390
05c512ca7ccaa4381bf69c564da641fb91b85bfda2de97941ca0fb22fe98df4d

getblockhash 325423
8a54b64d926664cfb4a48966012f83f31bd58601d06f0ac8d1f9101f039c3b66

getblockhash 325431
26b52b8dd5c4109da7bc53f8f5bedaa8715ab84a0642f489d63cee48a064d10b

BUT... Quite a number of my masternodes are on block numbers that are way ahead!

[DRPD]

i guess no point in comparing hashes?

from my windows wallet debug windows (note i have not restarted the wallet btw the commands):

08:25:47
getblockhash 325390
08:25:47
05c512ca7ccaa4381bf69c564da641fb91b85bfda2de97941ca0fb22fe98df4d

08:42:19
getblockhash 325390
08:42:19
c84469e88d2736aa9d4ea3c703e51b75b4960dc557f949a5d161ca74ef4d6d63

lol so the wallet jumped from one chain to another without a restart, sound like the same problem we had last week to me ...

we realy need a word from the devs about this thanks.

edit i forgot to mention: i have this 3 lines still in my conf:
addnode=173.245.158.8
addnode=68.108.10.35
bantime=50

[coinwider]

Okay. Just got back from work and noticed mine is stuck also. Here are some hashes after restart.

getblockhash 325390
05c512ca7ccaa4381bf69c564da641fb91b85bfda2de97941ca0fb22fe98df4d

getblockhash 325423
8a54b64d926664cfb4a48966012f83f31bd58601d06f0ac8d1f9101f039c3b66

getblockhash 325431
26b52b8dd5c4109da7bc53f8f5bedaa8715ab84a0642f489d63cee48a064d10b

BUT... Quite a number of my masternodes are on block numbers that are way ahead!

can you check the connected MN to your wallet/MN?  which versions they run

[jakiman]

can you check the connected MN to your wallet/MN?  which versions they run

getblockhash 325445
77e1b61fd3385562a4c01c8e7e0d928e4cd74abb461ad9832ba3609407a33265

But yeah, I'm not sure if I'm on the right chain or not as I have no reference to go by.

[ronald0cz]

Hi, guys, newbie in this thread I have 2 questions. What is the difference between e.g. Dash and DNET? Where does DNET trade?

[DRPD]

@coinwider at least my 3 windows wallets are only showing connections to version /DarkNet Core:2.1.3/ and at least one of them is jumping btw forks, not checked my mn's

warning: the bittrex wallet is also stuck at 324999 and blocked i recommend to not transfer any coins anywhere atm!

[DRPD]

can you check the connected MN to your wallet/MN?  which versions they run

getblockhash 325445
77e1b61fd3385562a4c01c8e7e0d928e4cd74abb461ad9832ba3609407a33265

But yeah, I'm not sure if I'm on the right chain or not as I have no reference to go by.

  
getblockhash 325445  ca3077c775f5f2025a284b827b6e83667ea7ddcac35e041f53a2471844f91429

you are right we need a reference

[jakiman]

Hi, guys, newbie in this thread I have 2 questions. What is the difference between e.g. Dash and DNET? Where does DNET trade?

DASH is PoW and does not have a fully untraceable transaction.
DNET is PoS and goal is to achieve fully untraceable transactions.
Both utilizes masternodes. Currently trades mainly on Bittrex.

[coinwider]

can you check the connected MN to your wallet/MN?  which versions they run

getblockhash 325445
77e1b61fd3385562a4c01c8e7e0d928e4cd74abb461ad9832ba3609407a33265

But yeah, I'm not sure if I'm on the right chain or not as I have no reference to go by.

thx, i don't now either...

[jakiman]

I don't think there's any point in everyone trying to fix it. Doubt we can fix it ourselves anyways.

So please wait untill there's further updates from devs. (they are most likely asleep atm)

[pjcltd]

can you check the connected MN to your wallet/MN?  which versions they run

getblockhash 325445
77e1b61fd3385562a4c01c8e7e0d928e4cd74abb461ad9832ba3609407a33265

But yeah, I'm not sure if I'm on the right chain or not as I have no reference to go by.

  
getblockhash 325445  ca3077c775f5f2025a284b827b6e83667ea7ddcac35e041f53a2471844f91429

you are right we need a reference

08:15:21

getblockhash 325445


08:15:21

ca3077c775f5f2025a284b827b6e83667ea7ddcac35e041f53a2471844f91429

[dsutil]

My masternode was stuck also.

After restart:

getblockhash 325445
ca3077c775f5f2025a284b827b6e83667ea7ddcac35e041f53a2471844f91429
 

And my other node:

getblockhash 325445
77e1b61fd3385562a4c01c8e7e0d928e4cd74abb461ad9832ba3609407a33265


:-(

[jakiman]

Out of 20 masternodes that I just restarted, I have ended up with 6 different chains. So yeah, I'm giving up for now.

[DRPD]

Out of 20 masternodes that I just restarted, I have ended up with 6 different chains. So yeah, I'm giving up for now.

yep same here total forkmania lets wait.

thanks for the twitter warning

edit:
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html is moving again but not shure if on the right fork

[borris123]

tried doing some of mine as well. some were going on different forks as well.

have

bantime=50
addnode=68.108.10.35
addnode=173.245.158.8

latest wallet.

guess will have to wait for devs.