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

You are much better off using start-alias.

 synchro fast  @260278 with staking active btw
it seems ok for me

I restored an old copy of my wallet.dat file and that fixed it. But it locks up on me when I do the masternode start-missing

Only time I recall seeing this is if there is something wrong with the wallet.dat file, when it goes to write to the wallet on exit..

Yeah, one hell of a week!

One thing for all DNET hodlers to realize is that this is a pretty large undertaking. Although we tested quite a few times privately, its really hard to test conditions that will happen when the general public get on the chain and often times do bizarre things. This is still a work in progress and I am sure there will be plenty more changes to come. What we do know is that we have a chain moving forward and no more resets.

v2.1.3, v2.1.4, v2.1.5, v2.1.6 incoming this week end  
v2.1.8, v2.2, v2.2.1 next week  

Be ready !!
 

I had the same thing.  It corrupted the wallet.dat so I deleted it and replaced it with a backup.  Synced from fresh with no nodes and just the backup wallet, darknet.conf and masternodes.conf.

All is synced, masternodes running and MN payment incoming.

My wallet corruption happened after I tried to unlock the wallet.

Everything seems to be running smoothly for me now.  Give it a go and see if it works for you.

EDIT:  
Just had a crash but no corruption of either the wallet or blockdata

getblockhash 260259

d56608b91036ad724b82f0f272260d5f11e1afc40870fcc8029069f3db6abed1

EDIT:

Seems to be moving along nicely now. 

getblockhash 260269

b347d97409c802da53d25934e6d31c068305e8ee6006da686790f108646d0852

No, it's not necessary to totally unlock to stake. But I needed to restart the wallet and wait a bit for stake.

Looks like it works for me, all masternodes up, wallet reporting Staking Active.

If you are getting "stuck", check how many peers you have and check the end of the logfile.

If you are crashing, check the logs, maybe a corrupt wallet file. For me, using a backup from before PoS helped.

For masternodes, it's possible that wallet.dat even if it is empty could cause a problem too.

For those who posted blocks earlier... here is what I see...

$ darknet-cli getblockhash 259539
29faf736f01c608e206b853b10cf3fde2e3909a306f4fbc39123d4300349dd0a

$ darknet-cli getblockhash 259804
59b69b7ceaee9ebd668b7a873509d7b4425659437740d4426bfa7ad92339709c

$ darknet-cli getblockhash 260048
ac1be0a29bab70204ef81f11c29ab14952414ec840e8e36d6f3cf3df8f87a454

darknet-cli getblockhash 260140
$481e390a121c66fbe587f7c6acd5eb85db92480206bfc55d02ad2f35bc8c2558

darknet-cli getblockhash 260150
c36be63959cdb6194bc55149d11f1b32ae0655cd20ef27866550145765ac2e93

$ darknet-cli getblockhash 260176
37680d1fd0189f2b0f0044f70f74176270826182a08d3b810fb39cc2b04d8ab9

darknet-cli getblockhash 260224
33bf1fc91a1214044c64ecb980247f609bf5911a1d4013c60f81471ec794b780


All masternodes are "status" : "ENABLED" from the wallet, and "status" : "Masternode successfully started" on the masternode.

It would be nice if the category field when running listtransactions from darknet-cli was more clear...  (instead of just send and recieve)

I guess my  masternodes are approving blocks... transactions are all pretty close to 38.25 DNET.
Any ideas of what kind of balances are needed to stake at the moment?

If you are using the Linux darknet-cli ... here is a oneliner make limit the output of listtransactions to more relevant information.
Maybe someone would like to figure out add a comment that will put a dashed line between blocks or make a perl script.  :-)


Output looks like this... (with some additions sed to remove addresses...



Also, it's nice to see lots of TOR nodes. At the moment, the masternode distrubution is:

Total: 204
TOR: 133
IPv6: 35
IPv4: 36

I agree with borris123 that fixing things belongs in a testnet, probably more could have been done there initially,  understand that not all problems, behaviour, misbehaviour can be simulated in a test network.

So, is this another practice? Are there any more problems with the blockchain? Does Staking work? Are the remaining problems, having to do with improper configuration. Are we stable enough? Is this fair enough to for us to move on?

I unlock wallet for anon only and it says staking not active. Do I have to totally unlock to stake? My coins are way old in my wallet.

Fatal error whenever I exit the wallet. Have to rescan on every start:

Looks good, same hash in my wallet and my updated MN's

v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

Yes yes same here

same 

I get the same hash, looking good

Last check for the night.

getblockhash 260150
c36be63959cdb6194bc55149d11f1b32ae0655cd20ef27866550145765ac2e93

restart the darknet

./darknet-cli stop
sleep 5
./darknetd
sleep 10
./darknet-cli getinfo


it syncs

not sure sure about your hosting partner but if u use mp-hosting please be patient. i guess server (cpu/ram) and network traffic is at the limit atm.
everybody and his dog ist updating and resync so .....

some of my masternodes are not up to sync whys that?

1 seems stuck on 259500. fresh install as well. no nodes.
1 is at 259943. has the same hash as your 259804
1 stuck 259937.

controller stuck at 259988

what is up with this? spent far to many hours trying get this to work and we just having update after update of failed releases. revert back to the original code which works. make a test net so the farce doesnt happen again and only release when its working like every other reputable coin.