<?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: Mandie Brugman</title>
    <description>The latest articles on DEV Community by Mandie Brugman (@cryptoguuru).</description>
    <link>https://dev.to/cryptoguuru</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%2F4108156%2F792b4a18-e94a-4f4a-bc71-dbecf49ad495.png</url>
      <title>DEV Community: Mandie Brugman</title>
      <link>https://dev.to/cryptoguuru</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cryptoguuru"/>
    <language>en</language>
    <item>
      <title>What Is Proof of Liquidity on Berachain? From LP to BGT</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Mon, 16 Nov 2026 16:34:52 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/what-is-proof-of-liquidity-on-berachain-from-lp-to-bgt-3232</link>
      <guid>https://dev.to/cryptoguuru/what-is-proof-of-liquidity-on-berachain-from-lp-to-bgt-3232</guid>
      <description>&lt;p&gt;Proof of Liquidity on Berachain originally tied validator rewards to DeFi liquidity: validators directed BGT emissions to reward vaults, and users earned BGT by staking eligible positions. The &lt;a href="https://berachainbridge.app" rel="noopener noreferrer"&gt;Berachain bridge&lt;/a&gt; brought assets from other chains onto Berachain, where they could enter those positions. This design separated BERA, the gas and validator staking token, from BGT, a non-transferable governance and reward token; HONEY was Berachain’s stablecoin. Berachain’s current documentation now describes WBERA emissions instead, making this the original BGT model.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Did Proof of Liquidity Turn Liquidity Into Rewards?
&lt;/h2&gt;

&lt;p&gt;Proof of Liquidity routed block rewards through validators into approved reward vaults. A validator staked BERA to secure the chain. When it produced a block, it received BGT emissions and chose which eligible vaults would receive the distributable share. A vault divided incoming BGT among users staking its accepted receipt token. Each user’s share depended on their stake relative to the vault’s total and on how much BGT validators sent there.&lt;/p&gt;

&lt;p&gt;Take an illustrative USDC holder. They move USDC through the Berachain bridge, convert part of it into HONEY, and supply both assets to an eligible USDC/HONEY pool. The pool issues an LP token representing their share. They stake that token in the matching reward vault. Only then does their position participate in that vault’s BGT stream. The bridge moves capital; the pool creates liquidity; the vault connects that liquidity to emissions.&lt;/p&gt;

&lt;p&gt;The user can delegate earned BGT to a validator. More delegated BGT increased that validator’s boost and its BGT emissions when producing blocks. The validator could send more BGT toward the vault supporting the user’s pool. That is the loop: liquidity earns BGT, BGT delegation strengthens a validator’s reward capacity, and validator allocation attracts liquidity. A user could instead burn BGT 1:1 for BERA, giving up its governance and delegation role.&lt;/p&gt;

&lt;p&gt;Protocols had a reason to enter this loop. One seeking deeper USDC/HONEY liquidity could offer incentive tokens to validators that allocated BGT to its vault. Validators received those incentives for directing emissions and could share them with BGT delegators. A generous offer could attract capital quickly, but could also pull emissions toward the highest bidder rather than the pool with the most useful trading liquidity.&lt;/p&gt;

&lt;p&gt;In the BGT design, simply moving BERA onto Berachain earned no vault rewards. Ordinary users could not buy or bridge BGT: they had to stake an eligible asset in a reward vault to earn it. Holding an LP token outside its vault also missed that vault’s emissions. The useful question was which token a vault accepted and whether validators were sending emissions to it.&lt;/p&gt;

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

&lt;h3&gt;
  
  
  How Is BGT Different From BERA?
&lt;/h3&gt;

&lt;p&gt;BGT was non-transferable governance and reward power, earned by users through the original reward vaults and delegable to validators. BERA paid gas and backed validator staking; BGT could be burned 1:1 for BERA, but the reverse route was unavailable. In the current PoL system, BGT no longer controls allocation or pays vault stakers; WBERA emissions do.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Are Berachain Reward Vaults?
&lt;/h3&gt;

&lt;p&gt;Berachain reward vaults are contracts that accept a specified eligible token, such as an LP receipt token, and pay stakers their share of routed emissions. In the original BGT model, validators decided which approved vaults received BGT. Today the vault still links a staked position to network rewards, but the payout is WBERA. Before using one, identify its accepted token and current emission stream.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>shiba swap: How to complete and verify an Ethereum swap</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Fri, 06 Nov 2026 02:35:55 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/shiba-swap-how-to-complete-and-verify-an-ethereum-swap-1o5m</link>
      <guid>https://dev.to/cryptoguuru/shiba-swap-how-to-complete-and-verify-an-ethereum-swap-1o5m</guid>
      <description>&lt;p&gt;Connect your funded Ethereum wallet to shiba swap after verifying the interface and token contracts, then set the trade, approve spending if needed, and submit it. At &lt;a href="https://shibaswap.app" rel="noopener noreferrer"&gt;shiba swap&lt;/a&gt;, connection only selects your account. ShibaSwap has completed your trade only when the on-chain swap succeeds and the output token reaches that account.&lt;/p&gt;

&lt;h2&gt;
  
  
  The right account and token contracts make the quote meaningful
&lt;/h2&gt;

&lt;p&gt;Start with the wallet account that holds your input token, and select Ethereum before connecting it. Open the interface at an address you have independently verified, then connect a compatible wallet such as MetaMask. The connection lets the interface read your selected public account and show its balances. It does not move tokens or give permission to spend them. If your wallet has several accounts, compare the address shown in the interface with the one holding the tokens.&lt;/p&gt;

&lt;p&gt;On shiba swap, select the input and output tokens by their verified contract addresses, then enter the input amount. A familiar symbol or logo is not enough: different contracts can use the same name. Keep some ETH in the wallet alongside the token you are selling. Ethereum charges network fees in ETH, and an ERC-20 token approval, if required, and the swap are separate transactions that can each need a fee.&lt;/p&gt;

&lt;p&gt;Read the quoted output as an estimate for the trade you are about to submit. Price impact describes how much your trade moves the price against the available liquidity; it generally grows when the trade is large relative to that liquidity. Slippage tolerance sets how far the execution price may move before the swap fails. Review both, along with the wallet’s estimated network fee, before deciding whether the expected output is acceptable. A quote can change while you are reviewing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  An insufficient allowance requires a separate approval
&lt;/h2&gt;

&lt;p&gt;An ERC-20 approval gives a specified spender contract permission to use your input token, up to an allowance. ShibaSwap may prompt for this transaction before it offers the swap transaction. In the wallet prompt, compare the spender address with the verified contract you expect and read the allowance amount. Connecting your wallet granted neither this permission nor a completed trade.&lt;/p&gt;

&lt;p&gt;Consider two trades with the same wallet, input token, amount, and quote. In the first, that wallet has already approved the spender for at least the input amount. It can proceed to the swap without another approval. In the second, its allowance is below the input amount. That wallet must approve enough spending and wait for the approval to succeed on Ethereum before submitting the swap. The difference is the existing allowance, not the token balance or the quoted price.&lt;/p&gt;

&lt;p&gt;An approval for exactly this amount limits what the spender can draw under that permission, though a later trade may require another approval. A larger allowance can cover later trades but grants broader spending permission. Choose the amount deliberately. When the approval transaction succeeds, the wallet still holds the input tokens: the spender has permission to use them, but no exchange has taken place.&lt;/p&gt;

&lt;h2&gt;
  
  
  Submitting the swap starts execution, not completion
&lt;/h2&gt;

&lt;p&gt;Review the swap transaction in your wallet after the approval has succeeded, or immediately if no approval was needed. Confirm that it comes from the intended account on Ethereum and that the input amount matches your plan. Look again at the quoted output and the minimum output allowed by your slippage setting. If the quote has shifted enough to change your decision, revise the trade before signing. ShibaSwap can present the transaction, but only your wallet can submit it from your account.&lt;/p&gt;

&lt;p&gt;After submission, the wallet shows a transaction hash while Ethereum processes the swap. “Pending” means the network has received the transaction; it does not mean the exchange happened. Likewise, a successful approval hash proves only that spending permission changed. A swap can fail on-chain, for example when the execution price moves beyond the permitted slippage. A failed transaction can still consume ETH for gas even though it delivers no output token.&lt;/p&gt;

&lt;h2&gt;
  
  
  The receipt and output transfer establish the result
&lt;/h2&gt;

&lt;p&gt;Follow the swap transaction hash in an Ethereum block explorer and inspect its receipt once it is included in a block. A successful status establishes that the transaction executed. Then inspect its token transfers for the intended output token contract and your wallet address as recipient. Together, a successful swap receipt and the output-token transfer show that the exchange reached the intended account. An approval receipt or a pending swap cannot establish that result.&lt;/p&gt;

&lt;p&gt;Finally, compare the output token balance in your wallet with its balance before the trade. The amount received may differ from the earlier quote within the permitted slippage. If the explorer shows the transfer but the wallet does not display the token, add or view the verified output token contract in the wallet; a missing display entry does not undo an on-chain transfer. If the receipt failed, or its transfers do not show the intended output reaching your address, treat the swap as unfinished before trying again.&lt;/p&gt;

&lt;p&gt;For the next trade, keep the verified token contracts in your wallet’s token list and look at the existing allowance before starting. That saves another token search and makes it clear whether an approval prompt is expected.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Slippage Tolerance for Frequent DEX Traders</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Wed, 04 Nov 2026 22:59:08 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/slippage-tolerance-for-frequent-dex-traders-4e88</link>
      <guid>https://dev.to/cryptoguuru/slippage-tolerance-for-frequent-dex-traders-4e88</guid>
      <description>&lt;p&gt;Slippage tolerance is the maximum shortfall from a swap’s quoted output that you agree to accept before the transaction reverts. Set it to cover ordinary price movement while your transaction waits to be included, not to compensate for a poor route or a large price impact.&lt;/p&gt;

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

&lt;p&gt;A swap quote estimates how many output tokens the pools will return at the moment you request it. The router also receives a minimum output: the quote multiplied by one minus your tolerance. If the completed swap returns less than that minimum, the transaction reverts instead of delivering an amount below your limit.&lt;/p&gt;

&lt;p&gt;For example, a quote of 4.8 WETH with 0.5% tolerance sets a minimum of 4.776 WETH. You may receive more if the price improves before execution, but not less; if the output falls below 4.776 WETH, the swap fails. The key mechanism is that the router checks the final output against the minimum when it executes, after the route’s pools have been used.&lt;/p&gt;

&lt;p&gt;For routed trades, the state of any pool along the path can change before your transaction lands. When checking a quote, &lt;a href="https://telegra.ph/SpookySwap-How-Swaps-Move-Through-Multiple-Pools-11-02" rel="noopener noreferrer"&gt;how SpookySwap routes swaps through pools&lt;/a&gt; matters because activity in an intermediate pool can affect the final output too. A wider tolerance may let the trade complete after a move, but it does not make that move cheaper.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you choose a setting for a routed swap?
&lt;/h2&gt;

&lt;p&gt;Start with the quoted output and estimated price impact, then consider how much the market can move while your transaction is pending. Price impact is the route’s estimated effect on the pool prices from your trade itself; slippage tolerance is your limit on how much worse the realized output may be than the quote. Raising tolerance does not reduce price impact.&lt;/p&gt;

&lt;p&gt;Suppose SpookySwap quotes 1,000 USDC for 0.38 WETH and estimates 0.4% price impact. At 0.5% tolerance, the minimum is 0.3781 WETH. If ordinary movement during confirmation often exceeds that margin for this pair, a slightly higher setting may reduce failed swaps; if the pool is quiet and confirmations are quick, a lower setting can protect your output.&lt;/p&gt;

&lt;p&gt;Use the pair’s liquidity, route length, recent volatility and your chain’s confirmation time as your criteria. More hops mean more pools whose prices may change, but route length alone does not tell you the right tolerance: a deep, stable route can be safer than a short route through a thin pool. Check the quoted output and price impact each time rather than reusing a high setting simply because a previous swap reverted.&lt;/p&gt;

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

&lt;p&gt;First, confirm the output token and route, then compare the quote with the minimum output shown for your chosen tolerance. If the minimum is too low for the trade, refresh the quote or try a different route; accepting a much worse fill can cost more than the time saved by avoiding a retry. For a large order, splitting it may reduce price impact, though it can add transaction fees and extra steps.&lt;/p&gt;

&lt;p&gt;Second, check the transaction deadline if the interface exposes it. A deadline limits how long the swap can execute; after it expires, the transaction should fail rather than trade against a stale quote. A longer deadline can help when confirmation is slow, but it also leaves more time for pool prices to move before the minimum-output check.&lt;/p&gt;

&lt;p&gt;If a trade reverts, inspect the reason before changing settings. A minimum-output failure may justify refreshing the quote or nudging tolerance upward; an approval issue, insufficient gas, or an expired deadline needs a different fix. In my place, I’d keep tolerance near the smallest margin that covers normal confirmation-time movement and re-quote when the route or market changes.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How do I turn NFT sale proceeds into gas on another chain?</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Fri, 23 Oct 2026 17:41:45 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/how-do-i-turn-nft-sale-proceeds-into-gas-on-another-chain-j6m</link>
      <guid>https://dev.to/cryptoguuru/how-do-i-turn-nft-sale-proceeds-into-gas-on-another-chain-j6m</guid>
      <description>&lt;p&gt;You can swap NFT sale proceeds into the native coin used for gas on another chain. For example, if a sale pays USDC to your Ethereum wallet and you need SOL for transactions on Solana, swap USDC for SOL and send it to your Solana address. Check the route, fees and destination address before sending.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does the swap change?
&lt;/h2&gt;

&lt;p&gt;It turns sale proceeds into the coin your destination wallet needs to pay transaction fees. “Gas” means the fee for using a blockchain; on Solana, that fee is paid in SOL.&lt;/p&gt;

&lt;p&gt;Say you sell an NFT on Ethereum and receive USDC. USDC is a token, so it cannot pay Solana transaction fees. Chainflip lets you send supported Ethereum proceeds and receive native SOL on Solana, giving you the coin needed to make those transactions.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you move the proceeds?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Check which asset the sale paid and where it arrived. In your wallet, confirm the network as well as the token: USDC on Ethereum is different from USDC on Solana.&lt;/li&gt;
&lt;li&gt;Make sure you have enough of Ethereum’s native coin, ETH, to send the proceeds. The sending wallet pays Ethereum’s transaction fee separately from the swap.&lt;/li&gt;
&lt;li&gt;Choose Ethereum USDC as the source and Solana SOL as the destination in the &lt;a href="https://cryptonews-week.com/chainflip-for-treasury-check-the-route-before-you-swap/" rel="noopener noreferrer"&gt;Chainflip&lt;/a&gt; swap app. Enter your Solana wallet address, then compare the displayed output and estimated fees with the amount of SOL you want to keep.&lt;/li&gt;
&lt;li&gt;Review the quote before continuing. The protocol’s documented liquidity fee is typically 0.10%–0.15% per pool, plus a 0.10% network fee with a $0.50 minimum; Ethereum sending gas and the destination transfer fee vary. The shown output should account for those swap costs.&lt;/li&gt;
&lt;li&gt;Follow the app’s instructions to open a deposit channel, which gives you a one-time address for this swap. Send the selected USDC from Ethereum to that address promptly; channels last 24 hours, and a fresh swap needs a fresh channel.&lt;/li&gt;
&lt;li&gt;Wait for the swap and check your Solana wallet for SOL. Keep some available for a later transaction, since using nearly all of it may leave too little to pay that transaction’s fee.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What else do NFT sellers ask?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I swap any NFT sale token?
&lt;/h3&gt;

&lt;p&gt;No. The proceeds must be an asset supported on the source chain, and the desired gas coin must be supported on the destination chain. Check the exact network and asset in the swap app. If the marketplace paid an unsupported token, you may first need to exchange it for a supported asset on its current chain.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if the swap does not complete?
&lt;/h3&gt;

&lt;p&gt;Swaps can fail if the chosen route, price limits or timing do not allow execution. When you set up the swap, check the refund address and any minimum-output or price-protection settings offered. A refund may take time and can still incur network fees, so avoid sending more than you can afford to have temporarily tied up.&lt;/p&gt;

&lt;h3&gt;
  
  
  What would you do first?
&lt;/h3&gt;

&lt;p&gt;I’d check the sale token and network, then confirm the destination wallet address before opening the swap. I’d compare the displayed SOL output with my planned transaction needs and leave a small reserve for fees. For a large sale, I’d consider a smaller first swap to check the route and address.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What Does It Cost to Keep Concentrated Liquidity Active?</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Fri, 23 Oct 2026 00:51:20 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/what-does-it-cost-to-keep-concentrated-liquidity-active-31n7</link>
      <guid>https://dev.to/cryptoguuru/what-does-it-cost-to-keep-concentrated-liquidity-active-31n7</guid>
      <description>&lt;p&gt;Each range reset usually takes two on-chain actions: remove the old position, then add a new one. You may also pay for a swap to rebalance your tokens, so the cost depends on your network, pool fee, and chosen range.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens when the price leaves your range?
&lt;/h2&gt;

&lt;p&gt;Your liquidity earns swap fees only while the pool price is inside your chosen range. If the price moves past either edge, your position becomes inactive until the price returns or you set a new range.&lt;/p&gt;

&lt;p&gt;As the price moves through your range, the pool trades one asset for the other. Above the upper edge, your position holds only the asset being quoted, such as USDC in an ETH/USDC pool priced in USDC per ETH. Below the lower edge, it holds only ETH.&lt;/p&gt;

&lt;p&gt;Your position is not automatically sold or closed when it goes out of range. Fees earned before that point remain part of your position, but you must collect them on-chain if you want them in your wallet.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is a reset worth the cost?
&lt;/h2&gt;

&lt;p&gt;Reset when the chance of earning future fees in a new range seems worth the transaction costs and price risk. Being out of range alone is not a reason to rush: the price might return, and every reset can add gas costs or swap fees.&lt;/p&gt;

&lt;p&gt;Compare the network’s quoted gas cost with the fees you might earn before your next check. Also consider whether a narrower range would need frequent attention. A wider range can stay active longer, but spreads your capital across more prices.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much could a reset cost?
&lt;/h2&gt;

&lt;p&gt;Try this calculation with your own numbers. Say your ETH/USDC range is $1,800 to $2,200, and ETH rises to $2,300. Your position is now out of range and holds USDC. You could wait for the price to return, or reset around the new price.&lt;/p&gt;

&lt;p&gt;For example, a new range of $2,070 to $2,530 would put $2,300 near its middle. You would first remove the old position, then swap some USDC for ETH if needed, and add both tokens to the new range. The &lt;a href="https://todaycrypto.org/spookyswaps-place-in-a-treasurys-swap-and-liquidity-plan/" rel="noopener noreferrer"&gt;SpookySwap&lt;/a&gt; V3 specification explains that positions use custom ranges; in this example, the reset swap adds a cost that simply waiting does not.&lt;/p&gt;

&lt;p&gt;For a $500 rebalance swap through a 0.30% pool, the pool fee would be about $1.50, before gas and any price impact. SpookySwap V3 lists pool fee tiers of 0.01%, 0.05%, 0.30%, and 1%; the tier depends on the pool you use. A reset without a swap avoids that pool fee, but still requires on-chain transactions and gas.&lt;/p&gt;

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

&lt;p&gt;Check the current pool price, your position’s lower and upper bounds, and the tokens it holds. Then decide whether to wait, choose a wider range, or reset around a price where you expect trades to happen.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Confirm the token pair and fee tier for the pool.&lt;/li&gt;
&lt;li&gt;Check the wallet’s gas estimate on the correct network.&lt;/li&gt;
&lt;li&gt;Estimate any swap needed to get the token mix required by your new range.&lt;/li&gt;
&lt;li&gt;Remove the old position, collect fees if desired, and add liquidity to the new range.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;SpookySwap is one example of a decentralized exchange with concentrated-liquidity positions. Its pool price, network gas, and fee tier determine your actual costs, so check those figures before signing each transaction.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>5 Inputs That Change Identical Swap Routes</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Thu, 22 Oct 2026 12:18:38 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/5-inputs-that-change-identical-swap-routes-3631</link>
      <guid>https://dev.to/cryptoguuru/5-inputs-that-change-identical-swap-routes-3631</guid>
      <description>&lt;p&gt;If you are getting different splits for the same pair, the router is optimizing against a different trade size, liquidity snapshot, or cost model. A route is a quote for specific conditions, not a permanent property of two token symbols.&lt;/p&gt;

