Skip to content

Conversation

@pepebndc
Copy link
Collaborator

Closes #34

Copy link
Collaborator

@0xNeshi 0xNeshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work, approving in advance

pepebndc and others added 2 commits September 23, 2025 12:45
Co-authored-by: Nenad <nenad.misic@openzeppelin.com>
Co-authored-by: Nenad <nenad.misic@openzeppelin.com>
Copy link
Collaborator

@LeoPatOZ LeoPatOZ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@pepebndc pepebndc merged commit 389cd77 into main Sep 23, 2025
6 checks passed
@pepebndc pepebndc deleted the 34-block-range-scanner-should-return-rangeinclusive-instead-of-range branch September 23, 2025 10:49
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.

Block Range Scanner Should Return RangeInclusive instead of Range

4 participants