ENS

Where ENS is accepted

ENS names work in every place Beam expects a wallet, address, or recipient:

• beam --from alice.eth balance
• beam transfer bob.eth 0.01
• beam wallets rename alice.eth primary
• beam erc20 transfer USDC alice.eth 25

For signing commands (--from), the selector must still resolve to a wallet stored in the local keystore, even when you pass an ENS or raw address.

Validation

• Wallet names ending in .eth must resolve through ENS to that wallet's address before Beam accepts them.
• Beam first checks stored wallet names, then resolves .eth inputs through ENS.
• ENS lookups always use the configured Ethereum RPC — they never run against the active chain's RPC.
• Beam rejects the configured Ethereum RPC for ENS if it does not report chain id 1.

Reverse records

beam wallets import (with no --name flag) uses a verified ENS reverse record as the default wallet alias when one resolves back to the imported address. Otherwise the wallet falls back to the next wallet-N.

Resolution failures

If an ENS name doesn't resolve, Beam fails the command with a normal CLI error. The same applies if the Ethereum RPC returns the wrong chain id — Beam refuses to use it for ENS instead of silently mis-resolving.