Resolve with ENS

Every swop.id is a real ENS name, so you resolve it the same way you'd resolve vitalik.eth: with an ENS-aware library and an Ethereum mainnet RPC. The library handles CCIP Read for you (see how it works).

Resolve a name to an addressCopy Anchor Link

import { createPublicClient, http } from 'viem';
import { mainnet } from 'viem/chains';
import { normalize } from 'viem/ens';

const client = createPublicClient({
  chain: mainnet,
  transport: http('https://YOUR_MAINNET_RPC'),
});

const address = await client.getEnsAddress({ name: normalize('maya.swop.id') });
// '0x…' or null

CCIP Read is on by default in all three libraries. If you've turned it off (for example ccipRead: false in viem), swop.id names won't resolve.

Read the avatarCopy Anchor Link

The resolver serves selected public profile text records. Read the avatar the standard ENS way:

const avatar = await client.getEnsAvatar({ name: normalize('maya.swop.id') });

If a text record isn't set you get null. For the display name and Solana address, the Identity API is simpler.

Rules for paying a nameCopy Anchor Link

If your app sends money to a swop.id, follow these five rules. They're the same ones the Swop apps use.

1. Normalize the name first (normalize() in viem; ethers and web3.py do it for you).
2. Resolve through ENS on Ethereum mainnet with CCIP Read enabled.
3. Show the payer the resolved address and the network before they confirm.
4. Re-resolve right before you create the payment. Don't reuse an address you resolved minutes ago.
5. Fail closed. If resolution fails, or returns a zero or invalid address, don't send.

Contract addressesCopy Anchor Link

Your ENS library finds the resolver for you. You only need these to verify things yourself, for example in a block explorer.