Documentation for agents: an index at /llms.txt, every docs page in one file at /llms-full.txt, and Markdown for any docs page by adding .md to its URL.

Skip to Content
ensforgeSDK

wrapper.setFuses

Burns owner-controlled fuses on a wrapped ENSv1 name. Parameters, return value, errors and examples for wrapper.setFuses in @ensforge/sdk.

Writestable
Since v1.0.0View source

Burns owner-controlled fuses on a wrapped ENSv1 name. Resolves once the transaction is submitted.

When to use

Use to give up powers over a name for good, such as unwrapping or changing its resolver. Use setFusesSync to wait for the receipt.

Details

  • Fuses cannot be unburned before the name expires.
  • Needs parentCannotControl, burned by the parent or set on every wrapped .eth name; every fuse besides cannotUnwrap needs cannotUnwrap.

Gotchas

  • Burning cannotUnwrap keeps the name in the NameWrapper until it expires.

Signature

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

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

Parameters

OptionTypeDefaultDescription
name (required)stringWrapped ENSv1 name. Normalized automatically.
fuses (required)readonly Fuse.Name[]Owner-controlled fuses to burn.

Also takes the write options.

Returns

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

FieldTypeDescription
hashHexHash of the last transaction.
hashesreadonly Hex[]Every submitted transaction, in order.
idstringEIP-5792 bundle id when the calls were sent as one batch.
planPlanThe plan the write executed: its steps, in order, as they were submitted.

Errors

ErrorCodesWhen
InvalidInputErrorINVALID_NAME, INVALID_RECORD_VALUEinvalid input or fuses.
NameStateErrorNAME_EXPIRED, NAME_NOT_REGISTERED, NAME_NOT_WRAPPEDthe name is not wrapped.
NameStateErrorNAME_UNREACHABLEENSv2 resolution no longer reaches the name.
UnsupportedErrorUNSUPPORTED_PROTOCOLENSv2 names; migrated names have no NameWrapper.
UnauthorizedErrorNOT_OWNER, FUSE_BURNEDthe account may not burn them.
UserRejectedErrorUSER_REJECTEDthe user rejects the request.
WalletErrorCHAIN_MISMATCH, ACCOUNT_NOT_FOUNDthe wallet is on another chain or has no account to sign with.
UnsupportedErrorWALLET_BATCH_UNSUPPORTEDwith 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.

Examples

Burning fuses
const { hash } = await ens.wrapper.setFuses({ name: "alice.eth", fuses: ["cannotUnwrap"] })

Plan methods

Each method takes the same options as wrapper.setFuses and sends nothing. See Preview before sending.

MethodDescription
wrapper.setFuses.prepare(options)Builds the plan without sending anything.
wrapper.setFuses.simulate(options)Simulates the plan with eth_call, reporting each step.
wrapper.setFuses.estimateGas(options)Estimates the gas and ETH the plan needs.

Wait for the receipt with setFusesSync

Burns owner-controlled fuses on a wrapped ENSv1 name. Resolves once the receipt is in.

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

wrapper.setFusesSync takes the same options plus confirmations and timeout.

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

Burning fuses and waiting
const { receipt } = await ens.wrapper.setFusesSync({ name: "alice.eth", fuses: ["cannotUnwrap"] })

See also

Was this page helpful?