Address Lookup

The ENS Protocol aims to make it easy to use Ethereum. It does this by providing a simple way to use human-readable names instead of long machine-readable addresses.

Getting the users Ethereum Address
Forward Lookup

The goal here is to take a name, such as nick.eth, and convert it to an address, such as 0x225f137127d9067788314bc7fcc1f36746a3c3B5.

luc.eth➡️0x225...c3B5

The simplest thing you can do is start with a name, and resolve it to an address. We call this a "forward lookup". Think of places where users can enter names, such as sending transactions, chatting, etc.

Note that all dot-separated strings should be treated as potential ENS names, since ENS supports many TLDs. A common mistake is to only treat strings that end in .eth as ENS names.

Forward Resolution

import { useAccount, useEnsName, useEnsAvatar } from "wagmi";

export const Name = () => {
    const { data: ensName } = useEnsAddress({
        address: "luc.eth", // The name to lookup
        chainId: 1, // The chainId to lookup on
    });

    return <div>{ensName || address}</div>;
};

Try it out

import { normalize } from "viem/ens";
import { publicClient } from "./client";

const ensAddress = await publicClient.getEnsAddress({
    name: normalize("luc.eth"),
});

Try it out

package main

import (
	"fmt"

	"github.com/ethereum/go-ethereum/ethclient"
	ens "github.com/wealdtech/go-ens/v3"
)

func main() {
	client, _ := ethclient.Dial("https://rpc.ankr.com/eth")

	domain, _ := ens.Normalize("luc.eth")
	resolver, _ := ens.NewResolver(client, domain)
	address, _ := resolver.Address()

	fmt.Println("Address:", address.Hex())
}

// Setup: npm install alchemy-sdk
import { Alchemy, Network } from "alchemy-sdk";

const config = {
    apiKey: "<-- ALCHEMY APP API KEY -->",
    network: Network.ETH_MAINNET,
};
const alchemy = new Alchemy(config);

alchemy.core.resolveName("vitalik.eth").then(console.log);

import { http } from "viem";
import { mainnet } from "viem/chains";
import { createEnsPublicClient } from "@ensdomains/ensjs";

const client = createEnsPublicClient({
    chain: mainnet,
    transport: http(),
});

const subgraphRecords = client.getSubgraphRecords({ name: "ens.eth" });

const records = client.getRecords({
    name: "ens.eth",
    records: {
        coins: [...(subgraphRecords?.coins || []), "BTC", "ETH", "ETC", "SOL"],
        texts: [
            ...(subgraphRecords?.texts || []),
            "avatar",
            "email",
            "description",
        ],
        contentHash: true,
        abi: true,
    },
});

To learn what happens under the hood when you do a forward lookup, read the resolution section.

Multi-Chain Addresses (BTC, LTC, etc)
Multi-Chain

ENS Names aren't just limited to storing Ethereum addresses. Any blockchain address (BTC, LTC, SOL, etc.) can be queried by SLIP-0044 coin type or a value derived from an EVM Chain ID (specified in ENSIP-11). This includes Ethereum L2 networks such as OP Mainnet and Base.

For EVM Chains besides Mainnet Ethereum, always use its ENSIP-11 coin type, irrespective of being included in SLIP-0044 (like Ether Classic).

The standardization of multichain addresses was first introduced in ENSIP-9, and also EIP-2304.

Multichain Address Lookup

import { useAccount, useEnsAddress, useEnsAvatar, useEnsName } from 'wagmi';
import { formatAddress } from '@ens-tools/format';

export const MyAddresses = () => {
    const { data: name } = useEnsName({ address: "0x225f137127d9067788314bc7fcc1f36746a3c3B5" });

    // SLIP-0044 Coin Types
    const { data: bitcoin } = useEnsAddress({ name, coinType: 0 });
    const { data: litecoin } = useEnsAddress({ name, coinType: 2 });
    const { data: solana } = useEnsAddress({ name, coinType: 501 });

    // EVM Chain IDs (see ENSIP-9)
    const { data: optimism } = useEnsAddress({ name, coinType: 2147483658 });
    const { data: base } = useEnsAddress({ name, coinType: 2147492101 });
    const { data: polygon } = useEnsAddress({ name, coinType: 2147483658 });
    const { data: arbitrum } = useEnsAddress({ name, coinType: 2147525809 });

    return <div>{JSON.stringify({ name, bitcoin, litecoin, solana, optimism, base, polygon, arbitrum })}</div>;
};

Try it out

Network	Coin Type
Bitcoin	0
Litecoin	2
Dogecoin	3
Ethereum	60
Solana	501
OP Mainnet	2147483658
Polygon	2147483785
Base	2147492101
Arbitrum One	2147525809

... and many many more following SLIP-0044 and ENSIP-11

Decoding Address Hashes

ENS resolvers store all addresses in bytes, which may have to be encoded to their respective address formats. To do this, we recommend using the @ensdomains/address-encoder package.

Advanced

In-Depth ResolutionTo learn more about the resolution process, please read the Resolution section.Advanced

Address Lookup

Getting the users Ethereum AddressForward Lookup

Multi-Chain Addresses (BTC, LTC, etc)Multi-Chain

Decoding Address Hashes

Advanced

Getting the users Ethereum Address
Forward Lookup

Multi-Chain Addresses (BTC, LTC, etc)
Multi-Chain