fix(ensindexer): post-transaction reverse address healing #729
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.
This PR attempts healing over 35k unhealed reverse addresses that were created by proxy contracts instantiated from:
These 35k reverse addresses could not be successfully healed while handling their relevant
NewOwnerevent, as the ReverseRegistry contract would create reverse address labelhash based onmsg.senderwhich, in this case, is a newly-created wallet proxy contract address. This particular address is not available in theNewOwnerevent handler.Thankfully, there's
WalletCreatedevent emitted as the very last event during the given transaction.Debug info
Feel free to check transaction traces with
cast. For example: