JL0z
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 17, 2014, 11:41:50 PM |
|
Hi Everyone,
About 10 hours ago, I was just checking the mining pool and noticed that the current block had jumped to 39745, when earlier in the day, it was at 39725. I noticed that the pool found blocks were all orphaned. Then I checked my wallet - sure enough, back to 39745. The debug log shows that a number of blocks came through at 39679 that invalidated the previous chain. We must have forked back then - a group of us went on to 39745, and others had gone to 39700 or so, when mining was continued to 39725.
I had moved from the 39745 blockchain because I wanted to transfer coins to Cryptsy. Now it appears that Cryptsy is also on the 39745 blockchain.
What this means is that any transactions that occurred on the blockchain from 39679 to 39725 on the other blockchain have now disappeared, but if the wallet has sync'ed to 39745 - the transactions would resend.
The current block is now 39748 - just 15 minutes ago.
getpeerinfo shows:
[ { "addr" : "54.201.183.106:8550", "services" : "00000001", "lastsend" : 1400369407, "lastrecv" : 1400369714, "conntime" : 1400368698, "version" : 60001, "subver" : "/Satoshi:0.6.5.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 39747, "banscore" : 0 }, { "addr" : "50.149.31.242:8550", "services" : "00000001", "lastsend" : 1400369692, "lastrecv" : 1400369406, "conntime" : 1400368702, "version" : 60001, "subver" : "/Satoshi:0.6.4.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 39747, "banscore" : 0 } ]
getmininginfo shows:
{ "blocks" : 39748, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 7.19571781, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 858267, "pooledtx" : 1, "testnet" : false }
Any comments anyone?
|