<?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: Willson Lammy</title>
    <description>The latest articles on DEV Community by Willson Lammy (@jake-eth).</description>
    <link>https://dev.to/jake-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%2F4141412%2F16bcb616-60f2-4a50-9dcc-85530e066ead.png</url>
      <title>DEV Community: Willson Lammy</title>
      <link>https://dev.to/jake-eth</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jake-eth"/>
    <language>en</language>
    <item>
      <title>Constant Product AMM Formula: Swap Output and Minimums</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Tue, 17 Nov 2026 03:38:14 +0000</pubDate>
      <link>https://dev.to/jake-eth/constant-product-amm-formula-swap-output-and-minimums-2796</link>
      <guid>https://dev.to/jake-eth/constant-product-amm-formula-swap-output-and-minimums-2796</guid>
      <description>&lt;p&gt;A constant product AMM calculates swap output as (amountIn × (1 − fee) × reserveOut) ÷ (reserveIn + amountIn × (1 − fee)). This is the most the pool can pay while keeping the product of its fee-adjusted reserves at least as large as it was before the trade.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use the pool’s current reserves and fee to calculate a quote.&lt;/li&gt;
&lt;li&gt;Round the output down in token units, then set an acceptable minimum.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How Do Reserves and Fees Determine Swap Output?
&lt;/h2&gt;

&lt;p&gt;The pool starts with reserveIn = x and reserveOut = y. A swap adds input and removes output, so the constant product equation is (x + amountIn × (1 − fee)) × (y − amountOut) = x × y. Solving for amountOut gives the formula above. The full input enters the pool; the fee adjustment limits how much output the trade can take.&lt;/p&gt;

&lt;p&gt;Uniswap V2 implements its 0.3% fee with integers: amountOut = (amountIn × 997 × reserveOut) ÷ (reserveIn × 1000 + amountIn × 997). Multiply before dividing and round the final result down. This avoids prematurely truncating the fee-adjusted input and ensures the trade leaves the actual reserve product at least as large as before.&lt;/p&gt;

&lt;p&gt;Take a pool holding 1,000 A and 1,000 B. Swapping 100 A produces about 90.66 B: (100 × 997 × 1,000) ÷ (1,000 × 1,000 + 100 × 997). Each additional unit of A buys B at a worse rate as the trade moves the reserves.&lt;/p&gt;

&lt;p&gt;Suppose the input rises to 110 A while those starting reserves stay the same. Output rises to about 98.83 B, but output per A falls from about 0.9066 B to 0.8985 B. The same equation still applies; the trade’s size relative to the reserves changes its rate.&lt;/p&gt;

&lt;p&gt;Pools on shiba swap derive from SushiSwap, a Uniswap V2 fork, and use the same formula. The &lt;a href="https://shibaswap.app" rel="noopener noreferrer"&gt;shiba swap&lt;/a&gt; exchange provides context for where these reserve-based quotes become swaps.&lt;/p&gt;

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

&lt;h3&gt;
  
  
  What is price impact in an AMM?
&lt;/h3&gt;

&lt;p&gt;Price impact is the change in the pool’s exchange rate caused by the trade itself. It grows as input becomes larger relative to the reserves, so an integration should calculate each quote from live reserves.&lt;/p&gt;

&lt;h3&gt;
  
  
  How is slippage tolerance set in a swap?
&lt;/h3&gt;

&lt;p&gt;Slippage tolerance sets amountOutMin below the current quote. With a roughly 90.66 B quote and 1% tolerance, the minimum is roughly 89.75 B, rounded down in raw token units. If reserves change before execution and the resulting output falls below amountOutMin, the swap reverts. A quote from stale reserves can therefore pass in your app and fail on-chain.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Happens Beyond a Single Pool?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How do multi-hop routes calculate output across pools?
&lt;/h3&gt;

&lt;p&gt;Each hop uses its own live reserves and fee. Feed one pool’s rounded-down output into the next pool as amountIn, then apply amountOutMin to the route’s final output.&lt;/p&gt;

&lt;h3&gt;
  
  
  How are LP fees accrued in the reserves?
&lt;/h3&gt;

&lt;p&gt;The fee stays in the input reserve. Because output is calculated from the fee-adjusted input while the pool receives the full input, the actual reserve product increases, accruing value to liquidity providers.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Do Bitcoin Cross-Chain Bridges Work: Where Your BTC Goes</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:05:59 +0000</pubDate>
      <link>https://dev.to/jake-eth/how-do-bitcoin-cross-chain-bridges-work-where-your-btc-goes-3k1h</link>
      <guid>https://dev.to/jake-eth/how-do-bitcoin-cross-chain-bridges-work-where-your-btc-goes-3k1h</guid>
      <description>&lt;p&gt;Your Bitcoin does not travel to another chain when you bridge it: you send BTC to a Bitcoin address, then receive a token or a swapped asset on the destination chain. In &lt;a href="https://teleswap.net" rel="noopener noreferrer"&gt;TeleSwap&lt;/a&gt;, a collateralized Locker receives the BTC, and proof of that payment allows teleBTC to be minted on an EVM chain. Bitcoin cannot run that chain’s smart contracts, so the BTC stays on Bitcoin while its value becomes usable elsewhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who Holds My Bitcoin When I Bridge It?
&lt;/h2&gt;

&lt;p&gt;The Bitcoin address receiving your deposit tells you who can release the coins later. A bridge must also establish that you paid that address before it gives you anything on the destination chain. Depending on the route, a custodian confirms the payment, a node network observes it, or a smart contract checks a proof against a Bitcoin light client.&lt;/p&gt;

&lt;p&gt;With WBTC, a custodian holds the backing BTC. Authorized merchants handle minting and redemption: when WBTC is redeemed and burned, the custodian releases BTC. Your route back to Bitcoin therefore depends on that custody and merchant process.&lt;/p&gt;

&lt;p&gt;TeleSwap uses a different holder. You send BTC to a Locker’s Bitcoin address; a light-client proof lets the EVM contract verify the payment and mint teleBTC to you. To return, you burn teleBTC and specify a Bitcoin address. The Locker must pay BTC there. If it fails under the protocol’s rules, its posted collateral can be slashed. The burn starts the return process; the Locker’s Bitcoin payment completes it.&lt;/p&gt;

&lt;p&gt;Imagine sending the same amount of BTC to reach the same EVM chain. On a WBTC route, a custodian controls the backing address and handles release through the merchant process. On a teleBTC route, a Locker controls the address, while collateral creates an on-chain penalty for failing to pay. Both routes give you a spendable token, but they place the release obligation on different parties.&lt;/p&gt;

&lt;p&gt;THORChain and Chainflip take a third route: you send native BTC to a Bitcoin vault controlled by bonded node operators and receive an asset paid from liquidity on the destination chain. There is no wrapped BTC token for you to redeem on that route. The operators’ shared control of the vault and their bonds matter because they govern how deposits and payouts are handled.&lt;/p&gt;

