certain features implied by the ENS team require the reverse mapping of node -> Name, which requires materialization of the canonical registries and a domain's canonicalNode and canonicalName.
perhaps a difficult/complex task within ENS protocol semantics additionally constrained by ponder primary-key-only cache semantics but would very much improve query-time performance, so perhaps worth it.
also unblocks "names pointing to this address" which needs to map from a resolver record (keyed by node) to a name. perhaps doable in ensv2 without the reverse mapping since names are in input to resolvers, but need to check the events in PermRes. #1962
certain features implied by the ENS team require the reverse mapping of node -> Name, which requires materialization of the canonical registries and a domain's canonicalNode and canonicalName.
perhaps a difficult/complex task within ENS protocol semantics additionally constrained by ponder primary-key-only cache semantics but would very much improve query-time performance, so perhaps worth it.
also unblocks "names pointing to this address" which needs to map from a resolver record (keyed by node) to a name. perhaps doable in ensv2 without the reverse mapping since names are in input to resolvers, but need to check the events in PermRes. #1962