<?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: Milton Altenwerth</title>
    <description>The latest articles on DEV Community by Milton Altenwerth (@milton_altenwert).</description>
    <link>https://dev.to/milton_altenwert</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%2F4098909%2Fabfbb8eb-9088-45f4-9f7f-1aa07e2b5f2c.png</url>
      <title>DEV Community: Milton Altenwerth</title>
      <link>https://dev.to/milton_altenwert</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/milton_altenwert"/>
    <language>en</language>
    <item>
      <title>Native vs bridged USDC on Berachain: choose the right token</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Tue, 17 Nov 2026 02:14:31 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/native-vs-bridged-usdc-on-berachain-choose-the-right-token-4j7h</link>
      <guid>https://dev.to/milton_altenwert/native-vs-bridged-usdc-on-berachain-choose-the-right-token-4j7h</guid>
      <description>&lt;p&gt;Receive the USDC version your target Berachain pool accepts. Where both versions are available and accepted, choose Circle-issued USDC because it avoids the extra dependency on a bridge’s backing. The &lt;a href="https://berachainbridge.app" rel="noopener noreferrer"&gt;Berachain bridge&lt;/a&gt; is a cross-chain asset bridge for moving assets into Berachain DeFi; what matters for your position is the token contract it delivers. Circle’s published mainnet contract list currently has no Berachain entry, so verify any claim that a route delivers native USDC there.&lt;/p&gt;

&lt;h2&gt;
  
  
  The contract identifies the USDC you hold
&lt;/h2&gt;

&lt;p&gt;Native and bridged USDC are different tokens, even when an app displays the same USDC ticker for both. Their contract addresses identify who issued each token and what backs it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Native USDC:&lt;/strong&gt; Circle issues the token on a supported chain. It has no separate bridge collateral to recover, though it still carries the risks of USDC itself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bridged USDC:&lt;/strong&gt; A bridge issues a representation against USDC locked elsewhere. Its holder depends on the bridge’s backing and redemption mechanism as well as the underlying USDC.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That distinction matters when a bridge loses locked funds or its token trades below the value of the USDC backing it. The bridged token can become undercollateralised or difficult to redeem. Circle-issued USDC does not add that bridge layer. A familiar ticker, wallet icon or price near one dollar cannot establish which contract you received.&lt;/p&gt;

&lt;p&gt;Circle’s CCTP moves native USDC between supported chains by burning it on the source chain and minting it on the destination. A route using CCTP is therefore worth considering when the destination chain and the required native token are supported. Do not infer CCTP support from the presence of bridged USDC on Berachain.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pool address determines the route
&lt;/h2&gt;

&lt;p&gt;The destination pool’s USDC address determines which transfer route will leave you with a usable deposit token. Read that address from the pool contract or the app’s documentation &lt;em&gt;before&lt;/em&gt; bridging. Then compare the route’s stated output contract with it. Matching symbols are insufficient: the receiving contract must match the token the pool accepts.&lt;/p&gt;

&lt;p&gt;Say you hold USDC on Ethereum and want to supply a Berachain USDC/HONEY position. First identify the pool’s USDC token address, including whether it uses a bridge-issued token. Next find a route that delivers that exact address on Berachain. After the transfer, compare the received token’s contract in your wallet or a block explorer with the pool address. A match means you can proceed to the pool without converting the USDC first.&lt;/p&gt;

&lt;p&gt;Consider two otherwise identical USDC/HONEY positions funded from the same Ethereum balance. One pool accepts bridge-issued USDC; receiving that contract lets you deposit directly. Suppose a second pool accepts Circle-issued USDC after Circle publishes a Berachain contract: receiving bridged USDC for that pool would require a swap. The accepted contract is the decisive difference, even though the source asset and intended exposure are the same.&lt;/p&gt;

&lt;p&gt;Stargate uses LayerZero for cross-chain messaging, but its route name alone cannot tell you whether the delivered USDC is Circle-issued. A Berachain bridge route is useful for this transfer when its destination asset matches the pool. berachainbridge.app offers a cross-chain asset bridge for moving assets into Berachain DeFi; compare the USDC it would deliver with the address your position requires.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is USDC.e?
&lt;/h3&gt;

&lt;p&gt;USDC.e usually denotes bridged USDC rather than a token issued directly by Circle. Treat the suffix as a clue, then verify the contract against the bridge’s documentation and the target app’s accepted token address. A bridge may display its representation simply as USDC, so the suffix is not a complete identification method.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can you swap bridged USDC for native USDC?
&lt;/h3&gt;

&lt;p&gt;You can swap bridged USDC for native USDC when a verified native contract exists on the chain and a market offers the pair. Liquidity, price impact and trading costs determine what you receive. On Berachain, confirm Circle has published a native contract before treating any swap output as Circle-issued USDC.&lt;/p&gt;

&lt;p&gt;If your pool accepts both verified versions, choose native USDC; if it accepts only bridged USDC, choose the route that delivers that bridged contract and skip the extra swap.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Token Approval in Ethereum: How ERC-20 Spending Rights Work</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Mon, 16 Nov 2026 19:13:18 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/token-approval-in-ethereum-how-erc-20-spending-rights-work-bd1</link>
      <guid>https://dev.to/milton_altenwert/token-approval-in-ethereum-how-erc-20-spending-rights-work-bd1</guid>
      <description>&lt;p&gt;A token approval in Ethereum lets a named contract move up to a specified amount of one ERC-20 token from your address using transferFrom, until the allowance is spent or revoked. The token contract tracks that limit separately for each owner and spender, so an approval applies to the token and contract you specify.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Does an ERC-20 Token Approval Work?
&lt;/h2&gt;

&lt;p&gt;An ERC-20 approval sets a spending limit in the token contract before another contract pulls your tokens. Four parts determine what it permits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Owner:&lt;/strong&gt; the address holding the tokens.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Token:&lt;/strong&gt; the ERC-20 contract, such as USDC.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Spender:&lt;/strong&gt; the address allowed to pull them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Allowance:&lt;/strong&gt; the amount the spender may still pull.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Your wallet sends approve(spender, amount) to the token contract, which stores allowance[owner][spender]. The spender can then call transferFrom to move tokens from your address, up to the remaining allowance and your available balance. The &lt;a href="https://eips.ethereum.org/EIPS/eip-20" rel="noopener noreferrer"&gt;EIP-20 token standard&lt;/a&gt; defines these three functions: approve authorizes a spender up to an amount, allowance reports what remains, and transferFrom moves tokens from an authorized address. These rules govern the ERC-20 token contract involved in the swap.&lt;/p&gt;

&lt;p&gt;Say you approve 100 USDC for a swap. The approval is its own on-chain transaction and costs gas; signing it does not execute the swap. After it confirms, you sign the swap transaction separately. If the spender pulls all 100 USDC, the remaining allowance is zero. If it pulls less, or the swap never happens, the unused allowance remains available until you change it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Much Should You Approve for a Swap?
&lt;/h2&gt;

&lt;p&gt;For one swap, approving the quoted input amount limits what the spender can pull. Compare two approvals for the same 100 USDC trade and the same spender: an allowance of 100 USDC can cover that trade, while an unlimited allowance can also cover later USDC sent to your address. If the spender contract is exploited, the amount left available to it changes with that one choice.&lt;/p&gt;

&lt;p&gt;An unlimited approval sets the allowance to the maximum uint256 value. It can save the gas of another approval on repeat trades with the same spender, but the approval can stay active after today’s swap finishes. Even a smaller approval may leave a remainder when the swap uses less than expected. Review the remaining allowance after the trade, rather than assuming the swap cleared it.&lt;/p&gt;

&lt;p&gt;A wallet might show a signing prompt instead of a separate approve transaction. EIP-2612 permit lets a signature set an ERC-20 allowance when someone submits it on-chain. Permit2 can use signed permissions after you have approved that token for the Permit2 contract; its permissions may cover a limited amount and duration or a single transfer. Read the token, spender, amount and deadline in a permit prompt: a signature can carry spending rights even though signing itself costs no gas.&lt;/p&gt;

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

&lt;h3&gt;
  
  
  How do I revoke a token approval?
&lt;/h3&gt;

&lt;p&gt;Revoke an ERC-20 approval by setting that spender’s allowance to zero. Look up your address in the Etherscan Token Approval Checker, select the ERC-20 token and approved spender, then submit its revoke transaction from your wallet. Revocation costs gas and takes effect when the transaction confirms. If you used Permit2, review its spender permissions as well as the token’s allowance to Permit2.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is an unlimited token approval safe?
&lt;/h3&gt;

&lt;p&gt;An unlimited token approval gives the named spender ongoing access to that token, subject to your balance. Its convenience is most useful when you expect repeat trades with the same contract and accept that continuing exposure. For a one-off trade, an amount sized to the input gives the spender less room to act if something goes wrong.&lt;/p&gt;

&lt;p&gt;On a first USDC swap that uses a 0x settlement contract, your wallet asks you to approve that contract before the separate swap transaction. When using &lt;a href="https://matchaswap.pro" rel="noopener noreferrer"&gt;Matcha swap&lt;/a&gt;, a decentralized exchange aggregator that finds routes across liquidity sources, compare the spender shown in your wallet with the swap quote and approve the USDC amount you intend to trade.&lt;/p&gt;

&lt;p&gt;After the swap, verify the remaining allowance and revoke any access you no longer need.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>crypto</category>
      <category>security</category>
      <category>web3</category>
    </item>
    <item>
      <title>How Can Fraxswap Swap Tokens Without a Direct Pool?</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Fri, 06 Nov 2026 08:15:58 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/how-can-fraxswap-swap-tokens-without-a-direct-pool-3k31</link>
      <guid>https://dev.to/milton_altenwert/how-can-fraxswap-swap-tokens-without-a-direct-pool-3k31</guid>
      <description>&lt;p&gt;If a Fraxswap quote shows an unfamiliar token between the one you hold and the one you want, it can connect pools through that token even without a direct pool for your pair. The middle token is an intermediary asset: one swap produces it, and the next uses it as input. Both legs execute as one spot trade on the same network. What matters is connected liquidity, not a dedicated pool for every token combination.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Fraxswap Routes a Spot Swap
&lt;/h2&gt;

&lt;p&gt;Fraxswap's spot routes move input through one or more Pair contracts, which hold the tokens and liquidity used for each swap. In a quote on &lt;a href="https://fraxswap.co" rel="noopener noreferrer"&gt;Fraxswap&lt;/a&gt;, an intermediary token between input and output names a stop along that route. You are choosing a path through pools, not taking delivery of the middle token as the final result. The selected router or interface must support the path; connected pools alone do not guarantee that every interface will quote it.&lt;/p&gt;

&lt;p&gt;A token selector can blur three distinct things. A token contract identifies an asset, such as token A. An A/B pair is a pool holding liquidity for swaps between A and B. A route is the ordered sequence of pairs that takes input A to output B. Listing A and B does not establish an A/B pair or another sequence that can carry the trade.&lt;/p&gt;

&lt;h2&gt;
  
  
  Direct and Multihop Routes
&lt;/h2&gt;

&lt;p&gt;A direct route takes A to B through one A/B pool, with no intermediary token. A multihop route takes A to C in an A/C pool, then C to B in a C/B pool. The output of the first swap becomes the input of the second. Both swaps occur within one transaction on one network. A multihop spot route therefore uses connected pools; it does not require you to place two separate orders.&lt;/p&gt;

&lt;p&gt;The path in a quote makes the distinction visible: A → B uses one pool; A → C → B uses two. More intermediaries mean more pools to traverse, and each pool needs usable liquidity for the amount routed through it. The middle token may be unfamiliar, but its role is specific: it connects pools that share that asset.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Changes When a Quote Adds a Hop
&lt;/h2&gt;

&lt;p&gt;Adding a hop adds another pool fee and another liquidity dependency, but it does not necessarily reduce the amount received. Compare two quotes with the same A input, B output, trade amount, network, and router. Keep the A/C and C/B pools the same too. In the first case, the A/B pool has ample liquidity, so the one-pool route may give more B after its fee. In the second, only the A/B pool's liquidity is thin. The direct trade can move its price enough that the A/C/B route gives more B even after two pool fees. The decisive change is liquidity in the direct pool.&lt;/p&gt;

&lt;p&gt;Pool count is a clue, not a ranking. For your intended amount, compare the quoted output, the assets in the path, and the minimum received after your slippage setting. A small trade may fit a direct pool comfortably, while a larger one may face more price impact there. The result depends on current pool liquidity and fees. Path selection matters too: one interface may show a supported route that another does not offer.&lt;/p&gt;

&lt;h2&gt;
  
  
  When No Route Is Available
