Change now is a Classic Flow swap from wallet setup to receipt

Moving USDT on Ethereum into native SOL

A ChangeNOW Classic Flow order fits this cross-chain move only when the sending wallet holds USDT on Ethereum and the receiving wallet supplies a native Solana address for SOL.

The order has three address roles: the sender, ChangeNOW's generated deposit address and the wallet selected for the payout.

Match the asset instance

USDT identifies value, not the network. In the input selector, Tether USD (Ethereum) points to the ERC-20 token, while Tether USD (Solana) points to an SPL Token mint. MetaMask can source the Ethereum side; Phantom can receive native SOL. A Solana address pasted into an Ethereum field fails format validation, yet a valid EVM address can still belong to the wrong chain. Read the network label beside both tickers.

Create the order

Enter the amount, keep Classic Flow selected and paste the Phantom receive address. The estimate is not an entitlement to a fixed SOL quantity. Confirm the pair, network labels, amount and payout address before ChangeNOW creates the order. If a separate refund field appears, use an address able to receive the original USDT on Ethereum. The generated deposit instruction then becomes the only primary action.

Submit the deposit and close the loop

From MetaMask, transfer the requested ERC-20 USDT amount once to the displayed Ethereum deposit address. ERC-20 transfers use an address without a memo; follow the order screen if it requests extra data. After the source transaction confirms, the order advances through exchange processing and ChangeNOW broadcasts native SOL to the Phantom address. Compare the payout signature, recipient and lamport change on Solana Explorer with the order page. The transfer is complete when that destination-chain record matches the order.

Classic Flow selection before the deposit

Classic Flow is the correct mode only when the sender accepts an estimated payout and wants ChangeNOW to execute against the rate available after the deposit reaches its required confirmation state.

Before creating the order, compare the asset labels and expected output, then decide whether that variable outcome fits the wallet move. Market price, liquidity available for the pair and the amount arriving after the source transaction determine the final conversion. The source wallet's broadcast time also matters because the rate is not fixed while the deposit waits for confirmations. ChangeNOW's classic order page keeps the deposit instruction available for about 24 hours; after that recognition window, create a fresh order and use its newly generated address. Sending late turns a clean automated path into an order-specific review.

Use the displayed minimum as a gate. Create the order only while that amount and the selected pair remain available.

Do the sending and receiving networks have to match?

The sending and receiving networks do not have to match each other in ChangeNOW, but each wallet leg must exactly match the network selected for that side.

Ethereum USDC to Solana USDC is a cross-network example; Bitcoin to XRP is a cross-asset example. On EVM networks, identical 0x address syntax does not identify the chain. Ethereum Mainnet uses chain ID 1, BNB Smart Chain uses 56 and Polygon PoS uses 137. MetaMask can display all three network names while retaining the same account address, so inspect the selected network rather than the address appearance alone. Solana uses a different address system and Phantom exposes network-specific assets.

Network matching ends at the custody endpoints: source wallet to deposit network and ChangeNOW payout network to recipient wallet. The route between them is the service's execution layer, so the two user-controlled endpoints can follow different chains. The pair works when both asset-network entries remain available and both wallets support their respective side.

The one-deposit rule

One ChangeNOW Classic Flow order accepts one deposit, so the sending wallet should broadcast one transfer for the requested asset and amount to the generated address. Do not split the amount across two wallet transactions or append a second transfer to the same order. Multiple deposits move the order to support review. A small test transfer needs its own order; after confirming that route, create a fresh order for the main amount. Create a fresh order whenever a second transfer is necessary.

Where should the refund address point?

A refund address should point to a wallet you control on the original deposit asset's network, because an unprocessed return follows the input side rather than the selected payout side.

For USDT on Ethereum, use an Ethereum address capable of receiving the same ERC-20 token. Do not paste the SOL destination simply because it is the intended output. ChangeNOW limits a return to the originating address or the refund address entered when the order was created, so this field is part of setup rather than an editable destination after deposit. An EVM address carries 20 bytes and displays as 40 hexadecimal characters plus the 0x prefix, creating the familiar 42-character form. EIP-55 mixed case supplies a checksum.

Shared-account networks add another identifier. XRP Ledger destination tags are 32-bit unsigned integers, while Stellar supports 28-byte text memos, 64-bit memo IDs and 32-byte hash memos. Copy the extra ID whenever the order shows one. The address and its memo or tag form one routing instruction; dropping either part changes how the service assigns the deposit or payout.

Source-chain proof before exchange processing

Source-chain proof begins with the sending wallet's transaction identifier, which must show the generated ChangeNOW deposit address, the selected asset and a successful or confirmed network state.

Bitcoin transaction identifiers

A Bitcoin transaction ID represents a 32-byte hash and displays as 64 hexadecimal characters. The explorer record should contain ChangeNOW's deposit address as an output and the intended BTC amount. Bitcoin targets a 10-minute average block interval, yet actual gaps vary, so count confirmations shown by the order instead of converting blocks into a promised clock time.

Ethereum transaction hashes

An Ethereum transaction hash is also 32 bytes and appears as 64 hexadecimal characters after 0x, making a 66-character string. Open it in Etherscan, confirm status success, inspect the To address and read the ERC-20 Transfers entry for tokens such as USDC or USDT. A successful outer transaction without the expected token transfer does not prove the deposit amount moved. Ethereum schedules one slot every 12 seconds and groups 32 slots into an epoch.

Solana transaction signatures

Solana Explorer uses the transaction signature as the lookup key. Confirm the result, source account, destination account, mint and token amount. A Solana account key is 32 bytes and a transaction carries at most 1,232 bytes. Those format checks separate the correct SPL Token transfer from a wallet's human-readable summary. Treat the source leg as proven when the explorer matches the order's deposit instruction.

Order states from deposit to payout

ChangeNOW order states separate the pipeline into awaiting deposit, confirming, exchanging, sending to your wallet and finished, letting each state clearly identify the next dependency. Awaiting deposit means ChangeNOW has not recognized a matching source transfer. Confirming means the network threshold remains unmet. Exchanging begins after acceptance, while sending to your wallet means conversion is complete and payout broadcast is underway. Finished marks service completion, but wallet receipt still requires the payout hash and recipient check. A warning state moves the order to the action shown on the exchange page.

How do you confirm the wallet received the payout?

A wallet has received the payout when the destination-chain transaction succeeds, names the intended recipient and changes the balance of the exact native asset or token contract selected in the order.

Explorer confirmation

Start with ChangeNOW's payout hash, then open the corresponding explorer rather than searching only by amount. Etherscan shows native ETH value or ERC-20 transfer logs; Solscan exposes SOL and SPL Token balance changes; XRP Ledger explorers expose the destination tag and validated result. Match the recipient, asset identifier and final state. For a token, compare the contract or mint with the wallet entry. Wallet interfaces may cache balances, but the chain record remains the receipt. Add the matching contract to MetaMask or mint to Phantom after checking the on-chain identifier.

Wallet display reconciliation

Receipt confirmation needs no outbound transaction from the receiving wallet; spending later is a separate action.

Amounts also need correct precision. One ETH equals 10^18 wei, one SOL equals 1,000,000,000 lamports and one XRP equals 1,000,000 drops. Native USDC uses 6 decimal places, while each ERC-20 or SPL Token defines its own decimal field. Wallet reconciliation is complete when the base units convert to the displayed payout quantity.

Clean exit records for wallet custody

A clean ChangeNOW exit preserves three linked records - the order ID, source transaction hash and payout transaction hash - until the destination wallet and explorer agree on receipt.

Record the selected input network and output network beside those identifiers because a hash without its chain is incomplete. Save the sent amount, estimated amount and actual received amount as separate fields; Classic Flow does not promise the estimate. On EVM chains, include the token contract address when the payout is ERC-20. On Solana, record the mint and recipient token account for an SPL Token payout. For XRP Ledger or Stellar destinations, retain the tag or memo attached to the recipient. These details let a portfolio tracker, accountant or later wallet migration reconcile the same transfer without reconstructing the order from memory, which is examined in Non-Custodial Cross-Chain Swaps.

Delete neither hash after the balance appears; the identifiers prove different legs of the same conversion.

Wallet custody begins when the payout reaches the address controlled by the recipient keys. ChangeNOW's finished state describes its order, while the destination chain describes settlement to that address. The clean exit closes only when both records point to the same asset, network, recipient and quantity.

Change now preflight decision checklist

The ChangeNOW preflight decision is ready only when the two wallets establish every address, network and routing field before the user creates the Classic Flow order.

• Choose the input entry carrying the exact token and source network, such as USDT on Ethereum.
• Choose the payout entry for the chain the receiving wallet supports, such as native SOL on Solana.
• Confirm the source balance covers the displayed deposit and the network's send requirement.
• Enter a same-asset, same-network refund address when the field appears.
• Copy every memo or tag and plan one deposit within the roughly 24-hour classic window.

If any line remains uncertain, resolve it before order creation; the selected network changes the address, transfer record and final receipt.