&lt;p&gt;The useful question is therefore who controls the Bitcoin address and what happens if they fail to release the BTC. Bitcoin cannot enforce a contract on another chain itself. Once you identify the custodian, collateralized Locker, or bonded vault operators, you can understand both what you receive and what your return to Bitcoin depends on.&lt;/p&gt;

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

&lt;h3&gt;
  
  
  Is Wrapped Bitcoin the Same as Bitcoin?
&lt;/h3&gt;

&lt;p&gt;Wrapped Bitcoin is a token on another chain backed by BTC held on Bitcoin. WBTC and teleBTC can move through supported smart contracts, but neither is native BTC in your Bitcoin wallet. To get native BTC back, follow that token’s redemption process and confirm the separate Bitcoin payout.&lt;/p&gt;

&lt;h3&gt;
  
  
  Are Bitcoin Bridges Safe?
&lt;/h3&gt;

&lt;p&gt;Bridge risk depends on control of the BTC and enforcement of the payout. For a custody route, identify the custodian and redemption path. For a Locker route, examine the collateral and slashing rules. For a vault swap, examine who signs vault transactions and how operators are bonded. These checks tell you which party or mechanism you rely on after sending BTC.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Should I Check Before Bridging BTC?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How Long Does a Bridge Transfer From Bitcoin Take?
&lt;/h3&gt;

&lt;p&gt;Transfer time depends on the Bitcoin confirmations the route requires, followed by proof verification or node observation and the destination transaction. Look for those stages in the route’s status display. A confirmed Bitcoin deposit means the first stage is complete, not necessarily that the destination asset has arrived.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Fees Do I Pay When Bridging BTC?
&lt;/h3&gt;

&lt;p&gt;Review the quote for the Bitcoin network fee, bridge or Locker fee, destination gas, and any swap spread or liquidity fee. Compare the final amount you will receive, because a native swap and a wrapped-token route can deduct costs at different stages.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which Wallets Work With Bitcoin Bridges?
&lt;/h3&gt;

&lt;p&gt;Use a Bitcoin wallet that can send to the route’s deposit address and a wallet that supports the destination chain and asset. For redemption, provide a Bitcoin receiving address you control and keep enough destination-chain gas to submit the burn. Confirm the supported networks and address formats before sending BTC.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Should I use full-range or concentrated liquidity on shiba swap?</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Fri, 06 Nov 2026 12:48:23 +0000</pubDate>
      <link>https://dev.to/jake-eth/should-i-use-full-range-or-concentrated-liquidity-on-shiba-swap-5db0</link>
      <guid>https://dev.to/jake-eth/should-i-use-full-range-or-concentrated-liquidity-on-shiba-swap-5db0</guid>
      <description>&lt;p&gt;If you cannot monitor price bounds or pay to reposition, choose full-range liquidity on shiba swap when that pool type exists for your pair. Because full-range coverage avoids a selected boundary, inspect the available pools on &lt;a href="https://shibaswap.app" rel="noopener noreferrer"&gt;shiba swap&lt;/a&gt; before depositing. ShibaSwap concentration puts more liquidity inside chosen bounds, but earns trading fees only where trades use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How shiba swap coverage changes fee eligibility
&lt;/h2&gt;

&lt;p&gt;Full-range liquidity spans possible prices, while concentrated liquidity serves trades only between the lower and upper prices you select. If you have provided liquidity in a traditional full-range pool, you already know that your share of trading fees varies with activity and competing liquidity. The additional choice in a concentrated pool is where your deposit will be active.&lt;/p&gt;

&lt;p&gt;Trades draw on liquidity available at the current price. By placing the same capital in a narrower range, you contribute more liquidity at prices inside that range and may earn a larger share of fees from trades there. Deposited value alone does not determine fee income: the position must be active when trades occur, and the pool needs trading volume. A range with little trading can earn less than a broader one despite its higher concentration.&lt;/p&gt;

&lt;p&gt;Make the comparison for the specific pair and network you intend to use. Pool types and activity may differ between Ethereum and Shibarium, so a coverage choice available for one pair or network does not establish what is available for another.&lt;/p&gt;

&lt;h2&gt;
  
  
  Leaving a range stops new fees and changes exposure
&lt;/h2&gt;

&lt;p&gt;An out-of-range concentrated position earns no new trading fees while price remains beyond its bounds. It can resume earning if price returns to the range and you have left the position in place. You can also move the position to new bounds, but doing so requires transactions and may require swapping tokens to supply the new range.&lt;/p&gt;

&lt;p&gt;Suppose you set a narrow range around today’s price and then stop watching it, expecting the deposit to keep earning as it did in a full-range pool. When price crosses a boundary, that expectation fails: trades at the new price use other active liquidity. The position has not disappeared, and previously earned fees remain distinct from whether it is earning new ones.&lt;/p&gt;

&lt;p&gt;At a boundary, the concentrated position’s liquidity becomes entirely one token. Which token it becomes depends on the direction of the price move and how the pair’s price is quoted. This matters if you deposited two assets because you wanted exposure to both. Waiting for price to return avoids a repositioning transaction, but it also means accepting the resulting single-token exposure and a period without new fees.&lt;/p&gt;

&lt;h2&gt;
  
  
  When can concentration improve net returns?
&lt;/h2&gt;

&lt;p&gt;Concentration improves net returns only when its extra fees outweigh the effects of price movement and the cost of managing the position. A narrow range can capture a greater share of active liquidity for the same capital, yet it may spend less time in range. Other providers can also add liquidity near the current price, reducing your share of fees even while your position stays active.&lt;/p&gt;

&lt;p&gt;Both full-range and concentrated positions change token composition as prices move. Either can finish worth less than simply holding the two assets you originally deposited; fees may or may not close that gap. Compare the value of the position plus earned fees with the value of holding those original amounts at the same time, then subtract transaction costs. That comparison is more useful than a displayed fee rate or a claim of higher capital efficiency.&lt;/p&gt;

&lt;p&gt;Repositioning has its own economics. Moving bounds may involve closing a position, opening another and swapping to the token amounts the new range needs. The cost depends on the network and the transactions required. Frequent adjustments can consume the fee advantage a narrow range appeared to offer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which coverage fits your management capacity?
&lt;/h2&gt;

&lt;p&gt;If avoiding range management is your priority, use an available full-range pool; if you can manage bounds and accept inactive periods, consider concentrated liquidity. Before choosing, decide how often you can review the position and whether you are comfortable holding only one token after price leaves the range. Set a budget for repositioning based on the transactions you might actually make, rather than assuming each adjustment will pay for itself.&lt;/p&gt;

&lt;p&gt;Then examine the available pools for your pair and their trading activity. A concentrated position needs enough trades within its bounds to justify the attention and costs. For a provider moving from full-range pools, I would start with coverage broad enough to tolerate normal price movement and narrow it only if monitoring the position fits your routine. If ShibaSwap offers only one relevant pool type for that pair and network, evaluate its exposure and activity on their own terms instead of treating the missing alternative as a return you could have earned.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Which Matcha Swap Mode Fits Your Trade?</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Thu, 05 Nov 2026 23:37:11 +0000</pubDate>
      <link>https://dev.to/jake-eth/which-matcha-swap-mode-fits-your-trade-12dl</link>
      <guid>https://dev.to/jake-eth/which-matcha-swap-mode-fits-your-trade-12dl</guid>
      <description>&lt;p&gt;Matcha swap mode follows the trade: choose Cross-chain for different networks, Limit Orders for a target price, Auto for supported trades with managed gas and slippage, or Standard for manual control. In &lt;a href="https://matchaswap.pro" rel="noopener noreferrer"&gt;Matcha swap&lt;/a&gt;, network, timing and gas balance narrow that choice. A Matcha DEX swap can use Auto only when its pair and network support it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Are the Source and Destination Tokens on Different Networks?
&lt;/h2&gt;

&lt;p&gt;Different source and destination networks call for Matcha Cross-chain Swaps. An Auto or Standard swap on one network cannot deliver tokens to another, even when the token has the same ticker on both. Select the source token and network where your balance sits, then the destination token and network where you want to receive it. Make this decision before weighing gas or slippage settings.&lt;/p&gt;

&lt;p&gt;A cross-chain route includes a bridge leg between networks and may include swaps around it. Its preview shows the expected destination amount, route, fees and estimated completion time. Source-chain confirmation means the first transaction succeeded; the destination leg can still be processing. Watch for destination-chain confirmation before treating the trade as complete. That second confirmation point is why a cross-chain swap can take longer than a swap on one network.&lt;/p&gt;

&lt;p&gt;Matcha’s supported swap networks are only a starting point: the selected tokens also need an available bridge route. If no route appears, changing a token or network may produce one. As long as the balance starts and ends on different networks, the trade still needs a cross-chain route.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can You Wait for a Target Price?
&lt;/h2&gt;

&lt;p&gt;If both tokens stay on one network, your timing decides whether to place Matcha Limit Orders. Choose a limit order when you will trade only at your chosen price or better and can wait for a fill. Set the amount, target price and expiry, then review the specified exchange amount before signing. The order can remain open until its conditions are met or it expires; placing it does not execute an immediate swap.&lt;/p&gt;

&lt;p&gt;Suppose you want to buy a token only after its price falls. A limit order below the current quote expresses that condition, but it may never fill if the market does not reach your price before expiry. Reaching the price alone may also be insufficient if available liquidity cannot fill the order under its terms. If receiving the tokens now matters more than reaching that price, choose an immediate same-chain swap instead.&lt;/p&gt;

&lt;p&gt;The order preview answers a different question from an immediate swap quote: it shows the price you requested, the amount tied to that price and how long the instruction stays active. Review any displayed fees as well. A favourable target price has no practical value for this trade if you cannot accept the possibility of an unfilled order.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can Auto Handle the Pair and Your Gas Balance?
&lt;/h2&gt;

&lt;p&gt;Matcha Auto fits a supported same-chain pair when you want managed gas and slippage settings. For an eligible trade, it can handle execution without requiring you to hold the network’s native gas token for that swap. It also removes the manual slippage setting. That makes Auto useful when your wallet holds the token to sell but no native gas, or when you want to trade now using the mode’s defaults.&lt;/p&gt;

&lt;p&gt;In a Matcha swap, managed gas does not mean execution has no cost. Read Auto’s quoted output and displayed fees to see the result of its route, then compare them with another eligible quote. A wallet gas charge of zero is less useful than the net amount of tokens you would receive. Price impact can still rise when the trade is large relative to available liquidity, even though Auto handles the transaction settings.&lt;/p&gt;

&lt;p&gt;Auto’s availability is the boundary to the gas rule. If the token or network is unsupported for Auto, its option may be unavailable regardless of your balance. You would need an eligible pair or enough native gas to use Standard. Re-enter the trade details and obtain a fresh quote after changing either input; support for one pair does not establish support for another.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do You Need to Set Slippage Yourself?
&lt;/h2&gt;

&lt;p&gt;Choose Matcha Standard when you need to set slippage tolerance or use its available manual controls for a direct swap. Slippage tolerance is the maximum price deterioration you permit between quoting and execution. A tighter setting limits the amount you may lose to a changing price, but the trade may fail if the price moves beyond it. A wider setting gives the transaction more room to execute while allowing a worse result.&lt;/p&gt;

&lt;p&gt;Standard requires native gas on the source network to submit the swap. On Polygon, for example, holding enough of the token you intend to sell does not by itself pay that network’s gas. Read the gas estimate alongside the output, particularly for a small trade where gas may materially change what you keep. If you have gas and do not need manual slippage, both Standard and Auto may be eligible; their current quotes decide which terms you prefer.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Should the Quote Show Before You Confirm?
&lt;/h2&gt;

&lt;p&gt;For eligible immediate swaps, compare Auto and Standard using the same token amount and network. Read the network fee, price impact and minimum received together. The fee shows the quoted execution cost; price impact indicates how the trade affects the quoted price; minimum received is the lowest output permitted by the quote’s slippage terms. A strong expected output can still come with a minimum you would not accept.&lt;/p&gt;

&lt;p&gt;A Matcha swap quote can change as liquidity and network conditions move. Suppose Standard shows better net proceeds, but your wallet has no native gas. It is not executable from that balance. If you add enough native gas, Standard becomes an option and its fee and minimum received deserve a fresh comparison with Auto. The network and need to trade now have not changed; the gas constraint has.&lt;/p&gt;

&lt;p&gt;For a limit order, confirm the target price, exchange amount and expiry rather than expecting an immediate minimum-received result. For Cross-chain, weigh the destination amount after displayed costs and the estimated time, then track both source and destination confirmations. Use four inputs to select the mode—source and destination networks, whether execution can wait, native gas balance and need for manual slippage—then confirm only if that mode’s actual preview meets your terms.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Token Decimals Change Route Comparisons</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Tue, 03 Nov 2026 17:22:09 +0000</pubDate>
      <link>https://dev.to/jake-eth/why-token-decimals-change-route-comparisons-2012</link>
      <guid>https://dev.to/jake-eth/why-token-decimals-change-route-comparisons-2012</guid>
      <description>&lt;p&gt;Token decimals change route comparisons because a token’s smallest units can represent very different fractions. To compare routes fairly, read each quote as a human amount first, then account for fees and gas.&lt;/p&gt;

&lt;p&gt;A token’s decimal count tells you how many tiny units make one whole token. For example, with six decimals, 1 USDC is 1,000,000 smallest units; with eighteen decimals, 1 token is 1,000,000,000,000,000,000 units. These smallest units are often called &lt;em&gt;base units&lt;/em&gt;. The Ethereum Improvement Proposals’ ERC-20 specification says the decimals field is optional, so check the token contract and network rather than guessing from a familiar symbol. &lt;a href="https://telegra.ph/ParaSwap-Get-the-Best-Net-Result-From-a-Token-Swap-10-31" rel="noopener noreferrer"&gt;How ParaSwap finds the best net result&lt;/a&gt; is useful context when judging what a route gives you after costs. Decimal handling is one part of that comparison.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do decimals change a route quote?
&lt;/h2&gt;

&lt;p&gt;A route quote starts with an amount of one token and estimates how much of another token you would receive. A decentralized exchange aggregator checks possible paths through pools, where traders swap tokens, and reports an output for each path. The math uses whole-number base units; the interface turns them into readable amounts.&lt;/p&gt;

&lt;p&gt;Say you swap 1.25 USDC, which has six decimals. The input is 1,250,000 base units. If the output token has eighteen decimals and a route estimates 2.47 tokens, its raw output is 2,470,000,000,000,000,000 units. Those large integers do not mean the route is unusually generous; they reflect the output token’s smaller unit size.&lt;/p&gt;

&lt;p&gt;Compare the readable output in the same token, not the raw integers. For example, a route offering 2.471 tokens beats one offering 2.470 tokens before costs. A display that applies the wrong decimal count can make that ranking look wildly wrong, even though the underlying amounts may be valid.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can rounding hide?
&lt;/h2&gt;

&lt;p&gt;Rounding can erase small amounts, especially when a token has few decimals. A token with zero decimals cannot represent a fraction at all, while one with six decimals can represent steps as small as 0.000001. If an interface rounds both route outputs to two decimal places, two different quotes may look identical.&lt;/p&gt;

&lt;p&gt;For an exact-input swap, you set the amount to spend and receive an estimate of the output. A &lt;em&gt;minimum received&lt;/em&gt; amount is the least output you accept after the quote changes before the trade lands. For example, if a route estimates 2.471 tokens, a 1% tolerance gives a minimum of about 2.446 tokens. The exact integer depends on the token’s decimals and how the app rounds down.&lt;/p&gt;

&lt;p&gt;Rounding is only one cost. A route may split a trade across pools or use several swaps, which can add network fees. Compare the final value after those fees, and make sure both routes use the same input, output token, network, and tolerance. When fees are paid in a different token, include their value in your comparison.&lt;/p&gt;

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

&lt;p&gt;First confirm the token addresses and decimal counts on the correct network; a name or ticker alone may refer to different tokens. Then convert each quoted output into a readable amount, check its minimum received value, and compare the estimated network cost. This reveals whether a tiny quote advantage survives fees and rounding.&lt;/p&gt;

&lt;p&gt;ParaSwap is an aggregator, so the same checks help you judge whether its route suits your trade. I would choose the route with the best estimated value after costs, provided its minimum output is acceptable and the token details match.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>No Direct Route: How to Bridge a Token Safely</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Fri, 23 Oct 2026 14:38:06 +0000</pubDate>
      <link>https://dev.to/jake-eth/no-direct-route-how-to-bridge-a-token-safely-58i2</link>
      <guid>https://dev.to/jake-eth/no-direct-route-how-to-bridge-a-token-safely-58i2</guid>
      <description>&lt;p&gt;When your chosen token has no direct route, use a bridge only if it supports your exact source chain, token, and destination. A missing route can mean the token is unsupported there, even when both chains appear in a bridge’s network list.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you tell if a bridge route fits?
&lt;/h2&gt;

&lt;p&gt;Check the full route in the transfer screen: source network, token, destination network, and the token you will receive. A route between two chains does not guarantee that every token can travel between them.&lt;/p&gt;

&lt;p&gt;For example, if a token route from Chain A to Chain B is offered, check the destination token’s name and address before sending. If it is a wrapped token, it represents an asset held or issued elsewhere; it may not be interchangeable with the destination chain’s native version.&lt;/p&gt;

&lt;p&gt;When comparing routes, I would choose a clearly named destination asset over a shorter path with an unclear token. Use &lt;a href="https://chainpulse-abh.pages.dev/wormhole-bridge-transfers-check-what-lands-before-you-send/" rel="noopener noreferrer"&gt;wormhole bridge transfers&lt;/a&gt; as a concrete example: check the offered token and route details before approving, rather than assuming the same ticker means the same asset.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens after you start the transfer?
&lt;/h2&gt;

&lt;p&gt;A bridge transfer starts with a transaction on the source chain. The bridge’s contract locks or burns the tokens and records a message for the destination chain.&lt;/p&gt;

&lt;p&gt;In Wormhole’s Token Bridge, Guardians verify and sign that message as a VAA, or verifiable action approval. The destination contract checks that proof, then releases the original tokens or creates a wrapped version for you.&lt;/p&gt;

&lt;p&gt;Some routes ask you to submit the proof in a second transaction. Others use a relayer, a service that submits it for you. Wormhole’s Token Bridge specification describes this source-message-proof-destination flow; the Ethereum ERC-20 standard defines the common token format used by many supported assets.&lt;/p&gt;

&lt;p&gt;This creates a useful contrast: if a route is fully relayed, you may confirm the source transaction and wait; if it is manual, you may need to claim the tokens yourself. Either way, the destination wallet needs the correct network selected, and a manual claim may require that chain’s gas token to pay its transaction fee.&lt;/p&gt;

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

&lt;p&gt;Compare the amount you send with the amount expected to arrive, and read the quote for network gas, bridge fees, and any relayer charge. These costs vary by chain, route, and network demand; the destination amount can also be lower after fees.&lt;/p&gt;

&lt;p&gt;Then check the recipient address, destination network, and token identity. A correct address on the wrong chain can leave you unable to use the funds, while a token with the right ticker but a different contract address may not be the asset you intended.&lt;/p&gt;

&lt;p&gt;If the direct route is absent, check whether another supported token or route reaches the destination, but only use an option whose final asset you understand. Avoid improvising a chain-by-chain detour unless each leg is supported and you can cover its fees.&lt;/p&gt;

&lt;p&gt;After sending, keep the transaction record and follow its status until the destination balance appears; a source confirmation alone does not prove delivery. Before a large transfer, try a small amount first, and keep enough destination gas for any manual claim.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to Protect a Treasury Swap From Sandwich Attacks</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Thu, 22 Oct 2026 21:42:53 +0000</pubDate>
      <link>https://dev.to/jake-eth/how-to-protect-a-treasury-swap-from-sandwich-attacks-2hc9</link>
      <guid>https://dev.to/jake-eth/how-to-protect-a-treasury-swap-from-sandwich-attacks-2hc9</guid>
      <description>&lt;p&gt;Protect a treasury swap from sandwich attacks by setting a firm price limit and routing the trade through an order flow that does not expose it as a predictable pending swap. A sandwich bot tries to profit by buying before your trade pushes a token’s price up, then selling after your trade executes. The result can be a worse price for the treasury.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set the trade’s limits before you submit it
&lt;/h2&gt;

