I too am seeing the "Checkpoint is too old." message. Is there anything to worry about with that?
Ya there is some issue with wallet but receiving coins from pool so no worries for now but need updated wallet soon.. It cant go like this
I'm watching the source code on
https://github.com/CapitalCoinDev/CapitalCoin and it appears that the dev has updated the checkpoints in kernel.cpp and checkpoints.cpp
We should be expecting an update soon to address the issue hopefully.
splitting@localhost:~/build/CapitalCoin/src$
CapitalCoin version v1.0.1.0-g32a928e-CPTL (2014-05-13 18:14:26 -0400)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 05/13/14 23:25:41
Default data directoryhome/splitting/.CapitalCoin
Used data directoryhome/splitting/.CapitalCoin
CapitalCoin server starting
dbenv.open LogDir=/home/splitting/.CapitalCoin/database ErrorFile=/home/splitting/.CapitalCoin/db.log
Bound to [::]:22033
Bound to 0.0.0.0:22033
Loading block index...
LoadBlockIndex(): hashBestChain=a707cbd01ae81f1f2c8a height=32226 trust=50834993218 date=05/13/14 22:12:48
LoadBlockIndex(): synchronized checkpoint 0000027f43dc7ba9c33a092198542c53be53765d5c8021fbe003b4d23dd6222f
Verifying last 2500 blocks at level 1
block index 38519ms
Loading wallet...
nFileVersion = 1000000
wallet 872ms
Loading addresses...
Loaded 327 addresses from peers.dat 3ms
mapBlockIndex.size() = 33815
nBestHeight = 32226
setKeyPool.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadRPCServer started
send version message: version 70001, blocks=32226, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
Look's like we're good to go, still no QT build yet
