json rpc – Acquiring historic orphaned blocks (chaintips) with out outdated node

0
57


I am trying to perform a little research surrounding orphaned blocks inside the Bitcoin community. From my understanding the most effective and actually solely approach to receive knowledge for blocks that not exist in the primary chain/department (together with orphaned blocks) is to execute the getchaintips RPC command. This command seems to be depending on how lengthy the precise node has been working (as blocks that aren’t in the primary chain don’t have any purpose to be downloaded to newer nodes).

Sadly, I not have entry to the node or knowledge I had setup in 2013 and due to this fact I’ve a restricted set of orphaned blocks to cope with (my present node is barely a number of months outdated).

Alternatively, I’ve ran this command on a web-based RPC question right here however the earliest recorded block peak is 283,421. Fortunately, this additionally permits me to question getblock and truly view the data from the discarded blocks, however doesn’t listing any blocks earlier than 283,421 (Mined in January of 2014).

The net block explorer Blockchain.data retains monitor of orphaned blocks however sadly they solely return to dam #291,122.

Whereas doing a little bit of googling, I used to be capable of finding extra of an “intensive” listing on PasteBin which dates again to dam peak 179,641. Nonetheless, I can not use getblock on any of those hashes from my node because it was not in existence when these blocks had been initially mined.


My query: Are there any methods to question blocks which have been discarded or orphaned with out requiring a node sufficiently old to witness them?

LEAVE A REPLY

Please enter your comment!
Please enter your name here