Missing 1 bitcoin block download causes subsequent blocks to fail #572
Assignees
Labels
Comments
MicaiahReid
added a commit
that referenced
this issue
May 7, 2024
MicaiahReid
added a commit
that referenced
this issue
May 8, 2024
github-actions bot
pushed a commit
that referenced
this issue
May 9, 2024
## [1.6.0](v1.5.1...v1.6.0) (2024-05-09) ### Features * add Bitcoin transaction index to typescript client ([#568](#568)) ([6f7eba4](6f7eba4)) ### Bug Fixes * add stacks event position to ts client ([#575](#575)) ([3c48eeb](3c48eeb)) * add starting stacks height for prometheus metrics ([#567](#567)) ([6a8c086](6a8c086)) * make bitcoin payload serialization deserializable ([#569](#569)) ([5f20a86](5f20a86)) * set `Interrupted` status for streaming predicates that fail ([#574](#574)) ([11bde53](11bde53)), closes [#523](#523) * shut down observer on bitcoin block download failure ([#573](#573)) ([f3530b7](f3530b7)), closes [#572](#572)
|
🎉 This issue has been resolved in version 1.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
vabanaerytk
added a commit
to vabanaerytk/chainhook
that referenced
this issue
Aug 7, 2024
## [1.6.0](hirosystems/chainhook@v1.5.1...v1.6.0) (2024-05-09) ### Features * add Bitcoin transaction index to typescript client ([#568](hirosystems/chainhook#568)) ([2ca8608](hirosystems/chainhook@2ca8608)) ### Bug Fixes * add stacks event position to ts client ([#575](hirosystems/chainhook#575)) ([3a9b1fb](hirosystems/chainhook@3a9b1fb)) * add starting stacks height for prometheus metrics ([#567](hirosystems/chainhook#567)) ([b2296aa](hirosystems/chainhook@b2296aa)) * make bitcoin payload serialization deserializable ([#569](hirosystems/chainhook#569)) ([4c0c03b](hirosystems/chainhook@4c0c03b)) * set `Interrupted` status for streaming predicates that fail ([#574](hirosystems/chainhook#574)) ([11282b0](hirosystems/chainhook@11282b0)), closes [#523](hirosystems/chainhook#523) * shut down observer on bitcoin block download failure ([#573](hirosystems/chainhook#573)) ([db1c566](hirosystems/chainhook@db1c566)), closes [#572](hirosystems/chainhook#572)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes when the Chainhook service receives a
new_burn_block, it then fails to download the block.I'm not entirely sure why this happens, as the same block will be downloaded (at pretty much the exact same time) by Ordhook.
But, when this does happen, because we have a gap in our fork pool, we fail to append all future bitcoin blocks. We should:
The text was updated successfully, but these errors were encountered: