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

update: setting up 47th master node, all current are reporting stable stake operation

Most of my masternodes have crashed also after the stall. Most wouldn't even start back up either.
So I deleted everything except darknet.conf and resynced from scratch. Seems to have fixed them.

It sure has been a busy 2 weeks for everyone involved with DNET.

I was finally able to get my wallet to crash, I had to do so much screwing around with it to get it to crash I am not 100% sure what I did that caused it. I did find that it would continue to crash until I replaced my wallet.dat with a backup and resynced. I was able to get the wallet to start again by starting it with -salvagewallet, but that would eventually crash again.

It seemed everything was running fine until the chain stalled, so I am hoping that once everyone gets things back to normal the problem will go away, I am still trying to find the underlying cause of the crashing issues.

Remote masternodes have empty wallets, so removing everything in the data directory except for the darknet.conf and restarting the daemon should fix the issue for them.

same for me..
Sometimes my masternode crashes then it's seems corrupt and need resync form the start with delete files ..

And
sometimes it's crashing when i shutdown wallet

*** System error while flushing: CDB : Error -30974, can't open database
*** CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery

Same is happening to me. 

Since the chain started moving again, all my nodes have corrupted. I resynced them all from scratch and only my controller wallet will run. My masternodes keep crashing and corrupting.
I see the masternode count is at 400 from 650 odd earlier, so looks like I am not the only one

How can I ensure staking is deactivated on my controller wallet?  I have had to re download the blockchain on all nodes because of a corruption error, none of my nodes, which were active received any payments in 40+ hours.  I am wondering if I have staking active and that is the problem.

as a local masternode on that wallet with darkcoin.conf only. it works great when I only use it for masternodeing. I get regular payements. However I tried to create another address and wire some coins on it. stacking activated. but as soon as I got the first staking payement the masternode stopped earning and only staking was.

Can you elaborate on that an provide details? I dont get it. Running exact the described setup, everything seems to be working as expected - Masternode payments and staking income.

To be extra clear - controller wallet with a lot of remotes.

Are you running just a local masternode on that wallet (Using just the darknet.conf file) ?? or are you setting it up as a remote node (using a masternode.conf file)??

thank you very much for this clear information. Shouldn't you have at least another devs have access to the private key in case of need? redundancy can always be very useful...

Smooth stacking now for me too. However I remarked that it isn't possible to have the same wallet run a masternode and have a separate stacking address on it. it breaks the masternode address once a staking payment is received. It divides the masternode coins address in 4 stash of around 2500 dnet but still on the same address. However the masternode refuses to launch after saying that the coins aren't good. Is that a normal and expected behavior?

Seems like that resolved it, at least all my nodes and wallet are back on track

Sporks are a way of mitigating network confusion and disagreement when there are either either hard or soft forks. If you run "spork show" in the console you can see the current state of the various sporks. When we push new updates that have protocol level changes we disable sporks 8, 9, and 10. Those are the ones needed the most. The others have not been needed by us so far.

Yes, I can control them, I am the only one with the associated private key needed to do so. That doesn't really effect decentralization, as beyond allowing older versions of a wallet to communicate with newer versions during transitional periods, they serve no other function. I can't use them to roll back the chain, disallow certain users, deny blocks, or any other type of thing.

The only spork that could even be misconstrued as a decentralizing thing is spork 10, the pay updated nodes spork. It is used after a protocol level change, which is generally a mandatory update, to decide when to stop sending masternode payments to masternodes still running the older version of the wallet. It lets older versions of the wallet continue acting as masternodes and getting paid for it during the transition, preventing a situation where there were no masternodes, or even very few, weakening that side of the network.

I really wish I was having these same problems so that I could, not only find the underlying cause, but also figure out an easy, one size fits all, way of getting back to normal. When you say the wallet won't start at all, do you mean that it does nothing, or gives you an error, or some third thing?

I have gotten past the stuck block.  My only issue is not receiving any masternode payments for 40+ hours despite all nodes being enabled and showing up on the list.  Is this normal?  

EDIT:

I just checked on the nodes and they must have gone down over night so I restarted them and checked the blocks and all seems good. 

getblockhash 264003

e4f42c2df7e7f392b6ac2299a1ebb21df5d09d57973cf5b6518410a914a966c3

Same on all nodes and controller wallet.

Still no MN payments though.

Hello StakeBox,

I can confirm that the chain is moving moving again. I don't understand what sporks... and what they do? Could you please enlighten me a little on the subject? From what I get from your message it's something that you can control. Does it affect the decentralized nature of DNET?

My wallet just got a new block but after my wallet crashed. Now my wallet isn't starting anymore. On my PC the same happened. So how can I sole it? It looks like the old corrupted wallet.dat issue.

OK folks, we re moving again. We are having an issue with one of the sporks, that is what caused the chain to stall for a bit the other day. When I disabled it the other day I just entered a date to activate as a few days in the future. That time passed last night stalling the chain again. I just changed the date to a couple months from now. We will have the issue resolved by then. Sorry about that.

Okay thanks guys. I hope it's like jakiman said and that it will resolve itself later... however I don't have any previous experiences with a POS coin...

I am curious to know what the Devs will say about this... Fingers crossed.

darknet-cli getblockhash 263844
8c0ffc3fd677bc2b30bdc8d56b6bb3cd39605a56c617e66aebf8fa2c64b33dd3