Display named smart contracts on L2 chains

ENS best practice details

When users interact with a contract on an L2 chain, use the ENSIP-19 standard to lookup the primary name of the contract. ENSIP-19 provides chain-specific primary names for L2 networks (including Optimism, Arbitrum, Base, Linea, and Scroll), with an automatic fallback to a default primary name (defined on mainnet) if no chain-specific primary name is defined. There are several libraries to choose from that support ENSIP-19 and all ENS best practices:

• ensnode-sdk (v1.0.0+)
• ensnode-react (v1.0.0+)
• Viem (v2.35.0+)
• Wagmi (v2.18.0+)

Libraries and tools for additional languages or frameworks can be found in the ENS documentation.

Additional Details

ENSIP-19 enables primary names to be set on any chain. Contracts deployed to an L2 chain benefit from this, as the contract can then configure its name directly on the chain it is deployed to without any need to update state on mainnet. If a contract has an ENS name, you can use the contract's ENS profile to power additional UX improvements such as displaying the contract's avatar, metadata, audit information, and more. More information can be found at this ENSIP.