&lt;p&gt;Start by writing down the trade the treasury actually needs: which wallet will trade, which token it will sell, how much, which token it will receive, and the minimum acceptable amount out. A swap’s “price impact” is the price change caused by the trade itself; a large order against a shallow liquidity pool can move the price even without an attacker.&lt;/p&gt;

&lt;p&gt;For a treasury swapping, say, 50,000 USDC into another token, compare quotes for the full amount and smaller portions. Splitting may reduce price impact, but it can add execution time and expose the treasury to price changes between trades. When you submit through cowswap, the signed order enters a batch auction for solvers to compete over; the &lt;a href="https://dune.com/cryptogurus/cowswap-order-types-explained-for-integrators" rel="noopener noreferrer"&gt;cowswap interface&lt;/a&gt; is useful here because the trade is handled as an order rather than sent as a public swap transaction waiting in the mempool.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the wallet and network.&lt;/strong&gt; Use the treasury’s approved wallet on the intended network, and check the token contract addresses against a trusted source. A correct ticker can still refer to a different token.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose the exact sell amount.&lt;/strong&gt; Check the available balance and any policy limit for the wallet. Leave enough of the network’s native token for any required wallet actions, such as approving token spending.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set a minimum receive amount.&lt;/strong&gt; Use the quote to decide the least the treasury can accept after fees and price movement. For example, if a quote offers 49,000 tokens, a 1% tolerance would set a floor near 48,510; that figure is illustrative, and the right tolerance depends on volatility and treasury policy.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Submit an order that can fail safely
&lt;/h2&gt;

&lt;p&gt;A limit price is the worst exchange rate your order permits. If the market moves past that price, the order should remain unfilled or expire instead of completing at a price the treasury rejected. Tight limits can protect value but may delay or prevent execution, so avoid loosening them just to force a fill.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Review the order details before signing.&lt;/strong&gt; Confirm the sell token, buy token, amount, minimum receive, expiration, and any displayed fee. A signature authorizes the order conditions; it is not the same as handing over unrestricted control of the wallet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Approve token spending only when asked.&lt;/strong&gt; Some tokens need an on-chain approval before the order can be filled. Check the spender and amount in the wallet prompt, and avoid granting unlimited approval if a smaller allowance is available and fits the treasury’s operating policy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign and track the order.&lt;/strong&gt; Signing submits the trade intent for matching; it does not mean the swap has already settled. In a batch auction, solvers look for matching orders—sometimes a “Coincidence of Wants,” where traders want each other’s tokens—or route the batch to available liquidity. If no valid execution meets your limit, the order may not fill.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Verify settlement before recording the trade
&lt;/h2&gt;

&lt;p&gt;Once the order fills, check the wallet’s token balances and the transaction or order status before marking the treasury trade complete. Compare the actual amount received with the minimum in the signed order, and record the transaction hash, amounts, network, and time in the treasury’s normal records.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Handle an unfilled or expired order deliberately.&lt;/strong&gt; Check its status before resubmitting; an old order may still be open. Cancel it if the interface offers cancellation, then get a fresh quote and reassess the minimum receive amount.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reconcile approvals and balances.&lt;/strong&gt; Confirm the tokens spent and received, and review any remaining allowance under the treasury’s policy. Keep the order record with the wallet’s transaction evidence for later review.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Batch auctions reduce the opportunity for a bot to target one visible pending swap, but no trading route guarantees a fill or removes every risk, including token and liquidity risks. For a large treasury trade, my practical tip is to test the wallet process with a small amount first, then use cowswap for the approved order with its price floor set before anyone signs.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>crypto</category>
      <category>security</category>
      <category>web3</category>
    </item>
    <item>
      <title>How Long Does ZeroFi Take to Bridge Monero Into zXMR?</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Thu, 22 Oct 2026 16:03:20 +0000</pubDate>
      <link>https://dev.to/jake-eth/how-long-does-zerofi-take-to-bridge-monero-into-zxmr-3ofh</link>
      <guid>https://dev.to/jake-eth/how-long-does-zerofi-take-to-bridge-monero-into-zxmr-3ofh</guid>
      <description>&lt;p&gt;ZeroFi is a cross-chain bridge that wraps Monero as zXMR; its current route requires 10 Monero confirmations, roughly 20 minutes after inclusion, plus bridge processing and mint time. As of 20 October 2026, that route ends on Ethereum Sepolia, a testnet, so it cannot put XMR into a live DeFi position.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Output Is a Wrapped Asset on a Specific Network
&lt;/h2&gt;

&lt;p&gt;The bridge gives you zXMR, an ERC-20 token representing XMR held for redemption. You can send that token to an EVM wallet and use it in an application that accepts the &lt;em&gt;exact&lt;/em&gt; token contract on the &lt;em&gt;same&lt;/em&gt; network. An app accepting zXMR on one network will not automatically accept zXMR on another.&lt;/p&gt;

&lt;p&gt;That distinction matters more than the token’s name. Native XMR remains on Monero, while the wrapped token moves on an EVM chain and follows that chain’s public transaction rules. Wrapping XMR does not carry Monero’s transaction privacy into the receiving app.&lt;/p&gt;

&lt;p&gt;The ZeroFi Monero bridge is the route visible in the public interface now. The protocol’s broader aim includes assets such as Bitcoin, represented as zBTC, and other EVM destinations; check the available route before treating either as ready to use. A token mentioned in a project description is not necessarily one you can deposit, spend, and redeem today.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Deposit Triggers Custody, Verification, and Minting
&lt;/h2&gt;

&lt;p&gt;A deposit starts with native coins sent from their own network to a bridge deposit address. Validator nodes observe the payment and wait for the required confirmations before the bridge credits the EVM address you supplied. The underlying coins stay in bridge custody while the corresponding wrapped tokens circulate.&lt;/p&gt;

&lt;p&gt;The ZeroFi crypto bridge describes that custody as shared among bonded nodes using threshold control, rather than a single holder of the funds. After the deposit is accepted, the bridge mints zXMR to the chosen EVM address. “Minted” is the key checkpoint: seeing your Monero transaction reach the deposit address does not mean the EVM token has arrived.&lt;/p&gt;

&lt;p&gt;The trip back runs in reverse. You request a withdrawal to a Monero address, the wrapped tokens are burned, and the custody nodes authorize a native XMR payout. Burning prevents those tokens from continuing to circulate after the backing coins leave custody; you still need to wait for the payout transaction to appear and confirm on Monero.&lt;/p&gt;

&lt;p&gt;For example, depositing 1 XMR should create a claim tied to 1 XMR before any quoted charges, and redeeming that claim should release the corresponding native amount. That one-to-one design depends on the bridge holding enough reserves and processing withdrawals. Before a large transfer, compare wrapped supply with reported custody reserves and check that recent payouts have completed.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Current XMR Route Has a Confirmation Wait
&lt;/h2&gt;