&lt;p&gt;When you compare quotes, hold the chain and amount constant first; &lt;a href="https://topcrypto.news/how-developers-integrate-paraswap-token-swaps/" rel="noopener noreferrer"&gt;ParaSwap&lt;/a&gt; exposes route breakdowns that help you see whether flow moved between pools or the total output changed. Then check the search and execution settings.&lt;/p&gt;

&lt;h2&gt;
  
  
  A route is an optimization result, not a pair property
&lt;/h2&gt;

&lt;p&gt;A router models pools as edges in a token graph, then evaluates candidate paths and, where supported, splits the input across paths. It selects a composition that scores well under its objective, usually output after estimated gas, subject to route-search limits.&lt;/p&gt;

&lt;p&gt;For example, a $100,000 USDC-to-WETH trade might use two direct pools and a USDC-to-DAI-to-WETH path. A smaller trade could favor one pool: the extra path may add gas without enough price improvement. A different block can also change pool balances and reverse that ranking.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five inputs change the composition
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Trade size:&lt;/strong&gt; Larger input moves a pool further along its price curve, so splitting can reduce price impact. Tiny allocations may be discarded if their marginal gain is below the added gas.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pool state:&lt;/strong&gt; Reserves, concentrated-liquidity ticks, and fees are read from a particular chain state. Even adjacent blocks can change the best split after a swap or liquidity update.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search limits:&lt;/strong&gt; A hop cap, eligible-source list, or pruning threshold changes which paths the router evaluates. A cap of 2–4 hops is a common kind of search constraint, but the setting varies by router and chain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gas model:&lt;/strong&gt; Each extra pool call and split adds execution cost. The router estimates gas and converts it into the quote’s value; a route with better gross output can lose after gas, especially for small trades.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Token behavior:&lt;/strong&gt; Fee-on-transfer, rebasing, or otherwise nonstandard tokens can make quoted amounts diverge from received amounts. A router may exclude a pool or token, or the transaction may fail if its transfer assumptions do not hold.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Compare routes by fixing the quote inputs
&lt;/h2&gt;

&lt;p&gt;To diagnose a changed composition, request both quotes for the same chain, exact-input or exact-output mode, amount, and block where possible. Compare per-path amounts, pools, fees, estimated gas, and net output; a changed split with nearly unchanged net output may simply be a tie broken differently.&lt;/p&gt;

&lt;p&gt;Keep slippage tolerance separate from route selection: it sets how much execution can move before a transaction reverts, not which pools the quote searches. I would start with the router’s default search limits, then inspect the ParaSwap SDK route data if the split itself matters to the app.&lt;/p&gt;

&lt;p&gt;For a production integration, log the quote parameters and block alongside the selected route. That makes a later route change reproducible. Practical tip: compare net output after gas at the same amount before deciding that a new composition is better.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can identical pairs return different routes seconds apart?
&lt;/h3&gt;

&lt;p&gt;Yes. Pool state can change between blocks, and another trade can shift a pool’s marginal price enough to change the best split. Searcher configuration or gas estimates may also change. For a controlled comparison, pin the block when the quote interface permits it and keep every other parameter fixed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does a different split always mean a better quote?
&lt;/h3&gt;

&lt;p&gt;No. It may produce nearly the same net output, or even a worse result if the route adds gas. Compare expected output after estimated gas and check whether the quote is exact-input or exact-output. A composition is useful only insofar as it improves the objective you care about.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why can a quoted route fail on execution?
&lt;/h3&gt;

&lt;p&gt;The quote uses a snapshot and assumptions; execution happens later against live state. Prices can move past the slippage limit, liquidity can change, or a token’s transfer behavior can differ from the router’s assumptions. For unusual tokens, verify support and test the exact transaction path before relying on the quote.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>crypto</category>
      <category>web3</category>
    </item>
    <item>
      <title>A Volatile Swap Is Pending or Failed: Set Slippage</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Wed, 21 Oct 2026 23:59:22 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/a-volatile-swap-is-pending-or-failed-set-slippage-3bb3</link>
      <guid>https://dev.to/cryptoguuru/a-volatile-swap-is-pending-or-failed-set-slippage-3bb3</guid>
      <description>&lt;p&gt;If a volatile token swap fails because the price moved, raise slippage tolerance a little and retry with a fresh quote. Tolerance sets the lowest amount you will accept; it does not guarantee that amount or make a pending transaction faster. Check the quote and expected output first, then choose a limit you can live with.&lt;/p&gt;

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

&lt;p&gt;Slippage tolerance is the maximum price movement you accept between the quote and the swap’s execution. The swap uses it to set a minimum output: if the trade would deliver less, it reverts instead of completing at that worse rate.&lt;/p&gt;

&lt;p&gt;For example, if a quote promises 1,000 tokens and you set tolerance to 1%, the minimum is about 990 tokens. At 3%, it falls to about 970. A higher setting makes execution more likely during a sharp move, but lets the trade complete at a less favorable rate.&lt;/p&gt;

&lt;p&gt;Two price changes can affect the result. Price impact is the change caused by your own trade using available liquidity; slippage is the extra change while the quote waits to execute. A thin or volatile pair can have both. Raising tolerance accommodates more movement; it does not improve the route or reduce the trade’s price impact.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should I do when a swap is pending or failed?
&lt;/h2&gt;

&lt;p&gt;A pending swap has not finished on the blockchain, so changing tolerance will not speed it up. Check the wallet’s status and network fee. If the transaction is still pending, wait or use your wallet’s supported speed-up or cancel option; do not submit another swap blindly, since both transactions could execute.&lt;/p&gt;

&lt;p&gt;If it fails, read the wallet’s error and check whether the transaction reached the blockchain. A reverted swap may still cost a network fee, even though the tokens were not exchanged. A stale quote, a price move beyond your minimum output, missing token approval, or too little fee to process the transaction can each cause a failure; only the first two point to slippage.&lt;/p&gt;

&lt;p&gt;ParaSwap compares routes across liquidity sources, but the chosen route still faces market movement before execution. Understanding &lt;a href="https://poppybdkd502980.idblogmaker.com/42109224/what-is-paraswap-and-how-do-you-use-it-for-token-swaps" rel="noopener noreferrer"&gt;how ParaSwap routes token swaps&lt;/a&gt; helps explain why a good quote can change while it waits. Check the new quote’s expected output and route before retrying, rather than assuming a higher tolerance will fix every error.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much tolerance should I set for a volatile pair?
&lt;/h2&gt;

