Peercoin v0.5.2 Release

Sunny_King 2016-03-08 07:13:20 UTC #1

v0.5.2 is now released.

Official build for linux:
https://sourceforge.net/projects/ppcoin/files/0.5.2/ppcoin-0.5.2ppc-linux.tar.gz/download
Official build for windows:
https://sourceforge.net/projects/ppcoin/files/0.5.2/ppcoin-0.5.2-win32-setup.exe/download

This release includes some additional API from bitcoin, in addition to protocol enhancement, which requires a mandatory upgrade from our users.

Upgrade deadline for users running v0.4.2 official release is extended to Monday April 25.

However, users running v0.5.1 RC2 release candidate must upgrade before next Monday - March 14. After March 14 v0.5.1 RC2 release candidate would be on a separate blockchain fork from main blockchain and will no longer be supported. It is generally not recommended for users to run release candidates for production purposes.

Upgrade instructions:
1) Back up wallet using the menu option or command line.
2) Note down your balance/stake in the wallet.
3) Shutdown peercoin client
4) Uninstall old client
5) Download and install v0.5.2 client
6) Start up v0.5.2 client
7) Confirm release name of the client as 0.5.2ppc-beta
8 ) Verify your balance/stake as correct.

For support, please post in this thread.

$ openssl dgst -sha256 ppcoin-0.5.2*
SHA256(ppcoin-0.5.2ppc-linux.tar.gz)= a4a6a7901bbe8f3c74d04458852cb84016f697ad3ca7461005077a2fab8e00bc
SHA256(ppcoin-0.5.2-win32-setup.exe)= 25efeebf131e2216bddcce503a324b7616b12134b1d18f2a405cb8b0a295492c

Sentinelrv 2016-03-08 08:54:57 UTC #2

Peerunity also needs to be upgraded correct?

K500 2016-03-08 09:26:12 UTC #3

Yes.

Sentinelrv 2016-03-08 09:40:54 UTC #4

And who is going to do that? Jordan's team built Peerunity, but they're preoccupied with two different projects.

K500 2016-03-08 09:46:02 UTC #5

I dont know. I posted a thread in the peerunity section of this forum bringing up the issue, im hoping that one of the devs will respond.

sandakersmann 2016-03-08 17:07:21 UTC #6

I can confirm these checksums:

ppcoin-0.5.2-win32-setup.exe
25efeebf131e2216bddcce503a324b7616b12134b1d18f2a405cb8b0a295492c

ppcoin-0.5.2ppc-linux.tar.gz
a4a6a7901bbe8f3c74d04458852cb84016f697ad3ca7461005077a2fab8e00bc

Sentinelrv 2016-03-08 18:26:25 UTC #7

Posted on social media. Please retweet and share...

irritant 2016-03-08 21:55:43 UTC #8

i see testnet port is 9903 in init.cpp

"Listen for connections on (default: 9901 or testnet: 9903)"

but in weekly update 74 it says

There is also a slight change to testnet node. Previously testnet node shares default rpc port (9902) with production node. Now testnet node has a separate default rpc port 9904 . Testnet node can be run simultaneously with production node, but if you use command line for rpc access make sure you use the -testnet switch to query testnet node.

im using 9903 now, this is the correct one?

learnmore 2016-03-08 23:05:00 UTC #9

The RPC port is different from the main incoming data port. 9903 is correct.

RPC is for sending commands to the wallet. Best to keep that port blocked from remote connections unless you have specific need.

irritant 2016-03-08 23:14:15 UTC #10

i see thanks

learnmore 2016-03-08 23:15:05 UTC #11

I'm just curious, sandakersmann, how can you confirm them?

It'd be nice if SK could start signing the builds with a PGP signature:
https://pgp.mit.edu/pks/lookup?op=vindex&search=0x18F34404D2B95E6A

...presuming that's really him :-/

Sentinelrv 2016-03-09 00:09:04 UTC #12

I asked the Nu team here if they could possibly help merge Peerunity with v0.5.2...

https://discuss.nubits.com/t/merging-peerunity-with-peercoin-v0-5-2/3628

mhps 2016-03-09 05:22:29 UTC #13

On my win7 laptop I run peerunity since 2014. I did the following to instal the offcial client v0.5.2 -
1. download the binary and run it.
2. copy addr.dat blk*.dat database/log* to the v0.5.2 data directory
3. run v0.5.2 client without a wallet, and wait for the block chain to download until seeing green tick at lower right corner. Check debug window this is really 0.5.2
4 quit client. wait until the files with "__" in the names are gone in the data directory.
5. copy wallet.dat from peerunity data directory to that of v0.5.2 client
6. run v0.5.2 client with current wallet. everything looks fine.

total in less than 1 hour (my peerunity blockchain was very uptodate)

mhps 2016-03-09 07:25:58 UTC #14

I try to compile 0.5.2ppc-beta on Raspberry Pi and is having problems.

I have a cloned git repository of v0.4.1 so I

[tt]cd ppcoin[/tt] into the git directory
1.5 (edit see here) [tt]git fetch origin[/tt]
[tt]git tag[/tt] and see many tags. v0.5.2 is the only one looks like what is needed. I don't see v0.5.2ppc-beta
[tt]git checkout v0.5.2[/tt]
[tt]cd src[/tt]
generally follow https://docs.nubits.com/nu-raspberry-minting/ to [tt]make -f makefile.unix[/tt]

The problem is I get bitcoind as the built binary and it demands ~/.bitcoin/bitcoin.cfg when started

How to fix the problem? Did I check out the wrong branch?

peerchemist 2016-03-09 08:58:21 UTC #15

Why dont you use debian package from Peerbox project?

mhps 2016-03-09 09:40:36 UTC #16

off topic: because of this problem and on peerbox controls are scattered in many places and difficult to remember after a while. and bug fixes are slower than if i compile myself.

peerchemist 2016-03-09 09:50:29 UTC #17

offtopic again:

Peerbox does not work like that anymore, it is not independent OS anymore. https://www.peercointalk.org/index.php?topic=4413.0

irritant 2016-03-09 10:21:10 UTC #18

try git checkout v0.5.2ppc

actually i didnt have to do git checkout v0.5.2

all i did was
git clone https://github.com/ppcoin/ppcoin.git
cd ppcoin/src
make -f makefile.unix
./ppcoind -daemon
./ppcoind getinfo
"version" : "v0.5.2ppc-beta",
yay

mhps 2016-03-09 10:32:59 UTC #19

I know the problem now. After [tt]cd ppcoin[/tt] I should do a [tt]git fetch origin[/tt]

peerchemist: will try it later. I am keeping similar setup for nu and bcexchange.

sandakersmann 2016-03-09 17:09:47 UTC #20

Confirm was maybe the wrong word here. Those were the sha256sum I got on my end.