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

[borris123]

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.,
  

what does discover=1 do?

There probably going to be another fixed release exe so i give it couple of days to see.

what block do we defo need to be switched over?

[1714068462]

1714068462

[EleanorZ]

what block do we defo need to be switched over?

86400.

[borris123]

what block do we defo need to be switched over?

86400.

plenty of time yet then. whats eta of this?

[borris123]

can you use ipv6 addresses for a node?

[EleanorZ]

Just to update, after re-indexing my VPS wallets, adding "discover=1", reloading everything, etc., my nodes are still missing/expired after an hour or so. The necessary ports are open on the VPSs so it's not that. I haven't received a payout in a few days now, I assume because the MNs aren't online long enough to develop seniority in the system.

Incidentally, assuming global hashrates stay the same through all of this, what happens? Do the MNs that ARE working get more coins because they're "covering" for all the ones that are offline or not syncing? For example, I've lost out on thousands of DNET over the past couple of days. Is my loss someone else's gain?

[BitcoinFX]

...

what does discover=1 do?

...

https://bitcoin.it/wiki/Running_Bitcoin - N.B. Some .conf settings are only relevant to Bitcoin.

-discover    Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)
 

[borris123]

Just to update, after re-indexing my VPS wallets, adding "discover=1", reloading everything, etc., my nodes are still missing/expired after an hour or so. The necessary ports are open on the VPSs so it's not that. I haven't received a payout in a few days now, I assume because the MNs aren't online long enough to develop seniority in the system.

Incidentally, assuming global hashrates stay the same through all of this, what happens? Do the MNs that ARE working get more coins because they're "covering" for all the ones that are offline or not syncing? For example, I've lost out on thousands of DNET over the past couple of days. Is my loss someone else's gain?

I lost out all yesterday. I have reverted back to 1.0.1.0 on everyone bar 2 which are on 1.0.2.1 but they have not been online enough yet to get rewards. Each wallet has not gone missing, expired or anything so 1.0.1.0 and 1.0.2.1 are all fine to run and once you have downgraded or upgraded and then waiting 12+ hours you will receive payments. I hoping there is going to be a solid updated exe before the switch over for rewards otherwise your switching the exe to much which resets the time and you lose out on so much.

[EleanorZ]

once you have downgraded or upgraded and then waiting 12+ hours you will receive payments.

No, mine are still missing/expired even after upgrading, so I'm not anticipating receiving payment any time soon.

[borris123]

once you have downgraded or upgraded and then waiting 12+ hours you will receive payments.

No, mine are still missing/expired even after upgrading, so I'm not anticipating receiving payment any time soon.

is ure controller on 1.0.2.1?

[EleanorZ]

is ure controller on 1.0.2.1?

Yup, controller and VPSs all on 1.0.2.1. Just tried re-indexing everything again for the hell of it. When at first you don't succeed, try the same thing over and over again until you do....

[cryptohunter]

dash attacking network..

[4x13]

Everyone needs to migrate to the New Wallet v1.0.2.1 ASAP. We have turned off Masternode Enforcement for the time being, and will turn it back on once the network has reached 90% upgraded. We are not expecting anymore issues..

Thank You for Flying Darknet Express.. Sorry for the Turbulance..

[borris123]

Everyone needs to migrate to the New Wallet v1.0.2.1 ASAP. We have turned off Masternode Enforcement for the time being, and will turn it back on once the network has reached 90% upgraded. We are not expecting anymore issues..

Thank You for Flying Darknet Express.. Sorry for the Turbulance..

if i update my mn to 1.0.2.1 will i have to update for a while? or are you planning a release just before or after the switch over to proper rewards?

[4x13]

The issue will not go away until everyone including wallets, pools etc. is upgraded to the new wallet. the rewards will update on block 86400. It may be a bumpy ride until everyone is on the same wallet.. hang on..

[bathrobehero]

The issue will not go away until everyone including wallets, pools etc. is upgraded to the new wallet. the rewards will update on block 86400. It may be a bumpy ride until everyone is on the same wallet.. hang on..

Is it possible to configure masternodes to only connect to nodes with the latest version and refuse connections to older versions?

I know I could use listen=0 with connect= to specific nodes but I'm curious if there's an automatic option to do so.

[EleanorZ]

We are not expecting anymore issues..

Whatever you did, my MNs haven't expired for the last five hours, which is 5x longer than they've made it for the past three days (touching wood). Nicely done, and thanks!

[etparle]

The issue will not go away until everyone including wallets, pools etc. is upgraded to the new wallet. the rewards will update on block 86400. It may be a bumpy ride until everyone is on the same wallet.. hang on..

Im sorry. I did not update. will update now. Anything special i need to kno about the update?

[4x13]

Nope, Just update as you normally would..

[DRPD]

if i do the upgrade with:

cd Darknet
cd src
./darknet-cli stop
cd
rm -rv Darknet
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
mkdir Darknet
cd Darknet
mkdir src
cd
unzip Darknet-Qt-Linux-Wallet-v1.0.2.1.zip -d Darknet/src
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknetd Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-cli Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-tx Darknet/src/
rm -rv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1
rm -rv Darknet/src/__MACOSX
rm -R Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
cd Darknet
cd src
./darknetd
./darknet-cli getinfo
./darknet-cli masternode start

anything running fine and no error but ./darknet-cli getinfo still shows: "version" : 1000100

confusing any eplanation?

[4x13]

I will have to verify this tomorrow when I get to my linux box, but  am almost 100% positive that the download is correct, and something got messed up in your process. I am assuming you have your daemon files in your home directory of your VPS (If not, run these lines after moving to the directory of your choice); that being said.. use this instead, Paste this entire line into your terminal when you first login to your VPS. assuming the darknetd is already running. if it is not running, remove "./darknet-cli stop &&" from the beginning of the line.

./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd