B16: Validate block lookup identities - #784
Closed
KillariDev wants to merge 1 commit into
Closed
Conversation
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
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.
Summary
Why
An RPC endpoint could return a structurally valid block for the wrong height. The client previously accepted it, so callers could act on unrelated block data and replacement detection could report a transaction from a height it never requested.
Validation
bun test shared/ts/ethereum.test.ts --timeout=600000(2 expected failures)bun test shared/ts/ethereum.test.ts --timeout=600000(33 pass)bun run tscbun run ensure-contract-artifacts && bun run check:shared-dependencies && bun run test:run -- --bail=1 --timeout=600000(3252 pass, 16 skip)bun run format:checkbun run check:changedbun run knipgit diff --checkFinal review: 100/100, no findings. Branch was current with
origin/mainat publication.