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

WALLET_NOT_CONFIGURED

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

ConfigErrorNot retryable
@ensforge/sdk

What happened

This action needs a wallet client with an account.

What to show users

TitleMessageAction
Wallet not connectedConnect a wallet to continue.Connect your wallet.

How to fix

Pass walletClient to Ensforge.create, or account to the action.

Retry safety

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

Actions that throw it

ActionWhen
permission.checkwithout account or a client account.
permission.getwithout account or a client account.
primaryName.setwhen no signing account is known.
primaryName.signClaimwhen no signing account is known.
record.setwhen the client has no wallet.
registration.commitwhen no signing account is known.
registration.registerwhen no signing account is known.
registration.renewwhen no signing account is known.
registry.deploywhen no signing account is known.
registry.upgradewhen no signing account is known.
resolver.createwhen no account is known to predict the address.
subname.createwhen no signing account is known.
subname.removewhen no signing account is known.

Any action can fail with ConfigError: it is part of Errors.CommonError.

Catch it

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

Was this page helpful?