&lt;p&gt;Start with the lowest setting that allows a fresh quote to execute. As a working example, I would try around 0.5–1% for a liquid pair and around 1–3% for a volatile or thinner pair, then adjust only if the error shows the minimum output was missed. These are starting points, not guarantees; the right setting depends on liquidity, trade size, and how quickly the price is moving.&lt;/p&gt;

&lt;p&gt;Before retrying, compare the expected output with the amount you would still accept. If a 3% limit means receiving too few tokens, do not raise it just to force the swap through. Reduce the trade size, wait for calmer prices, or choose another route if available. On networks such as Base, also keep enough of the network’s fee token to pay for the transaction.&lt;/p&gt;

&lt;p&gt;Choose differently when the pair is extremely thin, the quote shows high price impact, or the token has unusual transfer rules. In those cases, a wider limit can accept a poor execution without solving the underlying issue. Wait, trade less, or skip the swap if the minimum output you can accept is below the fresh quote’s floor.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Does Fermi Swap Need Live Quotes for Token Swaps?</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Tue, 20 Oct 2026 19:16:46 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/why-does-fermi-swap-need-live-quotes-for-token-swaps-10d2</link>
      <guid>https://dev.to/cryptoguuru/why-does-fermi-swap-need-live-quotes-for-token-swaps-10d2</guid>
      <description>&lt;p&gt;fermi swap needs live quotes because Ethereum blocks arrive roughly every 12 seconds while its market maker can reprice inventory within a block. It offers onchain swaps at prices set by that maker, often for major tokens and stablecoins. To use it, an integrator must check the current pair and executable size, protect the output, and account for a quote changing before inclusion.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is fermi swap, and what does it offer?
&lt;/h2&gt;

&lt;p&gt;It is an Ethereum proprietary automated market maker: one market maker fills trades from its own token inventory and controls the prices it offers. There is no public liquidity position for an integrator to deposit into. The useful output is an executable quote for a specific token direction and amount, settled by an Ethereum transaction.&lt;/p&gt;

&lt;p&gt;That distinction matters when comparing routes. A quoted price may be attractive at a small size yet widen or disappear when the maker reaches an inventory limit. With pair and size fixed, check &lt;a href="https://fermiswap.pro" rel="noopener noreferrer"&gt;fermiswap.pro&lt;/a&gt; against your live FermiSwap quote and gas estimate before committing the route. Compare the tokens the recipient will actually receive, rather than a headline price for another trade size.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does a live quote become an onchain fill?
&lt;/h2&gt;

&lt;p&gt;The maker publishes price updates to a block builder as its inventory and market view change. Titan Builder can pair a fresh update with a taker transaction in the block it builds, so the swap reads the updated price onchain and settles against the maker’s inventory. The builder may receive multiple updates during one Ethereum slot; the quote visible in the previous block is therefore a poor proxy for the next fill.&lt;/p&gt;

&lt;p&gt;For an offchain quote, read the maker’s current state snapshot and apply its &lt;em&gt;state overrides&lt;/em&gt; to an &lt;em&gt;eth_call&lt;/em&gt; against the swap contract or router. Pin the simulation to the snapshot’s target block and slot time, because quote validity can depend on the block timestamp. A plain call against the latest confirmed state may return an old price or no usable price even while the maker is publishing fresh liquidity.&lt;/p&gt;

&lt;p&gt;A streamed update is an input to simulation, not a promise of inclusion. The maker can replace it, reduce depth, or stop quoting; the intended builder might not build the block that includes your transaction. The onchain minimum output is what bounds the result when the executed state differs from your simulation. If that minimum cannot be met, the transaction must revert or take a fallback path you have explicitly allowed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which markets and trade sizes are available?
&lt;/h2&gt;

&lt;p&gt;The practical market list is the set of token pairs the maker is quoting &lt;em&gt;now&lt;/em&gt;, in the direction and size you need. Common examples include WETH/USDC, WETH/USDT and USDC/USDT; WBTC may appear in the maker’s inventory and routes. An inventory balance alone does not establish an executable market, so query both directions and the full intended input amount before displaying a pair as available.&lt;/p&gt;

&lt;p&gt;Titan Builder’s venue snapshots expose pair addresses, while its price levels show bids, asks and cumulative volume for the markets it can publish. Match ERC-20 contract addresses rather than ticker symbols, and handle decimals before comparing outputs: WETH uses 18 decimals, USDC and USDT use 6, and WBTC uses 8. A quote for 1 WETH says little about a 50 WETH order; test the actual size, since the maker may quote less favorably or decline it altogether.&lt;/p&gt;

&lt;p&gt;For a quick what-if, suppose 1 WETH returns a live quote of 2,400 USDC. At 50 basis points of output tolerance, your minimum is 2,388 USDC, expressed as 2,388,000,000 base units in calldata. That 50 basis points is an illustrative choice, not a venue setting: tighten it when a missed fill is acceptable, and widen it only if the possible worse fill still suits the user.&lt;/p&gt;

&lt;h2&gt;
  
  
  How should an integrator submit the swap?
&lt;/h2&gt;

&lt;p&gt;Start with Ethereum mainnet token addresses, the exact input amount, a recipient, and enough ETH for gas. For an ERC-20 input, approve the contract that will pull it; for an ETH-denominated user flow, check whether your chosen interface accepts native ETH or expects WETH. Keep the approval scoped to the intended spender, since approving a router and then calling the venue directly uses different allowances.&lt;/p&gt;

&lt;p&gt;One integration route is the LambdaClass PropAMM Router, which exposes &lt;em&gt;quoteVenueV1(venue, tokenIn, tokenOut, amount)&lt;/em&gt; and &lt;em&gt;swapViaVenueV1(venue, tokenIn, tokenOut, amountIn, amountOutMin, recipient, deadline)&lt;/em&gt;. Passing the Fermi venue address selects it first, while the router’s documented fallback can fill elsewhere if that attempt fails. If venue attribution matters to your application, inspect the returned or emitted execution venue after settlement; selecting a venue first does not guarantee it supplied the final tokens.&lt;/p&gt;

&lt;p&gt;Obtain the fresh quote using state overrides, set &lt;em&gt;amountOutMin&lt;/em&gt; from the net amount the user accepts, and use a short deadline—say five minutes—to stop a delayed transaction from executing unexpectedly. Simulate the exact calldata, sender and value before signing, then submit through a path that can carry the maker update into the target block. Where your route supports multiple candidates, requoting at inclusion can be more robust than fixing one maker from an earlier offchain snapshot.&lt;/p&gt;

&lt;p&gt;Read the receipt as the final record: check status, output balance change and execution venue rather than treating a submitted hash as a fill. If you index swaps, key individual fill events by transaction hash and log index; a split route can emit several fill events in one transaction. Keep quote age and target slot in your logs so a failed simulation can be distinguished from a quote that changed before inclusion.&lt;/p&gt;

