Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Author

Topic: Orphaned blocks & client propagating them? (Read 862 times)

zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
Orphaned blocks & client propagating them?
August 07, 2014, 07:59:05 PM
#2
I guess normally I would only receive 3190 because I didn't have it & it became part of the new longest chain?  Except blockchain.info has my IP as being first on both of those... so, where did 3190 exist prior?

oh... I can answer my own question, I think.  The 3190 was probably just propagated to a handful of IPs, but the same pool happened to get the next block.. so that's how blockchain.info could have IP as first on both.

So, ah, move this to service discussion?  The technical problem is solved, but there's still the issue of blockchain.info being confusing as hell on orphans  Undecided

ed: well, I guess there's still the issue of the 314442 reorg
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
Re: Orphaned blocks & client propagating them?
August 07, 2014, 07:48:21 PM
#1
Blockchain.info's report of orphaned blocks is screwy, atm...  blockexplorer doesn't list them afaik?  Is there a better place to view them?

Anyway,

Code:
2014-08-07 20:50:52 Requesting block 000000000000000015cc5bc028f347b03240358492a1da6cf0833515737ac943
2014-08-07 20:50:52 received block 000000000000000015cc5bc028f347b03240358492a1da6cf0833515737ac943
2014-08-07 20:50:52 UpdateTip: new best=000000000000000015cc5bc028f347b03240358492a1da6cf0833515737ac943  height=314442  log2_work=80.082099  tx=44073587  date=2014-08-07 20:56:39 progress=1.000012
2014-08-07 20:57:18 Requesting block 00000000000000002a808c7027f018b2beb9ea6d95980f95aa9693b2bd758ddf
2014-08-07 20:57:18 received block 00000000000000002a808c7027f018b2beb9ea6d95980f95aa9693b2bd758ddf
2014-08-07 20:57:18 UpdateTip: new best=00000000000000002a808c7027f018b2beb9ea6d95980f95aa9693b2bd758ddf  height=314443  log2_work=80.08219  tx=44074068  date=2014-08-07 20:57:08 progress=1.000000
2014-08-07 20:58:57 Requesting block 0000000000000000060584a105973230e6ab3b6c024479e613b65a436da471b4
2014-08-07 20:58:57 received block 0000000000000000060584a105973230e6ab3b6c024479e613b65a436da471b4
2014-08-07 20:58:57 ProcessBlock: ORPHAN BLOCK 0, prev=00000000000000003190b2158feaa9dc7904d20a980b4bdd0fb8e9c9b68c2f7d
2014-08-07 20:58:57 Requesting block 00000000000000003190b2158feaa9dc7904d20a980b4bdd0fb8e9c9b68c2f7d
2014-08-07 20:58:57 received block 00000000000000003190b2158feaa9dc7904d20a980b4bdd0fb8e9c9b68c2f7d
2014-08-07 20:58:57 UpdateTip: new best=000000000000000015cc5bc028f347b03240358492a1da6cf0833515737ac943  height=314442  log2_work=80.082099  tx=44073587  date=2014-08-07 20:56:39 progress=0.999995
2014-08-07 20:58:57 UpdateTip: new best=00000000000000003190b2158feaa9dc7904d20a980b4bdd0fb8e9c9b68c2f7d  height=314443  log2_work=80.08219  tx=44074077  date=2014-08-07 20:57:19 progress=0.999996
2014-08-07 20:58:57 UpdateTip: new best=0000000000000000060584a105973230e6ab3b6c024479e613b65a436da471b4  height=314444  log2_work=80.082281  tx=44074218  date=2014-08-07 20:58:50 progress=1.000000

I apparently broadcasted both the 6058 and the 3190 block, since blockchain.info has my IP as being the 'first' on both.  

questions, 1) how did I process the orphan block before receiving it?  2)  why did it reorg block #314442, when I already had 15cc as 314442?

actually... wtf, why does it say 3190 is orphan, when it is 314443, and 6058 is 314444?

Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Jump to: