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

[waffles99]

Need to reiterate my statement. several nodes with status enabled, were still stuck at blocks 707* mostly, one at 69*

I have had externalip= set from the beginning with all nodes. that problem still happened.

[1714185214]

1714185214

[1714185214]

1714185214

[DRPD]

Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

yes and even my masternodes running on the new version where the out of sync problem should be fixed expires all 2 hors or so

edit: masternodes on version 10001, 10002 and 1000201 all have the same problems will check the sync problem a littlebit further on version 1000201 as soon as i can ....

ok i just checked this again on several masternodes that are listed as expired again.
they are all in sync and syncprocess is going forward just fine on this matsernodes

some masternodes run on the latest version 1000201, some on version 10001 the behavior is the same.

seems the "epired / restart" problem has nothing to do with the sync problem or version.

all my masternodes where running fine for several days until version 10002 came out and nothing seems to solve the problem so far.

tetsted the following steps:
- every version from 10001 - 1000201
- restart  vps
- delete and clean reinstall of masternode sw (with all versions)
- all steps above on 2 different hoster (to be sure the problem is independent from hoster)

let me know if i can test anything else, i guess there must be a dnet network problem i have no other explanation - but i'm not a blockcain expert  

my last payout is also more than 12 hrs ago even if have a script running all 10 minutes to execute "masternode start-missing"

on the plus side the out of sync problem seems to be fixed in the latest version (note: my upgrade is only about 5 hrs ago )

[borris123]

Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

yes and even my masternodes running on the new version where the out of sync problem should be fixed expires all 2 hors or so

edit: masternodes on version 10001, 10002 and 1000201 all have the same problems will check the sync problem a littlebit further on version 1000201 as soon as i can ....

ok i just checked this again on several masternodes that are listed as expired again.
they are all in sync and syncprocess is going forward just fine on this matsernodes

some masternodes run on the latest version 1000201, some on version version 10001 the behavior is the same.

seems the "epired / restart" problem has nothing to do with the sync problem or version.

all my masternodes where running fine for several days until version 10002 came out and nothing seems to solve the problem so far.

tetsted the following steps:
- every version from 10001 - 1000201
- restart  vps
- delete and clean reinstall of masternode sw (with all versions)
- all steps above on 2 different hoster (to be sure the problem is independent from hoster)

let me know if i can test anything else, i guess there must be a dnet network problem i have no other explanation - but i'm not a blockcain expert  

my last payout is also more than 12 hrs ago even if have a scripts running all 10 minutes to execute "masternode start-missing"

on the plus side the out of sync problem seems to be fixed in the latest version (note my upgrade is only about 5 hrs ago )

My masternodes are on 1.0.1.0 downgraded using mp hosting. They are in sync and i am recieving regular payouts again now after 12 hours or so. i am running the 1.0.2.1 wallet on my controller windows pc and it has not got stuck yet...I am not risking upgrading the masternodes again until this is 100% fixed

[DRPD]

Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

yes and even my masternodes running on the new version where the out of sync problem should be fixed expires all 2 hors or so

edit: masternodes on version 10001, 10002 and 1000201 all have the same problems will check the sync problem a littlebit further on version 1000201 as soon as i can ....

ok i just checked this again on several masternodes that are listed as expired again.
they are all in sync and syncprocess is going forward just fine on this matsernodes
..................

My masternodes are on 1.0.1.0 downgraded using mp hosting. They are in sync and i am recieving regular payouts again now after 12 hours or so. i am running the 1.0.2.1 wallet on my controller windows pc and it has not got stuck yet...I am not risking upgrading the masternodes again until this is 100% fixed

my mn's on mp hosting also run on version 1.0.1.0 most of them (not all) go in expired mode from time to time .... no payout for 14 hrs now 
i guess you are lucky hehe

[Tecem]

Went back to version 1 wallet since version 2 was acting strange. Blocks where stuck. Now on version 1 it also went stuck a few times. Now its running fine but I didn't get a payout for 14+ hours. A friend is running a mastered at home and he got payed 8 times in 3 minutes. So something strange is going on. few days ago my mastered was just running fine with payments every 6-8 hours.

[jakiman]

For past 24 hours, I've received about 50% of what i should have got.

I just upgraded few MN to 1.0.2.1 along with my controller wallet.
But I've left most MN at 1.0.1.0 still. Let's see how this goes....

[BitcoinFX]

Linux / Cloud VPS - DNET command line upgrade guide from: v1.0.1.0 or v1.0.2.0 to: v1.0.2.1

Stop the Dnet daemon:

Code:

cd Darknet

Code:

cd src

Code:

./darknet-cli stop

Code:

cd

Remove the 'old' Dnet folder and daemon etc:

Code:

rm -rv Darknet

Download Dnet v1.0.2.1 :

Code:

wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/Darknet-Qt-Linux-Wallet-v1.0.2.1.zip

Re-make the Dnet directory:

Code:

mkdir Darknet

Code:

cd Darknet

Code:

mkdir src

Code:

cd

Unzip the download :

Code:

unzip Darknet-Qt-Linux-Wallet-v1.0.2.1.zip -d Darknet/src

Move the unzipped files to the 'default' directory :

Code:

mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknetd Darknet/src/

Code:

mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-cli Darknet/src/

Code:

mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-tx Darknet/src/

Tidy up:

Code:

rm -rv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1

Code:

rm -rv Darknet/src/__MACOSX

Code:

rm -R Darknet-Qt-Linux-Wallet-v1.0.2.1.zip

Restart the Dnet daemon:

Code:

cd Darknet

Code:

cd src

Code:

./darknetd

Code:

./darknet-cli getinfo

Code:

./darknet-cli masternode start

Guide at: http://xeronet.c0m.li/dnet-crypto.php - to be updated.

EDIT: Go here: https://github.com/Darknet-Crypto/Darknet - If you prefer to build from source.

[BitcoinFX]

For past 24 hours, I've received about 50% of what i should have got.

I just upgraded few MN to 1.0.2.1 along with my controller wallet.
But I've left most MN at 1.0.1.0 still. Let's see how this goes....

Guess everyone is pretty much in the same boat here, except those that didn't upgrade. 

Posted Upgrade instructions for linux cloud VPS above anyway.


P.S. This has all been a bit like 'upgrading' from Windows 7 to Windows 10 ?   

[DRPD]

Went back to version 1 wallet since version 2 was acting strange. Blocks where stuck. Now on version 1 it also went stuck a few times. Now its running fine but I didn't get a payout for 14+ hours. A friend is running a mastered at home and he got payed 8 times in 3 minutes. So something strange is going on. few days ago my mastered was just running fine with payments every 6-8 hours.

yeah same here i had payouts all 6-8 hours now nothing since 16 hrs for 35 masternodes  

the expire problem seems to be a lot worse with the newst version so i recommend to stay with version 1.0.1.0
with the new version they are listed as expired every 2 hrs regulary....

[borris123]

any updates on everyones results? i have 1 mn and controller going and they still in sync so far...

[djselery]

Had to restart my wallet and mn again was stuck visually at block 726xx with no rewards shown. After restart it seems it was running fine just the wallet was not updating because after restart and resync i had 300 dnet waiting for me in the chain. Is there a repairwallet command or something to fix this issue?

[EleanorZ]

yeah same here i had payouts all 6-8 hours now nothing since 16 hrs for 35 masternodes  

the expire problem seems to be a lot worse with the newst version so i recommend to stay with version 1.0.1.0
with the new version they are listed as expired every 2 hrs regulary....

Just confirming that mine are also still having the missing/expired problem. Have received two payouts in the last 48 hours. Annoying.

On the other hand, syncing is fine.

[borris123]

yeah same here i had payouts all 6-8 hours now nothing since 16 hrs for 35 masternodes  

the expire problem seems to be a lot worse with the newst version so i recommend to stay with version 1.0.1.0
with the new version they are listed as expired every 2 hrs regulary....

Just confirming that mine are also still having the missing/expired problem. Have received two payouts in the last 48 hours. Annoying.

On the other hand, syncing is fine.

what version?

[StakeBox]

Just an update folks, we have been working diligently to figure out what the hell is going on. s3v3n and I are in the same boat as everyone else, and are exhausting all of our options to remedy this. I have held off on saying much, but I think that the fact that there are wallets of all versions, 1.0.1.0, 1.0.2.0, and 1.0.2.1 acting up suggests that something other than a wallet issue is at play. We reverted most of the changes that were brought about in v1.0.2.0 with v1.0.2.1 just to make sure that there wasn't something we were missing, it would seem that there wasn't.

