Simple swap is a quote-to-wallet workflow with recoverable transaction states

Simple swap is a quote-to-wallet conversion flow. You select the assets and networks, enter a receiving address, send one deposit and track the payout. The quote, exchange ID, deposit TXID and final wallet balance form the evidence chain used to resolve a delayed or failed delivery.

Late and mismatched deposits break the quoted path

A late or mismatched SimpleSwap deposit breaks the connection between the quoted terms and the transaction the service receives.

A fixed quote holds its rate for 20 minutes. The deposit must also gain at least one blockchain confirmation inside that window. A deposit arriving later still proceeds at the original rate when that rate remains unchanged. If the rate has moved, the documented options are a refund or completion at a newly accepted rate. Wallet broadcast time alone doesn’t satisfy the condition because the chain must record the required confirmation.

The deposit address belongs to one exchange. Sending another asset, using another network, transferring below the displayed minimum or making a second deposit creates an order mismatch. The service can replace an inconsistent order with a new one, but the original quote no longer describes the received transaction. Save the exchange ID before sending so every later action stays tied to the right order record.

Fixed quotes, floating quotes and direct DEX execution

SimpleSwap offers two quote types, while direct DEX execution exposes wallet approval, on-chain route details and price limits in the signed transaction.

A fixed quote protects the displayed receiving amount during its 20-minute window, and that amount already includes the receiving-side network fee. Your sending wallet pays its own network fee separately. A floating quote shows an estimate, then prices the conversion when processing occurs; it has no strict deposit-time or upper-amount restriction, though the displayed minimum still applies. Uniswap and 1inch execute contract calls from a connected EVM wallet such as MetaMask. THORChain uses native cross-chain liquidity pools. SimpleSwap instead presents one deposit address and delivers the converted asset to the destination, so recovery follows an exchange record rather than a wallet contract call.

Simple swap quote inputs bind the asset, chain and address

Within those limits, Simple swap quote inputs bind four core fields: the sending asset, receiving asset, network on each side and destination address.

An EVM address can look identical across several chains, so its shape doesn’t establish the intended network. Ethereum Mainnet uses chain ID 1, OP Mainnet uses 10, BNB Smart Chain uses 56 and Polygon PoS uses 137. Base uses 8453 while Arbitrum One uses 42161. Tether’s USDT also exists through different token systems, including ERC-20 on Ethereum, TRC-20 on TRON, BEP-20 on BNB Smart Chain and SPL Token on Solana. The network label in the quote selects the ledger and token representation the payout must reach.

Use this pre-deposit decision checklist:

• Pair the ticker with the full asset name and token standard shown in the quote.
• Match the sending wallet’s network to the quote, including the chain ID for an EVM network.
• Confirm the destination wallet supports the exact receiving asset and network.
• Copy any required MEMO, Destination Tag or Extra ID with the address.
• Record the exchange ID, deposit address, quoted amount and selected rate type.

Any difference calls for a fresh quote before the wallet signs the transfer, preserving a clean link between intent and settlement.

Can you verify the deposit before the swap finishes?

You can verify a SimpleSwap deposit independently by matching the wallet transaction to the chain explorer and the exchange record.

Deposit trace

Bitcoin transaction IDs and Ethereum transaction hashes each contain 32 bytes, normally rendered as 64 hexadecimal digits. EVM tools add a two-character 0x prefix, producing a 66-character display. Search the exact identifier, then match the sender, SimpleSwap deposit address, asset, amount and confirmation state. The explorer proves what the network recorded; the exchange ID identifies the service order meant to receive it.

Service state

The service state should advance after the chain records enough confirmations for that asset. A pending chain transaction explains an unchanged confirmation state. When the explorer shows confirmation but the order still awaits a deposit, compare the selected network, transferred asset, amount and any MEMO or tag. Those fields reveal whether the chain event matches the quote.

Payout trace

