Common Errors

Transaction Not Accelerated

Symptom: Transaction sent successfully but not found in Dashboard's Consumption Details.

Possible Cause	Troubleshooting Method	Solution
Insufficient tip amount	Check if tip transfer is >= 0.0003 SOL	Increase tip amount to minimum requirement
Wrong tip account	Confirm transfer target is `7HkiWXe5deJvzn4D6kgMUFCADwX9Z4DMrdjNSSxN6bPp`	Correct tip account address
Wrong endpoint used	Check if pointing to Trading Boost endpoint vs standard RPC	Use booster-sg/hk/de/us.zan.top endpoints
Blockhash expired	Check time interval between transaction construction and sending	Shorten interval, get fresh blockhash for each retry

API Errors

Error Code	Description	Solution
-32600	Invalid request format	Check JSON-RPC request format
-32602	Invalid parameters	Check transaction base64 encoding and tip instruction
-32603	Internal server error	Exponential backoff retry (1s → 2s → 4s)
-32602	Insufficient tip amount	Increase tip to >= 0.0003 SOL
-32602	Invalid/expired API Key	Check API Key in ZAN console
-32602	Transaction format error	Check transaction serialization and signing

Transaction Confirmed but Business Logic Failed

Symptom: Transaction successfully reaches chain (visible on Solscan) but business logic fails (e.g., swap slippage exceeded).

📘
Note:
In Tips mode, if transaction ultimately fails to reach chain, tip is not consumed. However, if transaction reaches chain but business logic fails, whether tip is deducted depends on specific failure reasons.

Connection Issues

Symptom	Possible Cause	Solution
Connection timeout	Inappropriate region selection	Switch to closer regional endpoint
SSL/TLS errors	Using HTTPS with certificate issues	Verify correct domain usage, or switch to HTTP
DNS resolution failure	Wrong domain name	Check endpoint URL spelling