&lt;h2&gt;
  
  
  What costs and failure modes determine the choice?
&lt;/h2&gt;

&lt;p&gt;FermiSwap fees are best evaluated through the quoted output, rather than assumed to be a fixed percentage like a conventional pool fee. Add Ethereum gas and any fee your integration charges, then compare net recipient output for the same size. The LambdaClass router’s optional frontend fee is specified in basis points, capped at 100 basis points; its minimum output applies to what the recipient receives after that fee.&lt;/p&gt;

&lt;p&gt;Gas depends on the path taken. A single named venue needs less routing work than a transaction that requotes many venues or executes a fallback, and a gas estimate made against current state can miss a heavier branch at inclusion. Size the gas limit for the permitted branches and quote a maximum network cost from that limit and the transaction’s gas price; a reverted transaction can still spend gas.&lt;/p&gt;

&lt;p&gt;The less obvious edge case is a successful fallback that meets the aggregate minimum while giving a poor price on one portion of a split trade. If earlier portions already satisfy &lt;em&gt;amountOutMin&lt;/em&gt;, the remaining portion may have little price protection of its own. Set the aggregate minimum close to the total output the user genuinely expects, and decide whether the benefit of filling through another route outweighs that exposure.&lt;/p&gt;

&lt;p&gt;For a direct FermiSwap integration, also plan for absent snapshots, insufficient inventory, stale updates and a transaction landing in a block without the expected maker update. Treat each as a normal routing outcome: refresh the quote, choose another permitted route, or return a clear failure to the caller. Before acting, ask yourself: &lt;strong&gt;at this exact size, will the recipient’s minimum net output still be acceptable if the live quote changes before the transaction lands?&lt;/strong&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Threshold signatures for pooled bridge keys</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:20:28 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/threshold-signatures-for-pooled-bridge-keys-5a6f</link>
      <guid>https://dev.to/cryptoguuru/threshold-signatures-for-pooled-bridge-keys-5a6f</guid>
      <description>&lt;p&gt;A threshold signature lets a bridge spend pooled crypto without any one operator holding the whole private key, provided enough key holders cooperate and the bridge verifies the requested transaction. That helps hide the key from individual operators, but it does not remove the need to trust the bridge’s rules, software and quorum.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does a threshold signature authorize a pooled spend?
&lt;/h2&gt;

&lt;p&gt;At setup, a group of operators jointly creates a public key and divides control of its private key into shares. A threshold is set: for example, in a hypothetical 7-of-10 setup, seven participants must cooperate to sign, while fewer cannot. The complete private key is never assembled. NIST describes this as computing a cryptographic operation across parties whose key is secret-shared.&lt;/p&gt;

&lt;p&gt;Think of it like a lockbox whose key is never cut: several people each hold a special tool that helps turn the lock, but no one can take away a complete key. Unlike ordinary key fragments, though, the participants run a multi-round cryptographic protocol to produce one standard signature. The destination chain checks that signature against the public key; it does not need to know that several operators made it together.&lt;/p&gt;

&lt;p&gt;For a Bitcoin release, the bridge first needs to agree that a valid request exists, such as a confirmed burn of wrapped bitcoin and a destination address. Its operators select the pooled wallet’s unspent transaction outputs (UTXOs), build a transaction with the requested payment and a miner fee, then use their shares to sign it. Bitcoin’s Developer Guide explains the UTXO model and how signatures authorize spending; RenVM used threshold ECDSA so the resulting signature could be checked in the usual way.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did this look like in RenVM?
&lt;/h2&gt;

&lt;p&gt;RenVM organized operators, called Darknodes, into groups known as shards. For a Bitcoin-to-Ethereum transfer, a user sent BTC to a gateway address controlled by the shard; after the deposit met the required confirmation rule, RenVM authorized minting the corresponding wrapped asset. On the return trip, a burn on Ethereum triggered a Bitcoin transaction back to the user. If you are tracing that flow, check &lt;a href="https://telegra.ph/RenBridge-4-Things-to-Know-Before-Moving-Crypto-10-20" rel="noopener noreferrer"&gt;RenBridge renBTC bridge&lt;/a&gt; at the point where the BTC deposit becomes wrapped bitcoin, because that is where pooled custody and threshold authorization meet.&lt;/p&gt;

&lt;p&gt;The signature alone did not decide whether a spend was allowed. RenVM’s consensus process had to agree on the event and transaction details before the signing protocol ran. This separation matters: threshold cryptography protects the key from any one signer, while consensus and software determine what those signers are asked to authorize.&lt;/p&gt;

&lt;p&gt;Key changes also matter. When a shard’s membership changed, RenVM’s design rotated the gateway key and moved funds to an address for the new key set. Rotation reduces the risk that former operators keep useful shares, but it depends on the transition completing correctly. If too few current participants are online, a safe quorum may be unavailable and funds can become temporarily unspendable.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is threshold signing a better fit than multisig?
&lt;/h2&gt;

&lt;p&gt;Threshold signing suits a bridge that wants many operators to jointly control one pooled key while presenting a conventional signature to the destination chain. It can avoid publishing a multisig policy on-chain and can work with chains that do not support the bridge’s preferred native multisig format. Its cost is coordination: signers must communicate through a multi-round protocol, and faulty or unreachable participants can delay a transaction.&lt;/p&gt;

&lt;p&gt;A native multisig is a better fit when the chain supports it and visible, on-chain authorization by several keys is acceptable. The chain can enforce a rule such as “three of five keys,” which makes the spending policy easier to inspect. But transactions may carry extra signature data, and each chain’s multisig features and fees differ.&lt;/p&gt;

&lt;p&gt;A custodian is simpler when speed and operational support matter more than distributed control. One provider holds the key and signs withdrawals, so there is no quorum round; users instead rely on that provider’s security, solvency and withdrawal policies. I would compare the trust assumption first: threshold signing spreads key control, multisig exposes an enforceable chain rule, and custody concentrates control.&lt;/p&gt;

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

&lt;p&gt;Do not treat “threshold” as a complete security rating. Ask how many signers there are, what threshold must approve a spend, how membership changes, and whether the bridge checks deposits and burns independently before requesting signatures. A threshold that tolerates some faulty operators may still fail if too many are offline, and a compromised quorum can authorize a valid-looking but harmful transaction.&lt;/p&gt;

&lt;p&gt;There is also a cryptographic edge case: ECDSA signing relies on fresh, carefully managed nonce values. If a signer reuses or exposes nonce material, the private key can be recoverable from signatures; secure protocols therefore coordinate nonce generation and protect intermediate data. This is one reason to assess implementation and audits alongside the headline signer count.&lt;/p&gt;