&lt;p&gt;The public XMR route shows a 0.01 XMR minimum and credits deposits after 10 Monero confirmations. Monero targets a block about every two minutes, making that stage roughly 20 minutes after your payment enters a block. Inclusion can take longer, and the bridge’s later processing and EVM mint add time, so 20 minutes is a starting estimate rather than a delivery promise.&lt;/p&gt;

&lt;p&gt;ZeroFi currently labels the destination Ethereum Sepolia. Sepolia is a testnet: its tokens are useful for trying an integration, but they are not tokens on Ethereum mainnet. The subtle cost is that a deposit can spend real mainnet XMR even though the zXMR you receive sits on a test network; confirm the route and withdrawal path before sending anything.&lt;/p&gt;

&lt;p&gt;That creates two very different cases for someone comparing bridges. I would choose the &lt;a href="https://zerofi.pro/" rel="noopener noreferrer"&gt;ZeroFi protocol&lt;/a&gt; for a Sepolia trial when the receiving app supports its zXMR contract; for a live DeFi position, I would choose a route already operating on the required production network. The ZeroFi Monero bridge only solves the second case when that production route is actually available.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Cost Includes the Deposit and the Exit
&lt;/h2&gt;

&lt;p&gt;A full round trip can involve a Monero network fee, a bridge charge, EVM gas for using or burning zXMR, and any withdrawal charge shown at redemption. The 0.01 XMR figure is a minimum deposit, not a fee. There is no useful fixed total without an amount, a live bridge quote, and the intended EVM network.&lt;/p&gt;

&lt;p&gt;Read the quote as an amount received, not merely a percentage. Say a 0.10 XMR deposit shows an illustrative 0.0002 XMR bridge charge: you would expect 0.0998 zXMR before later app and withdrawal costs, subject to the interface’s actual calculation. If the fee field has not populated, wait for a valid quote instead of assuming the charge is zero.&lt;/p&gt;

&lt;p&gt;On Sepolia, an EVM wallet also needs Sepolia ETH to submit transactions such as an approval or burn. Testnet ETH is normally obtained from a faucet, but Monero sent from its mainnet is real. If you plan to return to XMR, check the withdrawal minimum and quoted payout before depositing; a small balance is of little use if the exit costs consume it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Right Route Depends on the Destination and the Exit
&lt;/h2&gt;

&lt;p&gt;The right route is the one that reaches the network and token contract your intended app accepts, with a redemption path you are willing to rely on. Start by checking the bridge’s source asset, destination network, minimum, displayed fee, and receiving address. Then check the app’s supported contract address; matching a ticker alone is insufficient.&lt;/p&gt;

&lt;p&gt;For a trial, connect an EVM wallet on Sepolia, obtain enough Sepolia ETH for any transaction you must submit, and enter an address you control. Generate the deposit instructions, send a small amount above the stated minimum from your Monero wallet, and keep the payment ID or transaction record. Track both the Monero confirmations and the eventual zXMR mint before trying to spend the token.&lt;/p&gt;

&lt;p&gt;For a larger amount, test the exit as well as the deposit. Burn a small zXMR balance to a Monero address you control, then verify the native payout arrives. That exercise tells you more about usable redemption than a successful mint alone, and it exposes any minimum or fee that matters when you want your coins back.&lt;/p&gt;

&lt;p&gt;If you need Bitcoin or a production EVM chain, first confirm that its deposit and withdrawal routes are live and that the receiving app accepts the issued token. Choose this bridge when its active route reaches your exact destination and you can complete the return trip at an acceptable cost.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Minimum Trade Sizes and DEX Routes in 2026</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Thu, 22 Oct 2026 09:04:25 +0000</pubDate>
      <link>https://dev.to/jake-eth/minimum-trade-sizes-and-dex-routes-in-2026-kc2</link>
      <guid>https://dev.to/jake-eth/minimum-trade-sizes-and-dex-routes-in-2026-kc2</guid>
      <description>&lt;p&gt;If your swap is too small to use every attractive pool, the router may drop tiny paths and send the trade through fewer venues. A “minimum trade size” can mean a venue’s own fill limit, but for an AMM pool it often means the smallest allocation that is useful after fees and execution costs.&lt;/p&gt;

&lt;p&gt;For a swap you’re building into an app, inspect the route for the exact trade amount before deciding how to present it. With &lt;a href="https://graph.org/3-ParaSwap-route-types-for-thin-liquidity-swaps-10-21" rel="noopener noreferrer"&gt;ParaSwap&lt;/a&gt;, for example, compare the quoted output and route at the amount your app will actually send; a route that looks good for a larger test amount may not be selected for a smaller user trade.&lt;/p&gt;

&lt;p&gt;Three things decide whether a small path survives:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Whether the venue can accept that amount.&lt;/li&gt;
&lt;li&gt;Whether its extra output outweighs the added gas.&lt;/li&gt;
&lt;li&gt;Whether rounding or token precision leaves a usable fill.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A tiny allocation can make a path unusable
&lt;/h2&gt;

&lt;p&gt;A router treats each possible swap path as a sequence of fills, then estimates what each allocation returns. It may split one trade across pools when the combined output improves, but each extra venue or hop adds work to the transaction. If a small branch saves less than that extra gas costs, the router can leave it out.&lt;/p&gt;

&lt;p&gt;Consider an illustrative 100-token swap. Before the minimum-size effect, the best estimate might allocate 98 tokens to one pool and 2 to a second. If the second pool’s minimum fill is 3 tokens—or that 2-token branch adds more gas than value—the router cannot use the split as quoted. Afterward, it may route all 100 through the first pool, or choose a different path through an intermediate token.&lt;/p&gt;

&lt;h2&gt;
  
  
  The useful threshold depends on the venue and the trade
&lt;/h2&gt;

&lt;p&gt;There is no universal minimum across decentralized exchanges. An AMM pool may accept a very small amount at the contract level, while an order book or quoted liquidity source can impose a minimum order. Even without a formal limit, token decimals and integer rounding can make a tiny allocation round down, and a shallow pool can give it poor output.&lt;/p&gt;

&lt;p&gt;The deciding test is net execution value: expected output after pool fees and price impact, weighed against gas and any venue-specific limits. The threshold changes with the chain, gas price, token pair, pool depth, and route length. A global slippage setting controls the transaction’s minimum acceptable output; it does not guarantee that every proposed branch meets a useful per-venue size.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quote the app’s real amount before choosing a route
&lt;/h2&gt;

&lt;p&gt;For a live app, request a fresh quote for the exact input amount, chain, and token pair, then inspect its route and estimated gas. If you use the ParaSwap API, treat its returned route as a quote for those inputs, not a promise that the same split will remain optimal when the user changes the amount or submits later.&lt;/p&gt;

