<?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: Robert</title>
    <description>The latest articles on DEV Community by Robert (@robert_defi).</description>
    <link>https://dev.to/robert_defi</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%2F4141429%2F3a97a1b8-37f1-41a6-9808-83c913900237.png</url>
      <title>DEV Community: Robert</title>
      <link>https://dev.to/robert_defi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/robert_defi"/>
    <language>en</language>
    <item>
      <title>Intent-Based Bridge vs Liquidity Pool Bridge: Speed by Amount</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Mon, 16 Nov 2026 22:14:25 +0000</pubDate>
      <link>https://dev.to/robert_defi/intent-based-bridge-vs-liquidity-pool-bridge-speed-by-amount-21pm</link>
      <guid>https://dev.to/robert_defi/intent-based-bridge-vs-liquidity-pool-bridge-speed-by-amount-21pm</guid>
      <description>&lt;p&gt;Intent-based bridging is usually faster than liquidity pool bridging for common tokens because a relayer delivers funds on the destination chain before getting repaid. &lt;a href="https://jumperbridge.io" rel="noopener noreferrer"&gt;Jumper bridge&lt;/a&gt; puts estimated arrival times beside route quotes, so you can compare that speed with the amount you will receive. A pool route waits for a cross-chain message to release funds, but it can be competitive when the transfer is too large for available relayers.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Do Intent-Based and Liquidity Pool Bridges Move Your Tokens?
&lt;/h2&gt;

&lt;p&gt;Both routes start with a deposit on the source chain and end with tokens in your destination wallet. The difference is who supplies those destination tokens, and when.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Intent route:&lt;/strong&gt; A relayer uses its own tokens to fill your requested transfer, then claims repayment after the fill is verified.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pool route:&lt;/strong&gt; Your deposit enters a source-chain pool; a cross-chain message authorizes release from a destination-chain pool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Result:&lt;/strong&gt; You receive the quoted destination token, less the costs shown in the route.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An &lt;em&gt;intent&lt;/em&gt; states the outcome you want, such as USDC on Base. A relayer is the participant with USDC already on Base who can pay you there. Across Protocol uses this model: relayers fill transfers first, while repayment follows settlement secured by UMA’s optimistic oracle. You see the fill before that repayment finishes.&lt;/p&gt;

&lt;p&gt;Stargate Finance illustrates the pool model. It holds tokens in pools across chains and uses LayerZero messages to coordinate transfers. The destination pool releases tokens after the message is processed. That message step is part of the user’s wait; in an intent fill, verification and repayment happen after the user receives funds.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Happens When You Bridge 500 USDC From Arbitrum to Base?
&lt;/h3&gt;

&lt;p&gt;In an illustrative 500 USDC transfer, you deposit USDC on Arbitrum and request USDC on Base. On an intent route, a relayer sees the deposit and sends the quoted amount from its Base balance, potentially within seconds. The relayer later claims repayment against your verified deposit. The transfer feels fast because the relayer carries the settlement wait.&lt;/p&gt;

&lt;p&gt;On a pool route, the Arbitrum deposit is recorded in the source pool. A cross-chain message then reaches Base, where the destination pool releases the quoted USDC after confirmation. You wait for that message, even though Base already has tokens available.&lt;/p&gt;

&lt;h3&gt;
  
  
  When Does a Pool Route Make More Sense?
&lt;/h3&gt;

&lt;p&gt;A pool route can make more sense when your amount exceeds the USDC that willing relayers can spare on Base. Relayers must fund fills up front and wait to reuse that capital. A large order may attract a higher fee, wait for capacity, or receive no fast quote. A pool with enough destination liquidity may then offer a better available route, despite its message delay.&lt;/p&gt;

&lt;p&gt;Token choice matters too. A less common token may have a usable pool route but few relayers holding it on the destination chain. Compare quotes for the exact token, chain pair, and amount: the word “intent” tells you how a route can be fast, while the quoted time and output tell you what this transfer is likely to cost.&lt;/p&gt;

&lt;p&gt;Jumper bridge lists different underlying routes, including intent and pool options. For your next transfer, read the provider name, estimated time, and amount received together; choose the fast fill when its price and capacity suit your amount, or the pool route when it offers the better usable quote.&lt;/p&gt;

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

&lt;h3&gt;
  
  
  What Is a Relayer in Crypto Bridging?
&lt;/h3&gt;

&lt;p&gt;A relayer is a participant that completes a cross-chain action, often by supplying tokens on the destination chain. In an intent route such as an Across fill, the relayer spends its own inventory and receives repayment later. “Relayer” can also mean a messenger in other bridge designs, so read what the named route asks it to do.&lt;/p&gt;

&lt;h3&gt;
  
  
  Are Intent-Based Bridges Safe?
&lt;/h3&gt;

&lt;p&gt;Intent-based bridge safety depends on the route’s deposit rules, fill verification, and settlement system. In Across, the deposit is escrowed, fills are matched to deposits, and repayment claims can be challenged through UMA’s optimistic verification process. Review the actual provider and destination token in the quote; speed alone says little about those protections.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Questions Come Next Before You Send?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What Happens If No Relayer Fills My Intent?
&lt;/h3&gt;

&lt;p&gt;An unfilled intent stays pending until the route’s fallback or deadline applies. Across can use a slower fill path on eligible routes; an expired, unfilled deposit can become eligible for a refund. Read the route’s status and deadline before submitting another transfer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why Do Bridge Fees Change With Transfer Size?
&lt;/h3&gt;

&lt;p&gt;Bridge fees change with size because a larger fill ties up more relayer capital, while pool pricing responds to available liquidity and utilization. Destination gas and any swaps also affect the quote. Requote your actual amount rather than scaling up the fee shown for a small test transfer.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Is Wormhole and How Does Mayan Use It?
&lt;/h3&gt;

&lt;p&gt;Wormhole supplies cross-chain messaging and token-transfer infrastructure. Mayan’s Wormhole Swap uses those messages and the Wormhole Token Bridge to move swap information and assets, with an auction determining execution. Read the specific Mayan route: its use of Wormhole does not by itself tell you that a relayer will pay you immediately.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I Bridge NFTs With an Intent-Based Bridge?
&lt;/h3&gt;

&lt;p&gt;Most intent routes quoted for fast token transfers handle fungible assets such as USDC, not individual NFTs. An NFT transfer needs a route that explicitly supports its collection, token ID, and destination chain. Look for those details in the quote before sending the NFT.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Shiba Swap Quotes, Minimum Received, and Treasury Records</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Mon, 09 Nov 2026 19:05:04 +0000</pubDate>
      <link>https://dev.to/robert_defi/shiba-swap-quotes-minimum-received-and-treasury-records-3039</link>
      <guid>https://dev.to/robert_defi/shiba-swap-quotes-minimum-received-and-treasury-records-3039</guid>
      <description>&lt;p&gt;For a treasury team converting tokens before recurring payouts, shiba swap’s quote is not the amount to record as received. It estimates output before execution. Minimum received is the lowest swap output the transaction will accept under its slippage setting; the completed amount comes from the confirmed transaction. This distinction keeps an estimate out of the payout record and gives the approver a useful limit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which figure tells us what arrived?
