<?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: Merissa Stemler</title>
    <description>The latest articles on DEV Community by Merissa Stemler (@cryptoexplorere).</description>
    <link>https://dev.to/cryptoexplorere</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%2F4108264%2F545894d9-15e4-4f45-9da0-b5d0786cc132.png</url>
      <title>DEV Community: Merissa Stemler</title>
      <link>https://dev.to/cryptoexplorere</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cryptoexplorere"/>
    <language>en</language>
    <item>
      <title>What Is cowswap Used for in DeFi: Where Does a Trade Go?</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Mon, 16 Nov 2026 23:10:02 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/what-is-cowswap-used-for-in-defi-where-does-a-trade-go-1023</link>
      <guid>https://dev.to/cryptoexplorere/what-is-cowswap-used-for-in-defi-where-does-a-trade-go-1023</guid>
      <description>&lt;p&gt;cowswap is a decentralized exchange interface built on CoW Protocol, the intent-based trading system that coordinates execution. That answers its DeFi use case: traders state acceptable exchange terms through the interface, while the protocol finds and settles a valid trade. For a trader, &lt;a href="https://cowswap.us" rel="noopener noreferrer"&gt;cowswap&lt;/a&gt; shifts the decision from choosing an AMM route to specifying the result a route must deliver.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does the Interface Submit to CoW Protocol?
&lt;/h2&gt;

&lt;p&gt;The interface submits a signed trade intent; CoW Protocol’s off-chain orderbook groups it with other intents for a batch auction. A trade intent is a signed message describing acceptable exchange terms. It gives a solver room to find a route, while requiring the final trade to satisfy the signed constraints.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Order entry:&lt;/strong&gt; the trader expresses the desired token exchange through the interface.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Batch auction:&lt;/strong&gt; solvers propose ways to satisfy grouped intents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Settlement:&lt;/strong&gt; a selected solution exchanges tokens on-chain under the signed terms.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Say you want to exchange USDC for DAI on one chain. Your intent specifies the tokens, amount, and acceptable output. It leaves route selection to solvers rather than committing to a particular pool. CoW Protocol gathers that intent with others, and solvers compete to construct settlements. The selected solution executes on-chain, where the exchange is checked against your signed constraints.&lt;/p&gt;

&lt;p&gt;The distinction matters when comparing trading choices. The interface supplies order entry; CoW Protocol supplies the auction and settlement system. Treating the interface as its own liquidity pool leads to the wrong comparison with a direct AMM swap. The same pool might supply liquidity in either case.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Can a Solver Find the DAI?
&lt;/h2&gt;

&lt;p&gt;A solver can source DAI from an opposing trade intent, an external liquidity venue such as Uniswap, or a combination. If another trader wants to exchange DAI for USDC, the solver may match the two orders. That match is a Coincidence of Wants: their demands offset each other without requiring an AMM for the matched portion.&lt;/p&gt;

&lt;p&gt;Suppose the opposing order covers only part of your USDC sale. The solver can match that portion, then obtain the remaining DAI from a Uniswap pool. Your order still began through the interface; Uniswap supplied liquidity to the solver’s settlement. This is why the source of liquidity matters more than the name of the order-entry interface.&lt;/p&gt;

&lt;p&gt;Competing solvers can propose different combinations of matched demand and external liquidity. CoW Protocol evaluates their proposed settlements, then executes selected solutions on-chain. The &lt;a href="https://docs.cow.fi/cow-protocol/concepts/introduction/fair-combinatorial-auction" rel="noopener noreferrer"&gt;batch-auction documentation&lt;/a&gt; explains how intents are grouped, bids are compared, and winning combinations are selected. Those rules allow a solver to improve an order by handling several traders together.&lt;/p&gt;

&lt;p&gt;In practice, traders use this architecture for swaps, limit orders with a required price, and TWAP orders that spread execution over time. Those order types change an intent’s conditions or timing. Solvers handle route selection and settlement within those conditions.&lt;/p&gt;

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

&lt;h3&gt;
  
  
  Is cowswap MEV protected?
&lt;/h3&gt;

&lt;p&gt;Trading through the interface reduces exposure to transaction-ordering attacks because intents remain off-chain until a solver submits a batch settlement. A public pending AMM swap can reveal a route that an attacker may trade around. Batch execution and uniform prices for the same directed pair make reordering orders less useful. Execution still depends on a valid solution under the signed terms.&lt;/p&gt;

&lt;h3&gt;
  
  
  cowswap vs Uniswap execution price?
&lt;/h3&gt;

&lt;p&gt;Compare executable net DAI output for the same USDC amount, network, and moment. A direct Uniswap swap uses its chosen AMM path; a solver may match opposing demand, use Uniswap liquidity, or combine both. Choose by the amount you can receive under the order’s constraints.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to use KyberSwap for a token swap</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Mon, 16 Nov 2026 16:43:41 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/how-to-use-kyberswap-for-a-token-swap-4fjd</link>
      <guid>https://dev.to/cryptoexplorere/how-to-use-kyberswap-for-a-token-swap-4fjd</guid>
      <description>&lt;p&gt;KyberSwap lets you swap tokens on one network by connecting a wallet, choosing the network and tokens, reviewing the quote and minimum received, approving the token if prompted, and confirming the swap in your wallet. Open &lt;a href="https://kyberswap.dev" rel="noopener noreferrer"&gt;KyberSwap&lt;/a&gt; to find a route for the pair you want to trade. The KyberSwap Aggregator finds routes across liquidity sources; your wallet authorizes each action.&lt;/p&gt;

&lt;h2&gt;
  
  
  What must be ready before using KyberSwap?
&lt;/h2&gt;

&lt;p&gt;A KyberSwap swap needs a self-custody wallet, the token you want to sell, and some of the network’s native token to pay gas. Gas is the network fee for recording a transaction. You need enough for the swap and, if your sell token requires an on-chain approval, that separate transaction too.&lt;/p&gt;

&lt;p&gt;Choose the network where your sell token already sits, then make sure the app and wallet show the same network. The aggregator supports networks including Ethereum, BNB Chain, Polygon, Arbitrum and Base. ETH pays gas on Ethereum, Arbitrum and Base; each network requires its own native-token balance. Having ETH on Ethereum, for instance, does not supply gas for a swap on Base.&lt;/p&gt;

&lt;p&gt;Have the buy token’s contract address ready from a source you trust. A ticker is only a short name: different contracts can use the same one. Matching the contract address and network helps you avoid selecting a copycat token.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you complete the swap and read each wallet prompt?
&lt;/h2&gt;

