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

2016-08-18 13:59:36 Masternode dump finished 23ms
2016-08-18 13:59:36 Verifying budget.dat format...
2016-08-18 13:59:36 Loaded info from budget.dat 0ms
2016-08-18 13:59:36 Proposals: 0, Budgets: 0, Seen Budgets: 0, Seen Budget Votes: 0, Seen Final Budgets: 0, Seen Final Budget Votes: 0
2016-08-18 13:59:36 Writting info to budget.dat...
2016-08-18 13:59:36 Written info to budget.dat 0ms
2016-08-18 13:59:36 Budget dump finished 2ms
2016-08-18 13:59:36 Verifying mnpayments.dat format...
2016-08-18 13:59:36 Loaded info from mnpayments.dat 8ms
2016-08-18 13:59:36 Votes: 1740, Blocks: 305
2016-08-18 13:59:36 Writting info to mnpayments.dat...
2016-08-18 13:59:36 Written info to mnpayments.dat 6ms
2016-08-18 13:59:36 Budget dump finished 15ms
2016-08-18 13:59:36 *** System error while flushing: CDB : Error -30974, can't open database
2016-08-18 13:59:40 CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2016-08-18 13:59:40 Shutdown: done

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. :-)

Code:

darknet-cli listtransactions "*" 1000 | grep -e account -e address -e category -e amount -e confirmations -e fee |grep -v -e txid -e bcconfirmations  | sed 's/\(.*account.*\)/\n\1/'

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

Code:

        "account" : "asdfg",
        "category" : "send",
        "amount" : 0.00000000,
        "fee" : 44.99998960,
        "confirmations" : 703,

        "account" : "",
        "address" : HIDDEN
        "category" : "send",
        "amount" : -38.25000884,
        "fee" : 44.99998960,
        "confirmations" : -1,

        "account" : "",
        "address" : HIDDEN
        "category" : "send",
        "amount" : -29.24998076,
        "fee" : 44.99998960,
        "confirmations" : -1,

        "account" : "",
        "category" : "send",
        "amount" : 0.00000000,
        "fee" : 44.99998960,
        "confirmations" : -1,

        "account" : "qwerty",
        "address" : HIDDEN
        "category" : "receive",
        "amount" : 38.25000884,
        "confirmations" : 312,

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?