Instaswap
Instaswap matches swap paths to the assets, amount, and addresses supplied for a transaction, subject to route limits
Updated ยท
Instaswap compares decentralized liquidity paths after a user chooses the input asset, output asset, amount, and receiving address. A usable path must support the selected assets on their respective networks, accept the amount, produce an acceptable expected output, and settle on the intended network. The interface also supports walletless deposits, connected sending on certain networks, and separate trading or distribution functions. The best choice is a current quote that fits the request and shows its costs and constraints. After execution, the status record and output transaction must provide verifiable completion evidence. Check for missing prerequisites before depositing. Then use the transaction goal, execution states, and settlement evidence to decide whether another Instaswap mode or an external route fits better.
Contents
Functions built around different transaction goals
Instaswap separates straightforward conversion, walletless transfer, distribution, and trading functions. Its routing layer draws on decentralized protocols that include THORChain, Chainflip, Maya Protocol, NEAR Intents, 1inch, Jupiter, and Uniswap. Each function solves a different transaction problem, so an available route in one mode does not establish availability in another.
Native and cross-chain swaps
Native swap routes exchange supported assets in their original blockchain form rather than requiring a wrapped representation. Some requests need one cross-chain leg, while others may combine cross-chain settlement with liquidity on the destination network. Route construction remains dynamic because the selected pair, amount, and available liquidity all affect the quote.
Walletless and connected sending
Walletless sending uses a temporary deposit address and a destination address supplied by the user. It removes the need to connect a wallet to the interface, but the sending wallet must still transfer the exact quoted asset and amount. Connected sending is a separate entry path available for certain wallet and network combinations.
Trading and distribution modes
Spot trading, perpetual contracts, Split Swap, payments, and tokenized stocks serve purposes beyond a direct asset conversion. Spot orders provide order-book execution, while perpetuals create leveraged price exposure and carry liquidation risk. Distribution tools divide settlement among destinations. Tokenized stocks remain subject to their issuers' eligibility rules and do not provide ordinary shareholder voting rights.
Inputs that determine route availability
Route selection begins with the full asset identity, including its network. A shared ticker does not prove that two token representations are interchangeable. The input network tells the system where funds will arrive, while the output network determines the required receiving-address format.
The amount also changes which routes are available. A small request may fall below a route minimum, while a larger request may encounter greater price impact or insufficient liquidity. The live quote, not Instaswap's general asset coverage, determines whether the requested amount fits a route.
Address compatibility is a prerequisite, not a finishing detail. The receiving address must belong to the output network. A refund address, when required, must be usable for the input asset so a failed route has a valid recovery destination.
- Input asset and its native network
- Output asset and destination network
- Deposit amount and route minimum
- Receiving and refund address compatibility
- Expected output, fees, and estimated duration
Liquidity, network conditions, and protocol availability can change between otherwise similar requests. A route shown for one amount cannot be assumed to support a different amount. Changing the asset representation or destination network creates another request rather than a minor edit.
Compare quotes using the same inputs. Holding those inputs constant makes differences in expected output, disclosed costs, timing, and recovery conditions easier to interpret.
What does a quote actually tell you?
A quote describes the proposed route for a particular pair and amount at that time. It can include the estimated output, a fee breakdown, an estimated duration, and the deposit information needed to create the swap. Expected output remains an estimate because execution and network conditions can move. The fee breakdown should be read together with the amount that reaches the destination, while the time estimate is a planning value rather than a completion deadline. A quote is not settlement evidence; the status record and receiving-chain transaction serve that purpose.
Limits that can rule out a path
Route limits identify whether the request can proceed as entered. Check them before sending a deposit, because changing the request afterward cannot correct a transfer made under incompatible details.
Asset and protocol coverage
Coverage depends on a supported input asset, output asset, and route between their networks. A listed asset may not form a usable pair with every other listed asset. Temporary protocol or network unavailability can also remove a path that appeared earlier.
Amount and liquidity boundaries
Minimum input requirements vary by asset and route, so the live quote must establish whether the requested amount is accepted. Available liquidity and price impact can make another route preferable even when both accept the same amount. Splitting a request changes the comparison and may add network costs.
Address and execution constraints
The receiving address must use the format of the selected destination network. The quoted deposit asset, network, amount, and address also need to remain together. Sending another asset, using another network, or altering the amount can prevent the system from matching the deposit to the intended execution.
A hypothetical route decision with an address mismatch
All changing inputs in this example are hypothetical: the input asset, output asset, destination network, receiving address, refund address, and an amount of 37.7 input-asset units. No live pair, rate, or recommended amount is implied.
In the normal path, the receiving address matches the hypothetical destination network, and the refund address matches the input network. Once the pair, amount, receiving address, and refund address are compatible, a live quote supplies the expected output, fees, duration estimate, and deposit instructions. After the exact deposit is detected, the status advances through execution. A confirmed output transaction at the supplied destination provides receiving-state proof.
In the edge case, the hypothetical receiving address belongs to another network. The address mismatch should stop the request before any deposit is sent. The safe correction is to replace it with a compatible address and obtain a fresh quote. The corrected request succeeds only if the pair, amount, and route remain available.
Once funds have been sent, a second improvised transfer does not repair the first request; its status and any refund state must be handled as their own records.
How can completion be checked?
Completion is established by matching the swap record with the output transaction on the receiving network. The documented lifecycle moves through awaiting deposit, deposit detected, swapping, and complete, with failed or refund states when execution cannot finish. Those states distinguish a missing deposit from a route that is already processing.
A complete state should correspond to an output transaction for the selected asset and destination. If the record remains at awaiting deposit, the first check is whether the quoted asset, network, amount, and deposit address match the transfer. A refund state proves recovery was initiated or recorded; it does not prove that the requested swap completed.
Custody, privacy, and route-specific risk
Risk depends on the mode and the protocols that carry the transaction. Non-custodial routing avoids an internal exchange balance, but it does not remove blockchain congestion, liquidity changes, address errors, smart-contract exposure, or protocol failure.
The custody boundary
Non-custodial execution means Instaswap does not maintain a customer balance that must later be withdrawn. The user controls the receiving address and initiates the deposit from a wallet or service, while the selected protocols handle the transaction during settlement. Funds still leave the sending wallet when the deposit is made, so the quoted route and recovery address remain material.
Privacy depends on the selected rail
Walletless operation means the interface does not require a wallet connection. That property alone does not make every transaction private or unlinkable. Private settlement is route-dependent and available only where the selected assets and rail support it. Public blockchains may still expose deposits, payouts, amounts, and timing.
Failure and refund evidence
A route failure can move the request into a refund state tied to the supplied refund address. That state is distinct from a completed output. The refund transaction, input-network confirmation, and final status should agree before the request is treated as recovered.
When another approach fits better
Another mode fits better when the user's goal differs from immediate conversion. A spot limit order may suit a same-market trade that needs explicit price control. Split Swap or payments suit distribution to several destinations. Perpetual contracts provide leveraged exposure, but they do not replace receipt of the underlying asset and introduce margin and liquidation conditions.
An external route may be necessary when no supported path accepts the pair, amount, destination network, or address type. The comparison should preserve the same intended outcome while accounting for custody, network steps, quoted output, and recovery options. Changing the goal merely to use an available route can create a transaction that completes technically but fails the original task.
Does the cheapest quote always make the best choice?
No. A route with the highest estimated output may still be unsuitable if its minimum, destination network, duration, address requirements, or refund conditions conflict with the request. Compare quotes using identical inputs, then judge the net output and execution conditions together. When settlement speed matters more than a small output difference, the faster compatible route may fit. When price control matters more than immediate conversion, an order-book trade may be preferable to an instant cross-chain swap.
Practical questions about Instaswap
Do I need an account to use a walletless swap?
No. A walletless swap does not require an Instaswap account or a connected browser wallet. You provide a compatible receiving address and, where required, a refund address before sending the quoted deposit to a temporary address. The sending wallet or service and the receiving wallet must still support the exact assets and networks selected for the route.
Is a wallet connection available for every input network?
No. Connected sending is documented for EVM-compatible and Solana wallets, while other input networks use the walletless deposit flow. Walletless operation still requires a separate wallet or service that can send the quoted asset on the correct network. It changes how the deposit is submitted, not the need to control a suitable sending address.
Can Instaswap accept fiat for an instant swap?
The current instant-swap service focuses on crypto-to-crypto transactions and does not offer direct fiat purchases. A card or bank balance therefore cannot serve as the quoted input asset. A reader who needs a fiat entry point must use a service that supports it, then evaluate that service's custody, identity, payment, and withdrawal conditions separately.
Does the developer API expose route quotes and status?
Yes. The API provides functions for discovering supported tokens and pairs, requesting a quote, creating a swap, and checking its status. Quote data can include estimated output, fees, and an estimated duration. Integrators should discover valid asset identifiers and minimums from the live token data rather than storing assumptions about permanent route coverage.
May a split distribution send different amounts to each address?
Yes. Split Swap supports multiple destination addresses with configurable allocation rather than requiring every destination to receive the same amount. The operation is quoted and validated before the deposit address is created, including applicable per-leg minimums. Each destination address must support its assigned output asset and network, even though the distribution starts from one deposit.
Are Bitcoin and Monero supported as native swap assets?
Yes. Bitcoin and Monero appear among the documented native assets supported by Instaswap. Their presence does not mean every pair, amount, or route is continuously available. The live interface must still produce a valid quote for the selected input, output, amount, destination address, and any required refund address before funds are sent.
What happens if I change the amount after receiving a quote?
Changing the amount creates a different routing request, so a fresh quote is needed. Minimums, available liquidity, price impact, expected output, fees, and timing can all depend on size. Sending an amount that differs from the deposit instructions may stop the system from matching or executing the intended swap, even when the asset and network are otherwise correct.
Do tokenized stocks provide shareholder voting rights?
No. The tokenized stocks available through Instaswap track referenced shares under third-party issuer terms, but they do not provide ordinary shareholder voting rights. Eligibility restrictions also apply, including exclusions for certain jurisdictions. These tokens should be assessed through their issuer conditions, collateral arrangement, market behavior, and wallet support rather than treated as conventional brokerage shares.