chore: use slim postage snapshot from batch-archive v0.1.0 - #5587
Merged
Conversation
gacevicljubisa
changed the title
akrem-chabchoub
approved these changes
Sep 2, 2026
aloknerurkar
approved these changes
Sep 2, 2026
sbackend123
approved these changes
Sep 3, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Checklist
Description
The snapshot is produced by ethersphere/batch-export, whose default slim encoding carries only the types.Log fields Bee reads today: address, topics, data, blockNumber, transactionHash (and logIndex). Any other field — BlockHash, TxIndex, Removed — decodes to its zero value here with no error.
Before consuming a new types.Log field anywhere downstream of this filterer (FilterLogs callers, listener.processEvent, transaction.ParseEvent), extend SlimLog in batch-export's pkg/filestore and republish the snapshot first; otherwise the field is silently empty for snapshot-sourced logs.
This currently reduces snapshot for 4MB.
Open API Spec Version Changes (if applicable)
Motivation and Context (Optional)
Related Issue (Optional)
Screenshots (if appropriate):
AI Disclosure