&lt;/h2&gt;

&lt;p&gt;A route is unavailable when the selected router or interface cannot find a supported path with usable liquidity at every hop for your amount. Seeing both token contracts in a selector does not establish a pool, a connected path, or enough liquidity for a useful quote. A path with poor quoted output is different from no route at all. Look at the amount and path before submitting the trade. Moving assets between networks requires bridging, which is separate from a spot route.&lt;/p&gt;

&lt;p&gt;A multihop spot quote also says nothing about whether the same path works for a Fraxswap TWAMM order. TWAMM spreads an order over time, so its supported paths and execution rules must be considered separately from a spot router's path.&lt;/p&gt;

&lt;p&gt;The quoted path lets you distinguish a listed token, an existing pool, and a usable route for the amount you want to trade.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>SyncSwap trade or pool: Which fits your crypto goal?</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Mon, 02 Nov 2026 02:30:10 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/syncswap-trade-or-pool-which-fits-your-crypto-goal-4lln</link>
      <guid>https://dev.to/milton_altenwert/syncswap-trade-or-pool-which-fits-your-crypto-goal-4lln</guid>
      <description>&lt;p&gt;Choose a SyncSwap trade if you want a different token now; provide liquidity if you want to hold both pool tokens and accept a changing mix. A swap ends when the tokens arrive. A pool position stays exposed to price moves until you withdraw.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens when you trade or join a pool?
&lt;/h2&gt;

&lt;p&gt;A trade takes one token from your wallet and returns another from a liquidity pool. A pool holds tokens supplied by users. Its pricing rule changes the exchange rate as trades change the amounts it holds.&lt;/p&gt;

&lt;p&gt;The SyncSwap DEX is a decentralized exchange: you approve trades from your wallet rather than deposit into a company account. For example, &lt;a href="https://syncswap.dev" rel="noopener noreferrer"&gt;SyncSwap trading fees&lt;/a&gt; explain one part of a quote; the pool’s available tokens also affect what you receive.&lt;/p&gt;

&lt;p&gt;If you supply tokens instead, you receive a position representing your share of a pool. Traders pay fees to use that pool, and your share can earn part of them. The pool you choose matters:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Classic:&lt;/strong&gt; Suits tokens whose prices can move far apart, such as ETH and a dollar token.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stable:&lt;/strong&gt; Favors tokens expected to stay near the same value, such as two dollar tokens.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Aqua:&lt;/strong&gt; Puts more trading funds near the current price as it moves. Check its live quote and pool size.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Can your wallet use the network and tokens?
&lt;/h2&gt;

&lt;p&gt;Your wallet needs the tokens on the same network you select for the trade or pool. SyncSwap supports networks including ZKsync Era and Linea, but each has separate balances and pools. A swap on one network cannot spend tokens held on another.&lt;/p&gt;

&lt;p&gt;If your funds are elsewhere, a bridge moves them between networks. Check its transfer cost and arrival time before deciding. You also need some ETH on the chosen network for gas, the charge for recording transactions.&lt;/p&gt;

&lt;p&gt;Check each token’s contract address, its unique identifier on that network, before you approve spending. A ticker alone is unreliable: USDC and USDC.e, for example, can be different tokens with different pools. If your intended pair has no usable pool, the displayed balance does not make a trade possible.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you judge a swap quote?
&lt;/h2&gt;

&lt;p&gt;Judge a swap by the tokens you will receive after fees and price impact, then add gas. Price impact is the worse rate caused by your own trade changing a pool’s balance. A smaller pool usually means more impact for the same trade.&lt;/p&gt;

&lt;p&gt;Say a Classic pool starts with 100 ETH and 200,000 USDC. Selling 1 ETH returns about 1,980 USDC before its trading fee, although the starting rate is 2,000. The missing roughly 20 USDC comes from price impact.&lt;/p&gt;

&lt;p&gt;SyncSwap may route a trade through more than one pool. Compare the final output, not just the fee shown for one step. A low fee cannot rescue a poor rate from thin liquidity.&lt;/p&gt;

&lt;p&gt;Check &lt;strong&gt;minimum received&lt;/strong&gt; before signing. It is the lowest output you permit if prices move while the transaction waits. For a 1,980 USDC quote, 0.5% slippage tolerance puts that minimum near 1,970 USDC; it does not remove the price impact already in the quote. A first trade may also need an approval, a separate transaction allowing the trading contract to spend your token.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does providing liquidity make sense?
&lt;/h2&gt;

&lt;p&gt;Providing liquidity makes sense when you want exposure to both tokens and expect your share of trading fees to justify the risk. Check the pool’s recent trading activity alongside its total deposits. High activity can mean more fees, but your share shrinks as more people deposit.&lt;/p&gt;

&lt;p&gt;The risk is clearest in a before-and-after example. Say you add 1 ETH and 2,000 USDC to a Classic pool when ETH costs 2,000 USDC. If ETH doubles, your share becomes roughly 0.707 ETH and 2,828 USDC as traders change the pool’s mix.&lt;/p&gt;

&lt;p&gt;That share is worth about 5.7% less than simply keeping the original tokens, before earned fees. This gap is called impermanent loss. In a Stable pool, the sharper concern is a token losing its expected peg: your withdrawal may contain more of the weaker token.&lt;/p&gt;

&lt;p&gt;Some SyncSwap pools let you deposit one token, but part is traded into the other. I would use that option only after checking the resulting amounts and cost. One-token entry does not turn a two-token pool into a one-token holding.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do you check before signing?
&lt;/h2&gt;

&lt;p&gt;For a trade, select the network, token pair and amount, then read the route, expected output, minimum received and gas estimate. If an approval appears, check its token, spending amount and contract. Confirm the swap only while its quote still meets your target.&lt;/p&gt;

&lt;p&gt;For a pool, open its deposit screen and check the two token amounts, your share and any fee for an uneven deposit. After confirmation, check the position in your wallet or pool screen. When you withdraw, review the current token mix and gas before signing.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Pool reward dilution: estimate your share after new farmers join</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Thu, 29 Oct 2026 09:52:26 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/pool-reward-dilution-estimate-your-share-after-new-farmers-join-41gi</link>
      <guid>https://dev.to/milton_altenwert/pool-reward-dilution-estimate-your-share-after-new-farmers-join-41gi</guid>
      <description>&lt;p&gt;Your reward falls when new farmers increase the eligible stake but the pool keeps distributing the same amount. To estimate the change, compare your share of eligible stake before and after they join, then check whether the reward rate or schedule also changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Calculate how new deposits change your share
&lt;/h2&gt;

&lt;p&gt;Your estimated reward is the pool’s reward for a period multiplied by your fraction of the eligible stake. If rewards are distributed continuously, the same calculation applies to the emission rate, such as tokens per day.&lt;/p&gt;

&lt;p&gt;Say a pool has 1,000 eligible tokens staked, including your 100. If it distributes 10 reward tokens per day, your share is 10%, or about 1 token per day. If new farmers add 400 eligible tokens and the rate stays at 10 per day, your share falls to 100 ÷ 1,400, or about 7.14%—roughly 0.71 reward tokens per day.&lt;/p&gt;

&lt;p&gt;Compare that with a second case: new farmers add the same 400 tokens, but the pool’s daily rewards rise from 10 to 14. Your share is still 7.14%, but the estimate becomes 1 reward token per day. The key is to check both the denominator (eligible stake) and the rewards available over the same period.&lt;/p&gt;

&lt;p&gt;Before calculating, identify the values the pool actually uses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your eligible position, after any multiplier or boost.&lt;/li&gt;
&lt;li&gt;The pool’s total eligible stake, not necessarily the token balance shown on a general pool page.&lt;/li&gt;
&lt;li&gt;The reward rate or total rewards scheduled for your chosen period.&lt;/li&gt;
&lt;li&gt;The schedule’s start and end dates, and the reward token.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check what a pending or failed transaction changed
&lt;/h2&gt;

&lt;p&gt;A pending deposit usually has not changed your active position yet; a failed transaction generally did not stake the intended amount. Check the transaction receipt on the relevant chain, then check your staked balance and the pool’s eligible total. A wallet’s pending display alone cannot tell you whether the pool has credited the deposit.&lt;/p&gt;

&lt;p&gt;When using the &lt;a href="https://dune.com/jack_defi_web3/sushiswap-4-checks-before-trading-or-providing-liquidity" rel="noopener noreferrer"&gt;SushiSwap exchange&lt;/a&gt;, distinguish a token swap from a farm deposit: the swap exchanges tokens, while the farm contract determines whether a position earns its scheduled rewards. A transaction can therefore succeed as a swap but leave you with no farm stake if the separate deposit did not complete. On a SushiSwap farm, use the pool’s own position and reward figures for the calculation, and confirm the selected chain and pool before retrying a failed action.&lt;/p&gt;

&lt;p&gt;If a transaction is still pending, do not submit the same deposit again until you know its status; a second transaction could create a larger position if the first later confirms. If it failed, inspect the receipt’s failure reason and your wallet balance before retrying. The failure may concern the deposit itself, an approval, or another required step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use the estimate to decide what to do next
&lt;/h2&gt;

&lt;p&gt;Recalculate when the pool’s total stake or reward schedule changes, and compare estimates over the same time window. If your position is 100 of 1,400 eligible tokens and the pool distributes 14 tokens daily, estimate about 1 token daily before accounting for changing stake, boosts, or claim conditions.&lt;/p&gt;

&lt;p&gt;An advertised APR is an annualized estimate, not a promise that your current daily reward will continue. It can assume a particular token price, stake total, or reward rate; APY also assumes rewards are reinvested. For a practical decision, use the pool’s current eligible stake and schedule, then account for any transaction costs and the value of the reward token. SushiSwap users should also verify whether the farm has a multiplier or tier, since that can make eligible stake differ from the number of tokens deposited.&lt;/p&gt;

&lt;p&gt;In short, estimate your share as your eligible stake divided by total eligible stake, then multiply by the rewards for the same period. If your transaction is pending or failed, first confirm what the chain and pool actually recorded; only then is the dilution estimate useful.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What Is a Mantle Treasury Funding Cycle and How Does It Work?</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Fri, 23 Oct 2026 09:00:59 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/what-is-a-mantle-treasury-funding-cycle-and-how-does-it-work-4dem</link>
      <guid>https://dev.to/milton_altenwert/what-is-a-mantle-treasury-funding-cycle-and-how-does-it-work-4dem</guid>
      <description>&lt;p&gt;For recurring payouts, set a target balance on Mantle Network and replenish it in planned batches from Ethereum before the balance reaches your minimum operating level. That turns bridge use into a treasury routine with clear owners, limits and records; Mantle Bridge is the route for moving assets between the two networks.&lt;/p&gt;

&lt;p&gt;A funding cycle is a liquidity decision, while &lt;a href="https://splytgenesis.com/mantle-bridge-which-route-to-choose-and-how-to-fix-delays/" rel="noopener noreferrer"&gt;how Mantle Bridge handles route delays&lt;/a&gt; is an execution question: the first decides when and how much to move, and the second concerns what happens to a transfer in progress. Keep those decisions separate in your runbook so a delayed transfer does not become an excuse to send a duplicate.&lt;/p&gt;

&lt;h2&gt;
  
  
  What balance should the team keep on Mantle?
&lt;/h2&gt;

&lt;p&gt;Set the target from expected outflows during the time it would take your team to notice a shortfall and replenish funds. Include payout value, transaction gas, and a reserve for an unusually busy day; a balance sized only to the average day can run out just when an urgent payout arrives.&lt;/p&gt;

&lt;p&gt;Use recent activity rather than a round number. For example, if payouts usually total 12,000 USDT per business day and a replenishment decision happens every two days, a starting target might cover several days of outflows plus a separate gas reserve. That is an illustration, not a recommended Mantle balance: your own payout history, settlement windows and risk limits determine the right amount.&lt;/p&gt;

&lt;p&gt;Define three thresholds in the treasury policy:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Target:&lt;/strong&gt; the balance you aim to restore after a scheduled funding run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reorder point:&lt;/strong&gt; the level that triggers a replenishment, with enough funds left to cover expected payouts during the transfer and review period.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Emergency floor:&lt;/strong&gt; the minimum balance that prompts escalation, payout prioritization or an approved contingency plan.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the emergency floor distinct from the reorder point. If both are the same number, the team may start a transfer only after it has already lost its operating cushion.&lt;/p&gt;

&lt;h2&gt;
  
  
  How should a recurring transfer run work?
&lt;/h2&gt;

&lt;p&gt;A recurring run should move a calculated amount, verify it arrived, and record the evidence before the funds are treated as available for payouts. Use a named operator and reviewer, even if the same person performs both roles on a small team; the second check can happen before signing or after settlement, according to your controls.&lt;/p&gt;

&lt;p&gt;Start by checking the current balance on Mantle Network and comparing it with the reorder point. Estimate upcoming payouts through the next planned run, then subtract the usable balance and add the reserve you intend to maintain. The result is the proposed transfer amount, subject to your approved limits and available funds on Ethereum.&lt;/p&gt;

&lt;p&gt;Before signing, confirm the asset, destination network, destination address, amount and expected fees in the wallet or treasury system. For USDT, verify the token contract and that the receiving account is set up to accept that asset on Mantle Network; a familiar ticker alone is not enough to establish that two token entries are the same asset. For ETH, decide how much belongs to payouts and how much is set aside for gas.&lt;/p&gt;

&lt;p&gt;After submitting through Mantle Bridge, save the source transaction identifier and record the status as pending. Mark the funds available only after checking the destination network for the resulting balance or transfer and confirming it matches the intended asset and amount, allowing for disclosed fees. A submitted source transaction is evidence that a request was made; it is not proof that the treasury can spend the funds on the destination.&lt;/p&gt;

&lt;h2&gt;
  
  
  How often should a team replenish funds?
&lt;/h2&gt;

&lt;p&gt;Choose a cadence that balances transfer overhead against the cost of holding excess funds on either network. Daily replenishment may suit frequent payouts or a volatile outflow pattern; a weekly run may suit predictable, lower-volume operations. The reorder point should still work between runs, so the calendar never becomes the only trigger.&lt;/p&gt;

&lt;p&gt;Batching can reduce operational work, but larger, less frequent transfers keep more working capital in one place and make a missed run more consequential. I would compare the cost of each run—including network gas and any bridge fee shown before confirmation—with the cost of holding the extra float. Use the actual quote and transaction record for the run rather than assuming fees are fixed.&lt;/p&gt;

&lt;p&gt;Set a cutoff time and a fallback owner for each scheduled run. If the balance crosses the reorder point after the cutoff, the policy should say whether to make an approved extra run, reduce or defer discretionary payouts, or escalate. A threshold alert is useful only if someone knows what action it authorizes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What records make the cycle auditable?
&lt;/h2&gt;

&lt;p&gt;Keep one record for each transfer that connects the treasury decision to both sides of the transaction. It should include the business purpose, approval, asset and amount, source and destination networks, addresses, quoted fee, submission time, source transaction identifier, destination evidence and final accounting entry.&lt;/p&gt;

&lt;p&gt;Reconcile the source debit and destination credit as a pair, including the fee and any timing difference. If the destination amount does not match, leave the item open and investigate the transaction details before posting a balancing adjustment. This catches common mistakes such as counting a pending transfer as settled or recording the gross source amount as the received amount.&lt;/p&gt;

&lt;p&gt;In the team runbook, I would set a target and emergency floor from observed payout demand, review the reorder point at a fixed interval, and require destination confirmation before funds enter the available balance. Then I would use Mantle Bridge for scheduled replenishments and retain each run’s evidence alongside the approval and accounting record.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>When Reversing a Cross-Chain Swap, Check Pool Depth</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Thu, 22 Oct 2026 17:54:20 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/when-reversing-a-cross-chain-swap-check-pool-depth-36db</link>
      <guid>https://dev.to/milton_altenwert/when-reversing-a-cross-chain-swap-check-pool-depth-36db</guid>
      <description>&lt;p&gt;Reverse swaps can return less than you expect because each direction meets different pool depth and price impact. A quote for A to B does not promise that B to A will undo the trade.&lt;/p&gt;

&lt;p&gt;A cross-chain aggregator compares available routes between assets on different networks. For example, &lt;a href="https://crypto-today.news/thor-swap-types-and-the-trade-offs-treasury-teams-face/" rel="noopener noreferrer"&gt;thor swap&lt;/a&gt; brings that route comparison into one interface; its quote depends on the direction and amount you enter.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does the reverse quote change?
&lt;/h2&gt;

&lt;p&gt;Each pool holds reserves of two assets, and a trade changes their balance. The pool’s pricing curve means a larger trade gets a worse rate as it uses more of the available depth.&lt;/p&gt;

&lt;p&gt;Say a pool has 100 units of A and 10,000 of B, with no fees for this illustration. Swapping 10 A returns about 909 B; swapping those 909 B back returns about 8.3 A. The difference comes from moving along the curve twice, not from a simple reversed exchange rate.&lt;/p&gt;

&lt;p&gt;Cross-chain routes may use more than one pool, so each leg adds its own price impact and cost. THORChain’s swap formula shows how pool balances and trade size determine output; the same direction check matters when comparing routes in thor swap.&lt;/p&gt;

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

&lt;p&gt;Compare the final amount you receive for the same input, in each direction. A quoted rate alone can hide the effect of pool depth, network fees, and any service fee on that route.&lt;/p&gt;

&lt;p&gt;Look for the route’s price impact, which estimates how much your trade shifts the pool price. Then check the minimum output: this is the least the swap will deliver before it fails, based on your slippage setting. Slippage is the allowed gap between the quote and the executed result.&lt;/p&gt;

&lt;p&gt;Pool depth can change between quotes as other trades arrive. THORChain’s public pool data reports live pool depths, which helps explain why a route’s reverse quote may change even when the asset pair stays the same.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you check before swapping?
&lt;/h2&gt;

&lt;p&gt;Use the route and amount you actually plan to trade, then compare both directions separately.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Enter the asset you will send, the asset you need, and the exact amount.&lt;/li&gt;
&lt;li&gt;Record the quoted output, route, price impact, network costs, and minimum output.&lt;/li&gt;
&lt;li&gt;Reverse the asset pair and enter the amount you would receive; read the new quote rather than inverting the first rate.&lt;/li&gt;
&lt;li&gt;If the result is poor, compare another route or reduce the amount, then request a fresh quote before approving.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For a one-time task, proceed only when the minimum output still meets your need after costs. If it does not, lower the trade size or wait for deeper liquidity, then quote again.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>4 Checks Before Approving a Wallet Bridge Transfer</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Thu, 22 Oct 2026 06:32:51 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/4-checks-before-approving-a-wallet-bridge-transfer-2mb6</link>
      <guid>https://dev.to/milton_altenwert/4-checks-before-approving-a-wallet-bridge-transfer-2mb6</guid>
      <description>&lt;p&gt;Check the destination token, amount received, wallet network, and route before approving a bridge transfer; the quote depends on the route and current network conditions. If you are used to an exchange, think of this as checking the withdrawal address and final amount before sending. With your own wallet, you also pay network fees and may need to finish the transfer on the destination chain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the Quote as the Amount You Expect to Receive
