# record.getAddress

> For the complete documentation index, see [llms.txt](https://ensforge.com/llms.txt).

Reads one address record of an ENS name, for Ethereum by default or any coin (ENSIP-9, ENSIP-11). Options, result, errors and examples for record.getAddress.

Source: https://ensforge.com/docs/reference/sdk/record/get-address

<ApiMeta kind="Read" stability="stable" since="1.0.0" source="packages/sdk/src/actions/record/getAddress/index.ts#L58" batchable />

Reads one address record of an ENS name, for Ethereum by default or any coin (ENSIP-9, ENSIP-11).

## When to use [#when-to-use]

Use to find where to send funds for a name. Use `record.get` to read several coins at once.

## Details [#details]

- `coin` is a symbol (`"btc"`), an EVM chain (`{ chainId: 8453 }`) or a coin type (`0n`).
- EVM coins return a checksummed `Address`; other coins their native format.
- EVM chains other than mainnet fall back to the default EVM address (ENSIP-19).
- Returns `null` when the record is not set, unless `strict` is set.

## Signature [#signature]

```ts
function getAddress<const coin extends CoinType.Input | undefined = undefined>(
  client: Like,
  options: getAddress.Options<coin>,
): Promise<getAddress.ReturnType<coin>>
```

Call it as `ens.record.getAddress(options)` on a client, or `Actions.record.getAddress(client, options)`.

`record.getAddress.request(options)` builds a deferred read for `Actions.batch`. See [Look up many at once](/docs/sdk/look-up-many-at-once).

In React, use [`useAddress`](/docs/reference/react/use-address).

## Parameters [#parameters]

| Option | Type | Default | Description |
| --- | --- | --- | --- |
| `name` (required) | `string` |  | ENS name to read. Normalized automatically. |
| `coin` | `CoinType.Input` | `"eth"` | Coin to read: a symbol, `{ chainId }` or a coin type. |

Also takes the [read options](/docs/reference/sdk/client#read-options).

## Returns [#returns]

Resolves to `getAddress.ReturnType`. An `Address` for EVM coins, the coin's native format otherwise; `null` when not set.

## Errors [#errors]

| Error | Codes | When |
| --- | --- | --- |
| [`InvalidInputError`](/docs/reference/errors/invalid-input-error) | [`INVALID_NAME`](/docs/reference/errors/INVALID_NAME), [`INVALID_COIN_TYPE`](/docs/reference/errors/INVALID_COIN_TYPE) | invalid input. |
| [`NotFoundError`](/docs/reference/errors/not-found-error) | [`RECORD_NOT_FOUND`](/docs/reference/errors/RECORD_NOT_FOUND), [`RESOLVER_NOT_FOUND`](/docs/reference/errors/RESOLVER_NOT_FOUND) | with `strict`. |
| [`UnsupportedError`](/docs/reference/errors/unsupported-error) | [`RESOLVER_PROFILE_UNSUPPORTED`](/docs/reference/errors/RESOLVER_PROFILE_UNSUPPORTED) | with `strict` when the resolver supports none of the records. |
| [`GatewayError`](/docs/reference/errors/gateway-error) | [`GATEWAY_REQUEST_FAILED`](/docs/reference/errors/GATEWAY_REQUEST_FAILED), [`GATEWAY_RESPONSE_INVALID`](/docs/reference/errors/GATEWAY_RESPONSE_INVALID), [`OFFCHAIN_LOOKUP_INVALID`](/docs/reference/errors/OFFCHAIN_LOOKUP_INVALID) | an off-chain gateway fails. |
| [`DnsError`](/docs/reference/errors/dns-error) |  | a DNS name's DNSSEC proof does not verify. |
| [`NetworkError`](/docs/reference/errors/network-error) | [`RPC_REQUEST_FAILED`](/docs/reference/errors/RPC_REQUEST_FAILED), [`RPC_TIMEOUT`](/docs/reference/errors/RPC_TIMEOUT), [`RATE_LIMITED`](/docs/reference/errors/RATE_LIMITED) | the RPC request fails. |

It can also fail with the errors every read can (`Errors.CommonError`: `ConfigError`, `ContractRevertError`, `InternalError`, `NetworkError`).

See [How errors work](/docs/sdk/errors-explained).

## Examples [#examples]

<Tabs groupId="api" items={["Client","Standalone","Effect"]} persist>
<Tab>
```ts title="Resolving an Ethereum address"
const address = await ens.record.getAddress({ name: "nick.eth" })
```
</Tab>

<Tab>
```ts title="Resolving a Bitcoin address with a bare viem client"
import { Actions } from "@ensforge/sdk"

const btc = await Actions.record.getAddress(publicClient, { name: "nick.eth", coin: "btc" })
```
</Tab>

<Tab>
```ts title="Resolving a Base address in an Effect program"
import { Actions } from "@ensforge/sdk/effect"

const base = yield* Actions.record.getAddress(ens, { name: "nick.eth", coin: { chainId: 8453 } })
```
</Tab>
</Tabs>

## Example response [#example-response]

Recorded from Ethereum mainnet on 2026-11-18 at block 26443964. Values change as the chain does.

```ts
await ens.record.getAddress({ name: "nick.eth" })
```

```json
"0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5"
```

## See also [#see-also]

- [`record.get`](/docs/reference/sdk/record/get) to read several records