ENS naming for contracts

[abhijeetbhagat]

Motivation

this issue #10604

Solution

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[zerosnacks]

Hi @abhijeetbhagat thanks for your PR,

In my opinion, as a principle Foundry does not directly integrate third party services to remain a neutral actor. I am against recording metrics from users and collecting possibly identifying data such as IP addresses.

[conor10]

Thanks for your comment @zerosnacks, we have two motivations for connecting to the service:

1. To provide the necessary ENS contract configuration for the various networks we support. Otherwise this will need to be provided by the user, or stored in Foundry. This would impact UX for users, as there's a number of contract addresses that are required, and they may change. Hence users may misconfigure the contracts, also Foundry could end up with out of date configuration as contract addresses can change.
2. To capture which contract ENS names are being registered by the service. This is so we can measure adoption. We are not trying to capture any information that doesn't end up onchain. If we can't measure adoption of the service, its much harder for us as a team to demonstrate traction and impact.