&lt;/h2&gt;

&lt;p&gt;The confirmed transfer into the receiving wallet tells you what arrived. Each figure has a different job:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Quoted output:&lt;/strong&gt; An estimate based on the current pool price and route. Another trade can move the price before yours executes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Minimum received:&lt;/strong&gt; The floor set by the chosen slippage tolerance. If the swap would produce less, it should fail rather than settle at that price.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Actual output:&lt;/strong&gt; The amount shown by the successful transaction after execution. It can differ from the quote while still clearing the minimum.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Think of the quote as an estimate on a purchase order, the minimum as its acceptance limit, and the confirmed transfer as goods counted at delivery. The analogy stops at delivery: an onchain swap either executes within its transaction rules or fails; it creates no promise to send tokens later.&lt;/p&gt;

&lt;h2&gt;
  
  
  What amount should we approve before signing?
&lt;/h2&gt;

&lt;p&gt;Approve against minimum received, because it defines the lowest swap output the selected slippage tolerance permits. Work backward from the tokens the payout batch needs in the treasury wallet. An approval for &lt;a href="https://shibaswap.app" rel="noopener noreferrer"&gt;shiba swap&lt;/a&gt; should identify the input amount, destination token, network, receiving wallet, and minimum received. ShibaSwap’s swap details show that floor alongside the route and price impact. The quote alone does not tell you whether a price move could leave the batch short.&lt;/p&gt;

&lt;p&gt;A tighter tolerance reduces the acceptable price movement but makes a price-driven failure more likely. A wider tolerance can let a worse price settle. Approve either setting only when its minimum still covers the tokens needed for payouts. If it does not, change the conversion amount or funding before signing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What belongs in the completed conversion record?
&lt;/h2&gt;

&lt;p&gt;A ShibaSwap conversion belongs in the completion record only after the transaction is confirmed and successful. Open its hash on the explorer for the network used and read the token transfer into the treasury wallet. Record the amount received, token, network, and transaction hash. Keep the quote and approved minimum as approval context, not as substitutes for the settled amount.&lt;/p&gt;

&lt;p&gt;If the token charges a transfer tax, reconcile the transfer with the wallet’s balance change: the wallet can receive less than the swap output shown. Gas is paid separately in the network token, so record its actual cost alongside the conversion. A pending transaction has no settled amount. A failed swap is no completed conversion, even if gas was spent.&lt;/p&gt;

&lt;p&gt;Revisit which transfer supplies the recorded amount if payouts start using a different receiving destination, such as a contract that forwards tokens immediately. In that case, reconcile the balance available at the final payout destination instead of treating the first transfer as the amount available to pay.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>RenBridge redemption: tracing a renBTC burn to Bitcoin</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Fri, 06 Nov 2026 01:59:47 +0000</pubDate>
      <link>https://dev.to/robert_defi/renbridge-redemption-tracing-a-renbtc-burn-to-bitcoin-3coa</link>
      <guid>https://dev.to/robert_defi/renbridge-redemption-tracing-a-renbtc-burn-to-bitcoin-3coa</guid>
      <description>&lt;p&gt;RenBridge redemption is verified only when a successful renBTC gateway burn links to a confirmed Bitcoin output for its intended recipient; the burn alone does not prove BTC arrived. &lt;a href="https://renbridge.net" rel="noopener noreferrer"&gt;RenBridge&lt;/a&gt; handled the burn and release as separate transactions on different blockchains, so a RenBridge burn receipt is just the starting record. Missing historical linkage can leave the answer inconclusive.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you find the successful gateway burn?
&lt;/h2&gt;

&lt;p&gt;Start with the chain on which you held renBTC, your wallet address, and any transaction hash or saved redemption session. Search that chain’s transaction history in a read-only explorer. If you no longer have the hash, look around the date you attempted the redemption and follow the relevant renBTC activity to its transaction details. A saved session can help identify the attempt, but the public transaction receipt establishes what happened on that chain.&lt;/p&gt;

&lt;p&gt;Separate the steps shown in that receipt. An approval gave a contract permission to spend renBTC; it did not redeem any. An ordinary token transfer moved renBTC on the host chain. A reverted call failed, even if your wallet displayed a redemption prompt or charged gas. For a successful redemption, identify the gateway burn in a successful transaction’s logs. The token movement alone is less useful than the gateway event, which ties the burned amount to the release request.&lt;/p&gt;

&lt;p&gt;Record the host chain, transaction hash, gateway contract, block number, burn event or identifier, and burned amount. Recover the Bitcoin recipient from the burn’s decoded event or input data, using the contract’s historical format if the explorer displays it as encoded bytes. Copy the resulting address carefully: the Bitcoin address you remember intending to use is not evidence of the address actually submitted.&lt;/p&gt;

&lt;h2&gt;
  
  
  RenBridge burn and Bitcoin release were separate
&lt;/h2&gt;

&lt;p&gt;A successful gateway burn started a burn-and-release operation. RenVM had to observe and process that burn, then authorize and broadcast a separate Bitcoin transaction. Bitcoin records outputs—specific amounts paid to specific addresses—rather than a change to your renBTC balance. Releases could share one Bitcoin transaction with other payouts, so the transaction hash alone does not identify which output was yours.&lt;/p&gt;

&lt;p&gt;Consider two attempts with the same successful burn status, amount, and encoded recipient. For the first, a retained RenVM release record associates its burn with a Bitcoin transaction whose confirmed output pays that recipient. That establishes the payout. For the second, you find a similar-sized Bitcoin payment near the burn time but no record connecting it to this burn. The payment may be real, yet its timing and amount cannot establish that it fulfilled this redemption.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you prove the Bitcoin payout?
&lt;/h2&gt;

&lt;p&gt;Use a retained release record, transaction history, or archived session that associates the burn identifier or host-chain transaction hash with a Bitcoin transaction ID. Treat that association as the cross-chain link, then inspect the Bitcoin transaction independently in a read-only explorer. Find the output paying the exact recipient encoded in the burn, and record its output index, amount, block height, and confirmations. A confirmed output is the evidence that native BTC reached that address.&lt;/p&gt;

&lt;p&gt;Do not require the Bitcoin output to equal the burned renBTC amount exactly. Protocol and Bitcoin transaction fees affected the net release, and a batched transaction may contain several recipient outputs plus change. Compare the recorded release details and the output addressed to your recipient; a matching total transaction value or nearby timestamp proves little when other redemptions share that transaction.&lt;/p&gt;

&lt;p&gt;An empty receiving wallet today does not undo a historical payout. Inspect the address’s transaction history for an incoming output at the release time and any later spend of that output. If the address was supplied by an exchange or custodian, the confirmed output establishes delivery to that address; whether the service credited your account is a separate question for its deposit records.&lt;/p&gt;

