Ensv2 deploys a new L2ReverseRegistrar contract on each of the well-known L2 chains and then migrates data from the v1 contract to the v2 contract.
from an indexing perspective, the v1 contract is source-of-truth until ENSv2 is activated, after which the v2 contract is source of truth.
annoyingly, we likely need to index both contracts in parallel and then during resolution, if ENSv2 is active, use the v2 contract-derived primary names.
after ensv2 is activated, the next release of ensnode can remove the knowledge and indexing of the v1 L2ReverseRegistrar contracts and just index the v2 versions
Ensv2 deploys a new
L2ReverseRegistrarcontract on each of the well-known L2 chains and then migrates data from the v1 contract to the v2 contract.from an indexing perspective, the v1 contract is source-of-truth until ENSv2 is activated, after which the v2 contract is source of truth.
annoyingly, we likely need to index both contracts in parallel and then during resolution, if ENSv2 is active, use the v2 contract-derived primary names.
after ensv2 is activated, the next release of ensnode can remove the knowledge and indexing of the v1
L2ReverseRegistrarcontracts and just index the v2 versions