Every transaction error, explained

badAloPxRejected

The order was add-liquidity-only, and its price would have crossed the book and taken liquidity instead of adding it. Add-liquidity-only exists to guarantee the maker fee, so rather than filling at taker terms the order is refused. The market moved between the price being chosen and the order arriving.

canceled

The order was cancelled. On Hyperliquid this is the trader's own cancellation, so if the user did not cancel it, an app or a bot acting for them did.

insufficientSpotBalanceRejected

There was not enough of the spot asset to place this order. Spot and perpetual balances are held separately on Hyperliquid, so funds sitting on the perpetuals side do not back a spot order until they are transferred.

iocCancelRejected

The order was immediate-or-cancel, and there was nothing on the book to fill it at that price, so it was cancelled instead of resting. That is what immediate-or-cancel asks for: fill now or not at all. Nothing was traded.

minTradeNtlRejected

The order was below Hyperliquid's minimum trade value. Every market has a floor in dollars rather than in coins, so a small order in a high-priced asset can be under it even when the quantity looks reasonable. Nothing was traded and nothing was charged.

perpMarginRejected

There was not enough margin for this perpetual order. Margin is the collateral the position needs, not the account balance, so an account can hold funds and still be unable to open more.

reduceOnlyCanceled

The exchange cancelled this resting reduce-only order because the position it was there to reduce is gone. The trader did not cancel it. Nothing was traded.

reduceOnlyRejected

The order was marked reduce-only, and there was no position left for it to reduce. That usually means the position had already been closed, or another order closed it first. Nothing was traded.

rejected

The exchange refused the order without naming a more specific reason. Nothing was traded.

triggered

A stop or take-profit condition was met, so the order was released onto the book.

insufficient balance or overflow

The account did not hold enough of the token this intent was going to spend, or the amounts involved were too large to process. Nothing was executed.

invalid intent

The intent this transaction carried was not one the contract would accept, usually because it had already been used, had expired, or was signed for different terms than the ones submitted. Nothing was executed.

E68

The price moved between the swap being quoted and it reaching the pool, by more than the slippage the swap allowed. Ref refuses rather than filling at a worse rate than agreed. Nothing was traded, only the gas was spent, and trying again with a slightly higher slippage tolerance, or a smaller size, usually goes through.

E76

The pool did not hold enough of the token being bought to complete this swap at the size requested. A smaller amount, or a different route, will usually go through.

BuySlippageBelowMinBaseAmountOut

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

BuySlippageBelowMinTokensOut

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

CoinCreatorMigratedToSharingConfig

coin creator has been migrated to sharing config, use pump_fees::reset_fee_sharing_config instead.

CreatorVaultMigratedToSharingConfig

creator_vault has been migrated to sharing config, use pump:distribute_creator_fees instead.

ExceededAmountSlippageTolerance

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

ExceededSlippage

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

InvalidSlippage

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

LessThanMinimumAmountOut

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

MinReturnNotReached

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

SlippageLimitExceeded

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

SlippageToleranceExceeded

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

TooLittleSolReceived

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

TooMuchSolRequired

The price moved between the quote and the transaction landing, so the trade would have returned less than your slippage setting allows. Nothing was swapped and only the fee was spent. Retry, and raise your slippage tolerance slightly if it keeps happening.

ACCOUNT_MERGE_DEST_FULL

Merging would take the destination account past the maximum balance it can hold.

ACCOUNT_MERGE_HAS_SUB_ENTRIES

The account still has trustlines, offers, signers or data entries, and all of those have to be removed before it can be merged away.

CHANGE_TRUST_INVALID_LIMIT

The trustline limit given was not valid, for example lower than the balance already held.

CHANGE_TRUST_LOW_RESERVE

Adding this trustline would take the account below its minimum reserve. Each trustline raises the XLM an account must keep, so more XLM is needed before it can be added.

CHANGE_TRUST_NOT_AUTH_MAINTAIN_LIABILITIES

The issuer has not authorised this account to maintain liabilities on the asset.

CLAIM_CLAIMABLE_BALANCE_CANNOT_CLAIM

This account is not able to claim that balance right now. A claimable balance carries conditions, most often a time window, and they were not met.

CLAIM_CLAIMABLE_BALANCE_DOES_NOT_EXIST

There is no claimable balance with that identifier. It may already have been claimed.

CLAIM_CLAIMABLE_BALANCE_LINE_FULL

Claiming this would take the account past the limit on its trustline for the asset.

CLAIM_CLAIMABLE_BALANCE_NO_TRUST

The account has no trustline for the asset in this claimable balance, so it cannot receive it.

CREATE_ACCOUNT_UNDERFUNDED

The funding account did not have enough XLM to create the new account with its minimum starting balance.

CREATE_CLAIMABLE_BALANCE_LOW_RESERVE

Creating this claimable balance would take the account below its minimum reserve.

CREATE_CLAIMABLE_BALANCE_MALFORMED

The claimable balance was not well formed, for example an invalid amount or claimant.

CREATE_CLAIMABLE_BALANCE_NO_TRUST

The account has no trustline for the asset it tried to lock into a claimable balance.

INVOKE_HOST_FUNCTION_ENTRY_ARCHIVED

The contract data this call needed has been archived. Soroban expires state that has not been used, and it has to be restored before the contract can run again.

INVOKE_HOST_FUNCTION_INSUFFICIENT_REFUNDABLE_FEE

The refundable portion of the fee was not enough to cover the contract's rent and events.

INVOKE_HOST_FUNCTION_RESOURCE_LIMIT_EXCEEDED

The contract call needed more resources than the transaction reserved for it. On Soroban a transaction declares its resource budget up front, so this is a budget set too low rather than an account short of funds.

INVOKE_HOST_FUNCTION_TRAPPED

The contract stopped partway through and rejected the call. The reason is defined by the contract rather than by Stellar, so what it means depends on the protocol. Nothing the transaction set out to do took effect.

LIQUIDITY_POOL_DEPOSIT_BAD_PRICE

The pool's price moved outside the range this deposit allowed, so it was refused rather than filled at a worse rate.

LIQUIDITY_POOL_DEPOSIT_NO_TRUST

The account has no trustline for the pool shares or for one of the pool's assets.

LIQUIDITY_POOL_WITHDRAW_UNDER_MINIMUM

The withdrawal would have returned less than the minimum set, so it was refused. The pool's composition moved between the quote and the transaction being applied.

MANAGE_BUY_OFFER_BUY_NO_TRUST

The account has no trustline for the asset it offered to buy, so it could not receive it.

MANAGE_BUY_OFFER_CROSS_SELF

This offer would have matched against the account's own existing offer, which Stellar does not allow.

MANAGE_BUY_OFFER_LINE_FULL

Filling this offer would take the account past the limit on its trustline for the asset it would receive.

MANAGE_BUY_OFFER_LOW_RESERVE

Keeping this offer on the book would take the account below its minimum reserve. Each open offer raises the XLM an account must hold.

MANAGE_BUY_OFFER_MALFORMED

The offer was not well formed, for example a non-positive amount or an invalid price.

MANAGE_BUY_OFFER_NOT_FOUND

The offer this was trying to change or cancel is no longer on the book. It may already have been filled or cancelled.

MANAGE_BUY_OFFER_UNDERFUNDED

The account does not hold enough of the asset it offered to pay with, once the reserve is taken into account.

MANAGE_SELL_OFFER_BUY_NO_TRUST

The account has no trustline for the asset it offered to buy, so it could not receive it.

MANAGE_SELL_OFFER_CROSS_SELF

This offer would have matched against the account's own existing offer, which Stellar does not allow.

MANAGE_SELL_OFFER_LINE_FULL

Filling this offer would take the account past the limit on its trustline for the asset it would receive.

MANAGE_SELL_OFFER_LOW_RESERVE

Keeping this offer on the book would take the account below its minimum reserve. Each open offer raises the XLM an account must hold.

MANAGE_SELL_OFFER_MALFORMED

The offer was not well formed, for example a non-positive amount or an invalid price.

MANAGE_SELL_OFFER_NOT_FOUND

The offer this was trying to change or cancel is no longer on the book. It may already have been filled or cancelled.

MANAGE_SELL_OFFER_UNDERFUNDED

The account does not hold enough of the asset it offered to sell, once the reserve is taken into account.

opTOO_MANY_SUBENTRIES

The account already holds the maximum number of subentries (trustlines, offers, signers and data entries), so another could not be added.

PATH_PAYMENT_STRICT_RECEIVE_LINE_FULL

The destination's trustline for this asset has a limit, and this payment would have taken it over. The recipient sets that limit and can raise it.

PATH_PAYMENT_STRICT_RECEIVE_MALFORMED

The swap was not well formed, for example a non-positive amount or an invalid asset.

PATH_PAYMENT_STRICT_RECEIVE_NO_DESTINATION

The destination account does not exist on the ledger. A Stellar account has to be created before it can be paid.

PATH_PAYMENT_STRICT_RECEIVE_NO_TRUST

The destination has no trustline for the asset being delivered. On Stellar an account has to explicitly trust an asset before it can receive it, so this is something the recipient sets up, not a problem with the payment.

