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
ensforge

UNSUPPORTED_PROTOCOL

What UNSUPPORTED_PROTOCOL means, why UnsupportedError throws it, what to show users and how to fix it in ensforge. Also covers retry safety.

UnsupportedErrorNot retryable
@ensforge/sdk

What happened

This operation is not supported for this names.

What to show users

TitleMessageAction
Not supportedThis action is not available for this name.

Retry safety

Retrying the same call fails the same way until the cause is fixed (retryable: false).

Actions that throw it

ActionWhen
approval.getTokenfor ENSv2 names and unwrapped subnames.
approval.setTokenfor ENSv2 names and unwrapped subnames.
name.reclaimfor wrapped, ENSv2 and non-.eth names.
name.setManagerfor wrapped and ENSv2 names.
name.setTtlfor ENSv2 names.
name.transferfor role: "registrant" on names without a registrant.
record.setfor records the resolver does not support (feature names them), a resolver that keeps its records off-chain or takes no writes, or resolver: "default" on an ENSv2 name.
registry.attachfor ENSv1 names.
registry.deploywithout ENSv2, or for an ENSv1 attachTo.
resolver.setfor "default" on ENSv2 names.
role.getfor ENSv1 names.
role.grantfor ENSv1 names.
role.revokefor ENSv1 names.
subname.createfor roles on ENSv1 or fuses on unwrapped parents.
subname.updatefor an ENSv2 owner change or an unwrapped ENSv1 expiry.
wrapper.setChildFusesfor ENSv2 names; migrated names have no NameWrapper.
wrapper.setFusesfor ENSv2 names; migrated names have no NameWrapper.
wrapper.unwrapfor ENSv2 names; migrated names have no NameWrapper.
wrapper.wrapfor ENSv2 names; migrated names have no NameWrapper.

Any write can fail with UnsupportedError: it is part of Errors.WriteError.

Catch it

Errors.hasCode("UNSUPPORTED_PROTOCOL") narrows to this error. See Handle errors.

Was this page helpful?