&lt;h2&gt;
  
  
  What if the historical link is missing?
&lt;/h2&gt;

&lt;p&gt;Record the missing link precisely. Save the burn transaction and decoded recipient, then note whether you have a release record, a candidate Bitcoin transaction, and a confirmed recipient output. If you can see an output to the address but cannot connect it to the burn, describe it as an unlinked payment. If the address history shows no relevant output, say that no on-chain payout to the submitted address was found in the history examined.&lt;/p&gt;

&lt;p&gt;Keep the paired transaction IDs, output index, and explorer details together when the link is established. When old RenVM or session records are unavailable, matching amounts and times may leave this specific redemption unresolved. The distinction matters: the burn proves renBTC was destroyed on its host chain, while the linked, confirmed Bitcoin output proves the historical payout.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related questions about the old bridge
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why was the service shut down?
&lt;/h3&gt;

&lt;p&gt;The original RenVM 1.0 service was sunset in 2022 after its development funding was disrupted. An audit of an earlier redemption therefore depends on historical transaction records, not on starting a new release through the old service.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which blockchains did it support?
&lt;/h3&gt;

&lt;p&gt;Bitcoin was the native chain for BTC payouts; renBTC appeared on host chains including Ethereum and BNB Chain. Support expanded over time. Use the chain shown by your burn transaction to identify where this particular attempt began.&lt;/p&gt;

&lt;h3&gt;
  
  
  How did it convert Bitcoin to renBTC?
&lt;/h3&gt;

&lt;p&gt;For a mint, RenVM observed BTC deposited on Bitcoin and authorized renBTC to be minted on a host chain. Redemption reversed the direction: burn renBTC on the host chain, then release native BTC on Bitcoin.&lt;/p&gt;

&lt;h3&gt;
  
  
  How should you assess RenBridge alternatives?
&lt;/h3&gt;

&lt;p&gt;For a new transfer, identify whether a route delivers native BTC or another wrapped token, which chains it supports, who controls the backing assets, and how redemption works. Those criteria tell you whether its outcome matches the one you need.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>3 Checks for an Acrossbridge Fee Quote</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Wed, 04 Nov 2026 21:07:41 +0000</pubDate>
      <link>https://dev.to/robert_defi/3-checks-for-an-acrossbridge-fee-quote-34g0</link>
      <guid>https://dev.to/robert_defi/3-checks-for-an-acrossbridge-fee-quote-34g0</guid>
      <description>&lt;p&gt;Before approving an acrossbridge fee quote, check how much leaves your source token, how much arrives, and the separate gas your wallet charges. You only bridge a few times a year, so a quick comparison can help you avoid approving a route that costs more than expected. The numbers to compare are on the quote and in your wallet.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. What does the quote take out?
&lt;/h2&gt;

&lt;p&gt;The difference between the amount you send and the amount you receive is the quote’s total fee. Across’s documentation says this covers relayer and liquidity-provider fees; the split can vary by token, route, pool use and destination-chain gas.&lt;/p&gt;

&lt;p&gt;For example, if you send 100 USDC and the quote says you will receive 99.82 USDC, the quoted fee is 0.18 USDC. Treat that as an illustration, not a typical rate: fetch a fresh quote for your route and amount, since fees change.&lt;/p&gt;

&lt;p&gt;Check that the quote shows the token and destination you actually want, then compare its receive amount with another quote for the same route. If you want to understand &lt;a href="https://www.tumblr.com/gladlyvirtualelement/832046822995394560/how-acrossbridge-moves-tokens" rel="noopener noreferrer"&gt;how to make an acrossbridge transfer&lt;/a&gt;, keep the token, networks and amount fixed while comparing; otherwise, you may be comparing different trades.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What does your wallet charge separately?
&lt;/h2&gt;

&lt;p&gt;Your wallet may charge source-chain gas in addition to the amount shown in the bridge quote. Gas pays for processing your deposit transaction, usually in the source chain’s native token; Ethereum.org explains that the cost varies with the computation required and network demand.&lt;/p&gt;

&lt;p&gt;So, if you send 100 USDC, the quote returns 99.82 USDC, and your wallet estimates gas at $0.07, your rough total cost is $0.25 if USDC is worth about $1. That last figure is illustrative, and the gas estimate can change before the transaction is included. Check which wallet account and network the gas estimate refers to before signing.&lt;/p&gt;

&lt;p&gt;Receiving tokens is different from spending them. You may need the destination chain’s native token later to make another transaction there, but that is not automatically part of the bridge fee. Check the quote and wallet screens for any separately stated charge instead of assuming destination gas is included.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Which quote should you accept?
&lt;/h2&gt;

&lt;p&gt;Choose by the amount that will arrive, after checking the network, token and recipient, rather than by a fee percentage alone. A small transfer can have a high fee as a share of its value because some costs, such as gas, do not fall in proportion to the amount sent.&lt;/p&gt;

&lt;p&gt;Before confirming, read the final wallet screen: verify the source network, token, amount and transaction fee. Then submit only if the quoted receive amount still makes sense for you. If the quote has expired or changed, refresh it and compare again; a stale number is not a reliable cost estimate.&lt;/p&gt;

&lt;p&gt;Across’s fee documentation describes the quote as the difference between input and output, while Ethereum.org explains why gas moves with network demand. Use both ideas when deciding: the receive amount shows the bridge cost, and your wallet shows the gas you also need to pay.&lt;/p&gt;

&lt;p&gt;For an occasional transfer, compare the final receive amount and wallet gas before signing; together they give you the clearest view of the cost.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>ParaSwap vs a direct swap: choosing your first trade</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Fri, 30 Oct 2026 22:19:46 +0000</pubDate>
      <link>https://dev.to/robert_defi/paraswap-vs-a-direct-swap-choosing-your-first-trade-322m</link>
      <guid>https://dev.to/robert_defi/paraswap-vs-a-direct-swap-choosing-your-first-trade-322m</guid>
      <description>&lt;p&gt;ParaSwap is worth choosing when its route gives you more after costs and its minimum return meets your limit. It is a decentralized exchange aggregator: it checks several places to trade tokens, then offers a path for your swap. A direct swap uses one trading pool, which is a supply of tokens set aside for trades.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does the route work?
&lt;/h2&gt;

&lt;p&gt;The route is the path your tokens take through one or more pools. The aggregator checks the price for your exact amount. It may split the trade between pools or swap through an intermediate token if that improves the result.&lt;/p&gt;

&lt;p&gt;ParaSwap then builds a transaction for a smart contract, a program that carries out the trade on the network. The official Augustus Swapper documentation describes both direct paths and paths with intermediate tokens. A better quoted rate is useful only if the extra steps do not cost more to execute.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which checks decide between the two?
&lt;/h2&gt;

&lt;p&gt;Four checks decide whether an aggregated route suits your trade. Make them for the same token pair, amount, network, and time, since quotes can change quickly.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Network and token availability&lt;/li&gt;
&lt;li&gt;Amount received after fees and gas&lt;/li&gt;
&lt;li&gt;Minimum received and price impact&lt;/li&gt;
&lt;li&gt;Route details and token approval&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Network and tokens:&lt;/strong&gt; First, check that both tokens are available on the network in your wallet. For example, USDC on Base and USDC on Ethereum are on different networks. A quote for one cannot be used to trade the other.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Net amount:&lt;/strong&gt; The ParaSwap quote shows the expected tokens you receive after costs within the trading pools. Once you know your pair and amount, check &lt;a href="https://paraswap.pro" rel="noopener noreferrer"&gt;ParaSwap fees&lt;/a&gt; for any added charge. Then account for gas, the network fee paid from your wallet. A first trade may also need a separate approval transaction, with its own gas cost.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minimum received:&lt;/strong&gt; This is the lowest output you agree to accept. Slippage means the price changes between the quote and the completed trade; your tolerance sets how much change you allow. Price impact is different: it is the price change caused by the size of your own trade. Check both figures when a token has little available liquidity, meaning few tokens are ready to trade.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Route and approval:&lt;/strong&gt; Look at the pools and any intermediate token before signing. If you sell a token such as USDC, an approval may let the trading contract spend it from your wallet. I would approve only the amount I plan to trade for a first swap, then wait for that approval to confirm before checking the quote again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can a quote comparison look like?
&lt;/h2&gt;

&lt;p&gt;Compare the amount left after gas, using quotes taken close together. Say you want to swap 1,000 USDC for ETH on Base. An aggregated route quotes 0.2860 ETH with estimated gas of 0.0003 ETH. A direct pool quotes 0.2854 ETH with estimated gas of 0.0001 ETH.&lt;/p&gt;

&lt;p&gt;In this example, the amounts after estimated gas are 0.2857 ETH and 0.2853 ETH. The route leads by 0.0004 ETH. That is a small edge: at a 0.5% slippage tolerance, a 0.2860 ETH quote could fill as low as 0.28457 ETH. I would check both minimum outputs before treating the higher estimate as a better trade.&lt;/p&gt;

&lt;p&gt;These figures are illustrative, not current prices or fees. Gas changes with network demand and the work a route requires. Compare any approval cost too, especially when a small trade needs two transactions.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you make the first swap?
&lt;/h2&gt;

&lt;p&gt;Start by connecting your wallet and choosing the network, input token, output token, and amount. Check the token details in your wallet so you do not select a lookalike token. Read the expected output, minimum received, route, and gas estimate before continuing.&lt;/p&gt;

&lt;p&gt;Keep some of the network’s native coin for gas. On Base, that means ETH, even if you are selling USDC to receive ETH. If the wallet asks for approval, check the token, amount, and spending contract. Refresh the quote after approval; approving a token does not lock in its price.&lt;/p&gt;

&lt;p&gt;For a first ParaSwap trade, I would start with a small amount and confirm what arrives in my wallet. The useful choice is the route whose likely and minimum returns justify its full cost for your trade.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Do I Move Manta Sale Proceeds To An Exchange?</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Fri, 23 Oct 2026 15:21:39 +0000</pubDate>
      <link>https://dev.to/robert_defi/how-do-i-move-manta-sale-proceeds-to-an-exchange-1i5n</link>
      <guid>https://dev.to/robert_defi/how-do-i-move-manta-sale-proceeds-to-an-exchange-1i5n</guid>
      <description>&lt;p&gt;To move marketplace sale proceeds from Manta Pacific to an exchange, withdraw them to Ethereum Mainnet first, then send them to the exchange’s Ethereum deposit address. For example, if your sale pays 100 USDC, you need enough ETH on Manta Pacific for the withdrawal and enough ETH on Ethereum for the final send.&lt;/p&gt;

&lt;p&gt;This works when your marketplace proceeds are in a token the bridge supports and your exchange accepts on Ethereum. A bridge moves assets between networks; it does not convert them into another token or send them into your exchange account.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should I check before withdrawing?
&lt;/h2&gt;

&lt;p&gt;Check the sale token, its network, and the exchange’s deposit instructions before moving anything. A token ticker such as USDC can exist on several networks, and an exchange may credit only deposits sent on the network it names.&lt;/p&gt;

&lt;p&gt;Open the exchange’s deposit page and choose the exact asset and Ethereum network. Copy the deposit address, but do not send funds yet. Compare the asset and network with the marketplace balance and the bridge’s available choices.&lt;/p&gt;

&lt;p&gt;If the proceeds are on Manta Pacific and you want them on Ethereum Mainnet, &lt;a href="https://www.tumblr.com/cloudypendulummercenary/831075026796183552/how-does-manta-bridge-work" rel="noopener noreferrer"&gt;Manta Bridge&lt;/a&gt; handles that network transfer for supported assets. Manta Pacific is an OP Stack network, a type of Ethereum scaling network; its bridge withdrawal has a waiting period before the funds can be claimed on Ethereum.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I withdraw and send the proceeds?
&lt;/h2&gt;

&lt;p&gt;Follow these steps in order. Keep some ETH in your wallet on both networks: ETH pays transaction fees, which are small payments for processing actions on a blockchain.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Check that your wallet shows the sale proceeds and some ETH on Manta Pacific.&lt;/li&gt;
&lt;li&gt;Open Manta Bridge, connect your wallet, and select Withdraw to Ethereum Mainnet.&lt;/li&gt;
&lt;li&gt;Choose the sale token and enter the amount. Review the estimated fee and the amount expected to arrive.&lt;/li&gt;
&lt;li&gt;Confirm the withdrawal in your wallet. Save the transaction record so you can check its status later.&lt;/li&gt;
&lt;li&gt;Wait for the withdrawal challenge period to pass, then complete the claim step if the bridge prompts you. A claim releases the funds to your Ethereum wallet.&lt;/li&gt;
&lt;li&gt;Once the token appears on Ethereum, send a small test amount to the exchange address you checked earlier.&lt;/li&gt;
&lt;li&gt;After the exchange credits the test, send the remaining amount. Wait for the exchange to show the required deposit confirmations.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, if you have 100 USDC, the bridge estimates 1 USDC in fees, and you reserve 5 USDC for a test, about 94 USDC remains for the final send. Use the live fee estimate and your exchange’s minimum deposit; both can change.&lt;/p&gt;

&lt;h2&gt;
  
  
  How long will it take, and what will it cost?
&lt;/h2&gt;

&lt;p&gt;Allow several days for the standard withdrawal, then extra time for the exchange to credit your deposit. L2BEAT lists Manta Pacific’s challenge period at about three days; the bridge status and current instructions should guide your timing. Ethereum.org explains that network fees vary with demand.&lt;/p&gt;

&lt;p&gt;You may pay Manta Pacific gas to start the withdrawal, Ethereum gas to claim it, and Ethereum gas again to send the exchange deposit. The bridge screen and wallet show estimates before you confirm. A low sale amount may not be worth moving if these fees take a large share.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick questions&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I send directly from Manta Pacific to an exchange?
&lt;/h3&gt;

&lt;p&gt;Only if the exchange explicitly supports deposits on Manta Pacific for that exact token. If its deposit page says Ethereum, bridge the proceeds to Ethereum first. Sending on the wrong network can delay recovery or make the funds inaccessible, so follow the exchange’s network instructions exactly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why is there a claim step?
&lt;/h3&gt;

&lt;p&gt;A standard rollup withdrawal waits while the network allows time to challenge a transaction result. After that waiting period, the claim step releases the funds on Ethereum. Keep the transaction record and return to the bridge to check whether it is ready; starting the withdrawal alone may not finish the process.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if the bridge does not show my sale token?
&lt;/h3&gt;

&lt;p&gt;Do not choose a different token just because its ticker looks similar. Check the token’s full name and network in the marketplace and exchange. If the bridge does not support it, ask the marketplace or bridge’s official support what route is supported before signing anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if the exchange has not credited my deposit?
&lt;/h3&gt;

&lt;p&gt;Check that the Ethereum transaction succeeded, the destination address matches, and the exchange’s required confirmations have passed. Use the transaction record to find the transfer status. If those checks look right, contact the exchange through its official support channel and provide the transaction details.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the token and exchange network.&lt;/li&gt;
&lt;li&gt;Withdraw through Manta Bridge and wait for the claim.&lt;/li&gt;
&lt;li&gt;Test a small Ethereum deposit before sending the rest.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>How to Fund a Rollup Credential Registration on Manta Pacific</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Fri, 23 Oct 2026 00:44:45 +0000</pubDate>
      <link>https://dev.to/robert_defi/how-to-fund-a-rollup-credential-registration-on-manta-pacific-djd</link>
      <guid>https://dev.to/robert_defi/how-to-fund-a-rollup-credential-registration-on-manta-pacific-djd</guid>
      <description>&lt;p&gt;To pay a credential registration fee on Manta Pacific, put the required payment token and a small amount of ETH on Manta Pacific, then submit the registration from the wallet that will own the credential. If your funds are on Ethereum, bridge them first; the app’s fee and the two networks’ gas charges are separate costs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what the registry will charge
&lt;/h2&gt;

&lt;p&gt;Before bridging, open the registration screen and identify the chain, fee token, fee amount, and registering wallet. A registry may collect a one-time ERC-20 fee with an allowance and &lt;em&gt;transferFrom&lt;/em&gt;, while the registration transaction itself still needs ETH for Manta Pacific gas. The amount and token are set by the app or contract configuration, so don’t assume a quoted fee in one token can be paid with ETH.&lt;/p&gt;

&lt;p&gt;Read the fee shown at the final confirmation step and note whether it is fixed or calculated at submission. Ethereum.org describes bridges as tools for moving assets between networks; for this task, the route matters because the registration contract executes on Manta Pacific. The guide to &lt;a href="https://aboutdefi.github.io/manta-bridge-offers-two-routes-from-ethereum-to-pacific/" rel="noopener noreferrer"&gt;how Manta Bridge routes assets&lt;/a&gt; covers the Ethereum-to-Manta Pacific transfer that gets funds to that execution environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bridge the fee token and gas to Manta Pacific
&lt;/h2&gt;

&lt;p&gt;Use Manta Bridge to deposit from Ethereum to Manta Pacific, selecting the exact token the registry accepts. Its asset selector and quote are the practical checks: availability can differ by token, and the amount received can be affected by the displayed bridge terms. There is no reliable flat cost to budget in advance; Ethereum gas varies with network demand, while the bridge quote and destination gas estimate are shown for the transaction.&lt;/p&gt;

&lt;p&gt;For example, if the registry charges an ERC-20 fee, bridge enough of that token to cover the fee plus a margin for any token-specific rounding or a changed fee before submission. Keep ETH on Manta Pacific for the registration transaction and any approval transaction. If you have only the fee token there, the transaction can fail for insufficient gas even though your balance appears to cover registration.&lt;/p&gt;

&lt;p&gt;Common mistake: bridging exactly the fee amount and arriving without ETH, or assuming the asset used for the fee also pays gas. Fix it by checking both balances on Manta Pacific before opening the registration confirmation. If the fee token is not offered by the bridge, you’ll need an accepted asset route or a swap on Manta Pacific; check the contract address and token identity before approving a substitute.&lt;/p&gt;

&lt;h2&gt;
  
  
  Submit once, then verify the registration
&lt;/h2&gt;

&lt;p&gt;After funds arrive, switch the wallet to Manta Pacific and confirm the app is connected to the intended account. If the app requests an allowance, approve only the fee token and the amount needed where the wallet supports a limited approval; then submit registration and wait for the transaction to confirm. A pending Ethereum deposit is not spendable on the rollup, so don’t start registration until the destination balance updates.&lt;/p&gt;

&lt;p&gt;If registration reverts, inspect the failed transaction’s reason before retrying. Typical causes are a stale fee quote, insufficient allowance, wrong chain, or insufficient ETH for gas. A successful transaction hash is not by itself proof the credential is usable: check the app’s registry status or the resulting credential identifier. EIP-20 defines the allowance and transfer methods commonly used for ERC-20 fee collection.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the registration chain, fee token, amount, and wallet.&lt;/li&gt;
&lt;li&gt;Bridge the accepted token and ETH for Manta Pacific gas.&lt;/li&gt;
&lt;li&gt;Wait for the deposit, approve if requested, and submit registration.&lt;/li&gt;
&lt;li&gt;Verify the registry status or credential identifier after confirmation.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>How Long Does a CoW Swap Take to Settle?</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Thu, 22 Oct 2026 12:18:29 +0000</pubDate>
      <link>https://dev.to/robert_defi/how-long-does-a-cow-swap-take-to-settle-1ce4</link>
      <guid>https://dev.to/robert_defi/how-long-does-a-cow-swap-take-to-settle-1ce4</guid>
      <description>&lt;p&gt;A CoW Swap can settle within seconds or take much longer. After you sign, your order waits for a suitable trade and an on-chain transaction to complete. The wait depends on price movement, available liquidity, network conditions, and whether your order is a market swap or a limit order.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens after I sign a swap?
&lt;/h2&gt;

&lt;p&gt;Signing submits your trade instructions; it does not send a blockchain transaction by itself. CoW Swap records the order off-chain, meaning it waits in an online order book rather than immediately appearing on the blockchain. For a regular token swap, you usually do not pay network gas just to place the order.&lt;/p&gt;

&lt;p&gt;CoW Swap groups orders into batch auctions, which let competing traders’ instructions be considered together. Solvers, specialist programs that find ways to execute trades, compete to produce a valid result. The &lt;a href="https://tareom.com/cow-swap-in-2026-choose-a-trade-fix-a-pending-order/" rel="noopener noreferrer"&gt;cowswap&lt;/a&gt; interface handles this process for you, then shows the order in your activity while it is pending.&lt;/p&gt;

&lt;p&gt;When a solver finds a result that meets your signed price conditions, it submits a settlement transaction to the network. Settlement means the blockchain processes the trade and transfers the tokens. Your swap is complete once that transaction is confirmed.&lt;/p&gt;

&lt;h2&gt;
  
  
  How long should I expect to wait?
&lt;/h2&gt;

&lt;p&gt;A well-priced market swap may settle in seconds or minutes, but there is no fixed completion time. “Market” describes an order based on a current quote, not a promise of immediate execution. A busy network, thin liquidity, or a fast price move can make the wait longer.&lt;/p&gt;

&lt;p&gt;For example, suppose you are swapping 100 USDC for another token. If the available price stays within the order’s allowed range, a solver may include it in an upcoming auction and submit settlement. If the price moves outside that range first, the order can remain pending instead of trading at a worse price.&lt;/p&gt;

&lt;p&gt;The auction itself is only one part of the wait. After settlement is submitted, the network must include and confirm the transaction. A wallet may show “pending” during either stage, so check the order status in the activity panel before deciding that something is stuck.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why is my order still pending?
&lt;/h2&gt;

&lt;p&gt;A pending order may still be waiting for a price that satisfies its limit. A limit price is the worst exchange rate you agreed to accept. With a market swap, the quote and slippage setting set a boundary; slippage is the price movement you allow before the order should stop.&lt;/p&gt;

&lt;p&gt;Fees can affect the price needed for a limit order to execute. CoW Swap may wait until the market offers enough value to cover both your requested price and network costs. So a chart touching your limit price does not guarantee execution at that moment.&lt;/p&gt;

&lt;p&gt;Check whether the order is open, partially filled, expired, or settled. A partial fill means only some of the requested amount traded; the remainder may still be open. If the order expired without trading, review the amount, price, and duration before placing another one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should I do if I need to act now?
&lt;/h2&gt;

&lt;p&gt;First, open your order history and confirm its status. If it is still open and you want to stop it, request cancellation. An off-chain cancellation is usually free, but it is not instant: the order could settle before the cancellation is processed.&lt;/p&gt;

&lt;p&gt;If timing matters more than keeping the original price, cancel the open order and place a new market swap with a fresh quote. Review the minimum amount you will receive and the receiving address before signing. A new order does not guarantee faster execution, but it replaces stale price conditions with current ones.&lt;/p&gt;

&lt;p&gt;If the activity shows settlement submitted, wait for the network confirmation rather than placing a duplicate trade. You can use the transaction details in the order history to check whether it has confirmed. The same status and confirmation checks apply when you use cowswap for an occasional trade.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What gas do I need to move USDC onto Mantle?</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Wed, 21 Oct 2026 23:24:35 +0000</pubDate>
      <link>https://dev.to/robert_defi/what-gas-do-i-need-to-move-usdc-onto-mantle-374d</link>
      <guid>https://dev.to/robert_defi/what-gas-do-i-need-to-move-usdc-onto-mantle-374d</guid>
      <description>&lt;p&gt;If you are moving USDC from Ethereum into your own Mantle wallet, budget ETH on Ethereum for the deposit and possibly a separate approval, then native MNT on Mantle for later transactions. The bridge moves the asset; it does not turn USDC or bridged ETH into gas for your next action.&lt;/p&gt;

&lt;h2&gt;
  
  
  ETH on Ethereum pays for the deposit
&lt;/h2&gt;

&lt;p&gt;Ethereum ETH pays the network fee for submitting a deposit from your wallet. The amount depends on Ethereum congestion, the transaction’s gas use and the fee settings at the time; check the wallet’s estimate before signing, since the amount can change between transactions.&lt;/p&gt;

&lt;p&gt;For example, if you hold USDC on Ethereum, you still need ETH in that same wallet to deposit it. The USDC pays for the asset transfer, not the Ethereum transaction fee. Leave enough ETH for any approval as well as the deposit, rather than spending your entire ETH balance on the first prompt.&lt;/p&gt;

&lt;p&gt;If USDC appears as an available asset for your route, &lt;a href="https://cryptoassetwire.pages.dev/mantle-bridge-moves-tokens-through-two-chain-transactions/" rel="noopener noreferrer"&gt;Mantle Bridge&lt;/a&gt; can move it from Ethereum to Mantle; check the displayed network, amount and fee before you confirm. Mantle documentation describes the bridge flow, while Ethereum.org explains why an Ethereum transaction needs gas paid in ETH.&lt;/p&gt;

&lt;h2&gt;
  
  
  An ERC-20 approval can add another Ethereum fee
&lt;/h2&gt;

&lt;p&gt;An approval lets the bridge contract spend a specified amount of your token. For an ERC-20 deposit, such as USDC, your wallet may ask you to approve the token first and then submit the deposit as a second transaction. Each submitted transaction has its own Ethereum gas fee.&lt;/p&gt;

&lt;p&gt;You may not see an approval prompt if you already approved that contract and the remaining allowance covers the deposit. Approval alone does not move funds: after it confirms, you still need to review and sign the deposit transaction. Check the spender and allowance in the wallet prompt, especially if it offers permission to spend more than the amount you intend to bridge.&lt;/p&gt;

&lt;p&gt;This is why the fee estimate for the deposit screen may not be the whole cost. If you are making your first USDC deposit, keep ETH available for both prompts; if an adequate allowance already exists, there may be only the deposit transaction. The exact total depends on the transactions required and current Ethereum conditions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Native MNT pays for transactions after arrival
&lt;/h2&gt;

&lt;p&gt;Once your funds are on Mantle, native MNT pays gas for ordinary wallet actions there, such as sending a token or interacting with an app. A balance of USDC cannot pay that fee, and bridged ETH is not automatically native MNT.&lt;/p&gt;

&lt;p&gt;For a practical example, suppose you bridge USDC to swap it on Mantle. You need MNT in the receiving wallet for the swap transaction, even if the USDC deposit succeeded. Arrange a small native MNT balance on Mantle before you need to transact; the amount depends on the action and the network’s fee estimate at that time.&lt;/p&gt;

&lt;p&gt;Check the wallet’s selected network and token details after the deposit. A balance can be present on Mantle while the wallet is showing Ethereum, or the wallet may need the correct token added before displaying it. Those display issues do not mean the USDC itself can pay Mantle gas.&lt;/p&gt;

&lt;h2&gt;
  
  
  Returning funds to Ethereum takes gas on both sides
&lt;/h2&gt;

&lt;p&gt;A withdrawal back to Ethereum uses MNT for the transaction you initiate on Mantle, and ETH for the Ethereum transaction that completes the return when the bridge makes it claimable. Keep ETH on the wallet that will claim; the assets waiting to arrive cannot pay that Ethereum fee for you.&lt;/p&gt;

