# wrapper.unwrap

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

Unwraps an ENSv1 name from the NameWrapper. Parameters, return value, errors and examples for wrapper.unwrap in @ensforge/sdk.

Source: https://ensforge.com/docs/reference/sdk/wrapper/unwrap

<ApiMeta kind="Write" stability="stable" since="1.0.0" source="packages/sdk/src/actions/wrapper/unwrap/index.ts#L57" />

Unwraps an ENSv1 name from the NameWrapper. Resolves once the transaction is submitted.

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

Use to return a wrapped name to the ENSv1 registry (and the `.eth` registrar). Use [`unwrapSync`](/docs/reference/sdk/wrapper/unwrap#wait-for-the-receipt-with-unwrapsync) to wait for the receipt.

## Details [#details]

- `owner` becomes the registry owner and, for `.eth` names, the registrant. Defaults to the
  signer.
- Blocked once `cannotUnwrap` is burned.

## Signature [#signature]

```ts
function unwrap(
  client: Like,
  options: unwrap.Options & Write.Options,
): Promise<unwrap.ReturnType>
```

Call it as `ens.wrapper.unwrap(options)` on a client, or `Actions.wrapper.unwrap(client, options)`.

## Parameters [#parameters]

| Option | Type | Default | Description |
| --- | --- | --- | --- |
| `name` (required) | `string` |  | ENSv1 name. Normalized automatically. |
| `owner` | `string` |  | Owner after unwrapping. Defaults to the signer. |

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

## Returns [#returns]

Resolves to `Write.Result`. Submitted transaction hashes and the plan that produced them.

| Field | Type | Description |
| --- | --- | --- |
| `hash` | `Hex` | Hash of the last transaction. |
| `hashes` | `readonly Hex[]` | Every submitted transaction, in order. |
| `id` | `string` | EIP-5792 bundle id when the calls were sent as one batch. |
| `plan` | `Plan` | The plan the write executed: its steps, in order, as they were submitted. |

## Errors [#errors]

| Error | Codes | When |
| --- | --- | --- |
| [`InvalidInputError`](/docs/reference/errors/invalid-input-error) | [`INVALID_NAME`](/docs/reference/errors/INVALID_NAME), [`INVALID_ADDRESS`](/docs/reference/errors/INVALID_ADDRESS) | invalid input. |
| [`NameStateError`](/docs/reference/errors/name-state-error) | [`NAME_EXPIRED`](/docs/reference/errors/NAME_EXPIRED), [`NAME_NOT_REGISTERED`](/docs/reference/errors/NAME_NOT_REGISTERED), [`NAME_NOT_WRAPPED`](/docs/reference/errors/NAME_NOT_WRAPPED) | the name is not wrapped. |
| [`NameStateError`](/docs/reference/errors/name-state-error) | [`NAME_UNREACHABLE`](/docs/reference/errors/NAME_UNREACHABLE) | ENSv2 resolution no longer reaches the name. |
| [`UnsupportedError`](/docs/reference/errors/unsupported-error) | [`UNSUPPORTED_PROTOCOL`](/docs/reference/errors/UNSUPPORTED_PROTOCOL) | ENSv2 names; migrated names have no NameWrapper. |
| [`UnauthorizedError`](/docs/reference/errors/unauthorized-error) | [`NOT_OWNER`](/docs/reference/errors/NOT_OWNER), [`FUSE_BURNED`](/docs/reference/errors/FUSE_BURNED) | the account may not unwrap it. |
| [`UserRejectedError`](/docs/reference/errors/user-rejected-error) | [`USER_REJECTED`](/docs/reference/errors/USER_REJECTED) | the user rejects the request. |
| [`WalletError`](/docs/reference/errors/wallet-error) | [`CHAIN_MISMATCH`](/docs/reference/errors/CHAIN_MISMATCH), [`ACCOUNT_NOT_FOUND`](/docs/reference/errors/ACCOUNT_NOT_FOUND) | the wallet is on another chain or has no account to sign with. |
| [`UnsupportedError`](/docs/reference/errors/unsupported-error) | [`WALLET_BATCH_UNSUPPORTED`](/docs/reference/errors/WALLET_BATCH_UNSUPPORTED) | with `mode: "batch"` or a paymaster when the wallet cannot send calls as one batch. |

It can also fail with the errors every write can (`Errors.WriteError`: the common errors plus `InsufficientFundsError`, `TransactionError`, `UnsupportedError`, `UserRejectedError`, `WalletError`).

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

## Examples [#examples]

<Tabs groupId="api" items={["Client","Standalone","Effect"]} persist>
<Tab>
```ts title="Unwrapping a name"
const { hash } = await ens.wrapper.unwrap({ name: "alice.eth" })
```
</Tab>

<Tab>
```ts title="Unwrapping a name with a standalone call"
import { Actions } from "@ensforge/sdk"

await Actions.wrapper.unwrap(ens, { name: "alice.eth" })
```
</Tab>

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

yield* Actions.wrapper.unwrap(ens, { name: "alice.eth" })
```
</Tab>
</Tabs>

## Plan methods [#plan-methods]

Each method takes the same options as `wrapper.unwrap` and sends nothing. See [Preview before sending](/docs/sdk/preview-before-sending).

| Method | Description |
| --- | --- |
| `wrapper.unwrap.prepare(options)` | Builds the plan without sending anything. |
| `wrapper.unwrap.simulate(options)` | Simulates the plan with `eth_call`, reporting each step. |
| `wrapper.unwrap.estimateGas(options)` | Estimates the gas and ETH the plan needs. |

## Wait for the receipt with `unwrapSync` [#wait-for-the-receipt-with-unwrapsync]

Unwraps an ENSv1 name from the NameWrapper. Resolves once the receipt is in.

Use when the next step depends on the change being on-chain.

`wrapper.unwrapSync` takes the same options plus [`confirmations` and `timeout`](/docs/reference/sdk/client#sync-options).

Resolves to `Write.SyncResult`. Receipts plus the submitted hashes and plan.

<Tabs groupId="api" items={["Client","Standalone","Effect"]} persist>
<Tab>
```ts title="Unwrapping a name and waiting"
const { receipt } = await ens.wrapper.unwrapSync({ name: "alice.eth" })
```
</Tab>

<Tab>
```ts title="Waiting with a standalone call"
import { Actions } from "@ensforge/sdk"

await Actions.wrapper.unwrapSync(ens, { name: "alice.eth" })
```
</Tab>

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

yield* Actions.wrapper.unwrapSync(ens, { name: "alice.eth" })
```
</Tab>
</Tabs>

## See also [#see-also]

- [`wrapper.wrap`](/docs/reference/sdk/wrapper/wrap) to wrap it