<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: David</title>
    <description>The latest articles on DEV Community by David (@robert-eth).</description>
    <link>https://dev.to/robert-eth</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4141416%2F97908bfe-7cea-46b8-a91e-aacda8b6877f.png</url>
      <title>DEV Community: David</title>
      <link>https://dev.to/robert-eth</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/robert-eth"/>
    <language>en</language>
    <item>
      <title>Best Decentralized Exchanges on TRON: Compare Swap Quotes</title>
      <dc:creator>David</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:07:12 +0000</pubDate>
      <link>https://dev.to/robert-eth/best-decentralized-exchanges-on-tron-compare-swap-quotes-5hi</link>
      <guid>https://dev.to/robert-eth/best-decentralized-exchanges-on-tron-compare-swap-quotes-5hi</guid>
      <description>&lt;p&gt;The best decentralized exchange on the TRON network for most TRC-20 swaps is SunSwap, because its generally deeper pools reduce price impact. The multiple pool versions and routing available through &lt;a href="https://sunswap.cc" rel="noopener noreferrer"&gt;SunSwap&lt;/a&gt; give traders more ways to find liquidity for a pair. A smaller DEX is worth considering when it lists a token unavailable there, but the quoted output for your trade size should decide where you swap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pool Depth, Token Availability, and Wallet Support Decide the Swap
&lt;/h2&gt;

&lt;p&gt;Pool depth matters because a swap changes the balance of tokens in its pool. The larger your trade relative to that pool, the further its execution price moves. JustMoney and SocialSwap list fewer pairs and may have thinner pools. A lower advertised fee can still leave you with fewer tokens if price impact outweighs the fee difference.&lt;/p&gt;

&lt;p&gt;Say you want to swap a sizeable amount of TRX for a TRC-20 token. Enter the same amount on each DEX, verify that each quote uses the same token contract, and compare the estimated tokens received after swap fees. Repeat the comparison with your full intended amount: a thin pool can look competitive for a small test trade and quote poorly for a larger one. Quotes change as trades and liquidity change, so review the output again before signing.&lt;/p&gt;

&lt;p&gt;Token availability comes next. Look for the exact TRC-20 contract and a pool or routed path that can complete the swap. JustMoney or SocialSwap may list a token that the SUN.io exchange does not offer; SunSwap operates as part of SUN.io. A listing gives you access, but a thin pool may still produce a poor quote. Verify the contract address before trading a token with a familiar name.&lt;/p&gt;

&lt;p&gt;Wallet support is the final practical test. Your chosen DEX must connect to your TRON wallet and show the correct network, tokens, and transaction before you sign. TRON DEX swaps also use network resources, typically Energy or TRX. Those chain costs are similar across the venues, though the amount used can vary with the transaction. For a small swap, include the estimated network cost when comparing what you receive.&lt;/p&gt;

&lt;p&gt;For a common pair, the SUN.io venue suits traders seeking a straightforward swap from a deep pool. JustMoney suits a trader who finds a needed token or a better quote there. SocialSwap serves the same purpose when its listing, pool, and wallet connection fit the trade. Choose by the tokens your wallet will receive, rather than by the exchange name or listed fee alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is SunSwap safe to use
&lt;/h3&gt;

&lt;p&gt;A trade on the SUN.io exchange still carries smart contract, token, and wallet approval risks. Use the official site, verify the token contract, and read the wallet prompt before approving a swap. The exchange’s liquidity cannot make an impersonator token safe.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I use Uniswap with TRON tokens
&lt;/h3&gt;

&lt;p&gt;Uniswap and PancakeSwap do not run on TRON. Using either with TRON assets requires bridged tokens on another chain, adding a bridge step and its risks. For a native TRC-20 swap, compare quotes on the TRON DEXs that list your pair, then sign the trade with the best usable output.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Do Teams Prepare for User- or Service-Signed TeleSwap?</title>
      <dc:creator>David</dc:creator>
      <pubDate>Fri, 06 Nov 2026 14:43:01 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-do-teams-prepare-for-user-or-service-signed-teleswap-290o</link>
      <guid>https://dev.to/robert-eth/how-do-teams-prepare-for-user-or-service-signed-teleswap-290o</guid>
      <description>&lt;p&gt;TeleSwap teams can assign signing and operations work before taking live requests once they decide whether users or a service control the spending keys. A user-signed application needs compatible wallets and readable transaction review; a service-signed application also needs a protected signer and explicit authorization rules. The direction, network, and custody arrangement determine who approves each spend.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate Transaction Construction From Spending Authority
&lt;/h2&gt;

&lt;p&gt;An application can construct a transaction without having permission to spend the funds in it. Construction selects inputs or contract calls, recipients, amounts, fees, and network details. Signing authorizes a particular transaction with a spending key. The team should record which component constructs the request, which party checks it, which key signs it, and who submits it.&lt;/p&gt;

&lt;p&gt;That division gives the two arrangements different owners:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Wallet-connected application:&lt;/strong&gt; The user controls the spending key and authorizes each transaction in a compatible wallet. The application prepares the request, presents its meaning, and tracks the result.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend with a separate service signer:&lt;/strong&gt; The service controls a key that can spend the funds assigned to its flow. The backend must decide which requests may reach that signer, while the signer enforces access and spending controls.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before choosing, identify whose funds each source transaction spends. If a service key spends only application funds, the team must define how user funds enter that flow. If it spends funds held for users, the team takes on responsibility for protecting those keys and authorizing withdrawals. An unsigned transaction from an API does not settle that ownership question.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prepare the User-Signed Application
&lt;/h2&gt;

&lt;p&gt;User signing works when the application can connect to wallets that support the required source network and transaction format. Frontend developers should establish wallet compatibility for each supported direction, including Bitcoin signing for a Bitcoin spend and the appropriate chain selection for an EVM transaction. A successful connection alone does not show that a wallet can sign the constructed request.&lt;/p&gt;

&lt;p&gt;The review screen should show the asset leaving the wallet, the source network, the destination network, the receiving address, and the amount the user is expected to receive or have credited. Present network fees and any TeleSwap fees where they can be determined, and identify an estimate as an estimate. The wallet may display raw transaction details, so the application’s explanation must agree with the transaction the user is asked to sign.&lt;/p&gt;

&lt;p&gt;For example, consider an illustrative Bitcoin-to-Ethereum request. If construction selects Bitcoin UTXOs, the wallet must sign the spend from those selected outputs; the frontend must show that the intended recipient is on Ethereum. The team should also decide what happens if the user changes wallets, rejects signing, or signs after the quoted terms expire. Those outcomes require a fresh review or a deliberate cancellation state, not an assumed payment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Map TeleSwap Transfer State
&lt;/h2&gt;

&lt;p&gt;A source transaction being signed, submitted, or confirmed is different from the destination outcome being complete. That distinction matters when the application promises a cross-chain result: a Bitcoin transaction ID confirms neither that the destination action has happened nor that the request needs to be paid again.&lt;/p&gt;

&lt;p&gt;In &lt;a href="https://teleswap.net" rel="noopener noreferrer"&gt;TeleSwap cross-chain transfers&lt;/a&gt;, Bitcoin transaction verification supplies evidence of the source payment, while collateralized Lockers form part of the operator arrangement for moving value across networks. A TeleSwap Bitcoin bridge integration therefore needs to associate the source transaction with the expected destination result. The application should show separate states for awaiting signature, submitted on the source network, source payment verified, and destination completion, using the states the integration can actually observe.&lt;/p&gt;

&lt;p&gt;For the illustrative Bitcoin-to-Ethereum request, persist one application request identifier alongside the selected Bitcoin inputs or submitted transaction ID, the Ethereum recipient, and the resulting destination transaction identifier when available. This record lets support distinguish a delayed handoff from a request that never received a signature. The same mapping must account for the reverse direction when the team enables it; the chain that supplies the spend and the chain that receives it change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prepare the Service Signer
&lt;/h2&gt;

&lt;p&gt;Service signing needs a separately controlled signing system and a rule for approving each transaction before that system uses its key. Keep signing credentials outside the transaction-building service, restrict which service identities can request a signature, and log the approved request and the transaction it produced. A hardware security module or managed key service can protect keys, but the team still has to define what the signer is allowed to sign.&lt;/p&gt;

&lt;p&gt;Authorization rules should bind a request to its asset, source network, destination, recipient, and maximum spend. Set limits that match the funds the service is meant to control, and require a deliberate process for changing those limits or adding destinations. If an API caller can replace a recipient after approval, the approval did not authorize the transaction that will be signed.&lt;/p&gt;

&lt;p&gt;The signer also needs chain-specific state. For Bitcoin, coordinate UTXOs so two requests do not attempt to spend the same output, and reserve enough value for transaction fees. For an EVM network such as Ethereum or Arbitrum, coordinate account nonces so concurrent submissions do not collide, and fund the signing account with the native asset needed for gas. Assign these duties to the signer or a single transaction coordinator rather than leaving them to independent API workers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Own Completion and Recovery in Both Arrangements
&lt;/h2&gt;

&lt;p&gt;Both arrangements need a persistent request identifier, status monitoring, and a named support owner before accepting real requests. The application should retain enough detail to match its request to source and destination transactions, including failures or rejections. The support owner needs a documented way to inspect that record and determine whether the next action belongs to the user, the signer, or an operator.&lt;/p&gt;

&lt;p&gt;A submission timeout is an uncertainty about the response, not proof that payment failed. If an API call times out after broadcasting, first reconcile the original transaction against the network and the stored request. Automatically constructing a new payment can spend funds twice; for a service signer, it can also consume a new nonce or different UTXOs while the first transaction is still pending.&lt;/p&gt;

&lt;p&gt;User signing is the fitting choice when users should retain spending control and supported wallets can present the required transactions clearly. Service signing fits when the application is authorized to control the funds and can operate the signer, limits, and transaction state. Revisit that choice if a new transfer direction, network, or custody arrangement changes who holds the spending key: it changes the authorization and operational duties the TeleSwap integration must assign.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Monad Bridge: How Do I Deposit When Monad Isn't Supported?</title>
      <dc:creator>David</dc:creator>
      <pubDate>Thu, 05 Nov 2026 23:46:55 +0000</pubDate>
      <link>https://dev.to/robert-eth/monad-bridge-how-do-i-deposit-when-monad-isnt-supported-3gpg</link>
      <guid>https://dev.to/robert-eth/monad-bridge-how-do-i-deposit-when-monad-isnt-supported-3gpg</guid>
      <description>&lt;p&gt;A Monad bridge can get funds from Monad credited at an exchange that rejects Monad deposits if it delivers a supported asset to your wallet on an accepted network. Use a &lt;a href="https://monad-bridge.org" rel="noopener noreferrer"&gt;Monad bridge&lt;/a&gt; for that transfer, then deposit separately from that wallet. This bridge from Monad succeeds when the exchange balance shows the credit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which asset and network will the exchange credit?
&lt;/h2&gt;

&lt;p&gt;Start at the exchange's deposit screen. Choose an asset, then read the networks currently available for deposits into your account. The address shown is usable only under those instructions: an address by itself does not establish that the exchange accepts the network you plan to use. Networks can use the same address format while keeping separate balances.&lt;/p&gt;

&lt;p&gt;Read the minimum deposit, any temporary suspension, the required number of confirmations, and any memo or destination tag. A memo is an extra identifier some exchanges need to assign an incoming transfer to your account. Copy the address and memo after choosing the exact network on the deposit screen. Exchange instructions determine whether you receive credit, even when a wallet allows the transaction.&lt;/p&gt;

&lt;p&gt;The asset matters down to its token version. A ticker such as USDC can label more than one token contract on the same destination network, including a native issue and a bridged representation. Seeing “USDC” in both a route quote and the exchange's asset list therefore does not prove the output is eligible. Compare the route's destination contract or token standard with what the exchange supports. If the exchange gives no way to verify that version, seek its confirmation before moving funds. Network and token standard are separate checks, as Kraken's deposit troubleshooting criteria illustrate.&lt;/p&gt;

&lt;h2&gt;
  
  
  What must a Monad bridge deliver?
&lt;/h2&gt;

&lt;p&gt;It must deliver the exchange-supported asset on the selected network into a destination wallet you control. That wallet is the staging point for a later deposit, so its address belongs in the route's recipient field. A Monad cross-chain transfer may involve a swap as well as a bridge, or issue a different representation of a familiar asset. Read the route's actual output token, destination network, recipient, expected received amount, and fees before signing.&lt;/p&gt;

&lt;p&gt;Keep enough MON on Monad to pay for any source approval and bridge transaction. You will also need the destination network's native gas token to send from your wallet to the exchange; for Ethereum, that means ETH. Bridged USDC in an Ethereum wallet does not itself pay an Ethereum transaction fee. Arrange that gas before committing to a route, and leave an eligible deposit amount after bridge fees and any exchange minimum. If no route delivers a token version the exchange accepts, choose another supported asset-network pair and reassess the route before sending anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bridge delivery and exchange credit are separate milestones
&lt;/h2&gt;

&lt;p&gt;A completed bridge delivers funds to your destination wallet, not to your exchange balance. For illustration, suppose funds begin as USDC on Monad and a route promises an exchange-eligible USDC version on Ethereum. Before the route, the balance exists on Monad. After delivery, the promised token appears in your Ethereum wallet. The network and possibly the contract have changed; the funds are still in your wallet. The exchange has received nothing yet.&lt;/p&gt;

&lt;p&gt;Keep the source transaction hash and the destination delivery record, since the bridge may show separate transactions on separate chains. Inspect the destination wallet on the destination network and verify the token contract and received amount, rather than relying on a route's “complete” label alone. This is also the point to notice an unexpected wrapped token or a smaller net amount. Neither a source confirmation nor destination delivery satisfies an exchange's deposit requirements.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you finish and verify the deposit?
&lt;/h2&gt;

&lt;p&gt;Send the eligible amount from your destination wallet using the exchange's exact asset, network, address, and memo instructions. Reopen the deposit screen before sending in case availability or instructions changed. Enter a memo if one is required, and ensure the amount arriving at the exchange clears its minimum after any transfer fee. The wallet transaction is a new send on the destination network, with its own transaction hash and gas charge.&lt;/p&gt;

&lt;p&gt;Follow that transaction on the destination chain, then follow the exchange's deposit status until the funds appear in your account balance. A chain confirmation means the send reached the address; the exchange may still be waiting for more confirmations or processing the credit. If the transaction confirms but no credit appears, compare its asset contract, network, amount, address, and memo against the exchange instructions, then provide the deposit transaction hash to exchange support. The exchange balance showing the credited amount is the final sign that both transfers achieved the intended deposit.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to set slippage for a ParaSwap swap</title>
      <dc:creator>David</dc:creator>
      <pubDate>Tue, 03 Nov 2026 20:35:28 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-to-set-slippage-for-a-paraswap-swap-44lj</link>
      <guid>https://dev.to/robert-eth/how-to-set-slippage-for-a-paraswap-swap-44lj</guid>
      <description>&lt;p&gt;Set slippage to the largest price change you can accept before the swap should stop. This sets a limit on how much less you may receive than the quote; it does not promise the quoted amount.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose a limit that fits the trade
&lt;/h2&gt;

&lt;p&gt;Slippage tolerance is the allowed fall in the amount you receive while your swap waits to run. A smaller limit protects your price more tightly, but a fast market move can make the swap fail.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check the tokens and amount.&lt;/strong&gt; Confirm the correct token is going in and the correct one is coming out. Then read the quoted amount and the “minimum received” figure, which is the least the swap will accept.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Look at the market and route.&lt;/strong&gt; A route is the path the trade takes through available pools, or token trading markets. A thinly traded token, a large order, or a route through several pools can make the quote more likely to move before execution.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set a tolerance you can live with.&lt;/strong&gt; For a liquid pair in calm conditions, you might start around 0.1% to 0.5%, if the app allows it. This is a starting point, not a guarantee; check the app’s displayed minimum received before signing.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, if a 100 USDC sale quotes 0.05 ETH, a 0.5% tolerance sets the minimum near 0.04975 ETH. The &lt;a href="https://cryptotalk.justblogged.com/how-swap-paraswap-fix-stuck-trade" rel="noopener noreferrer"&gt;ParaSwap crypto swap&lt;/a&gt; quote makes that limit useful: compare its displayed minimum with the amount you would accept for the trade.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the minimum before you sign
&lt;/h2&gt;

&lt;p&gt;The minimum received is the practical result of your tolerance, so use it to decide whether to proceed. If that amount is too low, lower the tolerance or reduce the trade size.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Review the final wallet screen.&lt;/strong&gt; Check the token addresses or names, the input amount, recipient, network, and minimum received. Wallets may show a shortened name or address; make sure the network matches the token you selected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare the network fee separately.&lt;/strong&gt; Gas is the fee paid to process a transaction on the blockchain. It is separate from slippage and may still be charged if a submitted swap fails; review the wallet’s fee estimate before signing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign only if both figures work.&lt;/strong&gt; The expected output is the quote; the minimum is your lower bound. If either one changed while you were reviewing, refresh the quote and check the new figures.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;ParaSwap’s published SDK describes slippage as a transaction limit applied to the quoted route. That distinction matters: raising the limit can help a moving trade execute, but it also permits a worse fill. Do not raise it simply to clear an error without checking the new minimum.&lt;/p&gt;

&lt;h2&gt;
  
  
  Adjust only when the cause is clear
&lt;/h2&gt;

&lt;p&gt;If the swap fails because the price moved beyond your limit, refresh the quote first. Then decide whether to wait, lower the trade size, or accept a slightly wider limit after checking the resulting minimum.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Refresh after a delay.&lt;/strong&gt; Prices and available liquidity can change while you wait. Get a new quote rather than signing from an old screen.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reduce a large trade before widening the limit.&lt;/strong&gt; A smaller order may move the market less and produce a better minimum. If the quote still needs a very wide tolerance, pause and check the token and route.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check a submitted transaction on the right explorer.&lt;/strong&gt; A block explorer shows a transaction’s status on its blockchain. Polygonscan’s transaction information explains statuses such as pending and failed; a pending transaction has not completed, so don’t submit a second swap until you know what happened to the first.&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>SushiSwap Options Explained: Trading and Liquidity</title>
      <dc:creator>David</dc:creator>
      <pubDate>Sat, 24 Oct 2026 00:34:48 +0000</pubDate>
      <link>https://dev.to/robert-eth/sushiswap-options-explained-trading-and-liquidity-89n</link>
      <guid>https://dev.to/robert-eth/sushiswap-options-explained-trading-and-liquidity-89n</guid>
      <description>&lt;p&gt;Use SushiSwap to exchange tokens from your own wallet when you want a trade; provide liquidity when you want to supply assets and earn a share of trading fees. Unlike a balance on a centralised exchange, the assets stay in your wallet until you sign a transaction. You need the correct network selected and some of its native coin to pay gas.&lt;/p&gt;

&lt;p&gt;Start by choosing between a trade and an ongoing pool position. A swap on &lt;a href="https://sushiswap.co" rel="noopener noreferrer"&gt;SushiSwap&lt;/a&gt; may draw from a single pool or use a route through several liquidity sources. SushiSwap V2 is the classic two-token pool model; other pools let providers concentrate liquidity within a chosen price range.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Trading Option Fits?
&lt;/h2&gt;

&lt;p&gt;A same-chain swap fits when the token you hold and the token you want are on the same network. Connect your wallet, choose the input and output tokens, and inspect the quoted amount received and price impact before signing. If the input token needs approval, that approval is a separate transaction: it permits spending but does not make the trade.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Same-chain swap:&lt;/strong&gt; Best for an immediate exchange on one network; it does not move assets to another chain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-chain swap:&lt;/strong&gt; Best when the destination token is on another supported network; it does not fit when the quoted bridge costs or delivery time are too high.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limit order:&lt;/strong&gt; Best when you will trade only at a chosen price; it may never fill, and availability depends on the network.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, suppose you swap $300 worth of a dollar-pegged token for ETH at an illustrative $3,000 per ETH. With a 0.3% pool fee, that is about 0.0997 ETH before price impact and gas. The actual quote can be lower if the trade moves the pool price, so check the minimum amount you will receive.&lt;/p&gt;

&lt;h2&gt;
  
  
  When Does Providing Liquidity Fit?
&lt;/h2&gt;

&lt;p&gt;Providing liquidity fits when you are willing to hold two assets and let traders exchange against them. A V2 position normally takes equal values of each token and earns a share of that pool’s fees. A concentrated-liquidity position can earn fees more efficiently within a selected price range, but stops earning them when the market moves outside that range.&lt;/p&gt;

&lt;p&gt;Choose a pool on the network where you hold the tokens, review its fee tier and activity, then approve and deposit the required assets. This does not fit if you need to preserve the exact quantity of either token: trades change the pool’s balance, and a price move can leave your position worth less than simply holding the pair. Fees may or may not offset that difference.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Should You Check Next?
&lt;/h2&gt;

&lt;p&gt;Check how the route executes, its full cost, and the limits shown in the quote before you sign. For a pool position, check the exposure you will hold after prices change.&lt;/p&gt;

&lt;h3&gt;
  
  
  How Does a Swap Work?
&lt;/h3&gt;

&lt;p&gt;A pool prices a trade from the amounts of its two tokens; buying one removes some of it and adds the other. A router can compare pools and combine routes to improve the amount received. Your wallet signs the transaction, and the resulting tokens arrive there after it confirms.&lt;/p&gt;

&lt;h3&gt;
  
  
  How Long Does It Take and What Does It Cost?
&lt;/h3&gt;

&lt;p&gt;Confirmation can take seconds or minutes, depending on the network and congestion; a cross-chain route can take longer. Pool fees commonly range from about 0.01% to 1% by pool type, with V2 typically around 0.3%. Gas and any cross-chain route charges are separate, so judge the final quoted amount.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Limits Apply?
&lt;/h3&gt;

&lt;p&gt;You can trade only tokens and network routes that are supported and have usable liquidity. A thin pool can make a modest trade expensive through price impact. Slippage tolerance sets how far the execution price may move from the quote; a tighter setting protects the minimum received but makes a failed transaction more likely.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which Option Fits?
&lt;/h3&gt;

&lt;p&gt;Use a same-chain swap for a trade on your current network, a cross-chain swap when the destination is elsewhere, and a limit order when price matters more than immediate execution. Consider liquidity provision only if you want ongoing exposure to both assets and can monitor the position. Choose by destination, timing, total quoted cost, and the assets you are willing to hold.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to Return Crypto to Ethereum Before a Mainnet NFT Buy</title>
      <dc:creator>David</dc:creator>
      <pubDate>Fri, 23 Oct 2026 14:52:18 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-to-return-crypto-to-ethereum-before-a-mainnet-nft-buy-4ood</link>
      <guid>https://dev.to/robert-eth/how-to-return-crypto-to-ethereum-before-a-mainnet-nft-buy-4ood</guid>
      <description>&lt;p&gt;Start your withdrawal several days before you plan to buy. From Manta Pacific, a standard withdrawal records your request, waits through a challenge period on Ethereum, then needs a final claim transaction; the challenge period is currently about 12 hours to three days, with processing time on either side.&lt;/p&gt;

&lt;p&gt;Say you found an NFT listed on Ethereum Mainnet and have funds on Manta Pacific. You need the right asset on Ethereum, plus enough ETH there for the NFT transaction fee.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what the NFT purchase requires
&lt;/h2&gt;

&lt;p&gt;Before moving anything, check the NFT’s price, accepted payment token, and checkout network. A listing may show a price in ETH, but the marketplace’s checkout screen is the place to confirm the asset and network.&lt;/p&gt;

&lt;p&gt;Then compare that amount with your Manta Pacific balance. If you hold a different token, you may need to swap it for the accepted asset before withdrawing; a swap trades one token for another and has its own price and fee.&lt;/p&gt;

&lt;p&gt;Leave some ETH on Manta Pacific for the withdrawal transaction. The bridge needs a transaction on that network to start the exit, even when the asset you are moving is a stablecoin.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understand the wait and the fees
&lt;/h2&gt;

&lt;p&gt;Manta Bridge withdrawals use a rollup exit: Manta Pacific records the request, Ethereum checks its proof, and Ethereum releases the funds after the challenge period. A challenge period is a set wait that gives participants time to dispute an incorrect network record. L2BEAT lists Manta Pacific’s current period as three days, with security quorums able to shorten it to as little as 12 hours.&lt;/p&gt;

&lt;p&gt;That clock does not include every step. The proof must become ready, and after the wait you may need to send a separate claim transaction on Ethereum. So if your NFT sale could end soon, a standard withdrawal may not arrive in time.&lt;/p&gt;

&lt;p&gt;The main costs are network fees, called gas: one on Manta Pacific to start the withdrawal and another on Ethereum to claim it. Ethereum gas changes with network demand, so check the wallet’s fee estimate before signing. Ethereum.org’s bridge explainer also notes that moving assets between networks can involve fees on both sides.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start the withdrawal and finish the claim
&lt;/h2&gt;

&lt;p&gt;For a return to Ethereum, &lt;a href="https://crypto-news-acxov85we3jlc7qno0wii.justblogged.com/how-use-manta-bridge-your-own-wallet" rel="noopener noreferrer"&gt;Manta Bridge withdrawals&lt;/a&gt; use the native route, while an NFT checkout on Pacific would let you skip the exit wait. For the mainnet purchase, follow these steps and keep the wallet address the same throughout.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open Manta Bridge and connect the wallet holding your assets on Manta Pacific.&lt;/li&gt;
&lt;li&gt;Select Withdraw, choose Ethereum Mainnet as the destination, and select the asset you need.&lt;/li&gt;
&lt;li&gt;Enter an amount that covers the NFT price, while keeping enough ETH for the Pacific transaction and a possible Ethereum claim.&lt;/li&gt;
&lt;li&gt;Review the displayed destination, token, amount, and gas fee, then sign the withdrawal in your wallet.&lt;/li&gt;
&lt;li&gt;Track the withdrawal in the bridge’s history until it is ready, then complete the Ethereum claim if prompted.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do not treat the first confirmed transaction as proof that the funds have arrived on Ethereum. It only records the request; check your Ethereum wallet balance after the claim completes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Buy only after the funds arrive
&lt;/h2&gt;

&lt;p&gt;Once the asset appears on Ethereum Mainnet, open the NFT checkout and confirm it still names Ethereum and the expected payment token. Keep enough ETH in the wallet for the marketplace transaction fee as well as the purchase price.&lt;/p&gt;

&lt;p&gt;If you are short, wait until the withdrawal finishes before deciding whether to bridge more. The practical rule is simple: start early, budget for both networks’ gas, and make the NFT purchase only after the right funds are visible on mainnet.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to recover a timed-out Wormhole transfer</title>
      <dc:creator>David</dc:creator>
      <pubDate>Thu, 22 Oct 2026 22:13:34 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-to-recover-a-timed-out-wormhole-transfer-4dij</link>
      <guid>https://dev.to/robert-eth/how-to-recover-a-timed-out-wormhole-transfer-4dij</guid>
      <description>&lt;p&gt;If a cross-chain transfer times out, check its source transaction first, then resume the claim on the destination chain if the source succeeded. A slow transfer is often waiting for a signed message or a destination transaction; it does not automatically mean the funds are lost.&lt;/p&gt;

&lt;p&gt;Keep these three points in mind:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A failed source transaction did not send the tokens.&lt;/li&gt;
&lt;li&gt;A successful source transaction may still need a destination-chain claim.&lt;/li&gt;
&lt;li&gt;Use the same destination wallet and the app that started the transfer.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check whether the source transfer succeeded
&lt;/h2&gt;

&lt;p&gt;Open the source transaction in that chain’s block explorer, a site that shows recorded transactions. Confirm it succeeded, and note its transaction hash, the unique ID for that transaction. If it failed, the token transfer did not happen; you may have spent a network fee for the failed attempt.&lt;/p&gt;

&lt;p&gt;If it succeeded, check the transfer status in the original app or Wormholescan, Wormhole’s transaction explorer. A cross-chain transfer may need a VAA, a signed message that proves the source-chain action, before the destination can finish. The Wormhole Core specification describes how Guardians check and sign these messages; delivery and the final claim are separate steps.&lt;/p&gt;

&lt;p&gt;Give the transfer time to reach the required confirmations, which are checks that the source transaction is settled. For Ethereum, Wormhole’s recovery instructions say finality can take up to around 20 minutes. If the status still shows that the message is pending, wait and check again before sending another transfer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Resume the claim with the original app
&lt;/h2&gt;

&lt;p&gt;If the source succeeded and the message is ready, return to the app you used to start the transfer. Look for an action such as “Complete,” “Redeem,” or “Claim,” connect the destination wallet, and approve the destination-chain transaction. That last step may require the destination chain’s native coin to pay its network fee.&lt;/p&gt;

&lt;p&gt;If your case involves a &lt;a href="https://ameblo.jp/jack32-defi/entry-12982263155.html" rel="noopener noreferrer"&gt;wormhole bridge&lt;/a&gt; transfer, use the same app and destination address shown in the original transaction. The transfer’s route can affect which app is allowed to finish it. Wormhole’s Portal FAQ notes that some transfers can only be redeemed by the app or contract that started them, even when another interface can display their status.&lt;/p&gt;

&lt;p&gt;For example, say you sent 100 tokens and the source transaction succeeded. The destination shows a 100-token claim ready, but your wallet has no destination-chain gas coin. Add a small amount of that coin, then submit the claim once. Check the destination transaction afterward; if it succeeded, confirm the tokens arrived at the intended address.&lt;/p&gt;

&lt;p&gt;If the app has no recovery button, use its support channel and provide the source hash, source and destination chains, and destination address. Never share your seed phrase or private key. If the destination address was wrong, or belongs to a contract that cannot release tokens, a successful source transfer may not be recoverable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Answers to common recovery questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does a timeout mean my tokens are gone?
&lt;/h3&gt;

&lt;p&gt;No. A timeout usually means the app stopped waiting, not that the transfer expired. Check the source transaction and destination status: if the source failed, tokens were not transferred; if it succeeded, the tokens may be awaiting message delivery or a destination claim. A confirmed destination transaction is the clearest sign that the transfer finished.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why can’t I claim through Portal?
&lt;/h3&gt;

&lt;p&gt;The original app may have reserved the right to complete the transfer. Return to that app and look for its claim action. If the source succeeded but no claim is available, share the transaction details with the app’s support team. I would avoid retrying the original send: a second transfer can send more tokens while the first is still pending.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to find a bridge for your exact token</title>
      <dc:creator>David</dc:creator>
      <pubDate>Thu, 22 Oct 2026 11:05:35 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-to-find-a-bridge-for-your-exact-token-1eni</link>
      <guid>https://dev.to/robert-eth/how-to-find-a-bridge-for-your-exact-token-1eni</guid>
      <description>&lt;p&gt;To find a bridge for your exact token, match its network and contract address before comparing routes. A token’s ticker alone cannot prove it is the same asset. Your wallet shows the network and usually lets you copy the token’s address.&lt;/p&gt;

&lt;h2&gt;
  
  
  Identify the token you actually hold
&lt;/h2&gt;

&lt;p&gt;Start with the token’s network and contract address, then use those details to check provider support. The contract address is the token’s unique on-chain identifier; two tokens can share a ticker but have different addresses. &lt;a href="https://chainbrief.pages.dev/super-bridge-routes-how-to-recover-a-stuck-transfer/" rel="noopener noreferrer"&gt;Super Bridge&lt;/a&gt; can compare routes from several providers, so you can check options without opening each bridge separately.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Open your wallet and note the source network.&lt;/strong&gt; This is the network where your token currently sits. Copy the token’s contract address from the wallet or a trusted block explorer, a site that shows public blockchain records.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enter the source network, token, amount and destination network.&lt;/strong&gt; Connect your wallet to the route finder and choose the token you hold. Super Bridge is useful here because it brings provider routes together for a single transfer search.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Check that the route accepts your source token
&lt;/h2&gt;

&lt;p&gt;A route is suitable only if its source side can use the token in your wallet. A provider might accept that token directly, or a route may first swap it for another asset, bridge that asset, then swap again at the destination.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Read the route details before choosing.&lt;/strong&gt; Check the input token and network, the destination token, the estimated amount received, and the fees. If the route swaps your token first, compare the final amount with a route that accepts it directly; extra swaps can change the price you get.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix the common ticker mistake.&lt;/strong&gt; If you searched “ABC” and found a route, check that the input address matches your token’s address. A matching ticker with a different address can mean a different asset. If there is no route for your exact token, look for a provider that lists its address or swap it yourself only after checking the costs and destination token.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Prepare your wallet before confirming
&lt;/h2&gt;

&lt;p&gt;A route quote does not mean the transfer is ready to send. Your wallet must hold enough of the source token and the network’s native coin, the asset used to pay transaction fees.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check the approval and fees.&lt;/strong&gt; For many wallet tokens, you first approve a provider to spend tokens for the transfer. EIP-20, Ethereum’s token standard, defines this approval step. Check which token and amount the wallet asks you to approve, and review the provider fee, network fees and estimated amount received.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the transfer and check the destination.&lt;/strong&gt; Read the wallet’s transaction details before signing. After the source transaction is sent, use the route’s status page or transaction record to see when the destination transfer finishes, then check the receiving network and token in your wallet.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Match the network and contract address first, then choose the route that clearly shows what leaves your wallet and what arrives.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>4 steps to compare cross-chain bridge quotes</title>
      <dc:creator>David</dc:creator>
      <pubDate>Wed, 21 Oct 2026 22:40:03 +0000</pubDate>
      <link>https://dev.to/robert-eth/4-steps-to-compare-cross-chain-bridge-quotes-2327</link>
      <guid>https://dev.to/robert-eth/4-steps-to-compare-cross-chain-bridge-quotes-2327</guid>
      <description>&lt;p&gt;A cross-chain bridge quote estimates what you will receive, what you will pay, and how long a token transfer may take on a route between networks. The key condition is that the quote must match the exact token, amount, destination chain, and recipient you intend to use.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Compare the destination amount after fees, not a headline fee by itself.&lt;/li&gt;
&lt;li&gt;Check which token arrives and whether the estimate includes a destination-chain swap.&lt;/li&gt;
&lt;li&gt;Treat quoted time as an estimate: route design and network conditions affect completion.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What should you compare in each quote?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Match the transfer details.&lt;/strong&gt; Enter the same source chain, destination chain, token, amount, and recipient for every route. A token with the same ticker can have a different contract address on another network, so check the destination asset’s identity before comparing amounts. &lt;a href="https://blockdigest.pages.dev/super-bridge-native-routes-follow-the-rollups-settlement-path/" rel="noopener noreferrer"&gt;Super Bridge transfers&lt;/a&gt; let you compare eligible native and third-party routes in one place, which can save you from checking providers one by one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare the amount you will receive.&lt;/strong&gt; Record the quoted destination amount and any minimum amount, often shown as “minimum received” or “to amount min.” The LI.FI API specification separates estimated output from minimum output and lists route fees, illustrating why the largest displayed figure alone may not be the amount you can rely on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add up the costs and steps.&lt;/strong&gt; Check source-chain gas, bridge or relayer fees, any swap fee, and destination-chain gas if the route requires a separate transaction. Also note approvals: an ERC-20 transfer may require a wallet signature to approve token spending before the bridge transaction. Ethereum.org’s bridge guidance identifies gas and route-dependent fees as parts of transfer cost.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How do you choose between routes?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Choose by usable output, timing, and route design.&lt;/strong&gt; For example, say you want to move 1 ETH from Optimism to Base. Route A quotes 0.995 ETH in five minutes; Route B quotes 0.998 ETH in 20 minutes. If you need funds quickly, the extra 0.003 ETH may not be worth waiting for; if timing is flexible, compare the full fees and route details before deciding. These figures are illustrative, and estimates can change with liquidity and network conditions.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I would select the route that delivers the token I need at an acceptable net amount and time, then review its provider and transaction details before signing. A route aggregator such as Super Bridge can surface different paths, but the route still determines how the transfer is carried out; a native bridge and a third-party liquidity route can differ in trust assumptions and withdrawal process. Recheck the quote if the amount or network conditions change.&lt;/p&gt;

&lt;h2&gt;
  
  
  What else should you know before sending?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is the lowest fee always the best route?
&lt;/h3&gt;

&lt;p&gt;No. A low stated fee can come with a lower destination amount, a slower estimate, or an extra swap or claim step. Compare what reaches your wallet after all quoted charges, then weigh the time and route design. For a small transfer, a separate destination transaction can matter more than a small difference in the bridge fee.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does the received amount change after I request a quote?
&lt;/h3&gt;

&lt;p&gt;Quotes depend on current liquidity, gas costs, and market conditions. A route may also involve a token swap, where price movement and available liquidity affect output. Treat the estimate as a snapshot: refresh it shortly before signing, and make sure the wallet transaction still matches the amount and destination you reviewed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does a faster route use the same bridge mechanism?
&lt;/h3&gt;

&lt;p&gt;Not necessarily. A route that uses destination-side liquidity can pay out before the source-chain transfer has fully settled, while a native bridge may wait for its own verification or finality process. Faster delivery can therefore involve different providers and trust assumptions. Check the route details and its stated completion process rather than inferring the mechanism from speed alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  What should I check in my wallet before confirming?
&lt;/h3&gt;

&lt;p&gt;Confirm the source network, token contract, amount, recipient, and any approval or swap shown in the transaction. Check that the wallet’s gas estimate is affordable and that the destination address is correct. If the final wallet transaction differs materially from the quote, pause and request a fresh quote before signing.&lt;/p&gt;

&lt;p&gt;Choose by the amount you can use, the time you can accept, and the route you understand—not by one fee number.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>3 checks for cross-chain bridge verifiers</title>
      <dc:creator>David</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:05:56 +0000</pubDate>
      <link>https://dev.to/robert-eth/3-checks-for-cross-chain-bridge-verifiers-2c31</link>
      <guid>https://dev.to/robert-eth/3-checks-for-cross-chain-bridge-verifiers-2c31</guid>
      <description>&lt;p&gt;A cross-chain transfer usually asks you to trust 2 separate things: the source chain’s finality and the bridge’s verifier. On a centralised exchange, the exchange handles both behind the scenes; from your wallet, you approve a transaction and rely on another system to confirm it on the destination chain. A route through &lt;a href="https://defi-handbook.gitbook.io/defi-handbook-docs/mayan-bridge-explained-routes-costs-and-settlement" rel="noopener noreferrer"&gt;Mayan bridge&lt;/a&gt; shows why the route matters: an app can offer several ways to move assets, each with its own checks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Source-chain finality sets the first wait
&lt;/h2&gt;

&lt;p&gt;Finality means the point when a transaction is treated as settled and unlikely to be reversed. A bridge verifier must decide when the source transaction is settled enough to act on it.&lt;/p&gt;

&lt;p&gt;For example, Wormhole Guardians watch supported chains and sign a message after observing an event. A destination contract checks those signatures before acting. Wormhole requires 13 of 19 Guardians to agree, but the time they wait depends on the source chain and the chosen finality setting.&lt;/p&gt;

&lt;p&gt;Wormhole’s published estimates put finalized messages at around 14 seconds on Solana and 19 minutes on Ethereum. Those are estimates, and actual waits can vary. Faster confirmation can mean more chance that a source-chain reorganisation—a change to recently recorded blocks—undoes the event.&lt;/p&gt;

&lt;h2&gt;
  
  
  The verifier decides whose report counts
&lt;/h2&gt;

&lt;p&gt;A bridge verifier sets the rules for accepting a cross-chain message. In Wormhole’s model, a quorum, or required group, of Guardians signs a message, and the destination contract checks their signatures.&lt;/p&gt;

&lt;p&gt;Other routes can use a different trust arrangement. Circle CCTP, for instance, has Circle provide a signed attestation—a statement confirming a USDC burn on the source chain. The destination contract checks that attestation before minting USDC there. The underlying chain still determines when the burn is final.&lt;/p&gt;

&lt;p&gt;So “supported on both chains” does not mean “verified the same way.” The route may rely on a group of independent signers, a named issuer’s attestation, or another system. Even within one app, the verifier can change with the route selected.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the route before you approve
&lt;/h2&gt;

&lt;p&gt;Before signing, check which route the quote uses, how much you should receive, and which token will arrive. A quoted amount is the expected result; the minimum amount is the least the route promises under its stated conditions.&lt;/p&gt;

&lt;p&gt;A common mistake is to treat a bridge quote like an exchange order and assume the app handles every risk. Instead, check the source and destination chains, the route name, the token, and the minimum received. Also keep enough of the source chain’s native token—the coin used to pay transaction fees—to submit the transfer.&lt;/p&gt;

&lt;p&gt;After signing, the source transaction may confirm before the destination transfer finishes. A relayer, a service that carries the signed message to the destination, may still need to submit it. For Mayan bridge routes, the method shown for that transfer helps explain who verifies the message and why the wait can vary.&lt;/p&gt;

&lt;p&gt;The useful habit is to judge each route by its finality rule and verifier, then sign only when those checks and the quoted result make sense to you.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>crypto</category>
      <category>web3</category>
    </item>
    <item>
      <title>How to estimate your cross-chain transfer’s real cost</title>
      <dc:creator>David</dc:creator>
      <pubDate>Sat, 17 Oct 2026 03:31:38 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-to-estimate-your-cross-chain-transfers-real-cost-2c2e</link>
      <guid>https://dev.to/robert-eth/how-to-estimate-your-cross-chain-transfers-real-cost-2c2e</guid>
      <description>&lt;p&gt;Compare the value you will receive, not a fee headline. A cross-chain route may include a source-chain transaction, bridge or liquidity costs, and a swap; the useful figure is the final amount of the asset you want, after those costs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which costs should you add together?
&lt;/h2&gt;

&lt;p&gt;Count every cost between the assets in your wallet now and the asset in your wallet at the destination. A route that swaps as it crosses chains can bundle several of these into one quote, but the costs still affect the result.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Source gas:&lt;/strong&gt; the network fee to approve a token, if needed, and submit the transfer. Some tokens need a separate approval transaction; native assets do not.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bridge or liquidity cost:&lt;/strong&gt; a fee for moving value across networks, or a difference between the amount sent and the amount delivered. It varies with the route and available liquidity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Swap cost:&lt;/strong&gt; the pool fee and price impact if the route converts one token into another. Price impact is the way your trade size moves the exchange rate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Destination gas:&lt;/strong&gt; the network fee for a later action, such as swapping or sending the received token. It may not be part of the bridge quote.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ethereum.org’s bridge material describes fees as dependent on gas and route liquidity, which is why a single “bridge fee” cannot represent the whole cost. If your goal is to arrive holding a different token, &lt;a href="https://elijahfigw840705.like-blogs.com/42936603/how-to-use-acrossbridge-to-move-crypto-from-your-wallet" rel="noopener noreferrer"&gt;acrossbridge bridge&lt;/a&gt; can combine the cross-chain move and swap in one flow; compare its estimated output with the output from doing those actions separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you compare two routes fairly?
&lt;/h2&gt;

