UPDATE #7: Peercoin v0.6.1 Now Released, Upgrade Today! Blockchain Redownload Required! (Instructions Inside)

It was brought up on Bitcointalk that someone saw v0.4.0ppc-2108-gbcd7712 (V0.4.0) under About Peercoin. This is a known issue and the developers have said it will be fixed properly in a post release, v0.6.1.

1 Like

Upgrade went very smoothly… Well done PPC Devs

2 Likes

I like the new core client. Very sleek.

Shame we need to re-download the bockchain…

The blockchain is still under 1 Gb, so it shouldn’t take too long.

3 Likes

Congratulations on the v0.6 release! Impressive job from the Peercoin development team!

恭贺 0.6 版发布!祝 Peercoin团队 再接再厉,更上层楼!

10 Likes

So started off promising but windows client is hanging and crashing for me. Is there any bug reports/diagnostics or other information I can pass back to the dev team?

It seemed to be caused by allowing minting (unlocking the wallet for minting only) whilst the blockchain was still downloading.

1 Like

I believe there should be a file in your Peercoin folder called debug.log.

ok this is in the log just before the crash;

017-11-01 23:32:41 ERROR: mempool transaction missing input
2017-11-01 23:32:41 ERROR: mempool transaction missing input
2017-11-01 23:32:41 ERROR: mempool transaction missing input
2017-11-01 23:32:41 ERROR: mempool transaction missing input
2017-11-01 23:32:41 ERROR: mempool transaction missing input
2017-11-01 23:32:41 ERROR: mempool transaction missing input
2017-11-02 02:08:40

1 Like

This seems to have been reported here as well…

https://bitcointalk.org/index.php?topic=101820.msg23895362#msg23895362

1 Like

@Zangy Can you try downloading the chain with an empty wallet.dat file (just move it somewhere else).
You can put the wallet.dat file back after download.

Can you try if that fixes your issue?

The wallet.dat that you used during the crashes, I guess it was not encrypted using walletlock?
(During our tests we used encrypted wallets)

In next point release (0.6.1) we’ll fix this problem, basically we’ll disable minting while wallet is syncing. That’s what causing this problem.

2 Likes

I’ll add a note about this in the first post.

1 Like

I think the linux sha256 is wrong on peercoin.net

On peercoin.net there is the hash 177755712890bec1dc28213df2fb65b7e68c6f686ce10ad796fb7d280778ebc4
To me the 256 sha gives me a21f5ca1c9a5b0cc48da98888dfc376d55e4338ca1484ee701e049077976fd50

Thanks, we’ve let our webmaster know to fix it.

Sorry @hrobeers just got back from work. Still want me to try with a standard wallet.dat file or is this now superceded given peerchemist’ diagnosis…?

If your blockchain is now fully synced then it doesn’t matter anymore. The reason I believe hrobeers was asking you to use an empty wallet is because an empty wallet has no possibility of minting a block. As long as your wallet was not trying to mint while syncing, there should be no issue. However if your chain is fully synced then there is no way to test it unless you delete and redownload again.

Also, just in case you didn’t know, if you have a wallet with peercoins in it and it is unencrypted, then minting starts automatically. If the wallet is encrypted though, then it will not mint automatically and the only way is to hit “unlock wallet for minting only.”

Thanks, my wallet was encrypted and had peercoins in it. I did manually unlock it for minting during the blockchain sync which seems to cause the crashes so that is consistent with the findings from the dev team above. I’m happy to delete and re-test if that helps anyone, not a problem

1 Like

It’s fine, we got it. Please run that node already :slight_smile:

2 Likes

Only took about 1.5 hours. I was using PeerUnity. I just downloaded the new wallet and everything synced over perfectly to the new version.

1 Like