Severity:
Moderate. Not affecting wallets or main blockchain. Not affecting peercoin v0.5.3. Peerunity users are recommended to temporarily suspend transaction activity until a hot fix release is ready for upgrade.
If you are minting with peerunity, also consider suspending minting on peerunity, by locking wallet or shutting down the client. This allows main blockchain to catch up and the current peerunity clients to switch back to the correct fork.
[quote=“peerchemist, post:6, topic:3875”][quote=“glv, post:5, topic:3875”]I merged Matthew’s patch in the Peerunity repository and made Linux and Windows binaries for Peerunity 0.2.1.
Because of this fork issue, everything about Peerunity v0.2 in the newsletter that was sent out is now out of date, so I hope people will check the forum to realize that they need v0.2.1 instead now.
[quote=“glv, post:5, topic:3875”]I merged Matthew’s patch in the Peerunity repository and made Linux and Windows binaries for Peerunity 0.2.1.
The OS X version is included in that link, but I was under the impression it wasn’t ready for official release yet. I have not announced anything on social media yet about it either.
What will the final version number be, v0.2.1 or this v0.2.2? It doesn’t look good on us if we tell people that they need to upgrade back to back 3 different times in a row. I will avoid posting anything on Facebook, Twitter and Reddit until I know more. I think better communication is needed.
Edit: Also, can people just upgrade like usual or will they need to do anything special like redownloading the blockchain?
Exactly as @sandakersmann says. Most of users can just ignore the 0.2.2. Also I can delay it until some further date as it is not something very important.
This is what I am trying to accomplish with Linux packages, that users do not bother with updates manually but receive them trough the standard updates of their OS.
P.S.
About OS X link. I would not know anything about it, @glv just showed up and dropped that. AFAIK he did not participate in “Compiling for OS X megathread” and did not comment anything about it.
It depends on if they have downloaded the blockchain beyond the point of time that the fork happened. If they have gone past the time of the fork they need to re-download.
[quote=“peerchemist, post:12, topic:3875”]Exactly as @sandakersmann says. Most of users can just ignore the 0.2.2. Also I can delay it until some further date as it is not something very important.
This is what I am trying to accomplish with Linux packages, that users do not bother with updates manually but receive them trough the standard updates of their OS.
P.S.
About OS X link. I would not know anything about it, @glv just showed up and dropped that. AFAIK he did not participate in “Compiling for OS X megathread” and did not comment anything about it.[/quote]
It was said that the OS X version still needs to be signed and that it would cost money to do so. I’m unaware of what this means, but if the OS X version listed is not yet officially ready then it should be removed from that page until it is. Also, as long as it is in the list I cannot announce v0.2.1 for fear of people downloading the Mac version when it isn’t ready yet.
Then clear step by step instructions on how to do this will need to be provided in the announcement for people who don’t know. We can’t expect non-technical people to know things like this and will need to offer our help so no mistakes are made.
Then clear step by step instructions on how to do this will need to be provided in the announcement for people who don’t know. We can’t expect non-technical people to know things like this and will need to offer our help so no mistakes are made.[/quote]
Is there a specific date/time that can be identified, that indicates the point the fork happened. Alternatively, is there a way in which a user can check their client, to see if they need to download a new blockchain, or simply wait?
Linux: Before you start Peerunity after re-install, go to folder ~/.ppcoin and delete all files except ppcoin.conf and wallet.dat. Do NOT delete wallet.dat. This is your wallet containing your private keys.
Windows: Before you start Peerunity after re-install, go to folder C:\Users<username>\AppData\Roaming\PPCoin and delete all files except ppcoin.conf and wallet.dat. Do NOT delete wallet.dat. This is your wallet containing your private keys. C:\Users<username>\AppData\Roaming\PPCoin is a hidden folder. You can open the folder with Start menu -> Run if you can’t find it.
Peerunity clients have forked from main peercoin blockchain as of block height 233762.
OSX: Before you start Peerunity after re-install, go to hidden folder
Open Finder->open Menu: Go and type in: ~/Library/Application Support/PPCoin
and delete everything EXCEPT wallet.dat