Error Handling
Identify transaction failures and choose the correct recovery action.
Handle typed SDK errors before retrying. Continue only when the receipt status is "confirmed". After an RPC timeout, check the transaction hash before resubmitting. If the user rejects signing, wait for a new request. Refresh the affected state, quote or allowance before retrying.
Handle each error according to its cause:
LaunchpadTradingClosedError
Curve reached the boundary
Refresh Graduation status. Route to V4 only after poolCreated; otherwise show trading as unavailable.
LaunchpadTradeFeeConsumesInputError
Fees consume the gross amount
Refresh the fee quote. If snipe tax is active, wait for it to decay; do not increase input as a workaround.
LaunchpadInsufficientQuoteReserveError
Sell exceeds real reserve
Reduce size
LaunchpadSlippageError / LaunchpadDeadlineExpiredError
Stale quote
Get a fresh quote and deadline, then rebuild with user-confirmed slippage. Never raise tolerance automatically.
LaunchpadCreatorDeniedError
Per-account ban
Not retryable by that account
LaunchpadLaunchNotPermittedError
Global gate closed
Retryable if whitelisted or reopened
LaunchpadEconomicsHashMismatchError
Launch terms changed
Refresh the parameters, ask the user to confirm the updated terms, then rebuild the hash.
LaunchpadApprovalRequiredError
Missing allowance
Approve the spender it names — forwarder for launchAndBuy, factory for createToken, curve for trades
LaunchpadPhaseUnavailableError from prepareGraduate
Usually already graduated by someone else's trade
Re-read the status; launchpadGraduateIsIdempotentSuccess means done, not failed
Wallet and Holder recovery
Wallet rejected, missing account or wrong chain
Let the user reconnect/switch and prepare again; do not automatically resend
Deployment verification failed
Stop writes and reconcile the complete configuration/ABI version
Approval succeeded but the buy fails for allowance
Check the actual quoteInRaw, asset, spender, account and chain; refund previews do not reduce the upfront pull
Holder integration absent / quote asset disallowed
Disable that feature for this deployment/asset; do not substitute Testnet addresses
Unknown/unregistered distributor
Resolve the token's registered binding; do not infer one from an arbitrary fee recipient
Proof mismatch
Validate recipient, both asset amounts and proof against the on-chain epoch root; refetch for the correct project/chain
Already claimed, excluded, expired or rolled-over epoch
Refresh authoritative chain state and remove the unavailable action
Batch claim reverted
Identify stale/invalid allocations and rebuild the batch; it is all-or-nothing
Harvest returns zero
Display no collectible revenue; harvest does not publish an epoch or pay holders
For a transaction timeout, check the known hash before retrying. After an uncertain creation, also reconcile the consumed salt and creation events. Use Holder claim checks for complete recovery sequences.
Last updated
Was this helpful?