Errors

All typed errors extend PowfiSDKError, which extends Error. Import them from the package root and narrow with instanceof:

import {
  PowfiSDKError,
  PoolNotFoundError,
  PriceImpactTooHighError,
  InsufficientBalanceError,
  InsufficientLiquidityError
} from '@alephium/powfi-sdk'

try {
  await powfi.cpmm.swap(req, balances)
} catch (e) {
  if (e instanceof PriceImpactTooHighError) showWarning(e.message)
  else if (e instanceof InsufficientBalanceError) showTopUp(e.message)
  else if (e instanceof PoolNotFoundError) showCreatePool()
  else throw e
}

Typed errors

Error	Thrown by	Message
`PoolNotFoundError`	`cpmm.getPoolState`, `clmm.getPoolState`, `clmm.getPoolTokenBalances`, `clmm.findBestRoute`	`Pool does not exist for <poolId>`
`PriceImpactTooHighError`	`cpmm.swap` when `priceImpact >= 5`	`Price impact too high: 6.12% > 5%`
`InsufficientBalanceError`	`cpmm.swap`, `cpmm.addLiquidity` when you pass a `balances` map	`Not enough <SYMBOL> balance. Required: …, Available: …`
`InsufficientLiquidityError`	`CpmmModule.getAmountIn` (output ≥ reserve), `getInitLiquidityDetails` (initial liquidity ≤ `MINIMUM_LIQUIDITY`)	`Insufficient liquidity` / custom
`TokenListFetchError`	`token.fetchTokens` (wrapped, see below)	`Failed to fetch token list from <url> (status 404)`

TokenListFetchError exposes status?: number and the original error as cause.

Some module methods catch errors and re-throw them as a plain Error with a combined message (via logAndThrowError), for example Failed to fetch pool state on <id>, <original message>. TokenModule.getTokens() and fetchTokens() behave this way, so the TokenListFetchError text appears in the message but the thrown object is an Error. Match on the message if you need to tell them apart.

Validation errors (plain `Error`)

Message	Cause
`Signer not set`	A write method was called on an instance loaded without `signer`.
`Network <id> not found`	Unknown `networkId`.
`Either amountIn or amountOut must be specified`	CPMM quote with neither amount.
`Slippage must satisfy 0 <= slippage < 10000, received …`	Invalid `slippageBps` for CPMM.
`slippageBps must be in [0, 10000)`	Invalid slippage for CLMM.
`Unknown tokenInId … for pool …`	Token not part of the pool state you passed.
`Unknown token, id not found in token list: …`	Token missing from the token list (pool state lookups need every pool token to be listed).
`fee and feeRecipient must be provided together` (and other fee messages)	Invalid integrator fee.
`<Stake/Unstake/Claim> amount must be greater than zero`	Non-positive staking amount.
`TickOutOfBounds: <tick>` / `SqrtPriceX96OutOfBounds`	Tick outside `[MIN_TICK, MAX_TICK]` or price outside the representable range.

On-chain errors

If a transaction passes SDK validation but fails in the contract (slippage exceeded, deadline passed, price limit violated), the node rejects it during signing and @alephium/web3 throws with the VM error code in the message, for example Error Code: 501 when a CLMM swap hits its price limit before filling the full amount (106 if the limit is on the wrong side of the price). The most common causes:

Slippage or deadline: the pool moved between quote and submission. Re-quote and retry.
Insufficient ALPH for dust or deposits: see ALPH deposits and dust.
Wrong direction or price limit on CLMM swapTo: the target price is already past the current price.

SDK & API

Core concepts

Modules

Utilities

Guides

Reference

Typed errors

Validation errors (plain `Error`)

On-chain errors

​Typed errors

​Validation errors (plain Error)

​On-chain errors

Typed errors

Validation errors (plain `Error`)

On-chain errors