Omnigraph: ENSv2 L2ReverseRegistrars

[shrugs]

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

[coderabbitai]

🔗 Related PRs

#1566 - feat: separate ensv2 datasources out more correctly [merged]
#1575 - fix: add correct ensv1 and ensv2 addresses to sepolia-v2 namespace [merged]
#1659 - ENSv2: Refactor Namechain [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!