&lt;p&gt;As of 20 October 2026, RenBridge’s RenVM 1.0 basis shut down in December 2022, so treat its flow as a historical design rather than a live route for moving funds. Before using any bridge, verify that deposits and withdrawals are currently operating and that the exact asset and destination are supported; then compare the quorum, exit path and total transaction fees. My practical tip is to test the smallest useful amount first, especially when a bridge requires a burn before releasing the original asset.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>crypto</category>
      <category>security</category>
      <category>web3</category>
    </item>
    <item>
      <title>When a Token Taxes Transfers, Check Your Swap Output</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Sat, 17 Oct 2026 06:02:55 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/when-a-token-taxes-transfers-check-your-swap-output-3l50</link>
      <guid>https://dev.to/cryptoguuru/when-a-token-taxes-transfers-check-your-swap-output-3l50</guid>
      <description>&lt;p&gt;A transfer-tax token delivers less than the amount sent whenever its contract takes a cut during a transfer. When you swap into one from your own wallet, check whether the route supports that token and whether the quoted amount reflects the cut. The tax is part of the token’s rules, separate from network and swap fees.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;A token’s transfer tax can reduce the amount that reaches your wallet.&lt;/li&gt;
&lt;li&gt;A route may fail if its contracts cannot handle the token’s transfer rules.&lt;/li&gt;
&lt;li&gt;Check the exact token and network before you swap.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A transfer tax is taken when the token moves
&lt;/h2&gt;

&lt;p&gt;A transfer tax is a charge built into a token’s code, often taken each time the token moves between addresses. The contract may burn the cut, send it to another wallet, or distribute it to holders.&lt;/p&gt;

&lt;p&gt;For example, if a token charges 2% and a transfer sends 100 tokens, your wallet might receive 98. The exact result depends on the contract and which transfers it taxes. This charge is different from gas, the network payment for processing a transaction, and from a swap’s trading fee.&lt;/p&gt;

&lt;p&gt;On a cross-chain swap, the destination token’s rules matter when that token is delivered on its own network. A &lt;a href="https://ethereumnews.github.io/how-thor-swap-handles-a-btc-to-eth-trade-in-one-flow/" rel="noopener noreferrer"&gt;thor swap service&lt;/a&gt; gives you a way to handle a cross-chain move in one flow, while the token’s own rules still determine how much arrives. Check the destination token before choosing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tax can change the amount you actually receive
&lt;/h2&gt;

&lt;p&gt;The key figure is the amount credited to your wallet after the taxed transfer, not just the amount a quote says the swap produces. A quote may show the token amount before its transfer tax, depending on how the route handles that token.&lt;/p&gt;

&lt;p&gt;Consider two tokens. Token A has no transfer tax, so a 100-token delivery can credit 100 tokens; Token B takes 2%, so the same nominal delivery may credit 98. If you need a particular amount for a later trade or payment, that difference matters.&lt;/p&gt;

&lt;p&gt;Some swap contracts check that the expected amount arrives. If a token takes a cut along the way, the check can fail and the swap may revert. Uniswap, for example, documents fee-on-transfer tokens as incompatible with its v3 router contracts; support depends on the route’s actual contracts, not simply on whether the token exists on that network.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the token and route before moving funds
&lt;/h2&gt;

&lt;p&gt;Start by confirming the token’s contract address and network; names and symbols alone can be copied by impostors. Look for the token’s transfer fee rules in reliable project information, and check whether the route can process fee-on-transfer tokens.&lt;/p&gt;

&lt;p&gt;Then compare the estimated output with the amount you need to receive. If the route does not clearly account for the tax, treat its displayed output as uncertain. A thor swap search can lead you to cross-chain options, but the destination token’s contract rules still decide what lands in your wallet.&lt;/p&gt;

&lt;p&gt;For a practical cross-chain comparison, thorswap.us is where you would check how its service handles moving and swapping assets across networks. Before committing, make sure you have the destination network’s native coin for gas if you plan to move or swap the tokens again.&lt;/p&gt;

&lt;p&gt;If the token’s tax or route support is unclear, try a small amount first and confirm the wallet balance after it arrives. That costs an extra network transaction, but it can show whether the tax was applied as expected before you move more.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use the received balance to decide your next move
&lt;/h2&gt;

&lt;p&gt;After the transaction completes, check the destination network’s transaction record and your wallet’s token balance. The balance is what you received; a transaction record can help explain a difference between that amount and the quote.&lt;/p&gt;

&lt;p&gt;If the credited amount works for your plan, you can keep or use the tokens. If it does not, check the tax rate and route support before trying another swap. For the next thor swap, choose a destination token whose transfer rules and expected received amount fit the job.&lt;/p&gt;

&lt;p&gt;Before swapping, remember to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Verify the token contract and destination network.&lt;/li&gt;
&lt;li&gt;Check whether the route supports transfer-tax tokens.&lt;/li&gt;
&lt;li&gt;Plan around the amount credited after tax, and confirm it arrived.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>What Does a Failed Mantle Bridge Swap Cost?</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Fri, 16 Oct 2026 19:00:18 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/what-does-a-failed-mantle-bridge-swap-cost-4bhc</link>
      <guid>https://dev.to/cryptoguuru/what-does-a-failed-mantle-bridge-swap-cost-4bhc</guid>
      <description>&lt;p&gt;A failed destination swap usually costs the gas used by the reverted transaction; the bridge transfer may already have completed. What happens to the bridged token depends on the route’s fallback, so check whether it returned to your wallet or needs a separate recovery action before you try again.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can the swap fail after the bridge succeeds?
&lt;/h2&gt;

&lt;p&gt;A cross-chain transfer and a destination swap are separate operations, even when one service arranges them in a single flow. The source-chain transaction starts the transfer; after the destination network receives the bridged asset, a second transaction attempts the swap there.&lt;/p&gt;

&lt;p&gt;That second transaction can revert if its conditions are no longer met. A common cause is slippage: the swap’s minimum output is higher than the amount available when the transaction executes. Low liquidity, a token or route restriction, or an expired deadline can also prevent execution.&lt;/p&gt;

&lt;p&gt;For example, say a route bridges 100 USDC to Mantle and quotes a swap for 0.040 ETH, with a minimum output of 0.039 ETH. If the pool can provide only 0.038 ETH by the time the swap runs, the minimum-output check fails and the destination swap reverts.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens to the funds and fees?
&lt;/h2&gt;

&lt;p&gt;A reverted destination transaction normally rolls back that transaction’s contract changes, but it cannot undo a completed transaction on the source chain. The bridge transfer may therefore remain complete even though the requested swap did not happen.&lt;/p&gt;

&lt;p&gt;The route determines what you can do next. It may return the bridged input token to your wallet, leave it in a contract with a recovery or claim path, or handle the failed call in another way. Don’t assume the asset is lost or automatically available: check the destination transaction and the route’s status to see where the token ended up.&lt;/p&gt;

&lt;p&gt;You generally pay gas for the failed destination transaction because the network executed it up to the revert. You may also have paid source-chain gas and a bridge or service charge before the failure; those costs are not necessarily refunded. If you retry or claim the asset in a new transaction, that action can cost gas too. A swap that reverts does not complete its exchange, but the gas spent attempting it is still a cost.&lt;/p&gt;

&lt;p&gt;The total depends on the networks, transaction complexity, gas prices and route terms. For a Mantle bridge transfer, the destination transaction’s gas is paid on Mantle, while the source transaction’s gas is paid on the source network. Check the wallet’s network and fee estimate for each transaction rather than treating the full flow as one fee.&lt;/p&gt;

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

&lt;p&gt;First find out whether the bridge completed and where the input token is now. When choosing a route for &lt;a href="https://telegra.ph/Mantle-Bridge-Swap-Before-or-After-to-Save-Fees-10-14" rel="noopener noreferrer"&gt;fast Mantle bridge transfers&lt;/a&gt;, consider the failed-swap path as well as the quoted output: a cross-chain bridge and swap service can move assets between networks and swap them in one flow, but the route’s fallback determines how you recover if the swap fails.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the source transaction in its block explorer and confirm whether it succeeded.&lt;/li&gt;
&lt;li&gt;Find the destination transaction or route status and check whether the swap reverted, is still pending, or completed.&lt;/li&gt;
&lt;li&gt;Check your wallet on the destination network for the bridged input token, using its verified token details if it is not displayed.&lt;/li&gt;
&lt;li&gt;If the token is held by a route contract, follow that route’s stated recovery path before submitting another transfer.&lt;/li&gt;
&lt;li&gt;Before retrying, review the new minimum output and deadline, and make sure the destination wallet has enough native token to pay gas.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A wallet such as MetaMask can show different assets depending on the selected network, so switch to the destination network before checking your balance. A missing token display does not prove the transfer failed; use the explorer and transaction status to establish what happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is a retry sensible?
&lt;/h2&gt;

&lt;p&gt;Retry only after you can see the input token in your wallet or have confirmed how to recover it from the route. If the problem was a temporary price move, a fresh quote with a realistic minimum output may work; accepting a much lower minimum just to force execution can leave you with fewer tokens than intended.&lt;/p&gt;

&lt;p&gt;If the destination transaction is still pending, wait for its status before starting another flow. If it reverted and the bridged token is available, compare a new quote with the amount you actually hold and the extra gas a retry requires. The relevant comparison is the expected amount after fees against the value of keeping the token as it is.&lt;/p&gt;

&lt;p&gt;For a failed destination swap, remember these points:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The bridge transfer can succeed even when the swap reverts.&lt;/li&gt;
&lt;li&gt;The failed destination transaction still uses gas.&lt;/li&gt;
&lt;li&gt;The route determines whether the input token is returned or must be recovered.&lt;/li&gt;
&lt;li&gt;Verify the token and transaction status before retrying.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>How to Choose a Faster Monero-to-Solana Swap Route</title>
      <dc:creator>Mandie Brugman</dc:creator>
      <pubDate>Fri, 16 Oct 2026 13:23:34 +0000</pubDate>
      <link>https://dev.to/cryptoguuru/how-to-choose-a-faster-monero-to-solana-swap-route-7k5</link>
      <guid>https://dev.to/cryptoguuru/how-to-choose-a-faster-monero-to-solana-swap-route-7k5</guid>
      <description>&lt;p&gt;To cut the wait, compare the full settlement path, not just the destination chain. A cross-chain swap has to confirm your Monero payment, arrange the asset exchange, and deliver funds on the destination network; the slowest handoff sets the pace, while route fees and quote expiry affect the cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare the four parts that set the clock
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Monero confirmations:&lt;/strong&gt; how long the route waits before acting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exchange method:&lt;/strong&gt; whether it can pay from available liquidity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Destination delivery:&lt;/strong&gt; how quickly the receiving chain settles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quote conditions:&lt;/strong&gt; how long the rate and instructions remain valid.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Monero blocks arrive about every two minutes on average, but that is not a promise that a swap will complete in two minutes. The service handling the exchange may wait for several confirmations before releasing the destination asset; its policy, transaction size, and risk checks can add time. Treat the confirmation wait as a separate part of the estimate.&lt;/p&gt;

&lt;p&gt;The exchange method can matter more than the destination chain. A route with assets already available on both sides may be able to pay out after it accepts your deposit, while another path may need an additional trade or settlement. Like an airport connection, each handoff adds a chance to wait. When comparing a &lt;a href="https://aboutcryptotalks.gitbook.io/aboutcrypto/what-types-of-monero-bridge-are-there" rel="noopener noreferrer"&gt;Monero bridge route&lt;/a&gt;, check what the estimate says about confirmation and payout timing, rather than assuming a fast chain makes the whole trip fast.&lt;/p&gt;

&lt;p&gt;Solana can settle transactions quickly, but the route still has to submit and confirm its payout there. Congestion, failed transactions, or extra processing can affect delivery. Also check that the destination asset and address match: sending a token to an address or network that cannot receive it may create a much more expensive delay than block time.&lt;/p&gt;

&lt;p&gt;A quote is useful only while its assumptions hold. Check its expiry and what happens if Monero’s exchange rate moves before your payment is recognized. A short quote window can reduce rate uncertainty, but it leaves less time to prepare and broadcast the transaction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the quote as a time-and-cost budget
&lt;/h2&gt;

&lt;p&gt;Compare the amount you expect to receive after deductions, not a headline fee. The total can include a service charge, Monero’s network fee, any conversion spread, and the destination-chain fee. These vary with the route and market conditions, so use the actual quote for the amount you plan to send.&lt;/p&gt;

&lt;p&gt;For example, if a quote estimates a five-minute confirmation wait and a further payout period, don’t read “five minutes” as an end-to-end guarantee. It may describe only one stage. A route that costs slightly more can still be the better repeat-use choice if it removes an extra exchange or handoff; weigh that saving against the quoted net amount.&lt;/p&gt;

&lt;p&gt;For frequent transfers, compare the same input amount and destination across routes at roughly the same time. Record the quoted net output and estimated completion window, then compare them after a few uses. That gives you a practical baseline without treating one unusually quiet or congested period as typical.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prepare for the handoff before sending
&lt;/h2&gt;

&lt;p&gt;Before broadcasting, confirm the destination network, asset, and address, then check the deposit instructions and quote expiry. Keep enough time to send the Monero transaction while the quote is live. If your wallet shows a transaction as pending, avoid sending a second payment unless the route’s instructions explain how to handle it; duplicate deposits can require manual resolution.&lt;/p&gt;

&lt;p&gt;If speed matters more than a small price difference, choose the route with the fewest dependent handoffs and a clear estimate for both confirmation and payout. If cost matters more, compare net output and accept a longer stated window where it makes sense. Before acting, ask yourself: &lt;em&gt;Am I optimizing for the time until funds arrive, or for the amount that arrives?&lt;/em&gt;&lt;/p&gt;

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