&lt;p&gt;I’d show the user the best executable quote for their actual amount and avoid forcing a split just to use more venues. If a small trade gets a simpler route, that can be the better result once gas and minimum fills are counted.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>4 Steps to Set Slippage for Base Token Swaps</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Wed, 21 Oct 2026 22:37:26 +0000</pubDate>
      <link>https://dev.to/jake-eth/4-steps-to-set-slippage-for-base-token-swaps-217n</link>
      <guid>https://dev.to/jake-eth/4-steps-to-set-slippage-for-base-token-swaps-217n</guid>
      <description>&lt;p&gt;Slippage tolerance is the largest difference you will accept between a swap’s quoted output and the amount you receive when it executes. The key condition is whether the market can move enough before your transaction is included to cross that limit.&lt;/p&gt;

&lt;p&gt;Think of the quote as a price ticket with an expiry condition: the trade goes through only if the final output meets its minimum. When comparing routes on &lt;a href="https://web3dailyreport.github.io/baseswap-when-to-swap-tokens-and-when-to-add-liquidity/" rel="noopener noreferrer"&gt;BaseSwap&lt;/a&gt;, check that minimum alongside the estimated output and pool fee; a better-looking quote can still be less useful if it depends on a very thin pool. The same checks apply when comparing other decentralized exchanges.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does slippage tolerance control?
&lt;/h2&gt;

&lt;p&gt;It sets a floor for the tokens you will receive, not a cap on how much the pool price can move. If a quote offers 500 tokens and tolerance is 0.5%, the minimum output is 497.5; if the swap would return less, the transaction reverts instead of completing below your limit.&lt;/p&gt;

&lt;p&gt;Price impact and slippage are related but different. Price impact is the effect your own trade has on the pool’s price, while slippage is the difference between the quote and execution output. A large trade in a shallow pool may show substantial price impact before you submit it; changing tolerance does not remove that cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  How should you choose a setting before swapping?
&lt;/h2&gt;

&lt;p&gt;Use these four steps to compare routes and set a limit that fits the trade:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check the token and network.&lt;/strong&gt; Confirm the token contract and that your wallet is connected to Base. Keep enough ETH on Base for gas; a swap can fail even when you have enough of the token you intend to trade.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare the quote and pool depth.&lt;/strong&gt; Enter the amount, then review estimated output, price impact, and the pool fee. A route through a deeper pool may provide a steadier execution, while a route through a small pool can move sharply when your order lands.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set tolerance to match the trade.&lt;/strong&gt; Start with the interface’s suggested setting, if shown, and inspect the minimum received. For a stable, liquid pair, a tighter limit may be practical; a volatile or thinly traded token may need more room, but that also lets the trade complete at a worse price.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the final transaction.&lt;/strong&gt; Before confirming, check the minimum output, network, and gas estimate in the swap screen and wallet. If the minimum is unacceptable, reduce the trade size or wait for a better quote instead of raising tolerance blindly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, suppose a swap quotes 500 tokens and the screen shows a 2% price impact. That impact is already part of the quote; a 0.5% tolerance would set a minimum near 497.5 tokens. Raising it to 3% would permit execution down to 485, so first ask whether the trade’s price impact and pool depth justify accepting that extra range.&lt;/p&gt;

&lt;p&gt;On BaseSwap, as on any DEX, raising tolerance can help a transaction survive price movement or a token’s transfer fee, but it can also expose you to a worse fill. A failed swap may still consume gas, so repeated retries with progressively higher limits can cost money without improving the underlying route.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do traders ask after setting slippage?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does low slippage make a swap cheaper?
&lt;/h3&gt;

&lt;p&gt;No. A tighter limit reduces the worst execution price you will accept, but it does not lower the pool fee, network gas, or price impact already reflected in the quote. If the market moves beyond your limit, the swap reverts and you may still pay gas. Compare the quote and minimum output before deciding whether to retry.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why can a swap fail even when the quote looked good?
&lt;/h3&gt;

&lt;p&gt;The pool price may have changed before execution, the transaction may have waited in the network, or the token may charge a transfer fee. If the resulting output falls below your minimum, the swap reverts. Refresh the quote, check token details, and only adjust tolerance if the new minimum still makes sense for the amount you plan to trade.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should you split a large swap?
&lt;/h3&gt;

&lt;p&gt;Compare the quoted output and price impact for the full amount against smaller portions. Splitting can reduce the immediate effect on a shallow pool, but later portions may face a changed price, and each transaction can add gas cost. Use the total expected output after fees to decide; smaller trades do not guarantee a better overall result.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Verify the token and Base network.&lt;/li&gt;
&lt;li&gt;Compare quote, pool depth, fee, and price impact.&lt;/li&gt;
&lt;li&gt;Choose tolerance by reviewing the minimum output.&lt;/li&gt;
&lt;li&gt;Confirm gas and transaction details before signing.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>What Happens When a Cross-Chain Transfer Gets Stuck?</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:02:22 +0000</pubDate>
      <link>https://dev.to/jake-eth/what-happens-when-a-cross-chain-transfer-gets-stuck-14pk</link>
      <guid>https://dev.to/jake-eth/what-happens-when-a-cross-chain-transfer-gets-stuck-14pk</guid>
      <description>&lt;p&gt;When a cross-chain transfer gets stuck, the source transaction may still be waiting for confirmation, or it may have confirmed while the destination step is still processing. If your wallet shows pending or failed, start with the transaction hash: it tells you whether the transfer actually left the source chain. Knowing &lt;a href="https://dune.com/polly_defi/first-time-mayan-bridge-how-to-choose-a-route" rel="noopener noreferrer"&gt;how to choose a Mayan bridge route&lt;/a&gt; helps explain why two transfers between the same chains can take different paths and have different completion steps.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, did the source transaction confirm?
&lt;/h2&gt;

&lt;p&gt;A transfer cannot proceed until its source-chain transaction is confirmed. Open the transaction hash in the source chain’s block explorer and check its status there; a wallet’s spinner or error message alone does not establish whether the chain accepted it.&lt;/p&gt;

&lt;p&gt;If it is pending, the transaction has not yet completed on the source chain. On Ethereum, for example, a transaction can wait because its gas fee is too low for current demand. Avoid submitting the transfer again while the first transaction is unresolved: if both are later accepted, you could send twice. If your wallet offers a “speed up” or “cancel” option, check what it will replace before confirming; replacement behavior depends on the chain and wallet.&lt;/p&gt;

&lt;p&gt;If the explorer marks it failed, look for the failure reason and check whether the tokens were spent. A failed onchain transaction usually does not execute the transfer, but it can still cost a network fee. Save the hash and error details before deciding whether to try again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does “confirmed” mean if the tokens have not arrived?
&lt;/h2&gt;

&lt;p&gt;A confirmed source transaction is only the first milestone; the route may still need to arrange delivery on the destination chain. The source explorer proves what happened on the sending chain, while the destination explorer can show whether a separate delivery transaction has appeared.&lt;/p&gt;

&lt;p&gt;For an intent-based route such as Mayan Swift, the transfer can involve a solver: a service that uses its own funds to deliver the requested asset on the destination chain. Wormhole’s Settlement documentation describes solvers competing to fulfill these transfers and says Swift typically completes in around 12 seconds. Treat that as a typical case, not a deadline. Network congestion, the selected route, or a solver issue can extend the wait.&lt;/p&gt;

