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
| Title | Message | Action |
|---|---|---|
| Not supported | This 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
| Action | When |
|---|---|
approval.getToken | for ENSv2 names and unwrapped subnames. |
approval.setToken | for ENSv2 names and unwrapped subnames. |
name.reclaim | for wrapped, ENSv2 and non-.eth names. |
name.setManager | for wrapped and ENSv2 names. |
name.setTtl | for ENSv2 names. |
name.transfer | for role: "registrant" on names without a registrant. |
record.set | for 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.attach | for ENSv1 names. |
registry.deploy | without ENSv2, or for an ENSv1 attachTo. |
resolver.set | for "default" on ENSv2 names. |
role.get | for ENSv1 names. |
role.grant | for ENSv1 names. |
role.revoke | for ENSv1 names. |
subname.create | for roles on ENSv1 or fuses on unwrapped parents. |
subname.update | for an ENSv2 owner change or an unwrapped ENSv1 expiry. |
wrapper.setChildFuses | for ENSv2 names; migrated names have no NameWrapper. |
wrapper.setFuses | for ENSv2 names; migrated names have no NameWrapper. |
wrapper.unwrap | for ENSv2 names; migrated names have no NameWrapper. |
wrapper.wrap | for 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?