Simpleswap crypto

Simpleswap crypto is controlled by rate and network choices

Simpleswap crypto is a decision workflow in which the chosen rate mode sets quote behavior, while the selected blockchain fixes the valid deposit and payout routes. Before sending funds, match both assets to their networks, confirm the recipient address and any memo, and save the exchange ID. After broadcast, verification moves from the wallet’s transaction ID to SimpleSwap’s exchange states.

The important boundary sits at deposit broadcast. Up to that point, you can abandon the order and rebuild it. Once the wallet sends the transaction, the selected asset, network, amount, and destination govern execution.

It is a swap interface where users choose a pair, network, and rate, send funds, and track payout status by exchange ID; support needs that ID for a missing memo.

Where the quote and network costs separate

SimpleSwap’s displayed receive amount and your wallet’s sending fee belong to different sides of the same order.

The sending-side charge

Your wallet pays one deposit transaction on the sending network. Bitcoin prices that transfer in satoshis per virtual byte, while Ethereum applies its gas market to ETH and ERC-20 transfers. This charge doesn’t go through the quote. It rises with transaction size or network demand, so the wallet balance must cover both the stated deposit and its network fee.

The receive amount

For each Simpleswap crypto quote, the interface offers two rate modes: fixed and floating. A fixed-rate receive amount includes the network fee for sending the converted asset to your recipient address. The deposit-side fee remains separate. A floating quote stays an estimate until processing, so market movement, route liquidity, confirmation time, and the outgoing network cost influence the final payout.

The timing cost

A fixed quote introduces a 20-minute clock and requires at least one confirmation inside it. The wallet’s fee choice therefore affects more than the immediate deposit cost: it affects whether miners or validators include the transfer before the quote expires. Paying the cheapest selectable fee on a busy Bitcoin network puts the rate window at odds with Bitcoin’s 10-minute target between blocks. A floating order removes that strict clock, though its final receive amount remains unsettled until execution.

Build the order before the clock starts

A SimpleSwap order stays internally consistent when the asset, network, address, and tag describe one destination.

Pair and network

Select the sending asset and its source network first, then choose the payout asset and destination network. USDT illustrates the distinction: USDT on Ethereum uses ERC-20, USDT on TRON uses TRC-20, and USDT on BNB Smart Chain uses BEP-20. The ticker describes the asset, while the network selection determines the ledger and address context that SimpleSwap will use.

Recipient and extra identifier

Copy the recipient from the wallet’s receive screen for that exact network. MetaMask and Trust Wallet display the same hexadecimal account across several EVM chains, yet Ethereum Mainnet, Base, Polygon PoS, Arbitrum One, and BNB Smart Chain keep separate balances. A hosted XRP Ledger or Stellar destination also provides a Destination Tag or memo when its shared address needs account-level routing.

Refund route and record

Add a refund address when the sending source can’t reliably accept a return, and keep it on the deposited asset’s network. Save the exchange ID before opening the wallet. Keep a screenshot of the order page until the outgoing transaction appears in the recipient’s ledger. That ID identifies the SimpleSwap order; the later TXID identifies the blockchain deposit. Recording the deposit address, amount, pair, networks, recipient, and memo beside those identifiers leaves support with a coherent transaction record.

How do fixed and floating rates change the decision?

Typically, SimpleSwap’s fixed rate prioritizes a known receive amount, while its floating rate prioritizes flexibility around deposit timing.

In the simplest case, SimpleSwap holds a fixed quote for 20 minutes and requires at least one blockchain confirmation inside that window. The send action alone doesn’t satisfy the condition. The deposit must reach the blockchain soon enough for SimpleSwap to observe the required confirmation before the rate lock ends.

Network tempo changes the fit. Bitcoin targets one block every 10 minutes, leaving only two target intervals inside the fixed window, with no promise that either block includes a particular transaction. Ethereum divides time into 12-second slots and groups 32 slots into a 6.4-minute epoch, so first inclusion follows a different cadence. SimpleSwap’s confirmation requirement still governs the order, and its provider can require further processing afterward. Floating mode has no strict deposit deadline or upper amount limit, but the displayed minimum remains binding and the final receive amount moves with execution conditions.

Choose fixed when the quoted output matters and the sending wallet can broadcast promptly. Choose floating when timing flexibility outweighs output certainty.

Network identifiers that separate similar-looking routes

Network identifiers give a SimpleSwap order an objective check when tickers and hexadecimal addresses look deceptively similar.

An Ethereum account address encodes 20 bytes, rendered as 40 hexadecimal characters after the 0x prefix. That same account form appears across EVM networks, so its appearance alone doesn’t prove the selected ledger. Ethereum Mainnet uses chain ID 1, BNB Smart Chain uses 56, Polygon PoS uses 137, Arbitrum One uses 42161, and Base uses 8453. A wallet must already expose the intended network and recipient before the order is created; matching the chain name and identifier provides a stronger check than matching the address shape.

A TRON address encodes 21 bytes and normally appears as 34 Base58Check characters beginning with T. Only select TRON when both the order and recipient name that network. Compared with a ticker-only check, the chain ID or address format tests the route that will actually settle.

What changes after you send the deposit?

A SimpleSwap deposit becomes an on-chain transaction at broadcast, replacing editable form choices with a fixed transfer record.

Before broadcast, the order is an instruction set and you can leave it unfunded. The wallet signature creates the deposit TXID and commits the chosen asset, network, amount, destination, and memo. A Bitcoin payment consumes existing unspent transaction outputs and creates new outputs; an ERC-20 payment calls the token contract on its selected EVM chain. After confirmation, SimpleSwap observes the deposit, executes through its provider, and creates a separate payout transaction. The recipient’s ledger changes only when that outgoing transfer settles. Wallet history proves the deposit leg, while the payout TXID proves delivery better than the exchange label alone.

Read the exchange state and verify both legs

Even so, SimpleSwap’s exchange state tells you which system owns the next observable event: wallet, blockchain, routing, or payout.

The interface documents nine main states. Pending deposit waits for your transfer; Confirming waits for blockchain inclusion; Exchanging covers conversion; Sending covers the outgoing transfer; and Finished marks completion. Failed, Verifying, Expired, and Refunded describe exception paths that need closer review. These labels report the routed order rather than replacing the ledger. A Finished state should align with an outgoing TXID, the correct recipient, and the selected token contract or native asset.

Use two identifiers when checking progress. The exchange ID follows the order from creation through completion, while the deposit TXID follows the funds you sent. Etherscan exposes Ethereum records, BscScan covers BNB Smart Chain, TronScan covers TRON, and Blockstream Explorer displays Bitcoin transactions. Match network, asset, amount, and recipient on the relevant ledger. Compared with watching the status label alone, verifying both transaction legs shows where each state change occurred.

Recover a missing memo with the right evidence

A missing memo on a SimpleSwap deposit requires the exchange ID, deposit TXID, amount, asset, network, and intended identifier.

Identify the routing field

Memo fields route payments within a shared receiving account; they don’t change the underlying wallet address. XRP Ledger Destination Tags are 32-bit unsigned integers ranging from 0 through 4,294,967,295. Stellar supports a 64-bit unsigned MEMO_ID, a text memo up to 28 bytes, and 32-byte hash memo types. The exact value comes from the receiving service, so the transaction record must preserve it character for character.

Request manual attribution

Contact SimpleSwap support with the exchange ID and deposit TXID, then provide the intended memo or tag, deposit address, amount, and network. Support may request wallet screenshots or another ownership record, and recovery or refund network charges can apply. The published refund process allows up to 31 calendar days, so preserving the original evidence matters. A complete identifier pair gives support a clearer attribution path than sending another transaction to the same address.