Closed
Description
original issue at gnarly
If we are following the chain but then stop processing during a short-lived fork, once we restart the process the blockstream queue will be empty so it will blindly trust that the next block it sees is the main chain because it can't do any resolution since it doesn't know the blocks before that to calculate longest chain.
- Are there any solutions for this?
- Could we have an option to provide which block should blockstream start on so then we could simply go -10 blocks
Metadata
Metadata
Assignees
Labels
No labels