Simpleswap is a Cryptocurrency Exchange Aggregator for Wallet-to-Wallet Swaps

Simpleswap is a wallet-to-wallet crypto exchange aggregator, meaning it gathers several exchange quotes and sends converted assets to a receiving address. It draws on more than 20 centralized and decentralized liquidity sources, offers fixed and floating rates and does not require an account to create most crypto-to-crypto orders. A transaction can still enter risk-based identity review before completion.

The service suits users moving between native coins or token networks without keeping an exchange balance. Its routing convenience comes with temporary custody during execution, market-set quotes, blockchain fees and strict requirements for the selected network, amount and destination details.

Key takeaway: It is a crypto exchange aggregator that compares 20+ liquidity providers for wallet-to-wallet swaps, suited to cross-chain traders who accept risk-based KYC checks.

Cross-network conversion without an exchange balance

More than 20 liquidity sources give Simpleswap broad route coverage for users moving value between wallets and chains. A Bitcoin-to-Ethereum order illustrates the core use: the sender starts with one native asset and wants another at a separate address. The service selects a quoted route, accepts a one-off deposit and pays the converted asset outward. This format fits wallet rebalancing, native-coin conversion and transfers to a recipient who requires a specific cryptocurrency.

ChangeNOW, Changelly, THORChain and Uniswap on workflow and dependency

Four alternatives expose the main choice among address-based routing, liquidity-pool execution and connected-wallet signing. ChangeNOW, Changelly, THORChain and Uniswap each overlap with Simpleswap while assigning different work and dependencies to the user.

ChangeNOW is the closest workflow match: it generates a deposit address, offers standard and fixed quotes and gives a 10-minute funding window for its fixed rate. Changelly also routes deposits through outside trading venues; its published floating-rate fee is 0.25%, while fixed quotes incorporate a different rate. Both services ask the user to trust an off-chain route between deposit and payout. Their differentiators are pair availability, quoted output, fixed-rate window and handling rules at the moment the order is created.

THORChain uses RUNE-linked liquidity pools for native-asset swaps. A Bitcoin-to-Ethereum route crosses 2 pools internally, yet the user never handles RUNE. Uniswap uses a connected wallet, onchain approvals and smart-contract or intent-based execution; its crosschain interface uses Across for supported network combinations, while its Permit2 signature approval lasts 30 days in the app. Simpleswap suits a user who prefers an address-and-deposit order and accepts a provider-controlled execution interval. The best fit changes with the preferred workflow and dependency.

How does Simpleswap route a swap?

Four stages turn a Simpleswap quote into a payout: quoting, deposit confirmation, provider execution and outbound transfer. The routing engine compares available CEX and DEX liquidity, then presents one receiving estimate rather than a visible order book.

Quote creation

The practical side is covered in Simpleswap rewards. One order records the send asset, receive asset, networks, amount and recipient address. Fixed or floating mode changes when the rate is determined. The page also shows a minimum deposit, because the route must cover conversion and network costs. Creating the order produces a unique Exchange ID and a dedicated deposit instruction.

Deposit recognition

One transaction hash, or TXID, proves the sender broadcast the deposit. Simpleswap watches the selected chain until its provider’s confirmation requirement is met. Bitcoin targets a block about every 10 minutes, whereas Ethereum offers a slot every 12 seconds and groups 32 slots into a 6.4-minute epoch. After conversion, a separate chain wait begins when the payout network records the outbound transaction. Those protocol tempos explain why identical-looking quotes settle at different speeds.

Conversion and payout

One provider route converts the deposited asset and sends the output to the recipient address. The sender does not trade an order book, approve an ERC-20 contract or keep an internal balance for this crypto-to-crypto flow. Payout begins only after the deposit clears the confirmation and routing conditions recorded for that order.

Fixed rates trade flexibility for a 20-minute lock

Two rate modes let a Simpleswap user choose between a 20-minute rate lock and market-priced execution.

A fixed order preserves the displayed exchange rate for 20 minutes. The deposit must reach its address and gain at least 1 blockchain confirmation inside that window. A late deposit still proceeds at the original quote only if the underlying rate remains unchanged; otherwise the order moves to refund or requote handling. The receiving-side network fee is already included in the displayed fixed-rate amount, while the sender pays the deposit transaction fee from the sending wallet.

A floating order calculates final output when the route executes. It has no strict platform time limit or published upper amount limit, but every quote still carries a live minimum. Liquidity, price movement and confirmation time change the payout between quote creation and conversion. Fixed mode therefore favors a known receiving quantity; floating mode favors flexible funding when the chain’s confirmation pace approaches the 20-minute boundary.

Quote anatomy and the costs inside the payout

Three moving inputs shape a Simpleswap payout: the routed market rate, bundled service margin and blockchain network costs.

Two network-fee directions

The sending wallet pays an input-chain fee to broadcast the deposit. Simpleswap includes an estimated output-chain fee in its payout calculation, and fixed quotes display the receiving amount after that deduction. The service does not publish one universal crypto-to-crypto percentage; its margin appears inside the offered rate. Compare the final receiving amount for the same send amount, rate mode and networks, because those three settings define the economic comparison.

A worked quote from units to payout

Every changing input is hypothetical in this worked example: a 1000-unit deposit, a 4-unit input-chain fee, a gross route of 0.5 output units per input unit, a 1% bundled spread and a 2-unit output-chain cost. The wallet needs 1004 input units to send the exact deposit. The route starts from 500 output units, deducts 5 for the spread and leaves 495. Subtracting the 2-unit payout cost produces 493 output units at the receiving address. The user therefore compares a 1004-unit source debit with a 493-unit payout, while the displayed quote changes whenever any labeled input changes.