The only thing that can ever cause a Masternode's state to go to "EXPIRED" is if it hasn't been able to be pinged by the network for 65 minutes. If you go to http://www.yougetsignal.com/tools/open-ports/ and verify that you Masternode is reachable on port 51472 then you should sending and receiving pings. If it is reachable, and your Masternode is going to expired the only remaining explanation is that something, or someone, is blocking communication somehow. After checking quite a few Masternode addresses at random and finding them reachable, I have to assume there is something nefarious afoot.

Please bear with us as we work to figure out exactly what is happening, and how to alleviate the problem. Communication from us is limited as we are trying to focus all of our energy on getting things back to the smooth operations we had prior to this. Please, keep posting anything you are noticing, good, bad, or indifferent, we may not respond immediately, but are checking in here often for updates from you guys.

Thanks for your patience while we work this out, as soon as we are certain of the next move we will let you know.

[EleanorZ]

what version?

1.0.2 and 1.0.2.1. Haven't gone back to 1.0.1 yet since I was hoping for a fix in 1.0.2.1, but may be the next step. I was just letting the devs know that the "other" issue is still unresolved for me. I had no issues with 1.0.1 before, but the fact that others are now getting expired nodes even after downgrading makes me think there's something else going on.

And devs, thanks for the update. Good luck getting things sorted out--better to have hiccups now than later on in the roadmap, I guess.

[DRPD]

Just an update folks, we have been working diligently to figure out what the hell is going on. s3v3n and I are in the same boat as everyone else, and are exhausting all of our options to remedy this. I have held off on saying much, but I think that the fact that there are wallets of all versions, 1.0.1.0, 1.0.2.0, and 1.0.2.1 acting up suggests that something other than a wallet issue is at play. We reverted most of the changes that were brought about in v1.0.2.0 with v1.0.2.1 just to make sure that there wasn't something we were missing, it would seem that there wasn't.

The only thing that can ever cause a Masternode's state to go to "EXPIRED" is if it hasn't been able to be pinged by the network for 65 minutes. If you go to http://www.yougetsignal.com/tools/open-ports/ and verify that you Masternode is reachable on port 51472 then you should sending and receiving pings. If it is reachable, and your Masternode is going to expired the only remaining explanation is that something, or someone, is blocking communication somehow. After checking quite a few Masternode addresses at random and finding them reachable, I have to assume there is something nefarious afoot.

Please bear with us as we work to figure out exactly what is happening, and how to alleviate the problem. Communication from us is limited as we are trying to focus all of our energy on getting things back to the smooth operations we had prior to this. Please, keep posting anything you are noticing, good, bad, or indifferent, we may not respond immediately, but are checking in here often for updates from you guys.

Thanks for your patience while we work this out, as soon as we are certain of the next move we will let you know.

ok checked this ping thing   on port 51472 on 20 of my masternodes no problem Port 51472 is open.
i have to repeat: i have 2 hosters mp-hosting and a hoster in russia masternodes on both hosters have the same problem

thanks for working so hard on this and take your time! as we all know shit happens with IT stuff!

edit: i got some payouts until yesterday even with the expired problem. but now no payouts are incoming anymore.
some of my masternodes don't go to expired state (not much only ~5 of 35) so i guess there is a problem with payouts 2 even if the masternodes works fine without "expired" interruptions

[borris123]

my last payout was 3.15 and have stopped by looks of it. usually get regular hourly payments as well. All are still enabled tho. Only one is on 1.0.2.1 and that is still in sync and has been for a couple of hours now. The rest are on 1.0.1.0. the controller is 1.0.2.1 and that is in sync as well.

[danonthehill]

I am still receiving payouts from all my masternodes on MP hosting.  I only get MISSING EXPIRED or REMOVE if I use old .1 local wallet to connect to masternodes which are running newer .2.   

[Tecem]

I See a lot of traffic incoming to my mastered port. Is there an attack on the network going on what causes the payouts to be stuck? The problem isn't in the wallet it self. Seems an external issue with the blockchain or something.

the 10k coins are not locking also. so a lot seems to be messed up

[BitcoinFX]

Everyone upgrading to v1.0.2.1 seems the best option now - It is mostly the same as 1.0.1.0, with the block rewards corrected.

Best to reset / upgrade Masternodes and controller wallets asap. Advise server restarts, where possible.

Check for or add;

listen=1
discover=1

and/or

externalip=<put your masternode ip address here>

are added in your masternodes  darknet.conf

and reindex on re-start;

Code:

./darknetd -reindex

~ Also, now waiting to see if MN's are getting 'stuck' on blocks after upgrading. Monitoring nodes for any signs of 'packet flooding' etc.,