Guides

Resolving ENS names

ENS resolution is multi-step: namehash(name) → resolver lookup → addr / text / contenthash calls. The @ethernauta/ens package composes these into the high-level functions a dapp actually wants.

import {
  get_ens_address,
  get_ens_name,
  get_ens_text,
  get_ens_avatar,
  ens_normalize,
} from "@ethernauta/ens";
import { create_reader } from "@ethernauta/transport";
import { eip155_1 } from "@ethernauta/chain";

const reader = create_reader([eip155_1]);
const ctx = reader({ chain_id: eip155_1.chain_id });

Always normalize first

const name = ens_normalize("Vitalik.eth");  // → "vitalik.eth"

ENSIP-15 normalization is mandatory — namehash("Vitalik.eth") is different from namehash("vitalik.eth"). The orchestration functions in @ethernauta/ens do NOT auto-normalize; they assume their input is already normalized.

If the input came from a user form, normalize before any lookup.

Forward: name → address

const address = await get_ens_address({ name: "vitalik.eth" })(ctx);
// → "0xd8da6bf26964af9d7eed9e03e53415d37aa96045" | null

Returns null if the name has no addr record.

Reverse: address → name

const name = await get_ens_name({ address })(ctx);
// → "vitalik.eth" | null

Includes the forward-verification step — the reverse record is claim-only, so the function looks up the claimed name’s forward address and confirms it matches. If it doesn’t, the result is null.

Text records

const twitter = await get_ens_text({
  name: "vitalik.eth",
  key: "com.twitter",
})(ctx);

Common keys: email, url, description, com.twitter, com.github, org.telegram.

Avatars

const avatar = await get_ens_avatar({ name: "vitalik.eth" })(ctx);

AvatarResult is a discriminated union over the avatar’s URI scheme:

HTTP / HTTPS URLs.
IPFS / Swarm content hashes.
NFT pointers (eip155:1/erc721:0x...:tokenId).