PATH_PAYMENT_STRICT_RECEIVE_NOT_AUTHORIZED

The destination is not authorised by the asset's issuer to hold it. Some issuers require approval per account.

PATH_PAYMENT_STRICT_RECEIVE_OFFER_CROSS_SELF

The path would have matched against this account's own offer, which Stellar does not allow.

PATH_PAYMENT_STRICT_RECEIVE_OVER_SENDMAX

The swap would have cost more than the maximum you set, so Stellar refused it rather than spending more than you allowed. That maximum is your slippage protection doing its job: the price along the path moved between the quote and the transaction being applied. Nothing was swapped and only the fee was spent.

PATH_PAYMENT_STRICT_RECEIVE_SRC_NO_TRUST

The sending account has no trustline for the asset it tried to send, so it cannot hold or send it.

PATH_PAYMENT_STRICT_RECEIVE_TOO_FEW_OFFERS

There was not enough liquidity along any path to complete this swap. Nothing was swapped.

PATH_PAYMENT_STRICT_RECEIVE_UNDERFUNDED

The sending account did not hold enough of the asset being sent. On Stellar this includes the reserve: an account must keep a minimum XLM balance plus an amount for each trustline, offer and signer, so a visible balance is not always a spendable one.

PATH_PAYMENT_STRICT_SEND_LINE_FULL

The destination's trustline for this asset has a limit, and this payment would have taken it over. The recipient sets that limit and can raise it.

PATH_PAYMENT_STRICT_SEND_MALFORMED

The swap was not well formed, for example a non-positive amount or an invalid asset.

PATH_PAYMENT_STRICT_SEND_NO_DESTINATION

The destination account does not exist on the ledger. A Stellar account has to be created before it can be paid.

PATH_PAYMENT_STRICT_SEND_NO_TRUST

The destination has no trustline for the asset being delivered. On Stellar an account has to explicitly trust an asset before it can receive it, so this is something the recipient sets up, not a problem with the payment.

PATH_PAYMENT_STRICT_SEND_NOT_AUTHORIZED

The destination is not authorised by the asset's issuer to hold it. Some issuers require approval per account.

PATH_PAYMENT_STRICT_SEND_OFFER_CROSS_SELF

The path would have matched against this account's own offer, which Stellar does not allow.

PATH_PAYMENT_STRICT_SEND_SRC_NO_TRUST

The sending account has no trustline for the asset it tried to send, so it cannot hold or send it.

PATH_PAYMENT_STRICT_SEND_TOO_FEW_OFFERS

There was not enough liquidity along any path to complete this swap. Nothing was swapped.

PATH_PAYMENT_STRICT_SEND_UNDER_DESTMIN

The swap would have delivered less than the minimum you set, so Stellar refused it rather than filling at a worse rate. That minimum is your slippage protection doing its job: the price along the path moved between the quote and the transaction being applied. Nothing was swapped and only the fee was spent.

PATH_PAYMENT_STRICT_SEND_UNDERFUNDED

The sending account did not hold enough of the asset being sent. On Stellar this includes the reserve: an account must keep a minimum XLM balance plus an amount for each trustline, offer and signer, so a visible balance is not always a spendable one.

PAYMENT_LINE_FULL

The destination's trustline for this asset has a limit, and this payment would have taken it over.

PAYMENT_MALFORMED

The payment was not well formed, for example a non-positive amount or an invalid asset.

PAYMENT_NO_DESTINATION

The destination account does not exist on the ledger. A Stellar account has to be created and funded before it can be paid.

PAYMENT_NO_TRUST

The destination has no trustline for this asset. On Stellar an account has to explicitly trust an asset before it can receive it, so the recipient sets this up.

PAYMENT_UNDERFUNDED

The account did not hold enough of this asset to send that amount. On Stellar the reserve counts against you: an account must keep a minimum XLM balance plus an amount for each trustline, offer and signer, so the spendable balance is lower than the one displayed.

SET_OPTIONS_LOW_RESERVE

This change would take the account below its minimum reserve. Adding a signer raises the XLM an account must keep, so more XLM is needed first.

SET_TRUST_LINE_FLAGS_CANT_REVOKE

The issuer has given up the ability to revoke authorisation on this asset, so the flag cannot be cleared.

SET_TRUST_LINE_FLAGS_NO_TRUST_LINE

There is no trustline between that account and this asset, so its flags could not be set.

txBAD_AUTH

The signatures on this transaction did not meet the account's signing requirements. Nothing was applied.

txBAD_SEQ

The sequence number was not the one this account expected next. That normally means two transactions were submitted from the same account at once, or one was already applied. Reloading the account and rebuilding the transaction fixes it. Nothing was applied here.

txFAILED

One of the operations in this transaction failed, so the whole transaction was rolled back. Stellar applies a transaction all or nothing, so nothing it set out to do took effect.

txFEE_BUMP_INNER_FAILED

This was a fee bump transaction, and the inner transaction it was paying for is the one that failed. The fee bump itself was fine, so look at the inner transaction's own result for the reason.

txINSUFFICIENT_BALANCE

The account could not cover the fee while keeping its minimum reserve. On Stellar an account must always hold a base reserve plus an amount for each trustline, offer and signer, so an account can show a balance and still be unable to spend it.

txINSUFFICIENT_FEE

The fee offered was below what the network was accepting when this was submitted. Stellar prices by surge when a ledger is full, so a fee that works normally can be too low for a busy ledger. Nothing was applied, and resubmitting with a higher fee is the fix.

txINTERNAL_ERROR

The network reported an internal error applying this transaction. Nothing was applied.

txMALFORMED

The transaction was not well formed, so the network rejected it without applying anything.

txNO_ACCOUNT

The source account does not exist on the ledger. A Stellar account has to be created and funded before it can send anything.

txSOROBAN_INVALID

The Soroban resources declared by this transaction were not valid, so it was rejected before running.

txTOO_EARLY

The transaction carried a time bound that had not started yet, so the network would not apply it.

txTOO_LATE

The transaction expired before it was included. Stellar transactions carry a time bound, and this one passed while it was waiting, so it was never applied and nothing moved. Submitting again is safe: the expired one cannot execute later.

EBalanceManagerBalanceTooLow

The withdrawal asked for more than the balance manager holds of that coin. Funds in DeepBook sit inside your balance manager rather than in your wallet, and settled trades or open orders can hold part of it, so the amount available to withdraw is not always the amount you deposited.

ECapNotInList

The capability this transaction tried to use or revoke is not registered on this balance manager. It may already have been revoked.

EInvalidOwner

The balance manager this transaction used is not owned by the address that signed it. A balance manager belongs to one owner, and only that owner can act on it directly.

EInvalidProof

The trade proof presented with this transaction was not valid for the balance manager it was used against. A proof is generated for one balance manager and one purpose, so this usually means the wrong one was attached.

EInvalidTrader

The address that signed is not a trader authorised on this balance manager. The owner grants trading rights explicitly, and this address does not currently hold them.

EMaxCapsReached

This balance manager already has the maximum number of capabilities issued against it, so another could not be added. An existing one has to be revoked first.

EBadRedistribution

DeepBook stopped on an internal check (a redistribution between orderbook nodes that would have had no effect). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EBadRemove

DeepBook stopped on an internal check (an orderbook node in an unexpected state during removal). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EExists

DeepBook stopped on an internal check (a key that already existed in the orderbook structure). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EFanOutTooBig

DeepBook stopped on an internal check (an orderbook fan-out above the allowed maximum). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EFanOutTooSmall

DeepBook stopped on an internal check (an orderbook fan-out below the allowed minimum). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

ENotAdjacent

DeepBook stopped on an internal check (two orderbook nodes whose links did not match up). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

ENotEmpty

DeepBook stopped on an internal check (an orderbook structure expected to be empty and was not). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

ENotFound

The order this transaction referred to is no longer on the book. An order that has already been filled, cancelled or expired cannot be modified or cancelled again, and DeepBook has no record of it to act on. Nothing was completed and only the gas was spent.

ESliceTooBig

DeepBook stopped on an internal check (an orderbook slice size above the allowed maximum). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

ESliceTooSmall

DeepBook stopped on an internal check (an orderbook slice size below the allowed minimum). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EEmptyOrderbook

There are no resting orders on the side of the book this order needed to match against, so there was nothing to trade with.

EInvalidAmountIn

The input amount for this swap was not accepted by the pool. A swap has to name a positive quantity of one of the pool's two coins.

ENewQuantityMustBeLessThanOriginal

An order can only be modified downwards. Increasing the size means cancelling and placing a new order, which also gives up its place in the queue.

EOrderBelowMinimumSize

The order is smaller than the pool's minimum size. Each pool sets its own floor, and an order under it is rejected rather than rounded up.

EOrderInvalidLotSize

The order quantity is not a whole number of lots. Every pool has a lot size, and quantities have to be a multiple of it.

EBookOrderMismatch

DeepBook stopped on an internal check (a book entry that did not match its order record). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EFillMismatch

