[audit2] #11 Add reverse node claim to L2 Resolver #81
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.
From spearbit:
Missing explicitly claiming the reverse resolution record for L2Resolver
Status: New
Severity: Informational
AkshaySrivastav
AkshaySrivastav
created on Jul 22, 2024 at 05:52
Description
The current implementation of L2Resolver contract does not claim the reverse resolution record for itself explicitly.
Ideally just like RegistrarController, EARegistrarController & ENS's PublicResolver reverse record should be explicitly claimed for L2Resolver during its construction.
Recommendation
Add the IReverseRegistrar.claim call in L2Resolver::constructor: