Multichain: Resolve Issues with ENS Resolution and Address Book

[darkwing]

What is this about?

At present, the address book is current keyed off of chainId. In a multichain world, this structure will be problematic.

This issue represents coordination with Identity team and tracking progress on resolving the issue.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• [ ] Engineering (needed in most cases)
• [ ] Design
• [ ] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

No response

[Matt561]

Related issue - https://github.com/MetaMask/MetaMask-planning/issues/3561

[Matt561]

@darkwing do you know how far along the multi-chain effort is? I'm new to the identity team and want to gauge the priority of this item. I don't want this being a blocker.