ens

# ENS (Ethereum Name Service) — Skill

## What this skill does

Enables Gundwane to:
1. **Resolve ENS names** to Ethereum addresses (forward resolution)
2. **Resolve addresses** to ENS names (reverse resolution)
3. **Look up ENS profiles** (avatar, social records, text records)
4. **Help users register, renew, and manage** .eth names on Ethereum mainnet

## When to use

- User mentions any `.eth` name: "send to vitalik.eth", "look up nick.eth", "who is luc.eth"
- Displaying wallet addresses to the user — show the ENS primary name alongside the address
- User asks "what's my ENS?", "do I have an ENS name?", "set my ENS"
- User asks to register a new .eth name, renew an existing one, or update records
- User sends to or receives from an `.eth` address

## ENS Name Detection

Any token matching `*.eth` in user input is likely an ENS name. Examples:
- "send 0.1 ETH to vitalik.eth" → resolve `vitalik.eth`
- "what's the address for nick.eth?" → resolve `nick.eth`
- "register myname.eth" → check availability for `myname`

**Always resolve before using.** Never pass a `.eth` name directly to LI.FI or transaction tools — resolve to a `0x` address first.

## Resolution

### Forward Resolution (Name → Address)

Use `curl` to resolve an ENS name to its Ethereum address. Try in priority order.

#### Approach 1: ENS Subgraph (The Graph)

Best for detailed data (expiry, registrant, resolver). Requires `GRAPH_API_KEY` env var.

```bash
curl -s -X POST \
  --url "https://gateway.thegraph.com/api/$GRAPH_API_KEY/subgraphs/id/5XqPmWe6gjyrJtFn9cLy237i4cWw2j9HcUJEXsP5qGtH" \
  --header 'Content-Type: application/json' \
  --data '{"query":"{ domains(where: { name: \"vitalik.eth\" }) { name resolvedAddress { id } expiryDate registration { registrant { id } expiryDate } } }"}'
```

Response: `data.domains[0].resolvedAddress.id` = the `0x` address.

#### Approach 2: web3.bio API (free, no key needed)

Good for quick resolution + profile data in one call.

```bash
curl -s "https://api.web3.b...