&lt;p&gt;Put both routes on the same basis: same source amount, destination network, destination token, and time of comparison. Then compare the estimated final token amount, while recording any fees the quote excludes.&lt;/p&gt;

&lt;p&gt;For example, suppose you want to move 0.1 ETH from Ethereum to Arbitrum and finish with USDC. Route A bridges ETH first, then swaps on Arbitrum. Route B performs the transfer and conversion in one route. If A estimates 298 USDC after a $4 source transaction and a $1 destination swap fee, while B estimates 296 USDC with source gas included, A appears to deliver $2 more. These are illustrative values, not live prices.&lt;/p&gt;

&lt;p&gt;Check that the comparison includes any approval gas and that both estimates use the same USDC token on the same network. A USDC balance on Ethereum and one on Arbitrum are separate assets for this comparison. Also check whether the destination fee is included or whether you need to keep some ETH aside to use the funds after they arrive.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can the amount received change?
&lt;/h2&gt;

&lt;p&gt;A quote is an estimate for a particular market and network state. Gas prices change with demand, and swap output can change as liquidity or the token price moves before execution. A larger swap can have greater price impact, especially in a shallow pool.&lt;/p&gt;

&lt;p&gt;For a route that converts tokens, inspect the minimum output or slippage limit as well as the headline estimate. Slippage is the tolerated change between the quoted and executed price. For instance, a 0.5% tolerance on an expected $300 output permits roughly $1.50 of adverse movement; a tighter limit protects the rate but may cause the swap to fail if the market moves.&lt;/p&gt;

&lt;p&gt;Layer 2 fees are often lower than Ethereum mainnet fees, but the total still depends on the source transaction and route. Ethereum.org explains that rollups distribute mainnet costs across many transactions, while L2BEAT’s network comparisons are useful for understanding that networks have different designs and trade-offs. Treat the destination network’s low fee as one part of the calculation, not proof that the whole route is cheaper.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should you check before choosing?
&lt;/h2&gt;

&lt;p&gt;Use a short checklist before you commit. Acrossbridge is relevant when you want to compare a cross-chain transfer that also swaps into the token you plan to use, rather than calculate each leg by hand.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does the estimate end in the exact token and network you need?&lt;/li&gt;
&lt;li&gt;Are source gas, approvals, bridge costs, and swap costs included?&lt;/li&gt;
&lt;li&gt;Is the destination gas included, or must you reserve a little native token?&lt;/li&gt;
&lt;li&gt;What minimum output and slippage limit apply?&lt;/li&gt;
&lt;li&gt;Does the route deliver enough value to justify its extra steps or risk?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a small transfer, saving a few cents may not justify a route with several transactions; for a larger swap, a small percentage difference can outweigh a low gas fee. Compare the final amount, confirm what the quote includes, and choose the route whose cost and execution conditions fit the amount you are moving.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to Check a Cross-Chain Swap That Has Not Arrived</title>
      <dc:creator>David</dc:creator>
      <pubDate>Fri, 16 Oct 2026 18:20:40 +0000</pubDate>
      <link>https://dev.to/robert-eth/how-to-check-a-cross-chain-swap-that-has-not-arrived-4n0a</link>
      <guid>https://dev.to/robert-eth/how-to-check-a-cross-chain-swap-that-has-not-arrived-4n0a</guid>
      <description>&lt;p&gt;If you sent a cross-chain swap and cannot see the output yet, check the source transaction first, then trace its destination step. A confirmed source transaction does not always mean the other chain has finished the swap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what happened on the source chain
&lt;/h2&gt;

&lt;p&gt;A transaction hash is the unique code for a transaction; use it to find the record on the source chain’s block explorer, a site that lists chain activity. If the record says “failed” or “reverted,” the swap did not complete there. Check your wallet balance before trying again, especially if you approved token spending in a separate transaction.&lt;/p&gt;

&lt;p&gt;If the source transaction succeeded, the route may still need time to confirm it and carry out the destination step. &lt;a href="https://nikolaslavu076216.gynoblog.com/42057931/biswap-choosing-a-cross-chain-route-from-your-wallet" rel="noopener noreferrer"&gt;Biswap&lt;/a&gt; is a cross-chain bridge and swap service, so it is an example of a service that handles both moving and exchanging assets. The same source-to-destination check applies to a Biswap swap.&lt;/p&gt;

&lt;p&gt;The Ethereum.org explanation of transaction finality shows why a transaction may need time before a network treats it as settled. Timing varies by chain and route, so a pending status alone does not tell you that funds are lost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trace the destination step before acting
&lt;/h2&gt;

&lt;p&gt;Once the source transaction succeeded, check whether the destination chain recorded the expected token at your receiving address. biswap.uk can handle a cross-chain move and swap as one service. Compare the destination token and address with what you intended to receive.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Copy the source transaction hash from your wallet’s activity.&lt;/li&gt;
&lt;li&gt;Open the source chain’s block explorer and look for its result. Confirm the sending address and token match your transaction.&lt;/li&gt;
&lt;li&gt;Check the service’s transaction record, if available, for a status showing that destination processing is still underway or complete.&lt;/li&gt;
&lt;li&gt;Search the destination chain’s explorer for your receiving address and expected token. A successful destination transaction is stronger evidence of delivery than a wallet display alone.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, Arbitrum documents cross-chain messages that are submitted on one chain and executed separately on another. Some can need a later retry if automatic execution fails, so a successful source record and a missing destination record can describe an unfinished step, not a failed send.&lt;/p&gt;

&lt;p&gt;If the source succeeded but you cannot find a destination record, keep the hash and avoid sending a second swap until you know the first route’s status. If the destination record succeeded but your wallet still looks empty, check that the wallet is viewing the right network and token. The key is to confirm each chain’s step before deciding what to do next.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
