feat(hardano): implement immutable db chunk parsing #328
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
25 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The immutable db (confirmed blocks) of the Haskell node is based on a custom file format that relies on storing blocks as cbor in a sequential file, while keeping some extra indexes in separate files.
This PR introduces a naive approach for streaming blocks from these files.
Why do we need it in Pallas?
Because it's the format used in Mithril snapshots ;)
PS:
Hardanois a temporal name we'll be using to refer to the Haskell implementation of the Cardano node until a better name appears.