Skip to content
DegenX Docs
Arc mainnetOpen app

Errors & troubleshooting

Use the relevant contract ABI to decode a revert. RPC availability errors are different from contract reverts: an upstream 429/502 does not establish whether a transaction succeeded or failed.

Symptom Check
Buy is unauthorized Correct Arc registry, wallet blocklist status, and actual transaction caller
USDC balance looks a trillion times too large/small Native USDC uses 18 decimals; ERC-20 quote amounts use 6
Insufficient funds despite a trade balance Gas and trade input draw on the same underlying USDC balance
Allowance error Correct token, spender, amount and confirmed approval receipt
Quote is much smaller immediately after launch Launch-specific anti-snipe duration and buyer exemption
Minimum output error Non-zero minimum, fresh quote, correct units and acceptable slippage
Curve trade fails after completion Inspect pool/graduation state and route through the actual v4 pool
Pool swap encoding fails Current Arc Universal Router tuple includes minHopPriceX36
Creator withdrawal is unauthorized Live feeRecipient(token), correct launch escrow, and takeover window
Chart or feed is delayed Indexer cursor, RPC health and confirmed event ingestion

Keep the transaction hash. Query its receipt and the wallet’s latest/pending nonce before sending a replacement or repeating the action. A broadcast timeout does not mean the transaction was never received.

Do not fix a failed quote by setting minimum output to zero. The protocol rejects zero minimum outputs where required, and removing slippage protection is not a reliable diagnosis.

Confirm that you are using the right contract

Section titled “Confirm that you are using the right contract”

Names and symbols are not unique. Use the token address, resolve its gauge through the production launchpad, and use that gauge’s adapter after graduation. An implementation template address is not a user’s launch, and the newest factory adapter is not automatically the adapter for older launches.