Instaswap
Instaswap lets you compare quotes with fixed inputs and verify results from order and receiving records
Updated ยท
To compare Instaswap swap quotes, keep the selected assets, amount, and settlement mode constant. After creating a swap, verify the order against its status record and any available receiving-side evidence. The quote describes a starting state: the proposed input, estimated output, fee breakdown, and estimated time for the request being priced. Those live values may move when any input changes or a fresh quote is requested. Once an order exists, its transaction identifier, deposit instructions, and status become the handoff record. Use the quote to compare terms before commitment, then use the order record to verify what happened. If the records no longer describe the same request, stop the comparison and return to a fresh quote.
A sound comparison keeps quote inputs fixed, preserves the order record, and confirms completion through status and receiving-side evidence.
From quote request to verifiable result
The normal path begins with one complete request and ends when the recorded output reaches the intended destination. Keep the asset pair, networks, amount, and settlement choice unchanged while comparing quotes. Before creating an order, confirm the destination address and any refund address the route requires. If no valid route appears, revise one input and request another quote. This keeps the rejected request separate from the next comparison.
Before commitment
The quote stage establishes the proposed deposit amount, estimated output, disclosed fee components, and estimated completion time. These fields belong together. Comparing one quote's output with another quote's fees creates a false comparison, even when both requests use the same asset symbols.
After submission
The created order supplies a transaction identifier and deposit instructions for that specific request. Match the deposit amount, asset, network, and address before sending funds. From that point, use the same order identifier to follow status changes. A newly refreshed quote does not amend an order that already exists.
Choices that change the comparison
The comparison stays meaningful only when each changed input is identified. The four choices below show how the scope of a quote moves when a reader accepts, refreshes, or edits the request.
| Available choice | What stays fixed | What may change | Scope of the result |
|---|---|---|---|
| Use the displayed quote | Selected assets, networks, amount, and settlement mode | Market and routing conditions may move before commitment | The displayed asset and network combination |
| Refresh the same request | All entered inputs | Route, estimated output, fees, and estimated time | The newly priced quote only |
| Change the amount | Assets, networks, and settlement mode | Route availability, output, fees, and timing | The revised deposit amount |
| Change an asset, network, or mode | Only fields left unchanged by the reader | The full quote and later deposit instructions | The newly selected combination |
Destination and refund addresses belong to the created order, not the earlier price comparison. If either address must change, create a new order before sending funds. Do not pair an existing order's deposit instructions with a different destination or refund address.
How do you separate a live quote from a durable rule?
A live quote records market and routing conditions for one request, while a durable rule describes how the records relate. Expected output, fees, estimated time, and route availability can change. The requirement to match an order with its own identifier and deposit instructions does not depend on those values.
Stable relationships
A durable comparison keeps like with like. An asset must remain tied to its selected network, the deposit must follow the created order's instructions, and completion must refer to that order's status. Reusing only a ticker or estimated output cannot establish that two records describe the same swap.
Values that can move
A live parameter should be read from the latest applicable record, not copied from an earlier request. Instaswap scores every quote across applicable protocols, so a refreshed request can select a different route. The same inputs may therefore produce another estimate or fee breakdown without changing the underlying comparison method. Once funds move, the created order replaces the quote as the primary lifecycle record.
The starting record as a comparison baseline
The starting record should preserve enough context to reconstruct the decision without relying on memory. Keep the selected input and output assets, their networks, the requested amount, settlement mode, estimated output, fee breakdown, and estimated time. When the swap is created, also save the destination address, any required refund address, order identifier, and deposit instructions.
The quote and order answer different questions. The quote shows what Instaswap proposed before commitment. The order identifies what the system accepted and where the deposit belongs. A later status can then be checked against both: first for continuity with the order, and then for any material difference from the quote.
Status evidence across the handoff
The status record shows where the accepted order is in its lifecycle, from awaiting a deposit to a terminal outcome. It should remain tied to the same transaction identifier throughout that handoff.
The commitment point
The order identifier separates a created swap from an uncommitted quote. Deposit instructions name the asset, network, and address expected by that order. Sending to another address or through another network creates a mismatch that a favorable estimated output cannot repair.
Execution states
The walletless status record uses awaiting deposit, deposit detected, swapping, complete, failed, and refund states. These states trace the lifecycle, but elapsed time alone does not prove that the system advanced to another state.
Receiving-side confirmation
The receiving-side record answers a separate question: whether the intended network recorded the output at the supplied destination. A complete interface status is useful evidence, but a receiving transaction identifier or destination balance change provides the observable counterpart when the interface exposes it. The receiving record should show the output asset at the destination associated with the order.
Recovering from a record mismatch
Recovery starts by locating the first mismatch. Before a deposit, discard a stale or altered quote and price the complete request again. Do not combine fields from the old and new versions.
After a deposit, keep the existing order identifier. A delayed state does not authorize a second payment to the same or a newly displayed address. Compare the source transaction with the order's deposit amount, network, token, and address before taking another action.
A failed or refund state is a recovery outcome, not successful settlement. Follow the refund information attached to that order and confirm the returned asset on its stated network. The original estimated output no longer describes the result.
Missing or contradictory records leave the outcome unresolved. Preserve the quote, order identifier, source transaction, and visible status together so the discrepancy can be examined without reconstructing the request from partial details.
Choosing a route with verifiable records
Choose a route only when its quoted terms are acceptable and its records can verify execution. That means the request can be tied to a created order, the deposit instructions are unambiguous, and the status record reaches an outcome that can be checked against the receiving network.
Instaswap describes its swap routes as non-custodial and on-chain. That custody model does not make a live estimate permanent or replace order-specific evidence. If the route hides a condition that materially affects the decision, leave it out of the comparison. If the quote, order, and receiving record cannot be tied together, treat the swap as unresolved rather than marking it complete.
Questions and answers about Instaswap
Does changing the destination address invalidate an Instaswap order?
Treat a destination change as requiring a newly created order. The recipient address belongs to the submitted swap request, while an earlier quote mainly describes pricing for its selected assets and amount. Do not assume that editing an address updates existing deposit instructions. Use the transaction identifier and destination shown in the replacement order.
Can the estimated output be used as proof of settlement?
No, an estimated output describes the quote rather than the final receiving record. It helps compare available terms before commitment, but it does not show that the destination network accepted a payout. Use the order status and any receiving transaction information exposed for that order to verify the completed amount and destination.
Why did a refreshed Instaswap quote select a different route?
A refreshed quote may reflect another route because the aggregator evaluates the protocols available for that request again. Liquidity, fees, estimated timing, and route availability can move even when the entered assets and amount stay unchanged. Compare the complete new quote with the complete old one, and use only the version attached to the order you create.
Is a source-network deposit enough to mark the swap complete?
No, a source-network deposit proves only that funds were sent toward the recorded deposit address. Completion requires the order status to reach its terminal success state and the output to appear at the intended destination when receiving-side evidence is available. A detected deposit, processing state, failure, or refund records a different outcome.
How long should an Instaswap order remain in the swapping state?
The quote's estimated time is an estimate, not a fixed completion deadline. Actual progress depends on the selected route and the networks involved. If the estimate passes, keep following the same order identifier and compare its status with the source transaction. Do not resend the deposit merely because the order remains in the swapping state.