Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 353. (Read 782375 times)

35+ nodes doing fine here since yesterday. My educated guess is most errors now are related to configuration problems.
Join slack, these can usually be resolved in a couple of minutes. darknet slack is https://darknet-crypto.slack.com/

Transactions between 05.08. - 17.08. are affected by the chain reset, nothing else. Everything is on the blockchain and can be restored for sure.

Not sure i get what you are saying. Contact ttrex with your tx (if you send coins there), they will help you out. Their slack is here: http://slack.bittrex.com/

EDIT: It might be a useful pointer that you can dump your wallet private keys and import them to create a new wallet.dat anytime.

Just to check in:

getblockhash 261319
fc573e91240a7384ccb8de5d6be2c24e60726105bb0a8bc75ba493a2f5ca4d7a

And everything works fine in my MN's again. I think I'm in the correct fork, same as mikegi. 
If I get stuck again I will try going to sleep, this time has worked...

I transferred a nodes worth of coins out of my wallet to Bittrex and then sent 4 nodes worth back to a fresh wallet and fresh MN addresses and haven't had any problems, yet.

Looks like bittrex is up, I  guess sending a small amount first and seeing that it works.
I would be hesistant to use Yobit, especially if you want to get the coins out soon.

darknet-cli getblockhash 261100
faa767e489cb29df8184f423c36610ff9c78fbb8d360792d6d5f0d45c46d7a52

On all nodes and wallet.

Is everything fixed now with wallets forks and chains? I want to buy some more and transfer them to my wallet but need to be sure all is working fine.

Hi, my first time setting up masternode. I have followed the steps outlined in page 1.

When I run masternode start command, following error occurred:

Not capable masternode: Could not connect to 203.125.119.162:51472

My darknet.conf file contains:

rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
masternode=1
externalip=203.125.119.162
masternodeaddress=203.125.119.162
maxconnections=256
masternodeprivkey=xxxxx(my correct keys here)

Please assist/guide me. Thanks

I deleted wallet.dat but wallet still crashes.

I was able to get all my masternodes to start up now.
All of them has a matching block hash and to the MN info page.
FYI - I had to delete the wallet.dat to fix the crashing on some.

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

Yep correct hash, latest wallet and no nodes. synced from scratch without addnodes in config as suggested. I'm on the right chain, just somewhere along the line things vanished.

Type "getblockhash 260962"

Do you get:  65f08d0b41c148765eb182390a3bc49b14d7093fc7f53770f1ef7679bdc822b1

What wallet version are you using?

What addnodes are in your darknet.conf file?

Man this is messed up. Had the same issues as everyone else was having with corrupt wallet.dat, used a pre pos backup finally got it working chain synced but my transaction history is screwed. Basicly good until like March then one in June that isn't confirmed just n/a, had coins on Bittrex not showing up even after they updated. Pretty much lost most of my coins, mined at launch with nicehash been here since the start so yeah not cool results on my end. Tried salvage wallet, rescan transactions 1 and 2,  nada. Tried several backed up wallet.dats I figured once the chain sorted itself out my shit would either show up from Bittrex or at the least I would have what was in my wallet. Kinda bummed and out of ideas.

My node is stuck on 259396 but the hash matches the wallet.

d65e10141cf7a19e9cfb6294aa810906b6d665374eb205d7fd46e4392b72bf68

Tried a restart but it is still stuck.

Edit:

I stopped ./darknet-cli and cleared out the data folder using this super simple script (cleardata.sh in .darknet)

#!/bin/bash
echo "Clearing data folder"
rm -R blocks chainstate db.log fee_estimates.dat mncache.dat peers.dat mnpayments.dat debug.log budget.dat backups .lock
echo "Data cleared system ready for resync"
sleep 1
echo "all done"

I manually removed wallet.dat and resynced

Now everything seems to be on track

not 100% certain but think the wallet.dat might have been corrupt and thats why I was so far behind and not going anywhere.

Both the node and wallet seem to be good now.

Currently getting:


02:06:36

getchaintips


02:06:37

[
    {
        "height" : 260827,
        "hash" : "026acd1dc346f6ebdbe1aec6c4fd15fb96ccbaa62281d68f0a27270da2d3efc7",
        "branchlen" : 0,
        "status" : "active"
    },
    {
        "height" : 260779,
        "hash" : "5b28e92ab0999f9609e24ba10297241eac8b299a31be00e89ebb41ead67e420d",
        "branchlen" : 23,
        "status" : "valid-fork"
    },
    {
        "height" : 260773,
        "hash" : "a156b176784512a020fe9ebe7ad1c6873c067c14d85aa9f0c4927de41fe27243",
        "branchlen" : 61,
        "status" : "valid-headers"
    },
    {
        "height" : 260596,
        "hash" : "c9b71f5217f715c7bf8501a3fc286b71721f262152e36b52bf02fd42ba6e8eeb",
        "branchlen" : 17,
        "status" : "valid-fork"
    }
]

Moving again... :-/

Stuck:

darknet-cli getblockhash 260724
3289922ce601205fb0b9cf7aef5d3e7a7ce2e827fbd357dc19813510fa2052a

Not Stuck:

darknet-cli getblockhash 260724
6d5e6188e26fae2d44149a6b4d0e972975d2bf60c533b505553eb8058db3163c

darknet-cli getblockhash 260742
aa74039ff31212a746298450c3c7ab670528757e987093c906a191b536010f2

Same here.

EDIT: Looks like we just broke past that block. 

Me too. All at 260709.  

Same here. But due to the slow sync I have see something I think it's a bit weird. After being stucked at block260598 I have made the steps told by borris.  Stop wallet, and restart wallet. As an impacient man, I have done a getinfo, and block showed was 260589, then it have reached 260709 and stuck.  If you want PM a email and I will send you the screenshot. (Maybe this is normal, but for me that go back has been a bit surprising)

Same

defo stuck at 260709