&lt;p&gt;A same-chain swap moves from a wallet connection to a quote, a possible token approval, and a final swap transaction. Read the prompt at each stage for the permission it actually requests.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Open the official site and connect your wallet.&lt;/strong&gt; Select your wallet, such as MetaMask, and review the account and network in its connection request. Connecting lets the app see your selected public address and suggest transactions. It does not itself authorize a token transfer. Keep the wallet open for later prompts; a connection alone has not started the trade.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Select the network.&lt;/strong&gt; Match it to the network holding your sell token and native gas balance. If the wallet asks to switch networks, read the requested destination before accepting. A same-chain swap starts and ends on this selected network.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose the sell token, buy token and amount.&lt;/strong&gt; Compare each token’s contract address with the address you intended to use, especially when several results share a ticker. Say you hold USDC on Base and want to receive another token there. Select the Base version of each token, enter the amount of USDC to sell, and leave enough ETH on Base for gas.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the quote and slippage tolerance.&lt;/strong&gt; The route shows where the aggregator expects to source liquidity. Compare the expected output with the estimated gas: a route offering more tokens can also cost more to execute. Price impact describes how much your trade size moves the market price. Slippage tolerance is the adverse price movement you allow before execution. &lt;strong&gt;Minimum received&lt;/strong&gt; is the quoted output reduced by that tolerance; if the trade would return less, it should revert rather than complete at that rate. A higher tolerance permits a worse result, so choose one you can accept. The &lt;a href="https://docs.kyberswap.com/user-guide/swap/instantly-swap-at-the-best-rate" rel="noopener noreferrer"&gt;Aggregator user guide&lt;/a&gt; explains these quote fields and the approval and confirmation stages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Approve the sell token if prompted.&lt;/strong&gt; An approval gives a specified smart contract permission to spend that token up to an allowance. In the wallet prompt, inspect the token, the contract receiving permission, the spending cap and any gas fee. A cap equal to this trade limits the allowance; a larger cap can cover later trades. Approval &lt;em&gt;does not execute the swap&lt;/em&gt;. An on-chain approval is its own transaction, so wait for it to confirm before continuing. Some tokens instead offer a permit: a signed message granting an allowance without a separate gas payment. If an existing allowance is sufficient, you may see no approval prompt. You may need to approve again if a later trade exceeds the remaining allowance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the swap separately.&lt;/strong&gt; Review the latest output and minimum received before sending the trade; a refreshed route or price can change the quote. Then read the wallet’s transaction request, particularly its network and gas estimate, and confirm it. This prompt submits the swap transaction. The wallet may describe a contract interaction rather than spell out the token pair, which is why the app’s final trade details matter. If the amount or network is wrong, reject the prompt and correct the trade first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wait for confirmation and verify the result.&lt;/strong&gt; Open the swap transaction hash on that network’s block explorer. A submitted transaction can still be pending; look for a successful transaction and the received token transfer to your address. Then view the new token balance in your wallet on the same network. If the explorer shows success but the wallet omits the token, add its verified contract address to the wallet’s token list. The swap is complete when the explorer shows success and the wallet shows the received balance.&lt;/li&gt;
&lt;/ol&gt;

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

&lt;h3&gt;
  
  
  Is KyberSwap safe to connect a wallet to?
&lt;/h3&gt;

&lt;p&gt;Connecting a wallet gives the app access to your selected public address; token spending requires a separate approval. Verify that you opened the official site, and treat an unexpected approval or signature request as a reason to stop. Review the allowance amount carefully: disconnecting a site does not revoke an approval already recorded on-chain.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does KyberSwap need an account or KYC?
&lt;/h3&gt;

&lt;p&gt;A standard same-chain wallet swap does not require you to create an account or complete an identity check in the swap flow. Your wallet supplies the address and confirms the transactions.&lt;/p&gt;

&lt;h3&gt;
  
  
  How to add the received token to the wallet?
&lt;/h3&gt;

&lt;p&gt;In MetaMask, select the network used for the swap and import the token using its verified contract address if the balance is missing. &lt;a href="https://support.metamask.io/manage-crypto/tokens/how-to-display-tokens-in-metamask/" rel="noopener noreferrer"&gt;MetaMask Support&lt;/a&gt; explains how to display a token by address. Use the explorer’s successful transfer as the first check that the token reached your wallet.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Does SunSwap Turn a Quote Into a Completed Trade?</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Fri, 06 Nov 2026 02:52:30 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/how-does-sunswap-turn-a-quote-into-a-completed-trade-45ad</link>
      <guid>https://dev.to/cryptoexplorere/how-does-sunswap-turn-a-quote-into-a-completed-trade-45ad</guid>
      <description>&lt;p&gt;SunSwap turns your token selection into a trade by quoting pool liquidity, then submitting a signed swap to smart contracts; the displayed output remains conditional until execution. On &lt;a href="https://sunswap.cc" rel="noopener noreferrer"&gt;SunSwap&lt;/a&gt;, SunSwap liquidity pools supply the assets behind that quote, while trade size, routing, and on-chain changes can affect what reaches your wallet.&lt;/p&gt;

&lt;h2&gt;
  
  
  SunSwap Quotes Follow Liquidity, Not Orders
&lt;/h2&gt;

&lt;p&gt;A quote reads available liquidity in smart contract pools, rather than matching your trade with another person’s order. Liquidity providers deposit assets that traders exchange through those pools. You select an input token, an output token, and an amount; the exchange calculates how much output the available pools can provide at that moment.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Pool depth:&lt;/strong&gt; More usable liquidity near the current price usually lets a trade move the price less.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trade size:&lt;/strong&gt; A larger input consumes more of that liquidity, so its average execution price can be worse than the price shown for a small trade.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Route:&lt;/strong&gt; A direct pool may handle the swap, or the trade may pass through an intermediary token and a second pool. Each leg has its own liquidity and fee.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Pool design matters as well. In a V2-style pool, exchanging assets changes its reserves and therefore its price. SunSwap V3 concentrates liquidity within price ranges, so a pool’s total deposits do not tell you how much is usable for your trade. The route and expected output are better evidence than the mere existence of a trading pair.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does the Displayed Output Actually Promise?
&lt;/h2&gt;

&lt;p&gt;The displayed output describes current execution; it does not promise that exact receipt. It accounts for the route’s pool prices, the effect of your trade on those prices, and pool fees. &lt;em&gt;Price impact&lt;/em&gt; is the change your own trade causes as it draws from pool liquidity. It is already part of the quote.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Slippage tolerance&lt;/em&gt; addresses a different change: execution becoming worse between the quote and the on-chain swap. The transaction uses that tolerance to set a minimum acceptable output. Other trades can change pool balances before yours executes, and a route with several pools has several places where conditions can move. If the route cannot satisfy the transaction’s limits, the swap fails instead of delivering an output below the limit.&lt;/p&gt;

&lt;p&gt;Read &lt;strong&gt;minimum received&lt;/strong&gt; alongside expected output before signing. It is the useful decision point: if that minimum would be an unacceptable exchange, reduce the trade size or inspect another available route. Raising tolerance merely permits a worse result; it does not create liquidity or improve the quoted price. Tokens that deduct an amount on transfer or restrict transfers can also change the effective receipt or prevent execution.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Wallet Signs Permissions and the Swap
&lt;/h2&gt;

&lt;p&gt;Your compatible TRON wallet selects the account, supplies the input assets, and signs the required transactions. For a TRC-20 input token, the swap contract may first need an allowance to spend it. That approval grants permission and can require its own transaction; it does not exchange any tokens. The later swap signature authorizes the actual trade under its stated conditions.&lt;/p&gt;

&lt;p&gt;Separate trading costs from network costs when reading the wallet prompt. Pool fees reduce the output available through each leg of the route. TRON contract execution also uses network resources, including Energy and Bandwidth; the amount depends on the contract work and resources available to your account. If resources are insufficient, TRX may be consumed. A separate approval adds its own network cost, even though it produces no swap output.&lt;/p&gt;

&lt;h2&gt;
  
  
  Settlement Requires Execution and Receipt
&lt;/h2&gt;

&lt;p&gt;A swap settles when its transaction succeeds on TRON and the output tokens reach the recipient. After you sign, the wallet broadcasts the transaction. The contracts then take the permitted input, exchange it through the selected pool or pools, update pool balances or active liquidity, and deliver output only if the execution conditions hold. A signature shows intent; a broadcast shows submission. Neither alone proves delivery.&lt;/p&gt;

&lt;p&gt;The transaction can fail if a pool changes enough to breach minimum received, a required transfer fails, or a token’s behavior conflicts with the route. A wallet notification may arrive before you have confirmed the result. Look for a successful on-chain transaction and the actual token receipt in the destination account; together they establish what settled and how much arrived.&lt;/p&gt;

&lt;p&gt;Make minimum received your standard pre-signing check, then compare it with the receipt after execution. That small habit keeps the quoted estimate, the amount you authorized as acceptable, and the amount delivered from becoming one confusing number.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>4 Steps to Price an Exact-Output Swap From Your Wallet</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:02:56 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/4-steps-to-price-an-exact-output-swap-from-your-wallet-em2</link>
      <guid>https://dev.to/cryptoexplorere/4-steps-to-price-an-exact-output-swap-from-your-wallet-em2</guid>
      <description>&lt;p&gt;If you are used to placing a buy order on a centralised exchange, an exact-output swap lets you set how many tokens you want to receive and puts a ceiling on how much you will spend. The pool’s current reserves determine the input quote, which can change before your wallet transaction executes.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Set the amount you want to receive
&lt;/h2&gt;

&lt;p&gt;An exact-output trade fixes the quantity of the token you buy; the required input is calculated from the pool. That reverses the more familiar exact-input swap, where you choose what to spend and accept the resulting output.&lt;/p&gt;

&lt;p&gt;For example, you might ask a pool to deliver exactly 2,000 USDC. Your wallet or trading interface then estimates the required input and asks you to allow up to a maximum. If a pending wallet action leaves you unsure whether to retry, check the network and transaction nonce first; &lt;a href="https://kendra-koepp-jmbobse3wz4gkzybw-fg_.justblogged.com/spookyswap-stuck-transaction-recovery-explained" rel="noopener noreferrer"&gt;how to recover a stuck SpookySwap transaction&lt;/a&gt; explains how to decide whether to wait, replace, or resubmit.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The pool’s reserves set the required input
&lt;/h2&gt;

&lt;p&gt;In a constant-product pool, the reserve balances shape the price: the larger your requested output is relative to the available output tokens, the more input the pool requires. The calculation uses the reserves at execution time and includes the pool’s trading fee.&lt;/p&gt;

&lt;p&gt;For a V2-style pool, let &lt;em&gt;x&lt;/em&gt; be the input-token reserve, &lt;em&gt;y&lt;/em&gt; the output-token reserve, and &lt;em&gt;z&lt;/em&gt; your desired output. If the fee is &lt;em&gt;f&lt;/em&gt;, the required input is approximately &lt;em&gt;x × z ÷ ((y − z) × (1 − f))&lt;/em&gt;. Contracts round the result up to the smallest token unit so the pool receives enough after the fee. The Uniswap V2 Core whitepaper describes the constant-product mechanism behind this calculation.&lt;/p&gt;

&lt;p&gt;Say a pool holds 100 ETH and 200,000 USDC, and you request 2,000 USDC with an illustrative 0.3% fee. The quote is about 1.013 ETH, before network gas. At the pool’s starting ratio, 2,000 USDC would correspond to 1 ETH; the extra input reflects both the fee and the price impact of removing USDC from the pool.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Your maximum input limits what the wallet can spend
&lt;/h2&gt;

&lt;p&gt;The maximum input is the most the swap contract may take from your wallet to deliver the exact output. Set it above the current quote by your chosen slippage tolerance—the allowance for the quote to worsen before execution. If reserves move enough that the required input exceeds this ceiling, the swap reverts instead of taking more.&lt;/p&gt;

&lt;p&gt;Check the pool fee and estimated network gas separately: the fee is part of the trade calculation, while gas is paid to process the transaction. On SpookySwap, fees depend on the selected pool; its V3 documentation lists fee levels from 0.01% to 1%. A quoted amount can also change while the transaction waits to be included in a block.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Check the pool type before you submit
&lt;/h2&gt;

&lt;p&gt;For a V2-style pool, compare the requested output and maximum input with the displayed quote, then confirm that the wallet shows the intended network and tokens. A route through multiple pools is calculated hop by hop, so each pool’s reserves and fee affect the final input.&lt;/p&gt;

&lt;p&gt;The reserve formula above does not describe every pool. In a concentrated-liquidity pool, such as V3, the calculation follows liquidity available across the active price range rather than treating all deposited tokens as one reserve pair. If the quote requires more input than you accept, reduce the output or choose a route with better available liquidity; a larger order can make a thin pool expensive even when its displayed starting price looks attractive.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does exact output guarantee the price?
&lt;/h3&gt;

&lt;p&gt;No. It guarantees the requested output only if the swap executes within your maximum-input limit. If the pool changes before execution and needs more input than that limit, the transaction reverts; your wallet may still charge gas for the failed attempt.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why is the input quote higher than the starting pool price?
&lt;/h3&gt;

&lt;p&gt;The starting ratio reflects only the reserves before your trade. Buying output tokens reduces their reserve, moving the pool price as the swap progresses. The fee adds another cost, so the total input can exceed what the starting ratio alone suggests.&lt;/p&gt;

&lt;h3&gt;
  
  
  When should I choose a smaller exact output?
&lt;/h3&gt;

&lt;p&gt;Choose less when the quote or maximum input is beyond your budget, especially in a shallow pool where a large request moves the price sharply. For a concentrated-liquidity pool, the relevant factor is liquidity across the price range your trade crosses. If that range is thin, reducing the trade can improve its quoted cost.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Validators Agree a Deposit Really Happened</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Fri, 23 Oct 2026 18:56:53 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/how-validators-agree-a-deposit-really-happened-1507</link>
      <guid>https://dev.to/cryptoexplorere/how-validators-agree-a-deposit-really-happened-1507</guid>
      <description>&lt;p&gt;If you send crypto to a cross-chain swap, validators first check that the deposit happened on its source blockchain and then agree to record it. That check takes time because a new block can sometimes be replaced in a chain reorganisation. Knowing the steps helps you tell a normal confirmation wait from a deposit that needs investigating.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are validators checking?
&lt;/h2&gt;

&lt;p&gt;Validators check for a specific event, such as a transaction sending funds to an address the protocol is watching. They independently read the source blockchain using their own connections to its data, then report the transaction details to the protocol’s coordination chain. Those details can include the transaction ID, asset and amount.&lt;/p&gt;

&lt;p&gt;That report is called a &lt;em&gt;witness&lt;/em&gt;. It is a statement that a particular event occurred, rather than a cryptographic proof that the source blockchain can never change. Each validator in the active Validator Network must make its own observation; the process is not meant to rely on one operator’s report.&lt;/p&gt;

&lt;p&gt;Validators also wait for the source chain to meet a confirmation rule, known as a &lt;em&gt;safety margin&lt;/em&gt;. A confirmation means another block has been added after the block containing the deposit. The extra blocks lower the chance that a reorganisation will remove the deposit, but they cannot make that chance zero.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does one observation become an accepted event?
&lt;/h2&gt;

&lt;p&gt;After the required safety margin, validators submit witness transactions to the protocol’s coordination chain. A transaction submitted to a blockchain is often called an &lt;em&gt;extrinsic&lt;/em&gt;; here, it carries a validator’s report into the chain’s shared record. Other validators compare the report with what they observed.&lt;/p&gt;

&lt;p&gt;In Chainflip, that coordination chain is the State Chain, and the reports concern events on separate external blockchains. The State Chain accepts a witnessed event once enough validators in the active set report it consistently: the documented standard set has 150 validators, with 100 reports needed. That shared threshold is what turns individual observations into a protocol decision.&lt;/p&gt;

&lt;p&gt;If a validator reports different details from the others, its report does not help reach the threshold. The network can also punish a validator for a false report or for repeatedly failing to report events that the required majority observed. This makes agreement depend on independent observations and an on-chain threshold, rather than on trusting the first validator to notice a transaction.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens in a Bitcoin deposit example?
&lt;/h2&gt;

&lt;p&gt;Suppose you send Bitcoin to a deposit address for a swap. First, the transaction appears in a Bitcoin block. Validators look for it at the watched address, check the transaction details, and wait for the protocol’s Bitcoin safety margin: the current documentation lists two additional blocks.&lt;/p&gt;

&lt;p&gt;Then each validator submits its witness to the State Chain. When 100 of the 150 validators have reported the same deposit, the event is recorded as real for the protocol. That record lets the protocol account for the incoming funds and continue processing the swap; it does not mean the Bitcoin transaction has become impossible to reverse.&lt;/p&gt;

&lt;p&gt;For Chainflip users, this is a different step from the swap itself: the deposit first has to be recognised by validators, while the State Chain handles protocol accounting and swap instructions. If you are comparing how protocols handle cross-chain deposits, &lt;a href="https://defiledger-6f4.pages.dev/chainflip-swaps-what-integrators-need-to-know/" rel="noopener noreferrer"&gt;Chainflip&lt;/a&gt; is one example of a system that waits for external-chain observations to reach a validator threshold before treating an incoming transfer as recorded.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should you do while the network waits?
&lt;/h2&gt;

&lt;p&gt;Check that your wallet shows the transaction as broadcast, then use its transaction ID to confirm it appears on the correct source blockchain and pays the intended deposit address. Compare the amount and address with the deposit instructions you were given. A wallet’s “sent” status means it submitted a transaction; it does not by itself show that validators have accepted it.&lt;/p&gt;

&lt;p&gt;Allow time for both the source chain’s confirmation rule and the validator reports to complete. These waits vary by chain: Bitcoin blocks average about ten minutes, while other chains use different block times and confirmation rules. A slow block or temporarily unavailable validator connection can delay recognition, even when your transaction is valid.&lt;/p&gt;

&lt;p&gt;If the transaction is in a block but the protocol has not recorded it after the expected wait, keep the transaction ID and check the service’s status information before taking action. Do not send a second deposit just because the first one is still waiting; the original may be recognised later. The key detail is whether the source chain still includes your transaction and whether enough validators have witnessed it.&lt;/p&gt;

&lt;p&gt;For a chain with deterministic finality, validators may be able to accept a deposit after it is final in a block, without waiting for extra blocks. For a chain where blocks can be reorganised, expect a safety margin and a longer wait. That difference in the source chain’s finality is what should change your expectation—not the number of confirmations shown by a wallet alone.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Is My Portal Bridge Transfer Still Pending?</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Fri, 23 Oct 2026 01:13:31 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/why-is-my-portal-bridge-transfer-still-pending-49n9</link>
      <guid>https://dev.to/cryptoexplorere/why-is-my-portal-bridge-transfer-still-pending-49n9</guid>
      <description>&lt;p&gt;A cross-chain bridge can show a transfer as pending after the source transaction succeeds because the destination still needs a separate claim. The key question is whether a signed proof is ready and whether anyone has submitted it on the destination chain.&lt;/p&gt;

&lt;p&gt;In Portal Bridge, check the source transaction first, then look for a destination transaction. When the source is confirmed but the destination step is missing, use &lt;a href="https://cryptoposts.github.io/portal-bridge-transfers-depend-on-the-route-token-and-redemption/" rel="noopener noreferrer"&gt;Portal Bridge cross-chain transfers&lt;/a&gt; to resume that transfer; the signed proof identifies the original send, so you should not start another one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Manual redemption uses gas from your destination wallet
&lt;/h2&gt;

&lt;p&gt;With a manual transfer, you submit the final claim yourself and pay the destination chain’s transaction fee. The bridge’s validators, called Guardians, watch the source transaction and sign a proof called a VAA; that proof lets the destination contract release or mint the tokens.&lt;/p&gt;

&lt;p&gt;A confirmed source transaction does not mean the tokens are already spendable. Once the VAA is ready, your wallet must submit it on the destination chain. For a transfer to Arbitrum, for example, you need ETH on Arbitrum to pay the claim’s gas, even if the token you are moving is USDC.&lt;/p&gt;

&lt;p&gt;To estimate the cost, multiply gas used by the gas price. Say a claim uses 120,000 units of gas at 20 gwei: that is 0.0024 ETH. This is an illustration, not a current quote; the wallet’s estimate depends on the destination network and how busy it is. A failed claim can still use gas, so check the amount before signing.&lt;/p&gt;

&lt;p&gt;Manual redemption suits someone who has destination gas and wants to control when the claim is sent. It may not fit if you have no native coins on that chain. The Wormhole docs describe the proof and separate completion step; the destination block explorer shows whether a claim transaction succeeded.&lt;/p&gt;

&lt;h2&gt;
  
  
  An automatic relay submits the claim for you
&lt;/h2&gt;

&lt;p&gt;An automatic transfer uses a relayer, a service that submits the destination claim on your behalf. The route usually accounts for the relayer’s fee in its quote, and some routes let you include a small gas drop-off: native coins sent with the transfer for later transactions.&lt;/p&gt;

&lt;p&gt;This option suits someone who cannot pay destination gas upfront, if the route and token support it. It may cost more than a manual claim, and the transfer can remain pending while the source proof is prepared or the relayer works. Check the route’s quoted amount and any gas drop-off before approving the source transaction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the stage before you retry
&lt;/h2&gt;

&lt;p&gt;Use the source transaction hash to find out whether the send succeeded. If it reverted, no claim can complete from that attempt; if it succeeded, look for the VAA or a destination transaction before taking another step. A signed VAA is proof of the send, not proof that tokens reached your wallet.&lt;/p&gt;

&lt;p&gt;If the VAA is ready but no destination transaction appears, connect the wallet that matches the intended recipient, switch it to the destination network, and make sure it has that network’s native gas token. Retry the claim once and inspect its receipt in the destination explorer. A failed receipt means the claim did not complete, though the transaction may have spent gas; a successful receipt means the transfer is complete, even if the bridge page has not refreshed.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the source transaction succeeded.&lt;/li&gt;
&lt;li&gt;Check whether the VAA is ready and the destination claim exists.&lt;/li&gt;
&lt;li&gt;For a manual claim, fund destination gas; for an automatic route, review its fee and drop-off.&lt;/li&gt;
&lt;li&gt;Retry only the unfinished destination step, then verify its receipt.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>DEX Aggregator Routes: Pricing Shared Pools Fairly</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Thu, 22 Oct 2026 12:49:57 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/dex-aggregator-routes-pricing-shared-pools-fairly-482l</link>
      <guid>https://dev.to/cryptoexplorere/dex-aggregator-routes-pricing-shared-pools-fairly-482l</guid>
      <description>&lt;p&gt;Split trades can reach more pools if the router counts shared reserves once. This matters when you are comparing ways to swap a large amount: separate routes can improve your price, but overlapping routes can make available liquidity look deeper than it is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Splitting a trade can soften its price impact
&lt;/h2&gt;

&lt;p&gt;A router can divide your order among pools to avoid pushing the whole amount through one pool. A liquidity pool holds tokens for people to trade, and its price shifts as those reserves change.&lt;/p&gt;

&lt;p&gt;For example, imagine two separate pools each hold 1,000 A and 1,000 B, with no fees. Selling 200 A into one pool returns about 167 B; selling 100 A into each returns about 182 B combined. The split gets a better price because neither pool takes the full trade.&lt;/p&gt;

&lt;p&gt;If you are comparing a larger swap across separate sources, &lt;a href="https://christine-braun.mataroa.blog/blog/paraswap-swap-pending-or-failed-diagnose-and-retry-it/" rel="noopener noreferrer"&gt;ParaSwap&lt;/a&gt; can quote routes that split the order. Compare the estimated amount you receive after network costs, since extra pool calls can use more gas—the fee paid to process a transaction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shared reserves can make a route look better than it is
&lt;/h2&gt;

&lt;p&gt;Shared reserves are tokens that more than one candidate route would draw from. A route is the sequence of pools a swap follows; two routes may seem separate while relying on the same pool for one step.&lt;/p&gt;

&lt;p&gt;Suppose one candidate sends A through an A/B pool, then B/C. Another sends A through that same A/B pool. The router cannot safely add both quoted outputs as if each route had an untouched A/B pool: the first trade changes that pool’s reserves and price for the next one.&lt;/p&gt;

&lt;p&gt;A sound quote simulates the combined trade against each pool’s changing state, then checks the final output and minimum acceptable amount. This is the edge case that decides whether a split is real: routes must use independent liquidity, or the router must account for their overlap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose by net output and route overlap
&lt;/h2&gt;

&lt;p&gt;For a small trade, one direct pool may win because the price improvement from splitting does not cover the added gas. For a larger trade, splitting across independent pools can offset price impact enough to leave you with more tokens after costs.&lt;/p&gt;

&lt;p&gt;Pool design affects that cost. The Uniswap v4 whitepaper describes a single contract that manages many pools and tracks temporary balance changes before settlement. That shared contract can reduce work between pools, but each pool still has its own state and reserves; one pool’s liquidity is not automatically available to another.&lt;/p&gt;

&lt;p&gt;The ParaSwap API is one way to compare routes across sources, but the useful result is the net quote for your amount and chain. Choose a split when its gain after gas is clear and the routes do not count the same reserves twice; choose differently when the trade is small, routes overlap, or the quote’s minimum output is too low for your needs.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Treasury Swap Slippage for Occasional Users</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Thu, 22 Oct 2026 01:02:06 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/treasury-swap-slippage-for-occasional-users-2cc4</link>
      <guid>https://dev.to/cryptoexplorere/treasury-swap-slippage-for-occasional-users-2cc4</guid>
      <description>&lt;p&gt;Set a treasury swap’s price boundary before requesting execution. That boundary tells you how much worse the final exchange rate may be than the one you reviewed. If you only swap a few times a year, a written target and a quick quote check can prevent a rushed trade from spending more of the treasury’s value than intended.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate price impact from slippage before setting a limit
&lt;/h2&gt;

&lt;p&gt;Price impact is the change in price caused by the size of your trade; slippage is the difference between the price you saw and the price you actually receive. They are related, but a tight slippage setting cannot fix a poor quote or thin liquidity. For a treasury swap, compare the expected output with an independent market reference, then decide the lowest output the team will accept.&lt;/p&gt;

&lt;p&gt;For example, if a quote offers 50,000 units of a stablecoin for the treasury’s tokens, a 0.5% tolerance implies a minimum of 49,750 units, before any separate fees. Treat that figure as an illustrative boundary, not a recommended setting. The right limit depends on the trade size, token volatility, available liquidity, and how quickly the team needs execution.&lt;/p&gt;

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

&lt;p&gt;Set the minimum acceptable output in the asset the treasury will receive, and record it in the approval request. A narrow limit protects the exchange rate but may leave the order unfilled; a wider limit makes execution more likely while accepting a worse result. I would decide that trade-off before opening the swap screen, not while a quote is counting down.&lt;/p&gt;

&lt;p&gt;For a stablecoin-to-stablecoin trade, the reference price may be close to one-to-one, but token depegs and pool imbalance can make that assumption unsafe. For a volatile-token trade, refresh the reference price immediately before approval and use a deadline that reflects the treasury’s need. If execution is optional, a limit order can wait for the price; if it is time-sensitive, the team may need to accept a wider boundary or reduce the trade size.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the quote’s route and execution model
&lt;/h2&gt;

&lt;p&gt;Review the token pair, network, input amount, expected output, minimum output, and any displayed fee before signing. To make that review concrete, compare the quote in &lt;a href="https://paragraph.com/@quickswap/how-should-teams-use-cowswap-for-treasury-swaps" rel="noopener noreferrer"&gt;cowswap&lt;/a&gt; with the treasury’s recorded target, because a batch auction can use solver-chosen routes and the final result must still meet the order’s terms. A displayed estimate is not the same thing as an executed trade.&lt;/p&gt;

&lt;p&gt;CoW Swap’s batch auctions collect orders and let solvers compete to execute them using on-chain liquidity; some trades can also benefit from Coincidence of Wants, where orders directly offset one another. That process affects how a swap is routed, but the treasury still needs a clear acceptable output. Check whether the interface shows a minimum received amount or a limit price, and make sure it matches the approved boundary. If it does not, stop and resolve the difference before signing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Recheck the order before approving it
&lt;/h2&gt;

&lt;p&gt;Before you submit, confirm that the quote is still current and that the approval covers the intended token and amount. Token approvals can authorize a contract to spend tokens, so use the amount needed for the trade if the wallet or interface allows it. A quote that has expired, a changed output, or an unexpected approval is a reason to review the transaction again.&lt;/p&gt;

&lt;p&gt;After execution, compare the settled output with the recorded minimum and save the transaction details with the treasury’s records. If the order expires or fails, do not simply loosen the limit: check whether the market moved, the quote was stale, or the size exceeded available liquidity. Then obtain a fresh quote and have the team approve the revised terms.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Compare the quote with an independent market reference.&lt;/li&gt;
&lt;li&gt;Set and record the minimum acceptable output before signing.&lt;/li&gt;
&lt;li&gt;Check the pair, network, amount, fees, and approval.&lt;/li&gt;
&lt;li&gt;Confirm the settled output or investigate a failed order.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Portal Bridge Routes: What Each Transfer Type Delivers</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Tue, 20 Oct 2026 23:44:53 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/portal-bridge-routes-what-each-transfer-type-delivers-439o</link>
      <guid>https://dev.to/cryptoexplorere/portal-bridge-routes-what-each-transfer-type-delivers-439o</guid>
      <description>&lt;p&gt;Portal Bridge is a cross-chain transfer interface for moving supported tokens between blockchains. The condition that matters most is which token contract you need on arrival: a Wormhole-wrapped asset, an issuer-native token, or the output of a swap.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Match the route to the exact destination token, not its ticker alone.&lt;/li&gt;
&lt;li&gt;Choose manual or automatic redemption according to gas access and the quoted fee.&lt;/li&gt;
&lt;li&gt;Check finality, recipient address, and minimum received before signing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Route Determines the Asset You Receive
&lt;/h2&gt;

&lt;p&gt;A Portal Bridge route specifies both how value crosses chains and what settles in the recipient wallet. Wrapped Token Transfers (WTT) lock a token on its home chain and mint a Wormhole-wrapped representation elsewhere; sending it home burns that representation and releases the original. A native route can instead deliver a token issued or recognized directly on the destination chain.&lt;/p&gt;

&lt;p&gt;The distinction matters most when depositing into a lending market or exchange. Two tokens labeled USDC can have different contract addresses and different acceptance rules. Read the destination contract address in the route preview, then compare it with the contract the receiving application accepts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five Route Types Cover the Main Choices
&lt;/h2&gt;

&lt;p&gt;The Wormhole Portal Bridge interface can show different routes for the same chain pair as the selected asset changes. Availability also depends on token support, destination liquidity, and whether a relayer serves that route. These are the practical categories:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Manual WTT&lt;/strong&gt; — Best for a supported token when you can fund gas on both chains and redeem the signed message yourself. It does not fit when the recipient lacks destination gas or requires a native token.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automatic WTT&lt;/strong&gt; — Best for the same wrapped-asset outcome with destination redemption handled by a relayer. It does not fit when the token lacks relayer support or the relay charge consumes too much of a small transfer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native USDC through CCTP&lt;/strong&gt; — Best when both chains support Circle’s burn-and-mint route and the recipient needs native USDC. It does not fit a chain pair outside CCTP coverage; a WTT fallback would produce Wormhole-wrapped USDC.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Issuer-managed Native Token Transfers (NTT)&lt;/strong&gt; — Best when the token issuer has deployed its own cross-chain system and the receiving application recognizes that token on both chains. It does not fit arbitrary tokens; the issuer must have enabled the route.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native-asset or swap routes&lt;/strong&gt; — Best when the desired output is canonical ETH, USDT, or another quoted destination asset rather than a wrapped copy. They do not fit when the required pair lacks liquidity or the quoted price impact exceeds the benefit.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Manual and automatic describe &lt;em&gt;who submits the destination transaction&lt;/em&gt;; WTT, CCTP, NTT, and swap routes describe &lt;em&gt;how the asset is delivered&lt;/em&gt;. Treat those as separate choices. A route can look easier because it is automatic yet still deliver the wrong token contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Transfer Becomes Complete at Destination Redemption
&lt;/h2&gt;

&lt;p&gt;On Portal Bridge, a WTT source transaction locks the original token, or burns an existing Wormhole-wrapped token, and emits a transfer message. Wormhole Guardians observe the finalized transaction and sign a Verifiable Action Approval (VAA). That signed message is what lets &lt;a href="https://portalbridge.app" rel="noopener noreferrer"&gt;Portal Bridge transfers&lt;/a&gt; proceed to redemption: the destination contract verifies it, then mints the wrapped asset or releases a token held in custody.&lt;/p&gt;

&lt;p&gt;For manual WTT, you submit the VAA and pay destination gas; for automatic WTT, a relayer submits it under the quoted terms. A pending source transaction, an available VAA, and a completed destination transaction are distinct states. If delivery stalls, look up the source hash in Wormhole Explorer before sending again; an unredeemed VAA may still be claimable.&lt;/p&gt;

&lt;p&gt;WTT also normalizes transfer amounts to eight decimal places. For a token with 18 decimals, an amount such as 1.123456789 is carried as 1.12345678, with the smaller remainder left on the source chain. A token must also have its metadata attested on a destination chain before its wrapped version can first be created, so an obscure asset may need that extra step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fees and Wait Times Depend on the Route
&lt;/h2&gt;

&lt;p&gt;Portal Bridge transfer fees are a combination of source gas, destination gas or a relay charge, and any route-specific fee or swap spread shown in the quote. Manual redemption saves the relay charge but requires native gas in the destination wallet. Automatic redemption can include a gas drop-off, which converts part of the arriving value into destination gas and reduces the token amount received.&lt;/p&gt;

&lt;p&gt;Say you send 1,000 native USDC from Base to Arbitrum through an automatic CCTP quote showing a 0.30 USDC relay charge and no other deduction. The displayed arrival would be about 999.70 USDC before an optional gas drop-off; Base gas is paid separately. Those numbers are illustrative: inspect the live quote, especially for small transfers where a fixed charge is a large percentage.&lt;/p&gt;

&lt;p&gt;Finality often sets the wait. Ethereum.org puts Ethereum finality at roughly 15 minutes, so a conventional transfer originating there can take that long before redemption proceeds; a faster liquidity or intent route may quote seconds by using a different delivery mechanism. Other chains, relayer queues, and destination congestion change the total. Compare the quoted arrival time with the route’s finality assumptions, not only its advertised fastest case.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Destination Check Comes Before the Signature
&lt;/h2&gt;

&lt;p&gt;Set the source chain and asset, destination chain, recipient address, and amount, then inspect every available route’s output contract and minimum received. Portal Bridge can send to a connected destination wallet or a separately entered address; verify the chain as well as the address, particularly when sending to a treasury or exchange deposit. An address that looks valid is no proof that its owner can use the arriving token.&lt;/p&gt;

&lt;p&gt;Approve token spending if prompted, review the source transaction, and retain its hash. For a manual route, keep the destination wallet funded and complete the claim after the VAA appears. For an automatic route, wait for the destination transaction before treating the transfer as settled; if it stalls, check the recorded state and recovery option rather than repeating the source payment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four Questions Settle the Route Choice
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How does the transfer work?
&lt;/h3&gt;

&lt;p&gt;WTT locks or burns on the source chain, waits for a Guardian-signed VAA, and mints or releases on the destination. CCTP burns native USDC and mints native USDC after Circle’s attestation. Issuer-managed and liquidity routes use their own contracts and settlement terms. The destination token contract in the quote tells you which outcome you are accepting.&lt;/p&gt;

&lt;h3&gt;
  
  
  How long does it take and what does it cost?
&lt;/h3&gt;

&lt;p&gt;Expect source gas plus either destination gas or a quoted relay charge. A fast route may settle in seconds when liquidity and execution are available; a route waiting for Ethereum finality can take around 15 minutes or longer. Use the live estimate and minimum received for the exact amount and chain pair, since congestion and relay pricing move.&lt;/p&gt;

&lt;h3&gt;
  
  
  What limits apply?
&lt;/h3&gt;

&lt;p&gt;Support is specific to the token, chain pair, and route. Automatic delivery may require a minimum amount sufficient to cover relay costs, while a swap route may face liquidity and slippage limits. WTT requires destination token registration and carries at most eight decimal places of transfer precision. Check these constraints before approving a large or unusually small amount.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which option fits the destination?
&lt;/h3&gt;

&lt;p&gt;If the receiving application specifies a contract, choose a route that delivers that contract. If it accepts a Wormhole-wrapped asset and you have destination gas, manual WTT can be straightforward; otherwise compare automatic delivery with its charge. For native USDC or another canonical asset, inspect native and swap routes first, then judge their quote against the wrapped alternative.&lt;/p&gt;

&lt;p&gt;I would start with the required destination contract, then compare the routes that actually deliver it. I would send only after checking the minimum received, gas arrangement, and recipient address in the final quote.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>For Monthly Cross-Chain Payouts, Reconcile Both Chains</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:29:56 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/for-monthly-cross-chain-payouts-reconcile-both-chains-2mn9</link>
      <guid>https://dev.to/cryptoexplorere/for-monthly-cross-chain-payouts-reconcile-both-chains-2mn9</guid>
      <description>&lt;p&gt;For monthly cross-chain payouts, match each source-chain debit to a confirmed destination-chain credit before marking it complete. A submitted transaction or a balance change on one chain alone does not show that the recipient received the expected amount.&lt;/p&gt;

&lt;h2&gt;
  
  
  What counts as a completed transfer?
&lt;/h2&gt;

&lt;p&gt;A transfer is complete for treasury purposes when the source action is recognized by the bridge mechanism, the destination action has succeeded, and the recipient’s available balance reflects the net amount due. Those are separate events, often recorded in separate transactions, so one transaction hash cannot prove the whole path.&lt;/p&gt;

&lt;p&gt;Record the source transaction hash, destination transaction hash, and any bridge message ID as different identifiers. The message ID, when available, ties the cross-chain instruction together; the two hashes identify the transactions on their respective chains. Ethereum’s JSON-RPC documentation describes how a transaction receipt includes its status and generated logs, which can confirm what happened in that transaction.&lt;/p&gt;

&lt;p&gt;A successful source receipt may show that tokens were locked, burned, or sent to a contract, depending on the mechanism. It does not prove that the destination transaction has executed. When a payment is still waiting for source-chain confirmation, &lt;a href="https://graph.org/Moving-Tokens-From-Your-Wallet-How-a-Relay-Bridge-Works-10-20" rel="noopener noreferrer"&gt;how a relay bridge carries a transfer&lt;/a&gt; explains why a debit alone does not prove delivery; for reconciliation, keep the transfer open until you can verify the destination result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which records should your team match?
&lt;/h2&gt;

&lt;p&gt;Match transfers on a set of fields, not on amount alone. At minimum, capture the sending and receiving chain, token contract or asset identifier, sender, recipient, source amount, destination amount, fee, both transaction hashes, message ID if present, and timestamps. A spreadsheet can work for a small batch, but use one row per transfer and retain the underlying receipts or exports.&lt;/p&gt;

&lt;p&gt;Amounts need normalization before comparison. Chains store token quantities in base units, while treasury systems usually show decimal amounts; compare the displayed values only after applying the correct token decimals on each chain. Also distinguish the gross amount sent from the net amount received, since a fee, exchange, or rounding rule can make them differ.&lt;/p&gt;

&lt;p&gt;For example, a business sends 12,000 units to fund a payout wallet and the recipient receives 11,988 after a 12-unit fee. Reconcile the source debit of 12,000 to the destination credit of 11,988 and the documented fee of 12; do not treat the 12-unit difference as a missing payment. If the expected fee is not visible in the records, leave the row unresolved until the fee rule or destination event explains it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you handle pending, failed, or mismatched transfers?
&lt;/h2&gt;

&lt;p&gt;Use explicit statuses so a batch report distinguishes “submitted,” “source confirmed,” “destination pending,” “complete,” and “exception.” A source transaction can succeed while a later destination step remains delayed or fails, and a wallet interface may show only one side of that sequence. Set the completion threshold in advance, including how many confirmations or what finality signal your policy requires on each chain.&lt;/p&gt;

&lt;p&gt;On Ethereum, transaction documentation describes blocks progressing from inclusion toward finality; a receipt with success status is useful evidence of execution, while finality provides stronger assurance that the block will not be changed. Other chains use different confirmation and finality rules, so apply the relevant chain’s rule instead of copying an Ethereum wait time. The transfer mechanism’s own status can help locate a message, but verify the destination transaction and recipient balance independently.&lt;/p&gt;

&lt;p&gt;Raise an exception when the destination transaction failed, the recipient differs from the approved address, the asset is unexpected, or the net amount falls outside the agreed fee and rounding tolerance. A delayed destination is not automatically a loss, and a failed destination step does not mean the funds are safe to resend; first determine whether the mechanism supports retry, refund, or recovery. Keep the original row open and record the resolution against its identifiers.&lt;/p&gt;

&lt;h2&gt;
  
  
  A repeatable close process
&lt;/h2&gt;

&lt;p&gt;For recurring treasury transfers, use the same checks for every batch and separate reconciliation from approval to pay. The following sequence creates an auditable record without relying on a single explorer screen or dashboard:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Export the approved payout file with recipient addresses, assets, intended amounts, and an internal payment reference.&lt;/li&gt;
&lt;li&gt;After submission, save the source transaction hash, chain, timestamp, and receipt status against each payment reference.&lt;/li&gt;
&lt;li&gt;Wait for the source chain’s required confirmation threshold, then record the bridge message ID or equivalent tracking reference.&lt;/li&gt;
&lt;li&gt;Check for the destination transaction and verify its status, recipient, asset, and net amount against the approved payout.&lt;/li&gt;
&lt;li&gt;Record fees separately, mark only verified credits complete, and send pending or mismatched rows to an exception queue for follow-up.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A relay bridge can add a useful mechanism for recurring transfers, but the accounting control is the match between the two chain records and the approved instruction. The practical decision rule is simple: book a payout as complete only when its destination credit, recipient, and net amount match the approved payment after documented fees.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Some Bridge Routes Need Destination Gas</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Sat, 17 Oct 2026 07:01:38 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/why-some-bridge-routes-need-destination-gas-365n</link>
      <guid>https://dev.to/cryptoexplorere/why-some-bridge-routes-need-destination-gas-365n</guid>
      <description>&lt;p&gt;A cross-chain route can require destination gas because delivering an asset and executing a swap on the receiving chain are separate transactions, and the second transaction must be paid for there. If the route or recipient cannot supply that chain’s native asset, the transfer may wait, fail, or complete without the intended swap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does the destination transaction need its own gas?
&lt;/h2&gt;

&lt;p&gt;A bridge moves value between chains, but it cannot spend the source chain’s gas to run a transaction on the destination chain. After the source deposit reaches the required finality, a relayer, solver, or bridge contract must submit a new transaction on the destination network. That transaction consumes the destination chain’s execution resources and is paid for in its native asset.&lt;/p&gt;

&lt;p&gt;The distinction matters most on routes that bridge an asset and then swap it. A bridge-only delivery may be a simple transfer; a destination swap calls a router or other contract, which needs gas. If your pending route is meant to bridge first and swap on arrival, &lt;a href="https://heathrhcj130855.thelateblog.com/43143939/why-use-biswap-for-your-first-cross-chain-swap" rel="noopener noreferrer"&gt;Biswap&lt;/a&gt; is relevant because it combines the cross-chain move and asset exchange in one flow; check whether the destination action needs native gas before retrying.&lt;/p&gt;

&lt;p&gt;biswap.uk is a concrete example of a service that combines a cross-chain transfer and swap, so the destination action can affect what gas the route needs.&lt;/p&gt;

&lt;p&gt;Think of the bridge as moving a package to another city: paying the courier for the first leg does not pay the local fee for a service performed after arrival. Some routes include that local fee in their execution design; others leave it to the recipient or require a separate gas provision.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does “separate destination gas” mean in practice?
&lt;/h2&gt;

&lt;p&gt;It can mean one of two things: the recipient must already hold native gas, or the route must arrange gas for the destination execution separately. These are different operational requirements. A user may not need native gas simply to receive a token, but may need it to make a later transaction from that wallet.&lt;/p&gt;

&lt;p&gt;When a relayer submits the destination call, it typically pays gas and expects reimbursement through the route’s quoted economics, such as a deduction from the output or a separate gas provision. If that provision is missing or too small, the relayer may not submit the call. If the recipient must submit or retry a transaction themselves, their wallet needs native gas on that destination chain.&lt;/p&gt;

&lt;p&gt;On an EVM chain, transaction cost is approximately &lt;em&gt;gas used × effective gas price&lt;/em&gt;. A plain native-token transfer is commonly around 21,000 gas, while a router swap may use roughly 100,000–300,000 or more, depending on the contracts, token approvals, and route. Under EIP-1559, the effective price depends on the base fee and the priority fee; the gas limit is a cap, not the amount automatically charged.&lt;/p&gt;

&lt;p&gt;On Solana, fees are paid in SOL and execution uses compute units rather than EVM gas. Creating a token account can also require rent-exempt lamports. So a route that appears funded with the bridged token can still lack the native asset needed for a destination instruction or account creation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can a route stay pending or fail after the source transfer?
&lt;/h2&gt;

&lt;p&gt;“Pending” can describe different stages: waiting for source-chain finality, waiting for a relayer or solver, or waiting for destination execution. A slow source confirmation is not evidence of a destination gas problem. Once the source transaction is final, check the route’s status or transaction records to see whether a destination transaction was submitted and whether it succeeded.&lt;/p&gt;

&lt;p&gt;If no destination transaction exists, the executor may be waiting for sufficient gas provision, a quote to remain executable, or a solver to take the route. If a destination transaction reverted, it may have consumed gas even though the intended swap did not complete. The bridged asset may remain in a contract, return to the recipient, or be delivered without the swap, depending on the route’s settlement design.&lt;/p&gt;

&lt;p&gt;Do not resend the source transfer just because the destination step is pending: a finalized deposit may still be claimable or executable, and a duplicate can create a second transfer. First distinguish “source not final” from “source final, destination not executed.” If a destination transaction failed, use its receipt or explorer record to identify the revert and the asset’s resulting location before deciding whether to retry.&lt;/p&gt;

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

&lt;p&gt;Start with the destination chain and the exact action that remains. If the asset arrived but the swap did not, confirm whether it is in your wallet or held by a contract, then check whether retrying requires native gas in your wallet. If execution is handled by a relayer, look for a route status indicating a gas or execution shortfall rather than submitting another source-side transfer.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the source transaction is final and the destination chain matches the route.&lt;/li&gt;
&lt;li&gt;Check whether a destination transaction was submitted; if so, inspect its status and receipt.&lt;/li&gt;
&lt;li&gt;Estimate native gas for the remaining action, including token-account creation where relevant.&lt;/li&gt;
&lt;li&gt;Keep a buffer: for example, a swap estimated at 180,000 gas may need a higher gas limit, and the required native balance also depends on the live gas price.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I would retry only after the asset’s current location and the failed stage are clear. If the route can execute through a funded relayer, recipient gas may not be the blocker; if the recipient must submit the remaining transaction, funding that destination wallet is usually the deciding step. That answer changes when the source transfer is still unfinalized or the route’s settlement design keeps the asset outside the recipient’s control.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Swap Quote Expiry Before Signing, Explained</title>
      <dc:creator>Merissa Stemler</dc:creator>
      <pubDate>Fri, 16 Oct 2026 19:32:59 +0000</pubDate>
      <link>https://dev.to/cryptoexplorere/swap-quote-expiry-before-signing-explained-fe1</link>
      <guid>https://dev.to/cryptoexplorere/swap-quote-expiry-before-signing-explained-fe1</guid>
      <description>&lt;p&gt;A swap quote expiry is the time limit on an offered estimate of what you will receive for a crypto swap. It matters most when prices or route conditions can change before your transaction is submitted and confirmed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does an expiring quote mean?
&lt;/h2&gt;

&lt;p&gt;A quote is a snapshot: it describes a proposed trade using current prices, available liquidity, fees, and the route chosen to move the assets. Its expiry says how long that snapshot should be treated as current; it does not necessarily mean your wallet or funds expire.&lt;/p&gt;

&lt;p&gt;Before signing, check the quote’s timestamp or countdown, the asset and network you are sending from, and the minimum amount you are promised to receive. For a cross-chain swap, confirm the source and destination networks too; checking the &lt;a href="https://cryptoworldtoday.github.io/manta-bridge-transfers-and-swaps-where-the-extra-step-matters/" rel="noopener noreferrer"&gt;Manta bridge supported networks&lt;/a&gt; helps ensure the route matches where you intend the funds to go.&lt;/p&gt;

&lt;p&gt;Quote expiry and a transaction deadline are related but different. A quote can become stale before a transaction is signed, while a deadline is a condition some swap transactions enforce on-chain: after that time, the transaction reverts instead of executing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can change between the quote and the swap?
&lt;/h2&gt;

&lt;p&gt;Prices move as traders buy and sell, and a route may use one or more liquidity pools. If the price moves against your trade, the amount you receive can fall; if available liquidity changes, the proposed route may no longer work. Cross-chain routes also depend on activity and execution across more than one network.&lt;/p&gt;

&lt;p&gt;The key protection to understand is &lt;em&gt;slippage tolerance&lt;/em&gt;, the amount the final result may differ from the quoted result. A swap may encode a minimum output: for example, with a 1% tolerance on a quote of 1 ETH worth of output, the transaction might accept as little as about 0.99 ETH worth, depending on the exact assets and calculation. A tighter tolerance limits that difference but can make a transaction fail more often.&lt;/p&gt;

&lt;p&gt;Expiry alone does not guarantee a particular outcome. If an old quote is submitted, the service may reject it, the transaction may revert, or the swap may execute at a worse price if the transaction still satisfies its minimum-output condition. Some aggregator API documentation recommends refreshing quotes older than 30 seconds, but that is guidance, not a universal expiry rule.&lt;/p&gt;

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

&lt;p&gt;Imagine you are swapping ETH on Ethereum for an asset on Arbitrum. You receive a quote, then pause to compare it with another option. Before signing, refresh the quote if its timer has run out or the displayed terms have changed, and verify that the destination is still Arbitrum and the minimum received still makes sense to you.&lt;/p&gt;

&lt;p&gt;Read the wallet’s transaction summary as well as the quote. Confirm the token, amount, destination, and network, and make sure the transaction is the swap you intended to authorize. A wallet signature authorizes a transaction; on Ethereum, a submitted transaction is executed by the network, and a failed on-chain transaction can still use gas. Simply letting an unsigned quote expire does not itself submit a transaction.&lt;/p&gt;

&lt;p&gt;If the quote has expired, request a fresh one and compare the new minimum output and route with the old terms before signing. Ethereum’s transaction documentation explains how signed transactions are broadcast and executed, while swap API documentation describes quote refresh and deadlines; together, they show why the quote’s age and the transaction’s actual conditions both matter.&lt;/p&gt;

&lt;p&gt;Use an unexpired quote, check its minimum output and destination, and sign only when those terms still match your intent.&lt;/p&gt;

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