Skip to content

chore: use slim postage snapshot from batch-archive v0.1.0 - #5587

Open
gacevicljubisa wants to merge 1 commit into
masterfrom
batch-export
Open

chore: use slim postage snapshot from batch-archive v0.1.0#5587
gacevicljubisa wants to merge 1 commit into
masterfrom
batch-export

Conversation

@gacevicljubisa

@gacevicljubisa gacevicljubisa commented Sep 1, 2026

Copy link
Copy Markdown
Member

Checklist

  • I have read the coding guide.
  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

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

  • This PR contains code that has been generated by an LLM.
  • I have reviewed the AI generated code thoroughly.
  • I possess the technical expertise to responsibly review the code generated in this PR.

@gacevicljubisa gacevicljubisa changed the title chore: use postage snapshot from batch-archive v0.1.0 chore: use slim postage snapshot from batch-archive v0.1.0 Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants