DEV Community: Anna Botsford

Sending Crypto to an Exchange? Add the Right Tag

Anna Botsford — Thu, 22 Oct 2026 12:54:51 +0000

When an exchange asks for a destination tag or memo, enter the exact value it gives you before sending. The tag tells the exchange which customer account to credit when many customers share one receiving address.

Check the asset, network, address, and tag on the receiving exchange.
Enter the tag in the matching field before you approve the transfer.
For a first transfer, consider sending a small test amount.

A tag sorts deposits sent to one shared address

A destination tag is an extra number or text value attached to a crypto payment. A memo is a similar field, though its name and format depend on the network and wallet.

Some custodial wallets—services that hold crypto for customers—use one blockchain address for many accounts. The address gets the funds; the tag or memo tells the service which customer balance to update. The XRP Ledger documentation describes this as a way to identify the person behind a payment to a shared address.

A transfer to an exchange may need a tag, while a transfer to your own wallet often does not. Your own wallet usually has its own address, so it can identify your funds without a separate customer number. A thor swap search can lead to this same check: a swap route may handle the asset exchange, but the receiving exchange can still require its own tag. For the route question, compare a thor swap aggregator with a direct transfer: neither choice replaces a tag requested by the final recipient.

Check the receiving details before choosing a route

Open the receiving wallet’s deposit screen for the exact coin you plan to receive. Copy its address and tag or memo, then check the network name shown there; the same coin can sometimes move on more than one network.

For example, if an exchange gives you an XRP address and a destination tag, you need both when sending XRP to that deposit. If you send XLM, the exchange may call its identifier a memo instead. Stellar documentation explains that custodial services can use a shared account and a memo ID to match incoming payments to customer accounts.

Compare that with sending XRP to a self-custody wallet—one where you control the keys. The wallet may ask only for an address. Follow the receiving screen’s instructions rather than adding a guessed tag; the wrong extra information can also cause problems.

Enter the tag in its own field and review the transfer

Paste the address into the address field and the tag or memo into its own field. Some wallets label the field “Destination Tag,” “Memo,” or “Memo ID.” Keep any leading zeroes, and do not paste the tag onto the end of the address.

Before approving, compare the asset, network, address, tag, and amount with the receiving screen. If you are using a swap service, check that its final delivery details let you enter every required field. If the tag field is missing, pause and check with the service; a quoted route alone does not confirm that it can pass the tag through.

A test transfer can help when you are unsure. Send a small amount first, then wait for the exchange to show the deposit in your account before sending the rest. The test still has a network fee—the charge for recording a transfer—and may need to meet the exchange’s minimum deposit.

A missing tag can delay credit even when the transfer arrives

If the tag is missing or wrong, the blockchain may still deliver funds to the shared address, but the exchange may not know which customer to credit. The XRP Ledger can reject a payment without a tag when the receiving address has that rule enabled; other cases may need manual support.

Check the transaction status and details in the sending wallet, then contact the receiving service through its official support channel. Give it the transaction ID, asset, network, amount, destination address, and any tag you used. Do not send a second payment just because the first one is not visible yet.

For your next step, open the receiving deposit screen and confirm all five details before you move funds. When a thor swap route ends at a custodial wallet, treat that wallet’s tag requirement as part of the destination, just like its address and network.

Choosing a CoW Swap Order Cancellation Method

Anna Botsford — Thu, 22 Oct 2026 02:52:46 +0000

Choose off-chain cancellation when saving gas matters; choose on-chain cancellation when you want the order invalidated on the blockchain. Both can lose a race with a trade that is already being settled, so speed matters either way.

What changes when I cancel off-chain or on-chain?

Off-chain cancellation asks CoW Swap’s order book—the online list of open trades—to stop offering your order. It costs no network transaction fee, often called gas, but relies on the order book processing your request.

On-chain cancellation sends a transaction to the settlement contract, the blockchain program that checks and completes trades. The contract records that your order is invalid, so a later trade cannot use it. You pay the network’s gas fee for that transaction.

Think of the difference as crossing your name off a shop’s list versus changing the official record. The first is quicker and free when the shop acts promptly. The second creates a public record, but you still wait for the network to confirm it.

Which method should I pick?

For a routine change of mind, I’d pick off-chain cancellation. It avoids a fee, and the interface makes the request straightforward. In the cowswap interface, open your pending order and choose “Cancel order”; check that the right order is selected before confirming.

Choose on-chain cancellation if you prefer the order’s invalidation to be recorded by the contract instead of relying on the order book. It may suit a time-sensitive order when you can submit the transaction promptly and accept the gas cost. That cost changes with the network and congestion, so check the wallet’s fee estimate before signing.

Neither choice guarantees the order stops instantly. Solvers—automated traders that compete to complete orders—may already have included it in a batch auction, a process that checks a group of trades together. If a settlement transaction gets confirmed first, cancellation cannot undo the completed trade.

What is the race, and how do I check the result?

Cancellation races the trade through two different paths. With off-chain cancellation, the order book must process your request before a solver’s settlement can use the order. With on-chain cancellation, the invalidation transaction must be confirmed before the settlement transaction.

For example, if you request off-chain cancellation just after a solver has prepared a settlement, the order may still be included. An on-chain request also has a delay: until the network confirms it, the order can remain valid. A higher priority fee may help your transaction get processed sooner, but it cannot promise that cancellation wins.

After requesting cancellation, check the order’s status in the activity panel or CoW Explorer. For on-chain cancellation, also check that the transaction succeeded on the correct network. If the order shows as filled, compare its settlement time with your cancellation request; a later status update alone does not prove which happened first.

Are there cases where one method is unavailable?

Yes. Orders that use CoW Swap’s Eth-flow route for native ETH can only be cancelled on-chain. That route places the order through a contract that holds the ETH, so the cancellation must also reach the blockchain; a free off-chain request is not available for it.

Also, cancelling an order does not revoke your token approval. An approval lets the protocol spend approved tokens for valid orders; cancelling invalidates one specific order. Revoking the approval is a separate action and is not a substitute for cancelling the order.

For most ordinary orders, I’d start with the free off-chain request and check its status. Pick on-chain cancellation when contract-recorded invalidation matters enough to justify gas, and act quickly with either method.

TRON swap: How to Compare Routes and Complete a Trade

Anna Botsford — Wed, 21 Oct 2026 00:55:44 +0000

A TRON swap exchanges tokens on the TRON blockchain, often using TRC-20, its common token format. TRON swap works when both assets are on TRON and the amount you receive makes sense after costs. Compare a wallet-connected swap with a custodial exchange by checking the final amount and who holds your tokens.

How Does a TRON swap Work?

A wallet-connected swap sends your tokens to a smart contract, code that carries out the trade. It usually trades against a liquidity pool, a supply of both tokens provided by other users. The pool’s balance sets the price, so a large trade can move it.

After you connect a TRON wallet, select the tokens and enter an amount, you get a quote. If you are spending a TRC-20 token for the first time, you may need to approve it first. Approval is a separate transaction that lets the swap contract use a stated amount of that token.

You then confirm the trade in your wallet. The contract takes the input and sends the output to your wallet when the transaction succeeds. Some routes pass through an intermediate token if there is no suitable direct pool.

What Will the Trade Cost?

The total cost includes the pool fee, any price impact and the network cost. Some TRON pools charge 0.3% per trade; others use fee tiers from 0.01% to 1%. A route through two pools can incur two pool fees.

Price impact is the change your own trade causes in a pool. Slippage is a further price change while your transaction waits to execute. Say a quote offers 2,000 JST for 100 USDT with a 1% slippage limit. The trade should deliver at least about 1,980 JST or fail; check the displayed minimum before signing.

TRON charges Bandwidth for transaction size and Energy for contract work. Staked or delegated resources can cover these costs; otherwise, the network burns TRX. For example, an estimated 100,000 Energy costs around 10 TRX at the current rate if you have no Energy, plus any Bandwidth shortfall. Keep enough TRX for approval and the swap: even a failed transaction can consume resources.

How Do You Choose and Complete a Route?

Choose a route by comparing its minimum output, network cost and pool depth for your trade size. A deeper pool usually means less price impact. Compare the amount you expect to receive after all costs, especially when one route uses an extra pool.

A swap on TRON through a wallet-connected exchange lets you keep control of your tokens until you sign. A custodial exchange instead holds your deposit and trades within your account; check its trading fee, withdrawal fee and supported withdrawal network. A trade inside that account may settle there first, with a separate blockchain withdrawal needed to reach your wallet.

Before depositing or signing, confirm the token’s contract address, its unique on-chain identifier. Names and symbols can be copied, and USDT exists on several networks. If you want TRC-20 USDT in a TRON wallet, select the TRON network for withdrawal and check the address carefully.

Start with the route that gives an acceptable minimum output at an acceptable total cost, then verify the result in your wallet. For an unfamiliar token or service, try a small amount first so you can check the full path before sending more.

Destination-Chain Reorganizations and Bridge Transfers in 2026

Anna Botsford — Tue, 20 Oct 2026 14:29:48 +0000

A destination-chain reorganization can erase a bridge credit while the source transfer remains. This happens when the destination network replaces recent blocks with a different version of its history, removing the block that recorded the incoming transfer.

A how a relay bridge moves funds explanation follows the message from one chain to another; this article focuses on what can happen after the destination chain first records it. The key distinction is that a transaction can appear successful before the block containing it is secure enough for the bridge or its user to rely on.

What does a destination-chain reorganization undo?

A reorganization, often shortened to “reorg,” happens when a blockchain switches to a different branch of recent blocks. Transactions in discarded blocks are removed from the accepted history; they may be tried again, but their earlier effects no longer count. Ethereum.org’s glossary describes a reorg as a switch to a different canonical chain.

For a bridge transfer, imagine you send tokens on a source chain and the bridge locks them in a smart contract. A relayer node sees that event and submits a corresponding instruction on the destination chain, where a contract releases or creates tokens for you. If the destination block containing that credit is later discarded, the destination contract state rolls back too.

The source and destination chains keep separate records. Reversing the destination credit does not automatically unlock the tokens on the source chain, because the source contract has no built-in knowledge that the other chain’s history changed. You can therefore see a completed source transaction alongside a missing or pending destination transfer.

How can the transfer be reversed after it looks successful?

“Included” means a transaction appears in a block; “finalized” means the network’s consensus rules treat that block as settled. The bridge may act on a source event once it has enough confirmations, but confirmations reduce reorg risk rather than removing it in every network. The exact threshold and meaning of finality depend on the chain and the bridge’s rules.

Suppose a bridge sees a deposit, then credits you on the destination chain while that chain’s block is still recent. A competing branch becomes the accepted one, and the credit block is dropped. The relayer’s earlier report of success was accurate for the branch it saw, but it is no longer accurate for the chain’s current history.

Any later transactions that depended on that credit can also be affected. If you traded the bridged tokens in a block that is discarded along with the credit, that trade is discarded too. If the trade was recorded in a block that remains canonical but the credited tokens are absent, it may fail when retried because your balance is no longer sufficient.

Ethereum.org explains that proof-of-stake finality makes reverting finalized blocks require a major consensus failure. Solana’s transaction guidance distinguishes “confirmed” from “finalized” because a confirmed transaction can still belong to a dropped fork. Those terms are useful examples, not interchangeable labels: check the commitment level and finality rule for the particular chain.

What affects the wait and the cost?

Waiting longer for destination finality lowers the chance that a bridge transfer will be reversed, but adds time before you can safely use the received tokens. There is no universal confirmation count: the bridge chooses a threshold based on its security model, the destination chain’s consensus, and the value or risk it is willing to accept.

For a simple timing estimate, say a network produces a block every two seconds and a bridge waits for 20 confirmations. That is roughly 40 seconds for those blocks, before adding relayer polling, network congestion, and the time for the destination transaction to be included. Actual wait times can be longer, and a bridge that waits for stronger finality may take much longer still.

A reorg does not have one standard fee outcome. You may have paid the source transaction fee already, while a relayer or bridge operator may need to pay again to retry a destination transaction. Whether a user pays a retry fee, receives a refund, or needs to take action depends on the bridge’s terms and its recovery process.

What should you check if the destination credit disappears?

Start with the transfer’s status in the bridge’s tracker, then compare the transaction records on both chains. A source deposit that remains confirmed with a destination transaction missing or marked reverted points to a different issue than a source deposit that itself was removed by a reorg.

Confirm that the source transaction is still in the accepted chain history.
Check whether the destination transaction was included, reverted, or dropped with its block.
Look for a bridge status such as pending, retrying, or awaiting finality.
Check whether the bridge says it retries automatically or requires a manual claim.

Do not send the same transfer again just because the destination balance is temporarily missing; the original message may still be retrying, and duplicate submissions can create confusion or extra fees. Follow the bridge’s recovery instructions and use its official tracker to check whether the original transfer has been completed or can be claimed again.

A destination reorg can remove the receiving side of a bridge transfer without undoing its source-side lock or payment. When using a relay bridge, treat a visible destination credit as provisional until the bridge’s required finality threshold is met, and check both chains if that credit later disappears.

Destination Token Support in Cross-Chain Swaps Explained

Anna Botsford — Sat, 17 Oct 2026 07:10:26 +0000

Destination token support sets which cross-chain swaps your wallet can complete: the route needs an asset it can deliver on your chosen network. If that asset is missing, the route may be unavailable even when you can buy it on a centralised exchange.

Why does the destination token decide the route?

A centralised exchange can hold one balance for you and trade it against many listed coins. With your own wallet, each blockchain has its own ledger, and a token on one chain is not automatically available on another.

A bridge moves value between blockchains. A swap trades one token for another. A cross-chain swap combines both jobs, so the service needs a way to move your starting asset and deliver the token you asked for on the destination network.

Token support means the service has a usable route for that specific asset on that specific chain. A token’s ticker or name alone is not enough: tokens with the same name can have different contract addresses, which are identifiers for tokens on a network. Ethereum.org explains that bridging can create a wrapped token, a network-specific representation of an asset. That representation may not be the version your destination app accepts.

How do bridging and swapping fit together?

Imagine you hold 100 USDC on Ethereum and want a different token on Arbitrum, a separate network. A route could trade some USDC, move value across, then deliver the requested token on Arbitrum. Each step depends on the service having a supported asset and a working exchange route where needed.

Available liquidity—the tokens ready to trade—affects the amount you receive. For example, a quote might turn 100 USDC into 99.6 units of the destination token after a 0.2% service cost and 0.2% price impact. Those figures are illustrative: actual costs depend on the route, market prices, network fees, and available liquidity.

Some systems send a matching token representation across; others use a liquidity provider, a party that supplies tokens to complete a trade. Across Protocol’s documentation describes relayers that send tokens on the destination chain and are repaid later. The exact mechanism varies, but the practical limit is similar: a requested output needs support on the destination side.

That is where fast super bridge swaps can be relevant: super bridge is a cross-chain bridge and swap service for moving assets between supported networks. The key check is whether the destination token you want can be delivered on your chosen chain, not simply whether your starting coin is supported.

What should you check before sending?

Check the route as if you were checking an exchange’s trading pair, then confirm the chain and token version. Take these steps before approving a wallet transaction:

Choose the destination chain first. Confirm you are aiming for the right network, such as Arbitrum or Base.
Check the exact output token. Match its network and, where available, its contract address. Do not rely on the ticker alone.
Read the quoted amount. Compare what you send with what the route says you will receive. The difference can include service costs, network fees, and price impact.
Check destination gas. Gas is the network fee for using the destination chain. You may need its native token to move or spend your received assets afterward.
Send a small test amount if uncertain. This can confirm that the destination wallet recognizes the token before you move more.

If the output token is unsupported, look for a supported token on that chain that you can trade afterward, or choose another destination. The destination token sets the route’s boundary; checking its network and version helps you avoid receiving an asset you cannot use as planned.

How to Turn a Token Payout Into Marketplace Funds

Anna Botsford — Fri, 16 Oct 2026 20:16:38 +0000

Turn the payout into the exact asset on the exact blockchain the marketplace accepts, then send it from your wallet. A wallet is an app or device that lets you control crypto directly; unlike an exchange account, you make each transfer yourself.

What must match before you convert?

The token name alone is not enough: check the asset, blockchain, and payment details in the marketplace’s deposit instructions. A blockchain is the network that records transfers, and the same token can exist on several networks.

Asset: Check the exact token, such as USDC.
Network: Check the named blockchain, such as Ethereum or Polygon.
Amount: Check the marketplace’s minimum and the amount due.
Payment details: Check for a memo or tag, a short reference some services use to identify a payment.

Ethereum.org’s wallet guide warns that sender and recipient must use the same network for a token transfer. If the payout is USDC on Polygon but the marketplace accepts USDC on Ethereum, sending it directly may fail or leave it unrecoverable.

How do you convert and send it?

Convert only after confirming what the marketplace will credit. Follow these steps, and leave time for the swap and final transfer to be recorded on their networks.

Record the payout. In your wallet, note the token and its network. Check that the balance has arrived and is available to spend.
Choose the accepted destination. Copy the marketplace’s asset and network details. If it accepts more than one option, choose one you can identify confidently in your wallet.
Compare the conversion amount. A swap exchanges one crypto asset for another; a cross-chain swap also moves value between blockchains. Review the quoted amount after network costs and price impact, which is the price change caused by your trade size. A thor swap can handle this cross-chain task in one flow; the thor swap service moves and swaps assets across blockchains for that purpose.
Check the numbers. Say the marketplace needs 205 USDC and the quote shows 215 USDC after costs. That leaves 10 USDC of room; if the quote falls below 205, the payment may be short. Swap costs vary with network activity, route, and trade size, so use the live quote rather than a fixed estimate.
Send and verify. Keep enough of the destination network’s native coin, its main asset, to pay the transfer’s gas (network fee). Copy the deposit address carefully, include any required memo, then check the transaction record and marketplace balance.

For a payout on one chain and a marketplace deposit on another, thor swap describes the conversion step between them. I’d confirm the deposit details first, compare the final quoted amount with the amount due, and send only when both match.

4 Checks for Cross-Chain Swap Slippage

Anna Botsford — Fri, 16 Oct 2026 13:56:12 +0000

Set slippage from the swap legs’ execution risk, then check that the quoted minimum output still meets your needs; the right tolerance depends on liquidity and how long each leg waits to execute. A cross-chain quote can include a swap on the source chain, a transfer or settlement step, and a swap on the destination chain. Treating that whole route as one swap hides where the price can move.

1. Which parts of the route can reprice?

Map each exchange separately: a source-side swap can change the amount sent, and a destination-side swap can change the amount received. Some routes also involve a liquidity provider advancing destination assets before settlement; in that case, the provider’s pricing and settlement terms affect the quote, but they are not the same thing as AMM slippage.

For a like-for-like comparison, use the destination amount the quote promises after its stated fees, and identify whether that amount is guaranteed, conditional, or indicative. A crypto relay bridge can route a transfer and swap in one flow, which is useful when comparing the asset you start with against the asset you need to receive. The convenience of a single route does not mean every leg shares one slippage limit.

The usual mistake is to compare the source-chain amount or exchange rate while ignoring the destination minimum. Fix it by recording the input, expected output, minimum output, and any quoted fees for the complete route. A relay bridge can bundle these operations, but you still need to know what happens if a later swap cannot meet its output condition.

2. What does the slippage percentage actually bound?

For an exact-input swap, a common minimum-output rule is minOut = quotedOut × (1 − tolerance). If a quote is 1,000 units and the tolerance is 0.5%, the swap must return at least 995 units, before considering how the route displays or deducts fees. The tolerance is a bound on an execution result; it is not a prediction that the market will move by that amount.

AMM price impact is different: it is the effect your trade has on the pool’s price as it consumes available liquidity. Slippage is the difference between the expected and actual execution, which can arise because the pool changes between quote and execution. Uniswap’s protocol documentation describes the relationship between trade size, reserves, and price impact in constant-product pools; the same distinction helps when evaluating a routed swap.

Where both source and destination legs have independent output bounds, the total loss relative to quoted outputs can compound. For example, two legs each allowing 0.5% below their own quote can produce roughly 1% less than the combined quoted result, before fees and any other route adjustments. That calculation is illustrative: some routes expose one aggregate bound, and others execute only one swap.

3. How should you choose a tolerance?

Use the tightest limit that gives the route a realistic chance to execute under the conditions it faces. For a deep, stable pool with a prompt execution, a tolerance around 0.1%–0.5% may be workable; thinner pools, volatile assets, or delayed destination execution may need more. These are starting points, not safe defaults: pool depth, trade size, volatility, and route design decide the actual risk.

Check the implied minimum in units of the destination asset, not only as a percentage. If the quote promises 2.00 ETH-equivalent units at a 1% tolerance, the minimum is 1.98; ask whether receiving less than that still makes the transaction worthwhile. If the displayed minimum is already unacceptable, raising tolerance only permits a worse fill.

Do not widen the bound just to get past a failing quote without finding the cause. A low tolerance can cause a swap to revert when the price moves beyond its limit; a high tolerance can permit execution at a materially worse rate. The useful adjustment is the smallest increase that reflects actual execution uncertainty, followed by a fresh check of the minimum output.

4. What changes when execution spans chains?

Time and failure handling matter because the destination leg may run after the source transaction is included and the transfer or settlement step completes. The destination pool can change during that interval, so a quote that was executable when requested may no longer satisfy its minimum. Whether the user receives a refund, can retry, or must take another recovery path depends on the route’s design; check that outcome before committing value.

For example, suppose the source swap executes at its quoted minimum, but destination liquidity worsens before the second swap. If the destination leg enforces its own minimum, it may fail even though the source transaction succeeded. A route that offers a fallback asset or a recoverable destination balance handles this edge case differently from one that requires a manual recovery. Compare those outcomes alongside the quoted rate.

Before acting, ask yourself: if the route completes at its minimum output—or the destination leg fails after the source transaction—will I still receive an acceptable result, and do I understand how the route handles that failure?

Should you bridge and swap in one move or split it?

Anna Botsford — Fri, 16 Oct 2026 08:54:31 +0000

For a simple transfer, one cross-chain swap is usually easier. Splitting the job can give you more control, but it adds steps, fees, and chances to make a mistake.

One cross-chain swap: best for a direct move

A cross-chain swap moves value from one blockchain and exchanges it for an asset on another. You approve a transaction from your wallet, and the route handles the transfer and exchange as one request. A blockchain is a separate network with its own transaction records and rules.

In a common route, a service arranges the exchange on the source side, then uses a bridge to make funds available on the destination side. A bridge is a system that coordinates asset transfers between blockchains. Some routes use locked funds and matching assets on the destination; others use different designs, so the asset you receive may be a wrapped version rather than the original token.

Say you hold 100 units of one token on Ethereum and want a different token on another network. You compare the estimated amount you will receive, check the destination network and token, then approve the transaction in your wallet. Biswap is one service that handles a cross-chain transfer and swap in one flow; the Biswap bridge is relevant when you want that combined route.

This option is best when the route supports your starting and ending assets and the estimated result suits you. It may not fit if you need a token that the route cannot deliver, want to choose each exchange separately, or need to inspect how the bridge handles assets. Ethereum.org explains that bridges can have different trust and security assumptions, so a single quote does not tell you how every route works.

Bridge first, then swap: best for more control

With this option, you first move an asset to the destination network, then exchange it there. It suits you when the exact destination token matters or you want to choose the bridge and exchange separately.

For example, you could bridge a widely used token, wait until it arrives, then swap it for the token you need. This makes each part easier to inspect, but you usually sign at least two transactions and pay network fees on both sides. Gas means the fee paid to process a transaction on a blockchain.

Check that the received asset can be exchanged on the destination network. A token with the same name may have a different contract address, which is the on-chain identifier for that asset. Also keep some of the destination network’s own gas token for the swap; otherwise, the funds can arrive while you cannot use them.

A centralised exchange: best when you already use one

A centralised exchange holds funds for you and carries out trades through its own account system. It can suit you if your assets are already there and you are comfortable depositing, trading, and withdrawing through that company.

The trade-off is custody: the exchange controls the account and must support withdrawals to the correct network. You may also need separate deposit, trade, and withdrawal steps. Before sending funds, match the withdrawal network to the wallet’s destination network; selecting the wrong one can make recovery difficult or impossible.

What should decide your route?

Compare the amount you expect to receive after all costs, not just the displayed fee. Network fees pay for transaction processing; price impact is the change in exchange rate caused by the size of your trade or available trading funds. A route can look cheap but return less if its exchange rate is worse.

For a first wallet transfer, I would favour the route with a clear final amount, the right destination asset, and enough information to understand what you are approving. If you split the move, include destination gas in your plan; if you use one flow, check whether the result is the asset you intended. Biswap is another option to consider when you want the bridge and swap handled together.

Before you act, ask yourself: do I value fewer steps more, or do I need control over each part of the transfer?

How to Send a Cross-Chain Donation in the Right Token

Anna Botsford — Fri, 16 Oct 2026 04:34:45 +0000

A cross-chain donation may need two changes: moving funds to another network and swapping them into the charity’s accepted token. Check the charity’s exact token and network first, then compare routes by how much reaches its wallet after costs. A combined bridge-and-swap route can handle both changes in one flow.

What must match the charity’s instructions?

The token, network and destination address must all match. A token’s name alone is not enough: USDC on Ethereum and USDC on Arbitrum are separate network assets, and a charity may accept only one of them.

Ask whether the charity accepts direct transfers to the address it gave you, and whether it needs a donor name or reference. This matters if the address belongs to an exchange or donation platform, which may not credit an incoming transfer it cannot identify.

How do you compare and make the transfer?

Use these steps to compare routes before sending. Ethereum.org explains that bridges use different designs to move assets between networks, so check the route’s stated risks and final amount as well as its convenience.

Copy the charity’s details. Record the exact token, network and address from its own instructions. If it gives a token contract address, compare that too; different tokens can share a symbol.
Work out what you need to receive. Say the charity requests 100 USDC on Arbitrum, while you hold ETH on Ethereum. The needed input changes with the exchange rate and route costs, so judge each quote by whether it delivers at least 100 USDC to the correct destination.
Compare the complete route. A one-chain swap changes token but not network. A bridge moves value between networks, while a combined bridge and swap does both. When weighing that option, how Biswap combines a bridge and swap frames the key question: can one flow deliver the right asset on the right chain?
Check what the quote deducts. Network gas pays for blockchain transactions; route costs may also affect the amount received. Keep enough of the source network’s native token for gas, and confirm the quoted destination amount still meets the charity’s requirement.
Review every destination detail before approving. Confirm the destination network, token and charity address. Biswap is a cross-chain bridge and swap service for moving and exchanging assets across networks in one flow, which can suit this task when the charity’s required destination is available through the route.

How do you confirm the donation arrived?

Save the transaction record and check the destination chain for the transfer to the charity’s address. A source-chain confirmation alone does not prove the destination transfer finished; bridge routes can have separate stages.

If the destination token or address is wrong, pause and ask the charity before sending. Once the correct asset appears at its address, send any requested receipt or donor reference. Your next step is to get the charity’s exact network and token details, then compare routes against the amount it must receive.

How to Compare Cross-Chain Swap Quotes

Anna Botsford — Thu, 15 Oct 2026 23:06:15 +0000

Compare cross-chain swap quotes by checking how much you will receive after costs, and what can change before delivery. A quote is an estimate for exchanging one asset on one blockchain for another asset on a different blockchain. The best headline rate can still leave you with less in your wallet.

Compare the amount that reaches your wallet

Use the same starting amount, source asset, destination asset, and receiving address for each comparison. Then compare the estimated amount delivered, not only the exchange rate shown near the top. For example, one route might estimate 0.985 ETH and another 0.98 ETH from the same BTC amount. Those figures are illustrative; the stronger quote is the one that still delivers more after costs and changes.

Check whether the estimate includes the destination network’s transfer cost. That cost is often called an outbound fee: the charge to send the swapped asset to your wallet. A small fixed charge can take a bigger share from a small swap than from a large one.

Also check what happens if the swap cannot meet its stated minimum. Slippage means the price moves between the estimate and the actual swap. A minimum received amount sets the lowest result you accept; if the market moves beyond that limit, the swap may wait, fail, or be refunded, depending on the service. Before sending funds, confirm the receiving address matches the destination blockchain.

Find out why two routes give different estimates

Routes can use different pools, which are shared reserves used to exchange assets. A trade that is large compared with a pool’s available assets can move its price more; this is called price impact. The route with fewer visible steps can still return less if its pools are shallower or its costs are higher.

One route may swap through an intermediate asset before reaching your destination. That can help when direct trading is thin, but each swap can add price impact or a fee. A comparison of how thor swap routes assets gives context for route choice; here, focus on the amount each route estimates for your own transfer.

Costs can include the source network’s gas, the fee for using liquidity, and the destination transfer fee. Gas is the network charge for processing a transaction. Some routes may also include a service or referral fee, so compare the final receive amount rather than trying to add up labels that services may display differently.

Refresh the quote and check the full transfer

Quotes can change as prices and pool balances move. Refresh the estimate shortly before sending, and compare it again with the minimum received amount. A thor swap can handle the cross-chain exchange as one flow, but the source transaction still needs to be confirmed on its blockchain before the destination asset can arrive.

For the transfer itself, thorswap.us is a cross-chain bridge and swap service that lets you move and swap crypto assets between blockchains in one flow.

Before you confirm, check the asset names and networks on both ends, the estimated arrival amount, the minimum you will accept, and the address where the asset should arrive. If you are comparing a small swap, pay close attention to fixed network charges; for a large swap, focus on how the route’s pool depth affects price impact. That is the trade-off that often decides which quote is actually better.

Sending Bitcoin To Ethereum? Choose BTC Or ETH First

Anna Botsford — Thu, 15 Oct 2026 18:34:43 +0000

Choose a bridge-only route if you want Bitcoin represented on Ethereum; choose a bridge-and-swap route if you need ETH to spend. The right choice depends on what you plan to do with the funds after they arrive.

Bridge Bitcoin If You Need A Bitcoin Token On Ethereum

A bridge moves value between separate blockchains. Because Bitcoin and Ethereum do not share one ledger, the BTC you send cannot arrive as native Bitcoin inside an Ethereum wallet. It must arrive as a token on Ethereum that represents Bitcoin, often called wrapped Bitcoin.

This route suits you if you want Bitcoin exposure in an Ethereum app that accepts that specific token. For example, someone supplying Bitcoin value to an Ethereum lending app needs a compatible Ethereum token, not BTC on the Bitcoin network. Ethereum.org’s bridge documentation explains that a bridge can lock or burn assets on one chain and create a corresponding asset on another.

It does not fit if your goal is to hold or spend ETH. A Bitcoin token on Ethereum is still a token representing Bitcoin; it is not the ETH coin. Check the exact asset name and network your destination app accepts, since two tokens with similar names may not be interchangeable.

Bridge And Swap If You Need ETH

A bridge-and-swap route moves value across chains and exchanges it for the destination asset. A swap means trading one asset for another. This is the better fit when you want ETH ready for an Ethereum app or payment.

For example, compare two plans: Alex wants Bitcoin exposure in an Ethereum app, while Jo wants ETH to pay a network fee. Alex needs a Bitcoin token on Ethereum; Jo needs ETH. Sending the same BTC amount does not make these plans equivalent.

The combined route saves you from arranging a separate swap after the transfer, but the exchange rate affects how much ETH arrives. A difference between the quoted rate and final rate is called slippage. Review the expected amount and any minimum you must receive before committing. Ethereum.org’s guide to token swaps also explains that swaps exchange assets and can involve fees.

Acrossbridge is a cross-chain bridge and swap service for moving and swapping assets between networks in one flow. Use it when your aim is to turn Bitcoin into an Ethereum asset as part of the same cross-chain task; first decide whether that asset should represent Bitcoin or be ETH. Bitcoin’s confirmation process can affect the wait before a transfer proceeds, and how acrossbridge times vary by route is a concrete example of why timing depends on the route.

Choose the asset you want to use after arrival.
Check that the destination accepts that asset on Ethereum.
Review the expected amount before confirming the route.

5 Steps to Liquid Staking Through a Mantle Bridge

Anna Botsford — Thu, 15 Oct 2026 14:28:25 +0000

Use the bridge to place liquid staking exposure where your treasury needs it. The key decision is whether to stake ETH first and bridge the receipt token, or bridge funds to Mantle and acquire that token there; those routes have different execution, liquidity, and custody risks.

mETH represents staked ETH, and its ETH value can rise as rewards accrue.
Bridging mETH moves its token representation; it does not stake the underlying ETH again.
Choose the route by comparing net mETH received, settlement time, and exit requirements.

What exposure are you actually buying?

Liquid staking converts ETH into a transferable receipt token while the underlying ETH supports validator staking. For Mantle’s mETH, the receipt is value-accruing: its exchange rate against ETH changes as staking rewards accumulate, rather than each mETH rebasing into a larger token balance.

That distinction matters for treasury books. Track both the mETH quantity and its ETH-denominated value; a balance of 95.24 mETH might represent about 100 ETH at an illustrative rate of 1 mETH = 1.05 ETH. The rate moves, and the market price can trade above or below the value implied by redemption.

mETH exposure includes validator, protocol, smart-contract, and liquidity risks. Rewards vary with validator performance and protocol charges, while an on-chain redemption can require a request and later claim. For a payout reserve, treat mETH as a yield-bearing position rather than same-day ETH cash.

Which route should the treasury use?

If the treasury already holds ETH on Ethereum, staking there and bridging the resulting mETH can preserve direct protocol issuance: the staking contract mints the receipt, and the bridge carries its Mantle representation across. Verify the receiving token contract and route support before sending, since matching symbols do not establish that two tokens are interchangeable.

If the treasury holds assets on another supported network, a cross-chain bridge-and-swap service can move and swap those assets into the required Mantle-side asset in one flow. A how a Mantle bridge settles transfers explanation helps clarify why the destination token appears only after the cross-chain message is processed. If the flow ends in mETH on Mantle, account for it as a market acquisition unless the staking contract itself minted it; a swap does not create a new staking position.

The second route can save a separate transfer or swap, but it adds price impact and route liquidity to the bridge’s settlement assumptions. Compare the net destination amount against staking ETH first, including source-chain gas, destination gas, swap spread, and any time-sensitive exposure cost. Choose the route that meets the treasury’s settlement window and approved asset policy.

What does a 100 ETH allocation look like?

Suppose the allocation is 100 ETH and the illustrative conversion rate is 1 mETH = 1.05 ETH. Direct issuance would deliver about 95.24 mETH before protocol rounding or transaction costs; the same rate is a useful benchmark for a Mantle-side swap, but the swap’s actual execution price may differ.

If the route quotes 94.8 mETH after spread and price impact, the shortfall against that benchmark is 0.44 mETH, or about 0.46 ETH at the assumed rate. That is the execution cost to compare with the extra Ethereum transactions and bridge costs in the stake-then-bridge route. Recalculate from the live quote and exchange rate at execution; neither the rate nor market depth is fixed.

Set a minimum acceptable mETH amount or maximum effective ETH-per-mETH price in treasury policy. Split a large order if the pool’s quoted price worsens materially with size, but remember that multiple transactions can add gas and expose the treasury to market movement between fills.

How should operations execute and reconcile it?

Run the transfer as a controlled treasury position change: verify the route, record the expected output, and reconcile both chain transactions before reporting the position as complete.

Approve the allocation. Record the source asset, target mETH amount, permitted price deviation, and minimum Mantle gas reserve so execution and accounting share one instruction.
Validate the route and contracts. Confirm the source and destination networks, recipient address, mETH contract, and whether the destination token is the protocol’s recognized Mantle representation; reject an unverified lookalike.
Compare net outcomes. Quote the cross-chain swap against stake-then-bridge using the same timestamp and notional, including source gas, destination gas, slippage, and expected settlement delay.
Execute within limits. Submit the approved route and retain transaction identifiers; if the received asset or amount differs from policy, pause further deployment and reconcile before making another trade.
Reconcile and plan the exit. Match source debit to Mantle credit, record mETH quantity and ETH value separately, then document whether redemption requires an unstake queue, a secondary-market sale, or a return bridge.

A Mantle bridge can make liquid staking exposure available on Mantle, but the bridge and the staking position are separate parts of the transaction. For treasury use, decide whether you need freshly minted mETH or simply mETH exposure, then compare the complete route and its exit path before committing funds.