[Pushers L01]Missing Zero-Address Check in Linea and Scroll Buffer Constructors #68
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.
The LineaBuffer and ScrollBuffer constructors do not validate that the pusher_ argument is non-zero, while ZkSyncBuffer enforces this check at deployment time. Although both Linea and Scroll buffers perform this validation at runtime within their receiveHashes functions, the absence of a constructor check allows deployment of a non-functional buffer that would revert on every call. Similarly, zero address checks are missing in the constructors of LineaPusher, ScrollPusher and ZkSyncPusher.
Consider adding a zero-address check for the pusher argument in the constructors of LineaBuffer and ScrollBuffer to fail fast at deployment and maintain consistency across all buffer implementations. Likewise, consider including similar validations for the constructors of LineaPusher, ScrollPusher, and ZkSyncPusher. Additionally, consider removing this check within the execution of each receiveHashes function, as the value of the _pusher account would already be checked upon deployment.
Summary by CodeRabbit
Release Notes
New Features
Improvements
Tests