covr.Docs

Program reference

Program errors

What each error code from covr's program means, when a desk hits it, and what to do.

How codes are numbered

The program has one Anchor error enum. Anchor numbers custom errors from 6000. The enum counts up from 0, with fixed jumps (for example CustodyInvalidAccount = 1400), so its codes come in blocks: 6000 to 6014, 7400s, 7600s, 8000s, 8200s, 8300s, 8400s and so on. A unit test in the program pins every code.

A failed transaction shows the code in hex in its last log line, and the name and message in an Anchor log line:

text
Program log: AnchorError thrown in <source file>:<line>. Error Code: InvalidOrder. Error Number: 6003. Error Message: Invalid quote, lifecycle state, nonce or time window.
Program 8ZpbTPnDECPTDGN5VHHKH5gfer6EUTnRHcFwfUAbkJDg failed: custom program error: 0x1773

Codes below 6000 come from Anchor itself, and codes from another program (System, SPL Token) are that program's own. See Errors from Anchor and other programs.

Codes not listed on this page are not returned by the instructions in this reference.

Reason lines

For some errors the program also logs a line that names the exact cause. Look for it just above the AnchorError line.

Log lineComes withReasons you can see
COVR_TOKEN_ACCOUNTING: <reason>8302, from call and put fills and exitsUnbootstrapped (run bootstrap_mint_usage_v1), Paused (mint policy disabled), Terms (policy terms_id or profile_hash differs from the market), Limit (a mint policy cap would be exceeded), Identity, Arithmetic
COVR_TOKEN_CUSTODY: <reason>7400 to 7406InsufficientBacking (source account short), Frozen, Uninitialized, Identity (wrong mint or owner), RecipientDelegate, RecipientCloseAuthority, UnsupportedCapability { … }
COVR_RESTRICTED: <reason>8400 to 8405Terms, State, Time, Approval, Impaired, Escrow
COVR_MINT_PURCHASE: <reason>8302 from buy_position_v3, buy_put_position_v3 or a put purchase policy updateSame reasons as the accounting line, for your purchase policy

Order, signature and limits (6000 to 6014)

CodeHexNameMessage
60000x1770BadSignatureEthereum authorization does not match this program and Solana authority
60010x1771InvalidTermsInvalid immutable market terms or mint decimals
60020x1772InvalidAmountInvalid token amount
60030x1773InvalidOrderInvalid quote, lifecycle state, nonce or time window
60040x1774UnauthorizedAccount is not authorized for this action
60060x1776ExposureLimitMaker aggregate collateral exposure exceeds configured capacity
60070x1777PremiumBudgetExceededMaker premium spend exceeds its enabled lifetime ceiling or overflows
60080x1778JitoSolOrderLimitJitoSOL order exceeds 50 SOL of stake-pool backing
60090x1779InvalidJitoPoolJitoSOL stake pool identity, accounting state or epoch is invalid
60100x177aMintPolicyIdentityMint policy or usage identity does not match the canonical maker/mint/payment cohort
60110x177bMintPolicySchemaMint policy or usage schema or allocation length is unsupported
60120x177cMintPolicyGenerationMint policy generation is zero, stale or exhausted
60130x177dMintPolicyUnauthorizedOnly the registered maker owner or configured watcher may pause this policy
60140x177eMintPolicySettingsMint policy settings are not canonical or omit terms/profile identifiers
CodeWhen you hit itWhat to do
6000register_maker_v3: the grant was signed for another authority, program or deployment. fill_v3: the quote was signed in another market's domain, or for another writer, auction id, price, size or nonce. Also early_close_v3 and buy_position_v3.Sign in the domain from registrationGrantDomain() or quoteDomain(decodedMarket). Check your signer against the golden vectors. Signatures must be low-s with v 27 or 28.
6001configure_maker with a min_nonce below the current one. Vault instructions with a mint that does not have 6 decimals.Re-read your Maker and send a min_nonce at or above minNonce. Pass the USDC mint.
6002deposit or withdraw of 0. A fill whose premium or strike is not a whole USDC atom. early_close_v3 or buy_position_v3 with a 0 amount.Send a positive amount. Price with exactPriceAtOrBelow. Quote sizes that are multiples of minimumExactLot.
6003fill_v3: the market is paused, now >= expiry, now >= valid_until, valid_until > expiry, the nonce is below min_nonce or is u64::MAX, the size is 0 or above max_quantity_atoms, or the auction id is zero. exercise_v3: outside [expiry, expiry + window), or the position is not open. release_v3: before expiry + window, or not open. Also early close, sale and transfer outside their time rules.For fills: quote with a nonce at or above min_nonce, and a valid_until inside the market's life. For exercise: send inside the window, with margin for confirmation. Read the position's state first.
6004buy_position_v3 from a signer that is not the position's writer, or with a recipient that is not a plain wallet. Writer instructions with a recipient or refund account that holds data.Pass the current writer as seller and your authority's wallet as recipient.
6006fill_v3: exposure.active + quantity would exceed exposure.limit.Raise the limit with set_exposure_limit, or wait for open positions to settle.
6007fill_v3 or buy_position_v3: the budget is enabled and spent + amount would exceed limit. spent never goes down.Raise limit with set_premium_budget, or disable it.
6008A JitoSOL fill (call or put) worth more than 50 SOL of stake-pool value: quantity_atoms × total_lamports > 50,000,000,000 × pool_token_supply. The cap was 2 SOL before the 4 November 2026 upgrade.Quote smaller sizes, from a fresh read of the pool. The cap is per fill, not per desk. See JitoSOL size cap.
6009A JitoSOL fill with a different account in the stake-pool slot, with that account writable or signing, or before the pool has been updated for the current epoch. (A missing pool account gives 8800.)Pass JITO_STAKE_POOL read-only. Near an epoch boundary, retry after the pool updates.
6010update_mint_policy_v1 with a collateral mint whose token program or decimals changed, or a payment mint without 6 decimals. A fill whose policy or usage does not match your Maker, authority or this mint.Derive the policy and usage with deriveMintPolicy(maker, mint).
6011A policy or usage account of the wrong size or version.Pass the accounts created by initialize_mint_policy_v1.
6012update_mint_policy_v1 or pause_mint_policy_v1 with an expected_generation that is not current.Re-read the policy's generation (decodeMintPolicy(...).generation, or the u64 at byte 204) and retry.
6013pause_mint_policy_v1 signed by a key that is neither your authority nor the watcher.Sign with the authority or the watcher.
6014initialize_mint_policy_v1 or update_mint_policy_v1 with a zero terms_id or profile_hash, or a non-zero lifetime limit while it is disabled.Build settings with mintPolicySettingsFor(decodedMarket, caps).

Put setup and put fills return the same codes for the put accounts. 6006 is your put exposure. 6007 is your premium budget for the market's payment token. 6010 to 6014 are your put mint policy (MintPolicyV2), and init_mint_policy_v2 also refuses enabled = true with 6014: a put policy is born disabled. See Cash-secured puts for the codes only puts return.

Token custody (7400s)

Every V3 token movement goes through a checked custody step. It runs before the transfer, so a failed check moves nothing.

CodeHexNameMessage
74000x1ce8CustodyInvalidAccountCustody account identity, state or raw layout is invalid
74010x1ce9CustodyUnsupportedCapabilityThis token capability is not implemented by the custody adapter
74020x1ceaCustodyUnauthorizedCustody authority is not the verified owner signer or canonical program PDA
74030x1cebCustodyUnsafeRecipientCustody recipient has a delegate or foreign close authority
74040x1cecCustodyUnsafeSourceCustody source has a delegate or foreign close authority
74050x1cedCustodyInvalidAmountCustody transfer is zero, unbacked or overflows the recipient balance
74060x1ceeCustodyPostTransferMismatchCustody transfer did not produce its exact spendable balance changes
CodeWhen you hit itWhat to do
7400A token account in the transfer is frozen.Use an account that is not frozen. Wrong mint or owner shows up earlier as another code: TokenLifecycleIdentity (8300) for writer_payment and maker_collateral at exercise, and Anchor 2014 or 2015 for writer_collateral and the fill's customer accounts.
7401A token account carries a Token-2022 extension the program does not support.Use plain token accounts.
7403A destination has a delegate, or a close authority other than its owner. At exercise: writer_collateral, writer_payment or maker_collateral. At fill: the customer's USDC account or the fee account.Use a clean account. At exercise and release, use exerciseV3Instructions / releaseV3Instructions: they create fresh token accounts for the writer in the same transaction.
7405Your vault holds less than the gross premium (fill) or the strike (exercise, restricted funding). On a put: your vault for the payment token holds less than the premium, or your put asset vault holds less than the quantity at exercise. Also: the position's collateral vault holds less than its quantity, or the customer lacks the collateral or the lock at fill.Top up the vault with deposit (or the put asset vault with deposit_put_asset_v1). For an exercise, do it before the window closes. After the window, anyone can release the position.
7402, 7404, 7406Internal custody checks: the transfer authority is not the owner that signed or the program's own address (7402), a program-owned source account such as your vault or an escrow has a delegate or a foreign close authority (7404), or the balances after a transfer did not change by exactly the amount (7406).You should not see these with SDK builders and plain token accounts. Simulate, and keep the transaction logs if you do.

Maker and registration (7600s, 8000s, 8700s, 8800)

CodeHexNameMessageWhen you hit it and what to do
76000x1db0MakerFenceSchemaMaker fence allocation, discriminator, tail or current data is invalidThe account passed as your Maker is not a well-formed Maker. Pass deriveMaker(makerEthAddress).maker.
76020x1db2MakerFenceUnauthorizedMaker fence requires the canonical account and registered owner authorityThe Maker account is not the PDA of its own quote key, or not owned by the program. Pass deriveMaker(makerEthAddress).maker.
80000x1f40MakerOriginSchemaFirst-registration maker origin schema is unsupportedbootstrap_mint_usage_v1 with a wrong origin account. Pass deriveMaker(makerEthAddress).origin.
80010x1f41MakerOriginIdentityFirst-registration origin is not bound to this maker, deployment or payment cohortSame: the origin belongs to another Maker or deployment.
80020x1f42MakerOriginStateMaker birth fence or unused mint-usage bootstrap state is invalidbootstrap_mint_usage_v1 on a usage account that is already bootstrapped. It runs once per mint, so check bootstrapped (offset 204) first. Also initialize_mint_purchase_policy_v1 before bootstrap.
87000x21fcMakerMigrationSchemaMaker migration schema or provenance allocation is unsupportedAn internal account check failed: the origin account of a fill or sale is not your MakerOriginV1. You should not see this with SDK builders. Pass deriveMaker(makerEthAddress).origin.
87010x21fdMakerMigrationIdentityMaker migration provenance, historical record or selected seal differsAn internal account check failed: the origin account belongs to another Maker or deployment. You should not see this with SDK builders. Pass deriveMaker(makerEthAddress).origin.
88000x2260MakerMigrationHoldsSchemaMaker migration holds or terminal evidence schema is unsupportedWrong number of remaining accounts on a fill: a JitoSOL fill without the stake pool account, or any extra account. A JitoSOL fill takes exactly one (JITO_STAKE_POOL, read-only). Other mints take none. SDK builders add it for you.

Markets (8200s)

CodeHexNameMessageWhen you hit it and what to do
82000x2008MarketV3SchemaV3 market schema is unsupportedThe market account is not a 376-byte V3 market owned by the program, or its mode does not match the instruction (ordinary versus restricted). Decode it with decodeMarketV3 and use settlementMode.
82010x2009MarketV3IdentityV3 market identity or canonical address is invalidThe market is not at its own PDA, its payment or deployment is wrong, or the collateral mint changed since the market was created (for example a new mint authority). Fills on that market stay closed. Use a newer market.
82020x200aMarketV3TermsV3 market terms are invalidcreate_market_v3 with expiry less than 60 s or more than 90 days away, a window outside 60 to 3,600 s, a zero strike or size, a fee above 1,000 bps, or a zero fee owner.
82030x200bMarketV3UnsupportedToken requires a settlement capability not implemented by ordinary V3create_market_v3 with native SOL, a mint with a freeze authority, or a Token-2022 mint with extensions.

Position lifecycle (8300s)

CodeHexNameMessageWhen you hit it and what to do
83000x206cTokenLifecycleIdentityV3 lifecycle account identity is invalidAn account does not match the position or market: wrong exposure, budget, policy, usage, writer, mint or token program; a non-USDC payment mint; an extra remaining account on exercise or release. Rebuild the instruction with the SDK builder from a fresh, finalized read.
83010x206dTokenLifecycleTermsV3 lifecycle terms or transition are invalidbuy_position_v3 on a position whose terms do not match its market, or a writer instruction on a restricted position.
83020x206eTokenLifecycleAccountingV3 lifecycle accounting or admission rejected the transitionYour mint policy refused the fill. Read the COVR_TOKEN_ACCOUNTING reason line: Unbootstrapped, Paused, Terms or Limit. Fix the policy with update_mint_policy_v1, or wait for open positions to settle.
83040x2070TokenLifecycleAuthorityV3 lifecycle authority is invalidexercise_v3 or fund_restricted_exercise_v3 signed by a key that is neither your authority nor your current operator. early_close_v3 signed by someone other than the writer.

Restricted settlement (8400s)

Restricted markets are covr-only for now.

CodeHexNameMessage
84000x20d0RestrictedTermsRestricted timeout, terms identifier or record mode is not the agreed restricted terms
84010x20d1RestrictedStateRestricted position state does not permit this transition
84020x20d2RestrictedTimeRestricted transition is outside its funding, completion or cancellation time
84030x20d3RestrictedApprovalRestricted cancellation request does not bind both parties to the exact current amounts
84040x20d4RestrictedImpairedRestricted collateral vault no longer backs the full claimed quantity
84050x20d5RestrictedEscrowRestricted strike escrow is not exactly funded, fresh or fully refundable

RestrictedTime on fund_restricted_exercise_v3 means you are outside the exercise window. RestrictedImpaired means the position's collateral vault holds less than its quantity, so funding is refused.

Flash exercise (9100s)

begin_flash_exercise_v3, finish_flash_exercise_v3 and the flash policy instructions return these codes. Flash exercise explains each one. The flash put pair, begin_flash_put_v3 and finish_flash_put_v3, also returns 9100 to 9103, 9114 and 9118. Its policy and floor codes are in the 9200s.

CodeHexName
91000x238cFlashNotTopLevel
91010x238dFlashInstructionsSysvar
91020x238eFlashPairing
91030x238fFlashProtectedAccount
91040x2390FlashPolicySchema
91050x2391FlashPolicyOwner
91060x2392FlashPolicyDisabled
91070x2393FlashPolicyGeneration
91080x2394FlashPolicySettings
91090x2395FlashPolicyLimit
91100x2396FlashPairUnsupported
91110x2397FlashFloorArithmetic
91120x2398FlashFloorBelowPolicy
91130x2399FlashPaymentBelowFloor
91140x239aFlashDelegate
91150x239bFlashEndpoint
91160x239cFlashRecipient
91170x239dFlashContext
91180x239eFlashPositionState

Code 9000 (0x2328, LegacyCloseNeedsMigrationConsumption) also exists. It applies only when a migrated maker closes an old settled position. Desks registered with register_maker_v3 never see it.

Cash-secured puts (9200s)

The put instructions added on 4 November 2026 return these codes. Desks cannot quote puts yet: see Cash-secured puts. The Users error table lists which instruction returns which.

CodeHexNameMeaning
92000x23f0PositionKindThe market, position or policy is not a put, or its terms id is not the put terms id. For example, a call market passed to fill_put_v3.
92010x23f1AccountingVersionA USDC covered-call market or position was passed to a put instruction.
92020x23f2KindNotEnabledkind 0 (call) on a put setup instruction. This release accepts only kind = 2.
92030x23f3KindInvalidkind is neither 0 nor 2.
92040x23f4PaymentProfileThe payment mint is not a plain 6-decimal SPL Token mint (82 bytes, initialized, not native SOL), differs from the market's or the policy's, or has changed since your put policy last approved it. Re-approve it with update_mint_policy_v2.
92050x23f5PutFundingA put position carries funding fields or a cancellation timeout. Puts have neither.
92060x23f6PutStateThe put position's state is not open, exercised, released or early-closed.
92070x23f7PutBackingA put policy's put_backing is not 1, 2 or 3.
92080x23f8PurchasePolicyForeignThe purchase policy or usage passed to buy_put_position_v3 or update_mint_purchase_policy_v2 is not the buyer's own for this asset, payment token and kind.
92090x23f9PutEscrowThe strike escrow does not hold exactly T right after the fill's lock, or holds less than T at an exit.
92100x23faPutAssetSourceThe put asset vault passed is not your canonical one for this asset (seeds "put-asset-v1", Maker, asset), at exercise or when creating a flash put policy.
92110x23fbPaymentSpendLedgerYour spend ledger for this payment token is missing, belongs to another Maker or token, or is malformed. Create it with init_payment_spend_ledger_v1.
92120x23fcPaymentSpendBalanceFor a payment token other than USDC, your premium budget's spent no longer equals the ledger's total, or a ledger counter would overflow.
92130x23fdOriginRequiredReserved for call fills in a payment token other than USDC. No instruction returns it in this build.
92140x23feFlashPutPolicySchemaThe flash put policy's address, bump, size or version is wrong.
92150x23ffFlashPutPolicyOwnerA policy write not signed by your Maker's authority, or a policy whose stored Maker or owner differs from your Maker and its authority.
92160x2400FlashPutPolicyDisabledThe flash put policy is disabled.
92170x2401FlashPutPolicyGenerationexpected_generation (update) or expected_policy_generation (begin) is stale, exhausted or reserved. Re-read the policy and retry.
92180x2402FlashPutPolicySettingsInvalid flash put settings: enabled with a zero cap or a zero maximum price, a cap that overflows the floor math, or enabled = true in init_flash_put_policy_v1.
92190x2403FlashPutPolicyLimitThe position's quantity or lock is above the policy's caps.
92200x2404FlashPutPairUnsupportedThe asset and payment pair is not admitted (JitoSOL with USDC or USDT only), or does not match the position.
92210x2405FlashPutFloorArithmeticThe asset floor overflowed.
92220x2406FlashPutFloorBelowPolicyYour min_asset_atoms is below the policy floor max(Q + A, ceil(T × 10^d / R)), where A is your minimum asset surplus and R your maximum price.
92230x2407FlashPutAssetBelowFloorThe swap left less new asset in the output account than your floor.
92240x2408FlashPutEndpointA temporary input or output account has the wrong owner, mint, delegate, close authority or starting balance.
92250x2409FlashPutRecipientThe writer's asset account or your put asset vault is not acceptable as a destination: wrong owner, mint or program, frozen, native, or with a delegate or foreign close authority.
92260x240aFlashPutContextThe flash put context's address, version or bound accounts do not match.

Errors from Anchor and other programs

CodeHexFromMeaning for a desk
00x0System program, on an account the instruction createsThe account already exists. On fill_v3: that quote nonce already opened a position. On setup: you already ran that step.
10x1SPL Token, on deposit or withdrawInsufficient funds in the source account.
20010x7d1Anchor ConstraintHasOneThe signer is not Maker.authority, or an account does not belong to your Maker.
20060x7d6Anchor ConstraintSeedsAn account is not at the PDA the instruction expects. Re-derive it with the SDK.
20120x7dcAnchor ConstraintAddressA mint or program account is not the one the market names (for example, not USDC).
2014, 20150x7de, 0x7dfAnchor ConstraintTokenMint, ConstraintTokenOwnerA token account has the wrong mint or owner, for example a deposit source not owned by your authority.
30020xbbaAnchor AccountDiscriminatorMismatchAn account of the wrong type was passed, for example a Maker where a market is expected.
30070xbbfAnchor AccountOwnedByWrongProgramAn account is owned by another program, for example a Token-2022 mint passed to set_exposure_limit (the SDK's setExposureLimit refuses that before you send).
30120xbc4Anchor AccountNotInitializedAn account the instruction reads does not exist yet. Run the setup step that creates it.

Decode an error from a failed transaction

From the command line, solana confirm -v <signature> prints the logs of a sent transaction. In code, simulate first and read logs:

ts
import type { Base64EncodedWireTransaction, Rpc, SolanaRpcApi } from '@solana/kit';
import { PROGRAM_ID } from '@covrfun/maker-sdk';

const COVR_ERRORS: Record<number, string> = {
  6000: 'BadSignature', 6001: 'InvalidTerms', 6002: 'InvalidAmount', 6003: 'InvalidOrder',
  6004: 'Unauthorized', 6006: 'ExposureLimit', 6007: 'PremiumBudgetExceeded',
  6008: 'JitoSolOrderLimit', 6009: 'InvalidJitoPool', 6010: 'MintPolicyIdentity',
  6011: 'MintPolicySchema', 6012: 'MintPolicyGeneration', 6013: 'MintPolicyUnauthorized',
  6014: 'MintPolicySettings', 7400: 'CustodyInvalidAccount', 7401: 'CustodyUnsupportedCapability',
  7402: 'CustodyUnauthorized', 7403: 'CustodyUnsafeRecipient', 7404: 'CustodyUnsafeSource',
  7405: 'CustodyInvalidAmount', 7406: 'CustodyPostTransferMismatch', 7600: 'MakerFenceSchema',
  7602: 'MakerFenceUnauthorized', 8000: 'MakerOriginSchema', 8001: 'MakerOriginIdentity',
  8002: 'MakerOriginState', 8200: 'MarketV3Schema', 8201: 'MarketV3Identity',
  8202: 'MarketV3Terms', 8203: 'MarketV3Unsupported', 8300: 'TokenLifecycleIdentity',
  8301: 'TokenLifecycleTerms', 8302: 'TokenLifecycleAccounting', 8304: 'TokenLifecycleAuthority',
  8400: 'RestrictedTerms', 8401: 'RestrictedState', 8402: 'RestrictedTime',
  8403: 'RestrictedApproval', 8404: 'RestrictedImpaired', 8405: 'RestrictedEscrow',
  8700: 'MakerMigrationSchema', 8701: 'MakerMigrationIdentity', 8800: 'MakerMigrationHoldsSchema',
  9100: 'FlashNotTopLevel', 9101: 'FlashInstructionsSysvar', 9102: 'FlashPairing',
  9103: 'FlashProtectedAccount', 9104: 'FlashPolicySchema', 9105: 'FlashPolicyOwner',
  9106: 'FlashPolicyDisabled', 9107: 'FlashPolicyGeneration', 9108: 'FlashPolicySettings',
  9109: 'FlashPolicyLimit', 9110: 'FlashPairUnsupported', 9111: 'FlashFloorArithmetic',
  9112: 'FlashFloorBelowPolicy', 9113: 'FlashPaymentBelowFloor', 9114: 'FlashDelegate',
  9115: 'FlashEndpoint', 9116: 'FlashRecipient', 9117: 'FlashContext', 9118: 'FlashPositionState',
  9200: 'PositionKind', 9201: 'AccountingVersion', 9202: 'KindNotEnabled', 9203: 'KindInvalid',
  9204: 'PaymentProfile', 9205: 'PutFunding', 9206: 'PutState', 9207: 'PutBacking',
  9208: 'PurchasePolicyForeign', 9209: 'PutEscrow', 9210: 'PutAssetSource',
  9211: 'PaymentSpendLedger', 9212: 'PaymentSpendBalance', 9213: 'OriginRequired',
  9214: 'FlashPutPolicySchema', 9215: 'FlashPutPolicyOwner', 9216: 'FlashPutPolicyDisabled',
  9217: 'FlashPutPolicyGeneration', 9218: 'FlashPutPolicySettings', 9219: 'FlashPutPolicyLimit',
  9220: 'FlashPutPairUnsupported', 9221: 'FlashPutFloorArithmetic', 9222: 'FlashPutFloorBelowPolicy',
  9223: 'FlashPutAssetBelowFloor', 9224: 'FlashPutEndpoint', 9225: 'FlashPutRecipient',
  9226: 'FlashPutContext',
};

/** The first program that failed, its custom error code, and covr's name and reason if it is covr's. */
export function decodeFailure(logs: readonly string[]) {
  for (const line of logs) {
    const m = /^Program (\w+) failed: custom program error: (0x[0-9a-fA-F]+)$/.exec(line);
    if (!m) continue;
    const program = m[1], code = Number.parseInt(m[2], 16);
    const ours = program === PROGRAM_ID && code >= 6000;
    const reason = logs.find((l) => /^Program log: COVR_[A-Z_]+: /.test(l))?.slice('Program log: '.length);
    return { program, code, name: ours ? (COVR_ERRORS[code] ?? `covr error ${code}`) : undefined, reason };
  }
  return undefined;
}

export async function simulateAndDecode(rpc: Rpc<SolanaRpcApi>, tx: Base64EncodedWireTransaction) {
  const { value } = await rpc.simulateTransaction(tx, { encoding: 'base64' }).send();
  return value.err ? decodeFailure(value.logs ?? []) : undefined;
}

// decodeFailure(['…', 'Program 8ZpbTPnDECPTDGN5VHHKH5gfer6EUTnRHcFwfUAbkJDg failed: custom program error: 0x1773'])
// -> { program: '8ZpbT…', code: 6003, name: 'InvalidOrder', reason: undefined }

The first failed line belongs to the innermost program that failed. If it is the SPL Token program, the code is a token program error, not covr's.