Update address filter hashing to match provider spec - NIT-4754#183
Merged
joshuacolvin0 merged 1 commit intomasterfrom Apr 4, 2026
Merged
Conversation
Member
|
@clabot check |
Member
|
closing and re-opening to trigger cla-bot |
auto-merge was automatically disabled
April 4, 2026 22:53
Pull request was closed
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
3 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.
Summary
scripts/config.tsto match nitro#4586crypto.randomUUID())SHA256(salt_bytes + addr_bytes)to stringSHA256("{uuid}::0x{address}")docker-compose.yaml(curl→mc ready local)Testing
3ccf0cbf-..., address:0xddfAbCdc..., expected hash:0x8fb74f22...)--l2-tx-filtering, added address to filter list, confirmed tx was rejected, removed address, confirmed tx succeeded again