DeepBook stopped on an internal check (a fill that did not reconcile against its order). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EIncorrectMidPrice

DeepBook stopped on an internal check (a mid price that failed its consistency check). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EIncorrectPoolId

DeepBook stopped on an internal check (a pool id that did not match the one expected). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EOrderInfoMismatch

DeepBook stopped on an internal check (an order record that did not match its book entry). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

ENoDataPoints

There are no DEEP price points recorded for this pool, so a DEEP-denominated fee cannot be priced.

EMaxProposalsReachedNotEnoughVotes

The pool already has the maximum number of proposals this epoch, and this one did not have enough votes to displace one of them.

EProposalDoesNotExist

The proposal voted on does not exist in the current epoch. Proposals do not carry over between epochs.

EInvalidPrecision

DeepBook stopped on an internal check (a precision check in DeepBook's fixed point maths). This is a condition inside DeepBook's own bookkeeping rather than anything wrong with your order, so retrying the same request is unlikely to change the outcome. Nothing was completed and only the gas was spent.

EInvalidNewQuantity

The new quantity for this modification was not valid. An order can only be reduced, and not to zero, which is a cancellation instead.

EOrderExpired

The order had already expired by the time this transaction executed, so there was nothing left to act on.

EFOKOrderCannotBeFullyFilled

This was a fill-or-kill order and there was not enough resting liquidity to fill all of it at your limit price, so none of it was filled. That is the behaviour fill-or-kill asks for: all or nothing.

EInvalidExpireTimestamp

The expiry given for this order is already in the past. An order cannot be placed with an expiry that has passed.

EMarketOrderCannotBePostOnly

The order was sent as both a market order and post-only, which contradict each other. A market order takes liquidity and post-only refuses to.

EOrderBelowMinimumSize

The order is smaller than the pool's minimum size. Each pool sets its own floor, and an order under it is rejected rather than rounded up.

EOrderInvalidLotSize

The order quantity is not a whole number of lots. Every pool has a lot size, and quantities have to be a multiple of it.

EOrderInvalidPrice

The order price sits outside the range the pool accepts, or is not a whole number of ticks. Every DeepBook pool has a tick size, and a price between ticks cannot be placed.

EPOSTOrderCrossesOrderbook

This was a post-only order and it would have matched against an order already resting on the book. Post-only exists to guarantee you add liquidity rather than take it, so instead of filling at a worse price it cancels. The market moved between the price being quoted and the order arriving.

ESelfMatchingCancelTaker

This order would have matched against another of your own orders on the book, and the self-match rule chosen cancelled the incoming side. Nothing was traded with yourself.

EIneligibleReferencePool

The pool named as a price reference is not eligible to be one. DeepBook only accepts certain pools as a source of price.

EInvalidDeepPrice

The DEEP price reference this pool needs was not usable. DeepBook charges fees in DEEP and needs a price for it, and without one the trade cannot be priced.

EInvalidEWMAAlpha

The smoothing parameter given for the pool's moving average is outside the accepted range.

EInvalidFee

The fee supplied for creating this pool was not the amount the registry requires.

EInvalidOrderBalanceManager

The balance manager presented does not match the one the order was placed with. An order can only be modified or cancelled through the balance manager that created it.

EInvalidQuantityIn

The quantity sent into this swap was not accepted. It has to be a positive amount of one of the pool's two coins.

EMinimumQuantityOutNotMet

The swap would have returned less than the minimum you set, so it was rejected rather than filled at a worse rate. That minimum is your slippage protection doing its job. The price moved between the quote and the transaction arriving.

EPackageVersionDisabled

This transaction went to a version of the DeepBook package that has been turned off. That happens after an upgrade, and it means the app or SDK that built the transaction is pointing at an old address. Updating the app is the fix, and your funds are unaffected.

ECoinNotWhitelisted

This coin is not whitelisted, so it cannot be used where a whitelisted coin is required.

EPackageVersionNotEnabled

This transaction went to a version of the DeepBook package that is not enabled. That usually means the app or SDK that built it is pointing at an old package address. Your funds are unaffected.

EPoolAlreadyExists

A pool for this pair of coins already exists, so a second one cannot be created.

EAlreadyProposed

This balance manager has already made a governance proposal in the current epoch.

EMaxOpenOrders

This balance manager already has the maximum number of open orders on this pool. Cancelling or letting some fill makes room for another.

EHasOwedBalances

This operation cannot run while the balance manager still owes balances on the pool. Those have to be settled first.

EIncorrectQuantityReturned

The amount returned to close the flash loan did not cover what was borrowed. A flash loan has to be repaid in full inside the same transaction, so the whole transaction is undone.