Network identity decides where the payout lands

Three identifiers - the asset, network and extra tag - decide whether a Simpleswap payout reaches the intended balance. Network identity matters because one ticker can exist under several transfer standards.

USDT on Ethereum uses ERC-20, while USDT on TRON uses TRC-20. EVM-compatible networks can reuse the same 20-byte address format, so matching visible characters does not prove the selected chain. Wallets distinguish Ethereum mainnet with chain ID 1, BNB Smart Chain with 56, Polygon PoS with 137, Arbitrum One with 42161 and Base with 8453. A quote tied to one network expects that network for both the deposit and receiving address. Gas assets differ too: Ethereum, Arbitrum One and Base use ETH, BNB Smart Chain uses BNB and Polygon PoS uses POL.

Shared-address systems add another field. An XRP Ledger destination tag is an unsigned 32-bit value from 0 through 4,294,967,295. Stellar’s numeric memo ID is an unsigned 64-bit value, while its text memo accepts up to 28 UTF-8 bytes. If a receiving wallet supplies a memo or tag, copy it exactly beside the address; payout routing changes with that identifier.

A four-step entry path from quote to payout

Four actions complete a standard Simpleswap order: choose, address, deposit and track. Each action fixes one part of the route before funds move.

Choose the pair and rate

Start with the exact source asset and destination network. Enter the amount, then compare fixed and floating output. The minimum shown belongs to that route at that moment; sending less can prevent completion or make a refund uneconomic. If fixed mode is chosen, begin only when the sending wallet can broadcast promptly enough to meet the 20-minute confirmation condition.

Enter the receiving details

Copy the receiving address from Exodus, Tangem, Cake Wallet, Tonkeeper or another wallet supporting the destination asset and network. Add any memo, tag or Extra ID displayed by that wallet. Read back the asset, network and identifier as 3 separate fields. Tether’s USDT shows why: TRC-20 and ERC-20 keep one ticker while using different networks and address rules. A correct Ethereum-format address alone does not settle whether the intended network is Ethereum, Base or Arbitrum One.

Fund and track the order

Send the exact deposit asset through the exact network shown on the order. Save the Exchange ID before leaving the page and keep the TXID from the sending wallet. The order then moves through confirmation, conversion and payout. A block explorer verifies the deposit or payout transaction, while the Exchange ID reports the service-side stage.

Stop before broadcasting if the pair, network, amount or destination field differs from the wallet’s details. Once a confirmed blockchain transfer reaches the deposit address, cancellation is no longer an ordinary interface action. The next available path follows the status and refund terms attached to the funded order.

Temporary custody creates the central trade-off

One deposit address marks the point where a Simpleswap order becomes dependent on the service and its routed provider. Transactional custody lasts from confirmed deposit to payout or refund.

The service does not keep a standing customer balance for a normal wallet-to-wallet order. Even so, the deposit leaves the sender’s wallet before the converted asset reaches the recipient. During that interval, the user cannot sign the conversion leg or retrieve the asset on demand. Provider availability, asset maintenance, confirmation delay, price movement or a compliance review can pause progress. This time-bounded control differs from an onchain swap where a connected wallet signs the execution against a smart contract, although onchain routes carry their own gas, approval and pool-liquidity dependencies.

The key benefit is reach across assets and chains through one interface, especially when a direct decentralized pool does not connect the desired native coins. The corresponding limitation is counterparty and routing dependency during settlement. That balance changes with order size, chain speed and how readily the user can tolerate a manual review.

Risk-based KYC can interrupt an account-free flow

Two client-check levels, standard and enhanced, let Simpleswap escalate identity review for higher-risk transactions. No account requirement does not mean unconditional anonymity.

The review can request government-issued identification, address details, occupation information, source-of-funds evidence and a liveness check. Enhanced due diligence can also examine source of wealth and expected transactions. The policy calls for review at least annually and retains specified transaction information for no less than 5 years where its retention rules apply. A transaction can remain under review while these checks run. This dependency belongs to the service and its providers, so funding is appropriate only when the user can meet any resulting document request.

Exchange IDs turn an opaque route into a trackable status

Nine published statuses let a Simpleswap user separate blockchain waiting, provider execution and payout handling. The Exchange ID identifies one service order; a TXID identifies one blockchain transaction.

The core progression is Pending deposit, Confirming, Exchanging, Sending and Finished. Failed, Verifying, Expired and Refunded describe exception or recovery states. A Pending deposit order can simply be abandoned if no funds were sent. Once a deposit exists, the TXID shows whether the network included it, while the Exchange ID tells support which order to inspect. Simpleswap offers 24/7 support, but resolution time still follows provider response, network confirmation and any document review linked to the status.

Status reading keeps troubleshooting narrow. Confirming points to the source chain; Exchanging points to the routed venue; Sending points to the payout broadcast. Finished should match an outbound TXID and the destination wallet’s selected network. The useful next step changes with the stage rather than elapsed wall-clock time alone.

From a 2018 exchange service to wallet integrations

Since 2018, Simpleswap has developed from a browser exchange into a multi-source service with mobile and embedded distribution. It operates on 2 mobile platforms, iOS and Android, alongside the web interface. Integrations place the flow inside Exodus, Tangem, Cake Wallet and Tonkeeper, while an API and widget extend routing to other products. The through-line stays constant: one quoted order connects a sender’s asset to a recipient address without an ongoing exchange balance. The model remains useful where its providers and supported networks cover the requested pair.