group logs by transaction hash when calculating bloom filter #244
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.
TL;DR
Improved logs bloom calculation to properly group logs by transaction and maintain order.
What changed?
Modified the
CalculateLogsBloom
function to:How to test?
Why make this change?
The previous implementation treated all logs as if they belonged to a single transaction, which doesn't match Ethereum's approach of calculating bloom filters per transaction first. This change ensures our bloom filter calculation matches Ethereum's specification, where each transaction's logs contribute to the block bloom filter in the correct order, improving compatibility with Ethereum clients.