done :)[/quote]
Great 
Peerunity v0.1.3-RC1 is available for all platforms. You can download builds here:
Hmm, missing exactly 100 PPC in my PeercoinQT v0.4.0 linux 64 bit walletâs balance. No transaction record for the missing 100 PPC. A minting credit of 1.35 PPC was posted Nov 14 @ 13:58, but needs more confirmations before that will show up in my balance. Any advice, re. the missing 100PPC?
OK, maybe I can relax. A stake of 101.37 PPC has now shown up in a refreshed wallet. Whew, never seen that before.
First off, Iâd like to say âGreat work!â for noticing and addressing this fork problem quickly and proactively.
I think there still is some work to do⌠I noticed that the 64 bit machine I have running is on the wrong chain, or stuck⌠It lookâs like my version might be a bit old â0.4.0ppc-23-g57b8c8d-dirty-betaâ. I figured this out when I noticed an unusually low Difficulty (90M) and that there was a discrepancy between what my client showed and what some blockchain explorers showed⌠Obviously the block height is different too. Anyway, I guess some people are still mining on the fork. I include (more details about my installation at the end of the message.
It could also be worthwhile to implement some kind of blacklist for peers on the old blockchain.
[quote=âSunny King, post:15, topic:3691â]Status update: sigmike has published v0.4.1 RC1 including fixes for both 32-bit nodes and for 64-bit nodes locally built with openssl 1.0.1k+ (Great job, sigmike!). We have agreed that the checkpointed blockchain fork is the supported fork. This is the blockchain fork that all linux 64 bits running official v0.4.0 builds accepted, which includes the transaction sent by the attacker, using a signature format not recognizable by v0.4.0 32 bit builds.
If you are running official linux 64-bit client, no further action is necessary. Other users should avoid sending transactions before upgrading client once the official builds become available.
Official windows build of v0.4.1 RC1 has been started. Once it is ready I will post another update.[/quote]
Also this could be clarified with more information about the correct version. I thought I had a relatively new (thought not official) version and 64 bit on Linux so I thought I was safe. Of course I should have spent some time and effort to read a bit more into the details and versions.
I had a 32 bit machine machine running which was stuck with the error message⌠I shut that down and started the 64 bit installation when I first read about this problem on the 13. My 64 bit version has no error message but there is definitely something wrong.
Will get the latest from github and have the blockchain checked a bit more aggressively on restarting.
- Lyddite
ppcoind@dell:~$ ppcoind getinfo
{
"version" : "v0.4.0ppc-23-g57b8c8d-dirty-beta",
"protocolversion" : 60004,
"walletversion" : 60000,
"balance" : xxxxxxxxxxxxx,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 204897,
"moneysupply" : 22752131.33696300,
"connections" : 8,
"proxy" : "",
"ip" : "xxxxxxxxxxxxxxxxx",
"difficulty" : 90945646.23639995,
"testnet" : false,
"keypoololdest" : 1447399623,
"keypoolsize" : 101,
"paytxfee" : 0.01000000,
"errors" : ""
}
ppcoind@dell:~$ ppcoind getpeerinfo
[
{
"addr" : "66.150.105.77:9901",
"services" : "00000001",
"lastsend" : 1447593161,
"lastrecv" : 1447592914,
"conntime" : 1447399627,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 205065,
"banscore" : 0
},
{
"addr" : "198.15.82.166:9901",
"services" : "00000001",
"lastsend" : 1447592822,
"lastrecv" : 1447592822,
"conntime" : 1447399634,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-23-g57b8c8d-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 204784,
"banscore" : 0
},
{
"addr" : "76.74.177.224:9901",
"services" : "00000001",
"lastsend" : 1447593159,
"lastrecv" : 1447592914,
"conntime" : 1447399634,
"version" : 70001,
"subver" : "/Satoshi:0.8.6/Peercoin:0.4.0(v0.4.0ppc-1911-gc627cbc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 205065,
"banscore" : 0
},
{
"addr" : "75.161.31.167:9901",
"services" : "00000001",
"lastsend" : 1447592822,
"lastrecv" : 1447593159,
"conntime" : 1447399635,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.1(v0.4.1.0-g2c87899-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 205065,
"banscore" : 0
},
{
"addr" : "114.215.118.148:9901",
"services" : "00000001",
"lastsend" : 1447592822,
"lastrecv" : 1447592914,
"conntime" : 1447399648,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.1(v0.4.1ppc.rc1-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 205065,
"banscore" : 0
},
{
"addr" : "159.203.1.189:9901",
"services" : "00000001",
"lastsend" : 1447592822,
"lastrecv" : 1447592914,
"conntime" : 1447399665,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 205065,
"banscore" : 0
},
{
"addr" : "178.62.124.13:9901",
"services" : "00000001",
"lastsend" : 1447593109,
"lastrecv" : 1447593109,
"conntime" : 1447399673,
"version" : 60004,
"subver" : "/ppcwire:0.2.0/ppcd:0.11.0/",
"inbound" : false,
"releasetime" : 0,
"height" : 204784,
"banscore" : 0
},
{
"addr" : "146.185.137.249:9901",
"services" : "00000001",
"lastsend" : 1447592822,
"lastrecv" : 1447592915,
"conntime" : 1447406195,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 205080,
"banscore" : 0
}
]
ppcoind@dell:~$ uname -a
Linux dell 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64 GNU/Linux
ppcoind@dell:~$ openssl version
OpenSSL 1.0.1k 8 Jan 2015
ppcoind@dell:~$
[quote=âderelle, post:44, topic:3691â]Hmm, missing exactly 100 PPC in my PeercoinQT v0.4.0 linux 64 bit walletâs balance. No transaction record for the missing 100 PPC. A minting credit of 1.35 PPC was posted Nov 14 @ 13:58, but needs more confirmations before that will show up in my balance. Any advice, re. the missing 100PPC?
OK, maybe I can relax. A stake of 101.37 PPC has now shown up in a refreshed wallet. Whew, never seen that before.[/quote]
You just minted a Peercoin block and got your 1% reward⌠i take it you have had that 100PPC in that address for over a year now with 1.37% interest earnt?
Fuzzybear
Hahaha, must have just minted another Peercoin block - thanks for the heads up FuzzyBear. This time approx. 210 PPC reduced from my balance, along with a minting credit of .33 PPC. What is initially unnerving is the delay before a notification of stake appears in the wallet, to account for the missing balance amount. Confirmation apparently requires the processing of 520 blocks which probably explains it. When the .33 PPC credit is confirmed, my stake balance will probably update too.
This is new territory for me. I need to do my homework on this to understand the process more fully.
Thanks for your comments which helped put me at ease.
[quote=âmhps, post:48, topic:3691â]will
sudo git clone https://github.com/ppcoin/ppcoin.git
get me the correct source code?[/quote]
I got v0.5.0ppc.rc1-beta oh well it doesnât have the bug fix. Time to help test o.5 then.
Hi folks,
Could I just check. I clicked on the link for the upgrade 0.4.1rc1, and installed this. I didnât realise I had to deleted the original version first. The qt seems to be the 0.4.1rc1 version, but is still showing the message Warning checkpoint is too old etc. It says last block was 205138 downloaded 52 minutes ago. What should I do?
Many thanks,
Roister
[quote=âsandakersmann, post:33, topic:3691â][quote=âjreacher, post:30, topic:3691â]I am a newbie and just started 3 days ago with Peerunity, version 0.1.1 on Windows 10, 64-bit version installed I am also having the same invalid checkpoint.
Can any give me directions how I can solve the problem ?[/quote]
You must uninstall Peerunity 0.1.1 and then install Peercoin 0.4.1 RC1:
http://downloads.sourceforge.net/project/ppcoin/0.4.1%20RC1/ppcoin-0.4.1rc1-win32-setup.exe[/quote]
I am a bit confused by this, as it is recommending going from Peerunity to PPCoin. Is it not better, if one is on Peerunity, to go to Peerunity-0.1.3-RC1?
Yes, you are correct. I made that recommendation before Ben had made builds for Peerunity-0.1.3-RC1.
I have the same warning message âcheckpoint is too oldâ and Iam already using Peerunity v0.1.3-RC1-2-gb53729b. The strange thing is that the installler installed only a 32 bit version of the program although I am using 64 bit OS (Windows 10).
I compiled v0.4.1ppc.rc1-beta on Raspberry Pi (os is raspbian), redownloaded the blockchain, and it was able to run in minting mode for several days.
Today I moved the Pi to a new LAN where my peerbox used to run, and i get this error message a few minutes after starting ppcoind -daemon
ppcoind: kernel.cpp:427: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == hashGenesisBlock' failed.ppcoind dies instantly
the last lines in debug.log
Loading block index...
PPCoin Network: genesis=0x0000000032fe677166d5 nBitsLimit=0x1d00ffff nBitsInitial=0x1c00ffff nStakeMinAge=2592000 nCoinbaseMaturity=500 nModifierInterval=21600
had the same problem with nud
Ok updated to Peerunity v0.1.3-RC1-2-gb53729b, deleted everything prior to getting current wallet. Used saved wallet.dat from 3 weeks ago, still getting checkpoint to old error and will not update blocks past 205238. Please advise as I would love to be on the right chain and have a working wallet.
Have you tried deleting the old blockchain files and redownload the full blockchain? That worked for me
Cleared everything out, rebooted the system and then did fresh install of new wallet. It appears it is synced now, but the numbers do not match like they used to between âcurrent number of blocksâ and âestimated total blocksâ ⌠this is where my concern is now. shows current number of blocks @208107 and Estimated @205210 ⌠I am assuming I am now on the correct blockchain and this will correct itself.
I think the âestimated total blocksâ is a mean (or median) height of all the nodes youâre connected to, so itâs not always going to be accurate.
Note to say we need to contact anyone if possible that we can see or detect has the wrong fork just as there was a block explorer I saw on wrong chain.
Fuzzybear
Sent from my HTC Desire using Tapatalk 2