Timeline for Getting orphaned Blocks from the Blockchain
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 19, 2012 at 6:11 | history | bounty ended | cdecker | ||
Jul 19, 2012 at 6:11 | vote | accept | cdecker | ||
Jul 18, 2012 at 22:07 | comment | added | theymos | @cdecker Here's my printblocktree output on a node that's been running for a very long time: mirrorcreator.com/files/1EB4UZDD/printblocktree.txt.bz2_links | |
Jul 18, 2012 at 9:11 | comment | added | cdecker | That confirms what I was seeing. So if there is no archive that kept a log of all transactions I won't be able to reconstruct forks at all, right? Blockchain.info only has forks back to block 142257. Any idea where I can find more? | |
Jul 18, 2012 at 9:08 | vote | accept | cdecker | ||
Jul 18, 2012 at 9:08 | |||||
Jul 17, 2012 at 19:50 | comment | added | theymos | @cdecker Blocks are only relayed across the network once; nodes won't relay a block if it has already been seen or if it doesn't extend the currently-longest chain. So nodes that aren't online when a block is broadcast won't see it unless it becomes part of the main chain. | |
Jul 17, 2012 at 9:03 | comment | added | cdecker | Uh, I didn't think about them not being stored on nodes that haven't seen them in the original broadcast. So nodes that weren't online when the orphaned blocks still had a chance of becoming legit will never see it? How long has the orphaned node to be abandoned until it is no longer announced? | |
Jul 13, 2012 at 0:27 | history | edited | theymos | CC BY-SA 3.0 |
added 6 characters in body
|
Jul 12, 2012 at 19:22 | history | answered | theymos | CC BY-SA 3.0 |