Automatic Retries
When a transaction encounters issues, such as insufficient liquidity or network congestion, Aarc automatically retries the exact intended execution steps at regular intervals for up to 30 minutes:- Retry Intervals - Retries occur every 5 minutes, allowing time for liquidity or network conditions to improve.
- Static Call Data - The core transaction data (desired asset, amount, contract interaction) remains unchanged. However, Aarc’s Coprocessor Engine can adjust gas fees or switch bridging routes when needed.
- Higher Success Rates - Through systematic retry attempts, most temporary issues (like brief liquidity gaps or congestion) can be resolved.
Refund Mechanism
When all attempts fail, the system automatically refunds the user:- Where and How
- If the deposit fails before bridging, users receive their original token on the source chain.
- If it fails mid-route, users receive a stable token (USDC/USDT) or ETH on the chain where the failure occurred.
- Non-Refundable Fees - Gas and LP fees from partial execution cannot be reversed since third-party networks and liquidity providers have already consumed them.
- Designated Recipient
- For direct wallet deposits, refunds go back to the sender’s wallet.
- For CEX or fiat-based deposits, refunds go to the developer-specified fallback address (when direct CEX returns aren’t possible).
Common Failure Scenarios
- Insufficient Liquidity When DEXs or bridges temporarily lack sufficient liquidity for your swap/bridge.
- Network Congestion During severe network congestion or irregular block times, transactions may face delays. Aarc adjusts gas prices or waits for better network conditions. If completion remains impossible, the system ensures your refund.
- Slippage or Pricing Issues Transactions could revert in real-time if prices deviate significantly from the original quote.
- Contract Incompatibility When a target contract (such as a vault or staking contract) cannot accept the final call, leaves the transaction partially complete.