&lt;p&gt;Do not assume the outbound and return fees will match. They are transactions on different networks, with separate fee markets, and the withdrawal may have a later claim step. Check the bridge’s current withdrawal status and prompts, and keep the transaction hash so you can find the original transfer if you need to return to it.&lt;/p&gt;

&lt;p&gt;In short, keep ETH on Ethereum for the deposit and any approval, and native MNT on Mantle for activity after arrival. For a return, budget MNT to start the withdrawal and ETH for the claim. Check each wallet estimate when you act, because network fees vary.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>5 acrossbridge Steps When Token Approval Is Missing</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:36:20 +0000</pubDate>
      <link>https://dev.to/robert_defi/5-acrossbridge-steps-when-token-approval-is-missing-5891</link>
      <guid>https://dev.to/robert_defi/5-acrossbridge-steps-when-token-approval-is-missing-5891</guid>
      <description>&lt;p&gt;An acrossbridge transfer with missing token approval takes five steps: check the allowance, approve the spender, refresh the quote, deposit, and verify delivery. For a treasury sending an ERC-20 token, &lt;a href="https://acrossbridge.dev" rel="noopener noreferrer"&gt;acrossbridge&lt;/a&gt; clears the missing-approval hold-up after the origin wallet authorizes that spender; Across Bridge relayers can then deliver funds on the destination chain.&lt;/p&gt;

&lt;p&gt;Key points&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Approval gives a contract permission to spend a token; it does not send the transfer.&lt;/li&gt;
&lt;li&gt;Approve the spender and amount shown for the current route, then wait for confirmation.&lt;/li&gt;
&lt;li&gt;Get a fresh quote before depositing, especially when a multisig approval takes time.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why does acrossbridge need token approval?
&lt;/h2&gt;

&lt;p&gt;An ERC-20 transfer needs an allowance because the origin-chain contract must pull tokens from your wallet when you deposit. The allowance belongs to a specific token, spender, wallet, and chain. An approval left over from another token or contract will not satisfy the current transfer, even if the wallet holds enough funds.&lt;/p&gt;

&lt;p&gt;For example, a treasury may have 1,000 USDC on Arbitrum but see an insufficient allowance for a payment to Optimism. Signing the approval fixes that permission only. The separate deposit transaction creates the transfer intent: it escrows the input tokens, and a relayer uses its own funds to pay the recipient on the destination chain. The relayer is repaid later through the protocol’s verified settlement process.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five steps to prepare and send the transfer
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Get a quote for the exact transfer.&lt;/strong&gt; Enter the origin and destination chains, token contracts, amount, and recipient address. For a 1,000 USDC treasury payment, check that the quoted route supports that amount and that the wallet has USDC plus the origin chain’s gas token. Compare the quoted allowance with the required amount; a token balance alone does not establish permission.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Approve the quoted spender on the origin chain.&lt;/strong&gt; Check the token contract, spender address, chain, and allowance in the wallet or multisig transaction before signing. A common mistake is to treat the approval confirmation as proof that the payment was sent; no deposit has happened yet. An allowance limited to the planned amount reduces continuing exposure, while a larger allowance can avoid repeated approval transactions for regular payouts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wait for approval confirmation and refresh the quote.&lt;/strong&gt; A multisig proposal must be executed on-chain, not merely signed by enough team members. Confirm that the new allowance covers the quoted input, then check the recipient, output amount, fees, and quote expiry again. If approval took long enough for the quote to expire, use the new transaction details rather than submitting the old deposit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Submit the deposit transaction.&lt;/strong&gt; Check that the transaction is simulated successfully and that the wallet has enough native token for its gas. The deposit moves the approved tokens into the origin contract and records the recipient and minimum destination output. A relayer can then fill the intent on the destination chain, often within seconds after the origin deposit is observed; network conditions and available relayer liquidity can extend that time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verify the destination fill and reconcile the payment.&lt;/strong&gt; Match the origin deposit and destination transaction to the intended recipient, token, and amount before marking a payout complete. Record both transaction hashes, the received amount, and the fees for treasury records. If delivery is delayed, inspect the deposit status before retrying: a second deposit creates a second transfer rather than accelerating the first.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What fees do relayers charge on Across Bridge?
&lt;/h2&gt;

&lt;p&gt;Relayers have no single fixed charge across routes. The quote accounts for destination gas, the relayer’s cost of advancing capital, and its risk while awaiting repayment; a separate liquidity provider fee can rise as a route’s pool becomes more heavily used. The origin wallet also pays gas for the approval, when needed, and for the deposit. Those gas costs matter most on small transfers.&lt;/p&gt;

&lt;p&gt;Compare the input and expected output alongside the origin gas before approving. For example, if an illustrative quote takes 1,000 USDC and delivers 998 USDC, the 2 USDC difference is 0.2% of the input, with origin gas still to pay. Request a fresh quote for each batch: gas prices, pool utilization, route, and amount can change the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does it compare with a chain’s canonical bridge?
&lt;/h2&gt;

&lt;p&gt;A canonical bridge uses the chain’s own parent-to-child or child-to-parent transfer path; a relayer-based transfer pays for capital to reach the destination sooner. On Arbitrum One, a canonical withdrawal to Ethereum takes at least seven days before funds can be claimed. Moving from Arbitrum to Optimism through canonical bridges also requires going through Ethereum, adding transactions and time.&lt;/p&gt;

&lt;p&gt;The choice depends on the deadline, quoted net output, supported token route, and security process your team accepts. A fast fill arrives before the relayer’s later settlement, which relies on contract rules and a challenge process for invalid settlement proposals. Before authorizing the allowance, ask: does this exact route deliver the required token and amount to the approved recipient within the payment deadline, at a total cost the treasury accepts?&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Bridge Validators Never Hold The Whole Key</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:20:26 +0000</pubDate>
      <link>https://dev.to/robert_defi/why-bridge-validators-never-hold-the-whole-key-3o14</link>
      <guid>https://dev.to/robert_defi/why-bridge-validators-never-hold-the-whole-key-3o14</guid>
      <description>&lt;p&gt;Bridge validators never hold a complete custody key because splitting control makes it harder for one compromised operator to steal the assets. A threshold signing scheme lets several validators approve a transfer together while keeping the private key itself out of any one validator’s hands.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why not give one validator the key?
&lt;/h2&gt;

&lt;p&gt;A single-key bridge is simple to operate: one operator watches deposits and signs the transaction that releases funds or authorises wrapped tokens. It is also a single point of failure. If that operator’s key is stolen, misused, or lost, the bridge may be unable to protect or return the assets.&lt;/p&gt;

&lt;p&gt;For someone choosing a bridge, this model can be easy to understand, but it means trusting the key holder as a custodian. The key question is not how many people work for the operator; it is whether one person or system can produce a valid signature alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does threshold custody sign without rebuilding the key?
&lt;/h2&gt;

