Tonight, the switch time for the soft-fork activation will get passed.
const unsigned int nProtocolV06TestSwitchTime = 1507700000; // Wed 11 Oct 05:33:20 UTC 2017
You can follow the current majority percentage using: https://gist.github.com/hrobeers/3de9d6e8d378107fd226185c81539b76
I made sure it is close to 0% now, so we can really see the gradual activation happening.
Happy forking!
The soft-fork activated successfully on testnet a few hours ago!
Weāre at 91% PoS support.
getblockhash 300575
d0eea1db4d5f0a21b3a62dc9beca31a43bb217db58b2c4e79192d1942ca601ea
https://chainz.cryptoid.info/ppc-test/block.dws?300575.htm
Note that this explorer runs ppcoin v0.5
It follows the soft-fork as youād expect.
Sometimes it may be stuck on a fork for a few blocks until it reorgs to the soft-fork chain.
v0.5 clients follow the v0.6 soft-forked chain but are unable to produce valid blocks.
Thatās why we need the majority to be as high as 90%, the coins in v0.5 clients will keep accumulating coin-age until they max out.
Fork watchers might have noticed the large number of orphans recently:
https://chainz.cryptoid.info/ppc-test/orphans.dws
These are 0.5 blocks that got orphaned by the 0.6 soft-fork.
FYI the last block before the soft-fork was:
https://chainz.cryptoid.info/ppc-test/block.dws?000000004bae1e09044293af92899a151b25f6c3fbdb6597a5aecafd3b17a811.htm
Trying to update one of the minting test nodes still on 0.5 but stuck in the compilation process. Iām on Ubuntu and installed QT5-default and the qttools5-dev-tools but still compilation is terminated with:
In file included from src/qt/walletmodel.h:8:0,
from src/qt/bitcoin.cpp:10:
src/allocators.h:10:34: fatal error: boost/thread/mutex.hpp: No such file or directory
#include <boost/thread/mutex.hpp>
^
compilation terminated.
Makefile:1206: recipe for target ābuild/bitcoin.oā failed
make: *** [build/bitcoin.o] Error 1
Any suggestions how to continue?
Edit: apparently Iām missing a number of packages. Just installed:
libboost-all-dev
libssl-dev
libdb+Ā±dev
libminiupnpc-dev
Ok, this seems to be itā¦ I completed the compile now. Hope the above list is useful for others.
BTW Another tip: cross-machine compiling might not work for you as the libraries are not dynamically linked. Best to compile on the VM/PC you are going to run the client on.
Is there also a daemon available? Or what is needed to compile a daemon only (without QT)?
in the src folder: make -f makefile.unix -j4
Something is wrong here: that gives me a brand new compile of
āv0.4.0ppc-2059-g0c96982-betaā
āprotocolversionā : 70001,
āwalletversionā : 60000,
as per getinfo
.
Does it need a path added somewhere? Did run it from the new src folder.
Just looking at the script output and it did run from the new src folder. Is it maybe just something in the make file retrieving an old version file? Cannot see anything different where it picks up the version.d
The rc1 indeed still shows v0.4 this has been fixed in the develop branch.
Protocolversion 70001 indicates youāre running the new version.
Is there a daemon version for windows I can use, (graphical interfaces built with QT are not compatible with my screen reader). Also, when I try to clone the git repository, it asks for a username/password. I donāt have one for the peercoin code, though I do have one for github, will that one work?
The Windows daemon peercoind.exe can be built on Linux using MXE.
Instructions are here:
You can clone from Github w/o permission, with or without github account. Read-only usually uses the http: path, and r/w uses git@github.com: path.
EDIT: sorry thatās for the peercoin-qt.exe . Iāll see if i can do build instructions for the Windows peercoind.exe
We just published a second release candidate!
This rc2 includes the contributions following the rc1 test round.
Thanks for all the contributions!
Please help testing this version again, and if all is fine, we can update the fork logic for mainnet and go public!
Tried to build wallet with full feature support and noticed that libpng-dev is also required, for qr codes.
Ubuntu choose qt5 by default (16.04), so need to force qt4:
$ qmake -qt=qt4 "USE_DBUS=1" "USE_QRCODE=1" && make
As for the rest didnāt met troubles, running new version on testnet 24/7
v0.6 has been ported to Qt5 so itās a good idea to use Qt5.
Glad to hear you have no issues with Qt4 though.
Docs mention qt4 everywhere, so I thought it is preferred.
We are bad with docs indeed.
I have some docs on building the Windows and Mac versions for 0.6. They have worked for me but not bulletproof yet.
@peerchemist I didnāt get a chance to merge w/your wiki doc but will get there.