Old v2 Documentation (Deprecated)
Last updated
Last updated
The functionality of the Squid boils down to 3 main functionalities:
Route Requests(Fetching a Route): Calculating the most optimized path from one asset to another.
Route Execution: The submission and execution of that path on chain.
Transaction Status: The validation that the transaction has been completed.
There are 3 advanced functionalities enhance Squid's API capabilities:
Transaction Hooks (Pre/Post): Allow transactions to be prepended(prehook) or appended(posthook) to asset transfers for a user. Think unstaking then transferring an asset or transferring an asset across chain then staking.
Boost: Squids novel boost functionality allows cross-chain transactions to be settled in less than 20seconds by using an intent-model, a smart contract overlay which allows a provider to optimistically fulfill a transaction.
Collecting Fees: Always integrators to collect fees associated with transactions. Note, this function is currently not available for v2 yet.
All of the functionalities above are covered in-depth in the Key Concepts section.
We have a mainnet fork(s) simulation environment for testing cross chain transactions with Squid. Get in touch if you would like to use it. We strongly recommend this method. Docs coming soon.
The prices on Testnets are not realistic, so you can end up with swaps and bridges which look like 1 ETH --> 0.0000006 ETH. This is because Squid works by accessing DEX liquidity.
We recommend you swap only aUSDC --> aUSDC on Testnet.
aUSDC is the Axelar bridged version of USDC on testnet. A transfer of aUSDC --> aUSDC across chains has no swaps needed, so you can rely on a 1:1 exchange rate.