&lt;/h2&gt;

&lt;p&gt;The destination amount is the useful number to compare with your plan. A transfer may deduct a route fee or lose a small amount through a swap, so the amount sent can differ from the amount received.&lt;/p&gt;

&lt;p&gt;For example, if you start with 100 tokens and the quote says you will receive 98.7, use 98.7 when deciding whether the transfer is worthwhile. On Portal Bridge, the selected route determines the steps and costs shown before you approve. The &lt;a href="https://graph.org/Which-Portal-Bridge-Transfer-Type-Fits-Your-Integration-10-21" rel="noopener noreferrer"&gt;how to use Portal Bridge&lt;/a&gt; steps include selecting the chains and assets, then reviewing the transfer before you send it.&lt;/p&gt;

&lt;p&gt;Network fees, often called gas, pay for transactions on a blockchain. You may need some of the source chain’s native coin to start; some routes may also need a destination transaction or destination gas. Fees change with network traffic, so there is no single reliable flat cost for every transfer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Confirm the Asset, Chain, and Wallet Before Signing
&lt;/h2&gt;

&lt;p&gt;Check that the destination token is the one you intend to hold, and that the destination chain matches your plan. A token with the same ticker can be a different asset, especially if one version is wrapped, meaning it represents a token from another chain.&lt;/p&gt;

&lt;p&gt;Suppose you want USDC on Ethereum but your wallet is set to another network. Confirm the destination says Ethereum and the token is the expected USDC version before continuing. Also check the receiving address; if you connect the same wallet on both chains, confirm the displayed address is yours.&lt;/p&gt;

&lt;p&gt;A wallet approval is permission for a specific action, such as letting a bridge contract use a token. Read the wallet’s prompt and compare its network and amount with the transfer screen. If the prompt asks for a different amount or chain, reject it and review the setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Follow the Route’s Steps Until the Transfer Completes
&lt;/h2&gt;

&lt;p&gt;The route decides what happens after your source-chain transaction. On a lock-and-mint route, the source tokens are locked, a signed message confirms that transaction, and destination tokens are released or minted; another route may swap assets or complete more steps automatically.&lt;/p&gt;

&lt;p&gt;Use these four checks before you approve:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Choose the source and destination chains.&lt;/strong&gt; Confirm your source wallet is connected to the chain holding your tokens.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Select the exact asset and amount.&lt;/strong&gt; Check the destination asset and read the estimated received amount.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the route and costs.&lt;/strong&gt; Look for any route fee, swap impact, estimated wait, and whether destination gas or a second transaction is needed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Approve, then track completion.&lt;/strong&gt; Confirm the wallet prompt matches your review. Keep the transaction record and follow the route’s status until the funds arrive.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A source transaction can succeed before the destination transfer finishes. If the screen says you must claim or redeem the funds, that means completing a second transaction on the destination chain; follow the route’s instructions and keep enough native coin for its fee. Portal Bridge shows the route-specific flow, so use that flow to tell whether you are waiting or still need to act.&lt;/p&gt;

&lt;p&gt;Before sending a larger amount, I would make a small test transfer when the route or token is unfamiliar. Check the received asset and any extra steps, then use the same route for the rest.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>BaiBai explained: swaps, routes and costs on Base</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Wed, 21 Oct 2026 15:06:01 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/baibai-explained-swaps-routes-and-costs-on-base-411</link>
      <guid>https://dev.to/milton_altenwert/baibai-explained-swaps-routes-and-costs-on-base-411</guid>
      <description>&lt;p&gt;BaiBai is a decentralized exchange for swapping tokens from your wallet on Base, when someone can fill your trade. To see what a trade would return, use &lt;a href="https://baibai.pro" rel="noopener noreferrer"&gt;BaiBai&lt;/a&gt; for a live quote from professional traders and other Base trading sources. A BaiBai swap shows the expected token amount before you sign.&lt;/p&gt;

&lt;h2&gt;
  
  
  BaiBai swaps combine live quotes and Base liquidity
&lt;/h2&gt;

&lt;p&gt;Each trade checks prices from market makers and other supported trading sources. A market maker is a trader ready to buy or sell at a quoted price. The exchange’s PropAMM is a pool where market makers update those prices as markets and their token holdings change.&lt;/p&gt;

&lt;p&gt;The exchange also uses liquidity routing. That means it looks for enough tokens across several sources and chooses a route for your trade. If one source has a good price for only part of your order, the route can fill the rest elsewhere.&lt;/p&gt;

&lt;p&gt;Say you swap 1,000 USDC for ETH. A market maker might fill 200 USDC at its quoted price, while another pool fills 800 USDC. The useful comparison is the combined ETH you receive, after costs, against a quote for the same 1,000 USDC elsewhere.&lt;/p&gt;

&lt;p&gt;You sign from your own wallet, and the trade settles onchain. Your tokens do not need to move into a separate trading account. A live quote can change before settlement, so check the amount shown at the final signing step.&lt;/p&gt;

&lt;h2&gt;
  
  
  The final quote and costs decide which trade is better
&lt;/h2&gt;

&lt;p&gt;Compare the amount of the token you will receive for the same input, pair and trade size. A common mistake is comparing a small trade’s attractive rate with a much larger order. Enter your actual amount in each option; a larger order may exhaust the cheapest available tokens.&lt;/p&gt;

&lt;p&gt;Check the minimum received amount too. This is the lowest output you accept if the price moves before settlement. For example, a quote of 0.280 ETH with a 0.5% allowance sets the minimum at 0.2786 ETH. If the route cannot meet that minimum, the trade should not fill.&lt;/p&gt;

&lt;p&gt;The published trading fee is typically around 0.1%, or about 1 USDC on a 1,000 USDC trade. The service currently covers network gas for supported trades, so you can usually sign without holding ETH for the fee. Gas sponsorship is not guaranteed forever; review any wallet fee prompt before signing.&lt;/p&gt;

&lt;p&gt;To trade, connect your wallet, select Base, then choose the token to sell and the token to buy. Check each token’s contract address if its name could be shared by another token. Enter the amount, review the route and minimum received, then confirm.&lt;/p&gt;

&lt;p&gt;A first trade may request token approval. Approval gives the trade contract permission to spend that token, so inspect the spending limit in your wallet. After signing, check the trade receipt and your wallet balance for the amount actually received.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need to bridge to another chain first?
&lt;/h3&gt;

&lt;p&gt;No separate trading chain is needed when your tokens are already on Base. The route can use supported Base liquidity within the trade. If your funds are on another network, moving them to Base is a separate transfer that may have its own fee and delay. Confirm the destination network before sending tokens.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does the price guarantee cover any cheaper quote?
&lt;/h3&gt;

&lt;p&gt;The stated double-the-difference guarantee calls for a live comparison of the same token pair, trade size and moment. It also applies only to an amount the competing source could actually fill. An old screenshot or a better rate for a tiny trade does not establish a better price for your order. Compare executable output before relying on the guarantee.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What Happens When You Cancel a Partially Filled Limit Order?</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Wed, 21 Oct 2026 14:58:17 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/what-happens-when-you-cancel-a-partially-filled-limit-order-4i21</link>
      <guid>https://dev.to/milton_altenwert/what-happens-when-you-cancel-a-partially-filled-limit-order-4i21</guid>
      <description>&lt;p&gt;Canceling a partially filled limit order stops its remaining quantity only when the cancellation takes effect under that order system’s rules; any fill that wins the race may still settle. The filled portion stays filled, while the fate and availability of the remainder depend on whether the order is held onchain, by a service, or represented by a signed authorization.&lt;/p&gt;

&lt;h2&gt;
  
  
  What exactly does cancellation remove?
&lt;/h2&gt;

&lt;p&gt;Cancellation targets the &lt;em&gt;unfilled remainder&lt;/em&gt;, not the trade already executed. If an order was for 10 tokens and 4 have filled, a successful cancellation should leave the 4-token trade intact and prevent the other 6 from filling afterward.&lt;/p&gt;

&lt;p&gt;The important distinction is between an interface showing “cancel requested” and the order becoming unfillable. Some systems remove an order from an offchain order book when they receive a cancellation request; others require an onchain transaction or an onchain nonce change. Until the relevant state change is recognized, a filler may still submit a valid fill.&lt;/p&gt;

&lt;p&gt;For example, if a staged rebalance leaves 6 tokens unfilled and you intend to swap that remainder, first verify the order’s final state and available balance. On &lt;a href="https://tokenbearing.pages.dev/biswap-limit-orders-in-2026-how-partial-fills-work/" rel="noopener noreferrer"&gt;Biswap exchange&lt;/a&gt;, that check matters before routing the replacement trade: an order still eligible to fill can compete for the same inventory you expect to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can a fill land while cancellation is pending?
&lt;/h2&gt;

&lt;p&gt;A fill and a cancellation are competing state changes, and the chain’s transaction ordering decides which takes effect first. If a filler’s transaction executes before the cancellation, that fill can succeed; if cancellation executes first and invalidates the order, a later fill should fail its validity check.&lt;/p&gt;

&lt;p&gt;On an EVM chain, “submitted” does not mean “final.” A transaction can sit in the mempool, be replaced with a higher-fee transaction using the same sender nonce, or be included after another transaction that changes the order state. A wallet’s pending indicator is therefore weaker evidence than a confirmed transaction receipt plus an order status that reflects the resulting state.&lt;/p&gt;

&lt;p&gt;The mechanism varies by order design. A contract-held order may be canceled through a state-changing call, while a signed order can remain offchain and be invalidated through a nonce, hash, or filled-amount check. CoW Protocol’s limit-order documentation distinguishes an API cancellation from an onchain cancellation, illustrating why the cancel button alone does not identify the guarantee you have.&lt;/p&gt;

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

&lt;p&gt;Token availability depends on how the order was funded. If assets were escrowed in a contract, the unfilled balance may need to be released or claimed after cancellation; if the order uses an allowance or signature without escrow, the tokens may have remained in your wallet, though that authorization can still permit a fill until invalidated.&lt;/p&gt;

&lt;p&gt;Cancellation is not necessarily free. A cancellation transaction that writes to an EVM chain consumes gas, with the cost set by current network demand and transaction complexity; an offchain cancellation may have no direct chain fee but can provide a weaker guarantee until the protocol or settlement mechanism records it. Check whether you are paying for an immediate onchain invalidation, a service request, or only a user-interface action.&lt;/p&gt;

&lt;p&gt;Do not assume cancellation reverses gas, protocol fees, or price exposure from the already-filled portion. If the order filled 40% before cancellation, that executed quantity remains a trade, and any fee associated with it is governed by the order’s fee rules. Reconcile the actual fill amount and returned or still-available balance before calculating the replacement order size.&lt;/p&gt;

&lt;h2&gt;
  
  
  How should you cancel quickly and verify the result?
&lt;/h2&gt;

&lt;p&gt;Use the cancellation path that invalidates the order at the layer where fills are authorized, then verify that state before reusing the remainder. A fast offchain request can clear a displayed order quickly, but if the protocol supports an onchain invalidation and a fill race matters, the confirmed onchain state is the meaningful checkpoint.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Record the order ID or hash, the filled amount, and the remaining amount before canceling.&lt;/li&gt;
&lt;li&gt;Submit cancellation and monitor its status; if it is an EVM transaction, confirm inclusion and check for a revert.&lt;/li&gt;
&lt;li&gt;Refresh the order’s authoritative status and confirm the remainder is no longer fillable.&lt;/li&gt;
&lt;li&gt;Check token balances and allowances, then size any replacement trade from the balance actually available.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A practical edge case is a cancel transaction that remains pending while the market moves toward your limit. Speeding it up can reduce the window, but replacement works only if the wallet uses the same sender and nonce; sending a second cancel with a different nonce may leave both transactions competing. The next step is to verify the order state and balance together, then route only the confirmed residual amount.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Match token units to the destination chain</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Sat, 17 Oct 2026 10:29:13 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/match-token-units-to-the-destination-chain-44hp</link>
      <guid>https://dev.to/milton_altenwert/match-token-units-to-the-destination-chain-44hp</guid>
      <description>&lt;p&gt;To receive the asset you need, match both the token and its units to the destination chain. A balance can look different because tokens use different decimal places, or because the destination holds a different token altogether. These are separate problems, and the fix depends on which one caused the delay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what the destination chain accepts
