​
Developer Integration

Caldera domains are designed for seamless developer integration, leveraging full compatibility with the Ethereum Name Service (ENS) ecosystem. Every .era domain is automatically accessible through the .calderans.eth subdomain alias, allowing developers to utilize existing ENS tooling and libraries without modification. This compatibility means that applications already supporting ENS can immediately recognize and resolve .era domains, eliminating the need for custom implementation work. Developers can simply use standard ENS resolution methods to query user information, retrieve addresses, and access other on-chain data associated with .era domains, making the integration process straightforward and efficient across any Caldera chain.

​
Integration with ethers.js

Integrating .era domains with ethers.js is straightforward due to ENS compatibility. Developers can resolve .era domains to Ethereum addresses using the standard ENS resolution methods provided by ethers.js. When a user enters a domain like “username.era”, simply replace “.era” with “.calderans.eth” to create the ENS-compatible format and resolve it using the provider’s built-in resolver.

A basic example for .era domain lookup:

const ETH_L1_RPC = "example.rpc.ethereumrpc.com"; // Ethereum L1 RPC of your choice
const provider = new ethers.providers.JsonRpcProvider(ETH_L1_RPC);

const input = "demo.era";
const ensInput = input.replace('.era', '.calderans.eth');
const address = await provider.lookupAddress(ensInput);

​
Integration with wagmi

Integrating .era domains with wagmi is equally simple thanks to ENS compatibility. The wagmi hooks provide built-in support for ENS resolution, making it easy to resolve .era domains in React applications. Similar to the ethers.js approach, you’ll need to convert the .era domain to its .calderans.eth equivalent.

A basic example for .era domain lookup using wagmi:

import { useAccount, useEnsAvatar, useEnsName } from 'wagmi'

const input = "demo.era";
const ensInput = input.replace('.era', '.calderans.eth');
 
export const Name = () => {
  const { data: ensName } = useEnsAddress({
    address: ensInput, // The name to lookup
    chainId: 1,
  })
 
  return <div>{ensName}</div>
}

​
Using Other Libraries

Since .era domains are fully compatible with ENS, you can use any ENS-compatible library to resolve and interact with these domains. Simply convert the .era domain to its .calderans.eth equivalent as shown in the examples above.

For comprehensive documentation on integrating ENS with various libraries and frameworks, refer to the official ENS documentation:

These resources provide detailed guides for implementing ENS resolution across different programming languages and environments, all of which can be adapted for use with .era domains by applying the domain conversion pattern shown above.