A finished exchange adds a second on-chain identifier for the outgoing transfer. On Solana, the first Ed25519 signature serves as the transaction ID and each signature occupies 64 bytes. A recent blockhash remains valid for 150 slots; a wallet transaction expiring before broadcast needs a fresh blockhash and signature. For a payout already broadcast, its signature leads directly to the recipient account and token balance.

Transaction states from deposit to delivery

Beyond the basics, SimpleSwap transaction states divide deposit, confirmation, conversion, payout and recovery into checkpoints with separate operational meanings.

Ten documented labels cover the full order record. A normal path moves through Awaiting your deposit, Confirming transaction, Exchanging, Sending and Finished. Failed marks a stopped order, while Verifying marks additional monitoring. Expired means the required action missed its applicable time. Refunded records returned assets. New Swap Created shows SimpleSwap replaced the trade order after an inconsistency such as another coin, network or deposit amount. Reading the exact label prevents a payout delay from being mistaken for an unconfirmed deposit.

The chain record and service state answer different questions. SimpleSwap doesn’t accept order changes during three middle states: Confirming transaction, Exchanging and Sending. Confirmation counts come from the asset’s network, while Exchanging covers provider execution and Sending covers dispatch to the recipient address. Pairing the state with the relevant TXID narrows the next check to one system.

Output checks at the receiving wallet

Output verification compares the payout transaction, asset identifier and integer base units with the quote’s receiving asset and destination.

Asset identity and precision

Blockchain balances use fixed base units rather than decimal display text. One BTC equals 100,000,000 satoshis, one ETH equals 10^18 wei and one XRP equals 1,000,000 drops. One SOL contains 1,000,000,000 lamports. Token balances add a contract or mint address and a decimals setting. USDT on Ethereum and USDT on Solana therefore occupy different ledger objects even when a wallet shows the same ticker.

Destination balance and payout

Match the payout’s recipient, asset contract or mint, transferred base-unit amount and successful execution state. ERC-20 transfers appear in Ethereum-compatible token logs. SPL Token transfers credit a Solana token account linked to the wallet owner and mint. Some wallet interfaces hide an unfamiliar token until its contract or mint is added, while the explorer already shows the ledger balance. That distinction turns a display issue into a precise wallet-indexing task.

Recovery paths for failed, expired and refunded swaps

For a regular user, SimpleSwap recovery starts from the last confirmed fact: no deposit, confirmed deposit without conversion or payout without wallet display.

No deposit was sent

An untouched order needs no cancellation. Leave it unused and create a new quote with the corrected pair, network, address or rate type.

The deposit confirmed but processing stopped

Failed, Verifying and Expired states call for support with the exchange ID and deposit TXID. Include the asset, network, amount, destination and required MEMO or tag. A late fixed-rate deposit with a changed rate leads to a choice between a refund and execution at a newly accepted rate. A transfer below the displayed minimum has weaker recovery prospects because network costs can consume the amount required to return it.

Refund tracking

A refund goes to the original sending address or the refund address supplied with the order; SimpleSwap can require the original address in some cases. SimpleSwap states refund requests are processed within up to 31 calendar days. Network costs can come out of the deposit, and a token refund can require the chain’s native coin for network fees. The refund TXID then closes the evidence chain at the receiving wallet.

Route selection behind the quote

Under normal conditions, SimpleSwap route selection converts the completed trade order into one liquidity-provider execution and a separate wallet payout.

The selector evaluates the trading pair, amount, rate type and available provider terms before choosing an execution path. Centralized venues such as Coinbase and Kraken match trades through order-book infrastructure; decentralized systems such as Uniswap, 1inch and Jupiter route against on-chain liquidity. Those names describe established route families, not a claim about the provider chosen for a specific order. SimpleSwap keeps that provider decision behind the quote, then exposes the deposit state and final payout state to the user.

This separation explains why route detail and recovery evidence live at different layers. The rate reflects the chosen market path, the deposit TXID proves funding and the payout TXID proves delivery. When execution stalls, the exchange ID connects both chain records to the provider-side order, giving support a bounded case with identifiable inputs and outputs.

Simple swap: reader questions