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
| Title | Message | Action |
|---|---|---|
| Wallet not connected | Connect 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
| Action | When |
|---|---|
permission.check | without account or a client account. |
permission.get | without account or a client account. |
primaryName.set | when no signing account is known. |
primaryName.signClaim | when no signing account is known. |
record.set | when the client has no wallet. |
registration.commit | when no signing account is known. |
registration.register | when no signing account is known. |
registration.renew | when no signing account is known. |
registry.deploy | when no signing account is known. |
registry.upgrade | when no signing account is known. |
resolver.create | when no account is known to predict the address. |
subname.create | when no signing account is known. |
subname.remove | when 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?