&lt;p&gt;In multi-party computation (MPC), validators jointly generate and use a key without ever assembling it in one place. Each validator holds a secret share, and a signing protocol combines their contributions into a standard signature that the destination blockchain accepts.&lt;/p&gt;

&lt;p&gt;For example, say a group has 100 validators and requires enough of them to cooperate before it can sign. The exact threshold depends on the protocol; the key property is that a smaller group cannot sign by itself. Validators do not send their shares to a leader to reconstruct the key. Instead, they exchange protocol messages that let them calculate the signature together.&lt;/p&gt;

&lt;p&gt;This is the custody approach RenVM used for RenBridge. A user could send Bitcoin to a gateway controlled by a validator group; after the deposit was recognised, the network authorised minting a wrapped asset on a destination chain such as Polygon. To see the flow in context, read &lt;a href="https://dailynewscrypto.github.io/renbridge-explained-how-its-three-transfer-routes-worked/" rel="noopener noreferrer"&gt;how RenBridge works&lt;/a&gt;: the same group signing mechanism also mattered when a user burned the wrapped asset and requested the original coin back.&lt;/p&gt;

&lt;p&gt;The threshold protects against one validator acting alone, but it does not make the bridge risk-free. A sufficiently large colluding or compromised group may still be able to sign, and software bugs, poor validator coordination, or a mistaken approval process can undermine the design.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does an on-chain multisig fit better?
&lt;/h2&gt;

&lt;p&gt;An on-chain multisig requires several distinct keys to approve a transaction, and the blockchain enforces the rule. It can be a good fit when the chain supports the required wallet logic and users value a visible approval record. Each signer has a complete key, but no single signer can meet the threshold alone.&lt;/p&gt;

&lt;p&gt;The trade-off is that the bridge may have to use a contract wallet or a chain-specific multisig format. That can add transaction costs and complicate support across chains. MPC can produce a regular signature that looks like one key’s signature on-chain, which can make it easier to work with chains that do not offer the same multisig features.&lt;/p&gt;

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

&lt;p&gt;First, find out who controls the shares and what threshold is required. A “distributed” design is only as distributed as its operators: if one organisation runs most validators, the key may be split technically while control remains concentrated in practice.&lt;/p&gt;

&lt;p&gt;Next, check what happens when validators fail or leave. The bridge needs a way to rotate or redistribute shares without exposing the key, and it needs enough available validators to process legitimate withdrawals. A high threshold can resist collusion but may also make the bridge stall when too many validators are offline.&lt;/p&gt;

&lt;p&gt;Finally, check current operating status before sending funds. RenBridge’s RenVM 1.0 network shut down in December 2022, so its historical threshold-key design should not be taken as evidence that transfers are available today. For any bridge, verify that deposits and withdrawals are active and that the asset you would receive can still be redeemed.&lt;/p&gt;

&lt;p&gt;I would choose a bridge only after checking both its signing threshold and who actually operates the signers; splitting a key helps, but distributed control is what makes the protection meaningful.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How long does a partial cross-chain swap refund take?</title>
      <dc:creator>Robert</dc:creator>
      <pubDate>Sat, 17 Oct 2026 05:44:08 +0000</pubDate>
      <link>https://dev.to/robert_defi/how-long-does-a-partial-cross-chain-swap-refund-take-2hho</link>
      <guid>https://dev.to/robert_defi/how-long-does-a-partial-cross-chain-swap-refund-take-2hho</guid>
      <description>&lt;p&gt;A partial cross-chain swap refund arrives after the route accounts for input it did not spend and submits a return transaction; timing depends on chain confirmations and route design, so there is no universal minutes figure. If you swap only a few times a year, check the deposit and refund separately before trying again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a partial refund return?
&lt;/h2&gt;

&lt;p&gt;It returns the portion of your input asset that the swap did not consume. If a route receives 100 tokens and uses 62, the unspent 38 may be returned, while the spent portion is exchanged for the destination asset. Those figures are illustrative; the actual amounts depend on execution.&lt;/p&gt;

&lt;p&gt;A route can leave input unspent when a price limit prevents further swaps, or when a route executes only part of an intended trade. A liquidity pool prices each trade against its available reserves, so the amount it can exchange at an acceptable rate can change as the swap proceeds. The refund is the remainder of the input, not compensation for receiving less output than expected.&lt;/p&gt;

&lt;p&gt;Fees can make the amount you receive back smaller than the simple difference between your deposit and the amount exchanged. A route may have already paid network costs or completed part of the swap before it returns what remains. Check the transaction records for the amount consumed, any recorded fees, and the refund amount.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can a cross-chain refund take longer?
&lt;/h2&gt;

&lt;p&gt;On one chain, a contract can sometimes calculate the unused input and return it in the same transaction. Across chains, the route may need to confirm your deposit, execute one or more swaps, then send a separate refund transaction on the original chain. Each step needs to be recorded by its network.&lt;/p&gt;

&lt;p&gt;For example, a local exact-output swap can stop once it has bought the requested amount and return excess input in that transaction. In a cross-chain route, the destination-side swap might finish after the source deposit has already been confirmed, so any leftover input may require a later transaction back on the source chain. The delay depends on the route and the two networks, not on a fixed refund window.&lt;/p&gt;

&lt;p&gt;If a &lt;a href="https://chainpulse-abh.pages.dev/thor-swap-puts-btc-to-eth-conversion-in-one-cross-chain-flow/" rel="noopener noreferrer"&gt;thor swap&lt;/a&gt; is how you plan to move between assets such as BTC and ETH, it gives you a single cross-chain swap flow instead of making you handle each transfer separately. Keep in mind that one flow can still involve separate on-chain steps: a thor swap result and its refund, if any, should be checked as distinct transactions.&lt;/p&gt;

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

&lt;p&gt;Use the transaction hash for the deposit to confirm that it reached the route, then look for a completed swap or refund transaction. The source and destination chains’ block explorers show whether each transaction was confirmed and which token moved. Check the refund’s chain, asset, amount, and receiving address; a return in the original input token is different from destination-chain output.&lt;/p&gt;

&lt;p&gt;A tiny remainder can also be difficult to return if the route or network cannot process an amount that small. There is no single dust threshold that applies across chains and assets, so compare the recorded refund with the original deposit and fees. If the route has not reached a final state, wait for its transactions to settle before submitting the same funds again.&lt;/p&gt;

&lt;p&gt;My rule for an occasional thor swap is to verify the refund on-chain before deciding what to do next. Once the refund is confirmed, check that the amount is spendable in your wallet; then make a fresh swap only if the original destination and amount still suit you.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Separate unspent input from output shortfall.&lt;/li&gt;
&lt;li&gt;Allow for a separate refund transaction and network confirmation.&lt;/li&gt;
&lt;li&gt;Verify the refund asset, chain, amount, and address in the block explorer.&lt;/li&gt;
&lt;li&gt;Wait for a final transaction state before retrying.&lt;/li&gt;
&lt;/ul&gt;

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