&lt;p&gt;For MCTP, a route that uses Circle’s CCTP to move USDC, the source transfer must pass through the relevant chain finality and attestation steps before delivery. Wormhole’s documentation describes the attestation as evidence needed for destination redemption. That extra process can take longer than a fast solver route, so compare the transfer’s current stage with the route you actually selected before concluding it has failed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should you check while it is processing?
&lt;/h2&gt;

&lt;p&gt;Use the transaction hash and route status to identify the last completed step. Check that the destination address and token are the ones you intended, then look for a destination transaction or a route-specific refund status.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Source transaction pending:&lt;/strong&gt; wait for confirmation or use the wallet’s replacement option only after checking its effect.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source transaction failed:&lt;/strong&gt; read the explorer’s error and confirm whether the transfer executed before retrying.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source confirmed, destination absent:&lt;/strong&gt; check the bridge’s status page or route tracker for progress or a refund.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Destination transaction confirmed:&lt;/strong&gt; verify the recipient address and token contract; the wallet may not display a token automatically.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For Swift, Wormhole’s Settlement FAQ says funds are refunded on the source chain if no solver starts the auction before its deadline. A missing destination receipt is therefore not, by itself, proof that funds are lost. Look for the refund transaction too, and do not start another transfer until you know whether the first one delivered or returned funds.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is it time to seek help?
&lt;/h2&gt;

&lt;p&gt;Ask the bridge’s support team for help when the source transaction is confirmed but the route tracker shows no progress or refund after its stated window. Send the source hash, route, source and destination chains, and recipient address; never send a seed phrase or private key.&lt;/p&gt;

&lt;p&gt;If the destination transaction succeeded, the next step is to check the exact token address and destination account. If the source transaction never confirmed, resolve that transaction before retrying. The deciding condition is the onchain record: a confirmed source transfer needs route-status follow-up, while an unconfirmed or failed one needs source-side resolution first.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Does a Mantle Bridge Deliver Less Than You Send?</title>
      <dc:creator>Willson Lammy</dc:creator>
      <pubDate>Sat, 17 Oct 2026 02:32:25 +0000</pubDate>
      <link>https://dev.to/jake-eth/why-does-a-mantle-bridge-deliver-less-than-you-send-25kl</link>
      <guid>https://dev.to/jake-eth/why-does-a-mantle-bridge-deliver-less-than-you-send-25kl</guid>
      <description>&lt;p&gt;If you are used to a centralised exchange, your wallet can receive less after a Mantle bridge because the route may convert the asset and charge costs at different stages. The amount shown as “you receive” is not always the same as the total value leaving your wallet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four figures explain the difference
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Amount sent:&lt;/strong&gt; the token amount you choose to bridge or swap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Estimated output:&lt;/strong&gt; the destination amount predicted by the route.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network gas:&lt;/strong&gt; the cost of processing transactions on a blockchain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Minimum received:&lt;/strong&gt; the smallest destination amount allowed before a swap fails.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Amount sent&lt;/strong&gt; is the input to the route, not necessarily the amount that arrives. If you send one token and receive the same token, compare the source and destination token balances, and check whether the route lists a bridge charge.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Estimated output&lt;/strong&gt; reflects the route’s expected result. If you choose a different destination asset, the exchange rate affects the amount just as it would in a normal swap.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Network gas&lt;/strong&gt; pays for transactions, usually from a separate balance of the source network’s native token. An ERC-20 transfer may also require an approval transaction first, which can cost gas without moving the tokens themselves.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minimum received&lt;/strong&gt; is a protection used by many swap routes. If the market moves too far before execution, the swap may fail rather than deliver less than that threshold.&lt;/p&gt;

&lt;h2&gt;
  
  
  The transfer can contain more than one transaction
&lt;/h2&gt;

&lt;p&gt;A wallet transfer is not a centralised exchange ledger entry: it is a chain of public transactions and messages. The source transaction authorises or sends the asset, a bridge or liquidity route handles the cross-chain leg, and a destination transaction may deliver the asset or complete a swap.&lt;/p&gt;

&lt;p&gt;On an Ethereum-to-Mantle route, for example, a direct deposit may move a supported token into a bridge contract on Ethereum and release its corresponding representation on Mantle. A third-party route can work differently, using liquidity on the destination side and settling between providers later. The details depend on the route, so its quote should say what token arrives and what costs it includes.&lt;/p&gt;

&lt;p&gt;This distinction explains why “less received” does not always mean a fee was taken from the token amount. Source gas may reduce your wallet’s ETH balance separately; a bridge charge may be deducted from the transfer; and a swap may produce a different value because of its exchange rate, price impact, or stated fee.&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked quote separates output from total cost
&lt;/h2&gt;

&lt;p&gt;Suppose you route 1,000 USDT into ETH, and the quoted rate before route costs is 0.00032 ETH per USDT. That gives 0.32 ETH before any swap or bridge deductions. If the quote estimates 0.5% in combined route costs and price impact, the estimated output is about 0.3184 ETH.&lt;/p&gt;

&lt;p&gt;Now suppose the source transaction costs around $8 worth of gas. That gas is a separate wallet expense, not another 0.5% reduction from the 0.3184 ETH, unless the quote explicitly says gas is included or paid from the output. These are illustrative numbers; the actual exchange rate, gas estimate, route fee, and price impact vary with network conditions, liquidity, and the route chosen.&lt;/p&gt;

&lt;p&gt;For a like-for-like transfer, compare the same token on both networks and inspect any explicit bridge fee. For a bridge-and-swap, compare the destination output with a same-time reference rate, then account separately for source gas. This tells you whether the gap comes from conversion, fees, or the cost of executing the transactions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the quote and transaction record before retrying
&lt;/h2&gt;

&lt;p&gt;Before signing, confirm the source and destination networks, the token on each side, the estimated output, the minimum received, and whether gas is included. Keep enough native currency on the source network for the transfer and any required approval; also consider whether you will need native currency on the destination network to make a later transaction.&lt;/p&gt;

&lt;p&gt;After signing, use the source transaction record to confirm what left your wallet and whether the transaction succeeded. Then check the destination address and token balance. A confirmed source transaction can still be waiting for the cross-chain leg to complete; sending again before checking can create a second transfer.&lt;/p&gt;

&lt;p&gt;If you want to move and swap assets across chains in one flow, a &lt;a href="https://oraclewire.pages.dev/when-to-use-a-mantle-bridge-for-transfers-to-mantle/" rel="noopener noreferrer"&gt;Mantle bridge swap service&lt;/a&gt; can handle that cross-chain route for you. I would compare its quoted destination amount with the token and minimum you actually need, then check separately which network gas costs the quote includes. That gives you a useful basis for deciding whether to proceed from your wallet.&lt;/p&gt;

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