&lt;/h2&gt;

&lt;p&gt;First, check the destination network and the exact token you expected to receive. A token’s name and ticker, such as USDC, do not prove it is the same asset: a chain may have several tokens with that name. The token address on Ethereum, or the mint address on Solana, identifies the specific token.&lt;/p&gt;

&lt;p&gt;Decimal places set how a token’s smallest units appear as a human-readable balance. For example, one USDC with six decimals is stored as 1,000,000 smallest units; one ETH with 18 decimals is 1,000,000,000,000,000,000 wei. If acrossbridge is part of your recovery, an &lt;a href="https://kaitlynadlz621296.acidblog.net/74767814/how-long-does-acrossbridge-take-for-treasury-transfers" rel="noopener noreferrer"&gt;acrossbridge bridge&lt;/a&gt; can move and swap assets between chains in one flow, so you can target the asset the destination chain uses. Check the intended destination token before starting another transfer.&lt;/p&gt;

&lt;p&gt;Decimals do not change a token’s value or identity. A token with six decimals is not worth less than one with 18. A swap changes one asset into another at an exchange rate; a bridge may carry an asset to another chain in a corresponding form. The destination token’s identity and available route decide what arrives.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the pending or failed status before retrying
&lt;/h2&gt;

&lt;p&gt;A pending source transaction has not finished sending funds, so a destination balance may not appear yet. Open the source transaction in that chain’s explorer, a public record of transactions, and check whether it is still pending, confirmed, or failed. A confirmed source transaction means the send happened, but the receiving step can still be processing.&lt;/p&gt;

&lt;p&gt;If the source transaction failed, check the wallet and transaction record before retrying. Confirm whether the original tokens remain in your wallet or were returned; avoid sending again while the outcome is unclear. If the source shows confirmed but the destination has no balance, verify the destination network and token address or mint first. Also check whether your wallet can display that token; a missing display does not always mean the tokens failed to arrive.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the right correction for the mismatch
&lt;/h2&gt;

&lt;p&gt;Use the example of sending 1.25 units of a token with 18 decimals and expecting a destination token with six. The raw source amount is 1,250,000,000,000,000,000 smallest units. If the destination asset is the same token represented with six decimals, a correct transfer still displays 1.25 tokens; the software handles the unit conversion. Do not manually alter a raw amount unless the transaction details specifically require it.&lt;/p&gt;

&lt;p&gt;If you received the wrong token, or need a different destination asset, decimals alone cannot fix it. You need a swap into the token the destination accepts. For example, a route from ETH to USDC converts assets, and the USDC amount depends on the exchange rate and fees at execution. Acrossbridge may suit this task when you need a cross-chain move and a swap in one flow; check the destination asset before authorising a fresh transaction.&lt;/p&gt;

&lt;p&gt;My decision rule is simple: confirm the source outcome, identify the destination token, then retry only if the original funds are accounted for and the new route matches both.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why should you wait before swapping Monero mining payouts?</title>
      <dc:creator>Milton Altenwerth</dc:creator>
      <pubDate>Fri, 16 Oct 2026 23:57:08 +0000</pubDate>
      <link>https://dev.to/milton_altenwert/why-should-you-wait-before-swapping-monero-mining-payouts-537a</link>
      <guid>https://dev.to/milton_altenwert/why-should-you-wait-before-swapping-monero-mining-payouts-537a</guid>
      <description>&lt;p&gt;Wait until your mining payout is spendable before sending it through a Monero bridge. Pool payouts often need 10 Monero blocks to mature; solo-mined block rewards need 60, or about two hours at Monero’s usual block pace. Then check how much remains after fees and what asset you expect to receive.&lt;/p&gt;

&lt;h2&gt;
  
  
  When can you spend a mining payout?
&lt;/h2&gt;

&lt;p&gt;A pool payout is a regular transaction from the pool’s wallet, while a solo-mined reward comes from a newly mined block. Pool payouts commonly become spendable after 10 confirmations; solo-mined rewards unlock after 60 blocks. A confirmation means another block has been added after the payment.&lt;/p&gt;

&lt;p&gt;At Monero’s roughly two-minute block time, those waits are about 20 minutes and two hours. Actual timing varies with block production. Your wallet may show the funds before they are spendable, so check its unlocked balance before starting a swap.&lt;/p&gt;

&lt;p&gt;Pool payout thresholds matter too. If your balance is below the pool’s minimum payout, it may stay in the pool until the threshold is met. Check the pool’s payout rules if the expected payment has not arrived.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much of the payout will reach the other chain?
&lt;/h2&gt;

&lt;p&gt;Estimate the amount using the payout that is actually unlocked, then subtract the Monero transaction fee and the route’s quoted costs. For example, if 0.50 XMR is unlocked, the wallet estimates a 0.0001 XMR network fee, and the route quotes 0.48 XMR worth of destination coins, compare that quote with your target before sending. The figures are illustrative; network fees and swap quotes change.&lt;/p&gt;

&lt;p&gt;If your payout is spendable and you want value on Bitcoin or another chain, a &lt;a href="https://aboutdefi.github.io/a-monero-bridge-swap-starts-with-checking-the-route/" rel="noopener noreferrer"&gt;Monero bridge transfer&lt;/a&gt; is the cross-chain leg: XMR leaves Monero and another asset arrives on the destination chain. A bridge and swap service can handle that move in one flow; the quoted receive amount and expected wait are the practical comparison points.&lt;/p&gt;

&lt;p&gt;Small payouts can be poor candidates for a swap because fixed network costs take a larger share. If the quote leaves too little value after costs, waiting for another payout may make more sense.&lt;/p&gt;

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

&lt;p&gt;Mining connects your pool account or mining activity to the payout address. When XMR is swapped for an asset on a more transparent chain, later transactions may reveal more about that asset’s movement. Monero’s privacy does not carry over automatically.&lt;/p&gt;

&lt;p&gt;Before sending, check these three details:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The wallet shows the payout as unlocked and spendable.&lt;/li&gt;
&lt;li&gt;The receive amount covers your target after all quoted costs.&lt;/li&gt;
&lt;li&gt;The destination network and asset match where you need the funds.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For an occasional payout, I would first wait for unlock, then compare the quote with the amount you need to receive. If it fits, send only after checking the destination details; otherwise, let the next pool payout build the amount.&lt;/p&gt;

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