<?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: Mack Schneider</title>
    <description>The latest articles on DEV Community by Mack Schneider (@mack_schneider).</description>
    <link>https://dev.to/mack_schneider</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%2F4098907%2Ff187afbd-4493-4580-aa7a-b3d14d9e96b4.png</url>
      <title>DEV Community: Mack Schneider</title>
      <link>https://dev.to/mack_schneider</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mack_schneider"/>
    <language>en</language>
    <item>
      <title>Should I Wait, Replace, or Cancel a Pending Flashbots Tx?</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Fri, 06 Nov 2026 07:57:57 +0000</pubDate>
      <link>https://dev.to/mack_schneider/should-i-wait-replace-or-cancel-a-pending-flashbots-tx-56no</link>
      <guid>https://dev.to/mack_schneider/should-i-wait-replace-or-cancel-a-pending-flashbots-tx-56no</guid>
      <description>&lt;p&gt;If your Flashbots Protect transaction remains valid and wanted, wait; if it needs correction, replace it with the same nonce, and if unwanted, request cancellation while pending. Because private transactions can be absent from public pending views, &lt;a href="https://flashbots.app" rel="noopener noreferrer"&gt;Flashbots&lt;/a&gt; Protect status reports whether the submission is pending or included; an on-chain receipt confirms inclusion.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does a Pending Flashbots Transaction Mean?
&lt;/h2&gt;

&lt;p&gt;A PENDING status means Protect received your transaction and a builder is processing it, but inclusion is not guaranteed. The Flashbots Transaction Status API documentation defines PENDING, INCLUDED, FAILED, CANCELLED, and UNKNOWN, and reports a recent simulation error where available. UNKNOWN means Protect did not receive that hash; FAILED means its submission window ended without inclusion. If either appears and you still want the action, confirm the nonce remains free before resubmitting.&lt;/p&gt;

&lt;p&gt;Use the original hash to find Protect status and an on-chain receipt; also look for any included transaction from your address with the same nonce. If either was included, the nonce is spent. Even a reverted execution consumes it, so pending cancellation cannot undo inclusion. A missing public explorer pending entry proves little: private submissions stay out of the public mempool.&lt;/p&gt;

&lt;h2&gt;
  
  
  When Should You Wait, Replace, or Cancel?
&lt;/h2&gt;

&lt;p&gt;Choose by intent, simulation results, and whether the nonce remains unconsumed. Suppose two swaps have the same PENDING status, no simulation error, and an available nonce. If the trade still suits you, I would wait. If it is unwanted, I would request cancellation. The evidence is identical; your intent changes the useful action.&lt;/p&gt;

&lt;p&gt;If you still want the action but simulation reports SimErrorMaxFeePerGasTooLow, a corrected fee cap may justify a same-sender, same-nonce replacement. SimErrorInsufficientFunds points to ETH needed for value and gas; SimErrorNonceTooLow or SimErrorNonceTooHigh points to nonce order; SimErrorExecutionReverted may point to swap slippage or contract conditions, with revertReason offering detail. SimErrorOutOfGas points to the gas limit. Raising fees cannot repair funding, nonce, or execution failures. Replace only while the original nonce is unused: a higher nonce creates another transaction, potentially queued behind the first.&lt;/p&gt;

&lt;p&gt;If the action is unwanted and pending, Protect cancellation requests withdrawal off-chain. Protect Cancellations documents an authenticated same-sender, same-nonce self-transfer with empty data; Protect does not mine it, so the request costs no gas. An included same-nonce replacement instead spends the nonce and pays gas. Cancellation can lose a race to inclusion, and withdrawal from Protect cannot invalidate a copy sent elsewhere.&lt;/p&gt;

&lt;p&gt;These checks let you distinguish a submission worth waiting for from one that needs correction or withdrawal before its nonce is consumed.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Do These Cases Change the Answer?
&lt;/h2&gt;

&lt;p&gt;Expired swaps, delay measurements, and bundler submissions require evidence beyond the Protect status of a single transaction.&lt;/p&gt;

&lt;h3&gt;
  
  
  How should I record an expired swap for portfolio accounting?
&lt;/h3&gt;

&lt;p&gt;Keep the original hash, Protect status, and any eventual same-nonce receipt with your records. Expiry alone does not show an executed swap; record asset movement from what settled on-chain.&lt;/p&gt;

&lt;h3&gt;
  
  
  How can I measure inclusion delays across my transaction history?
&lt;/h3&gt;

&lt;p&gt;For included transactions, compare submission timestamps with receipt block timestamps using the same method for each. Keep expired and cancelled hashes separate: they have no inclusion time, so a zero delay distorts the result.&lt;/p&gt;

&lt;h3&gt;
  
  
  What changes when my wallet submits through an account-abstraction bundler?
&lt;/h3&gt;

&lt;p&gt;An ERC-4337 wallet submits a UserOperation to a bundler, which packages it into an on-chain transaction. Track the operation's status and nonce through the bundler; an ordinary Protect transaction hash and cancellation request may not describe that path.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>crypto</category>
      <category>web3</category>
    </item>
    <item>
      <title>What Are the Main ParaSwap Trade Types for Treasury Teams?</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Sun, 01 Nov 2026 18:20:06 +0000</pubDate>
      <link>https://dev.to/mack_schneider/what-are-the-main-paraswap-trade-types-for-treasury-teams-2dah</link>
      <guid>https://dev.to/mack_schneider/what-are-the-main-paraswap-trade-types-for-treasury-teams-2dah</guid>
      <description>&lt;p&gt;For a team managing treasury swaps, payouts, or regular transfers, ParaSwap offers five main trade types: Market swaps, Delta intent swaps, limit orders, TWAP orders, and OTC trades. Market settles an immediate transaction; Delta seeks a solver fill; limit orders wait for a price; TWAP spreads execution over time; and OTC settles terms agreed with a known counterparty.&lt;/p&gt;

&lt;h2&gt;
  
  
  ParaSwap Has Five Main Trade Types
&lt;/h2&gt;

&lt;p&gt;The five types differ in who submits the trade, when it can fill, and what the team commits to signing. Start with the obligation behind the transfer: a fixed amount to receive, a price threshold, a deadline, or an agreed counterparty. Those constraints matter more than the quoted rate alone.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Market swap — best for immediate, atomic settlement.&lt;/strong&gt; The wallet signs and broadcasts a transaction that routes through available on-chain liquidity. It does not fit a workflow that needs to wait for a target price or move value between chains in one order.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Delta intent swap — best when the team can allow solver execution.&lt;/strong&gt; The wallet signs an order; competing solvers seek a fill that satisfies its terms. It does not fit a transaction that must compose synchronously with another contract call. A crosschain swap is a Delta route, subject to available bridge routes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limit order — best when a minimum sale return or maximum purchase spend matters more than timing.&lt;/strong&gt; It is a resting Delta order with a price constraint and expiry. It does not fit a payout that must settle on a particular day: the price may never become reachable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TWAP order — best for spreading a larger trade across scheduled slices.&lt;/strong&gt; One signed Delta order governs the schedule and its remaining balance. It does not fit an exact, immediate payout, and it still needs sufficient liquidity when each slice becomes eligible.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OTC trade — best when two known parties have agreed the terms directly.&lt;/strong&gt; A maker signs an AugustusRFQ order naming the taker, who fills it on-chain. It does not fit an open search across liquidity sources for an unknown counterparty.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Routing and Settlement Determine What Actually Trades
&lt;/h2&gt;

&lt;p&gt;The ParaSwap DEX aggregator prices the specified token pair, trade size, side, and chain against liquidity available for that request. A route can use one pool, several pools, or intermediate tokens; splitting helps only when the improved execution exceeds the extra gas and venue fees. Compare the expected output after route costs, then check the route again near signing because the price is not reserved.&lt;/p&gt;

&lt;p&gt;For a Market swap, the price response contains a &lt;em&gt;priceRoute&lt;/em&gt; with the expected output, gas estimate, and path. The transaction build uses that route unchanged to produce calldata for the Augustus router. After the source token has the required allowance, the wallet broadcasts the swap; the router executes its hops and enforces the minimum destination amount. A failed hop or breached minimum reverts the whole swap, while the sender still pays gas.&lt;/p&gt;

&lt;p&gt;Delta uses a different commitment. The team obtains a route, approves the Delta spender for an ERC-20 source, signs an EIP-712 order, and submits it for a private solver auction. The winning solver supplies settlement calldata; the contract checks the signed terms before transferring funds. Track the order through completion, expiry, failure, or cancellation instead of treating signature submission as a completed transfer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Networks, Fees, and Approvals Set the Practical Limits
&lt;/h2&gt;

&lt;p&gt;Execution cost depends on the mode and the particular route. Market requires network gas for the swap and, if allowance is missing, usually a separate approval transaction; pool fees and price impact are reflected in the rate. Delta handles settlement gas within the solver flow, so “gasless” describes what the user pays on-chain, not a free economic execution. Check the net amount delivered, including any partner fee configured by an integration.&lt;/p&gt;

&lt;p&gt;A treasury holding USDC on Polygon cannot execute an Arbitrum Market quote as though both balances lived on one chain. Check &lt;a href="https://paraswap.pro" rel="noopener noreferrer"&gt;ParaSwap supported networks&lt;/a&gt; before fixing chain IDs and token contracts for a recurring flow. The ParaSwap exchange quote must use the actual source chain; a crosschain Delta route has separate bridge availability, fees, timing, and refund states to account for.&lt;/p&gt;

&lt;p&gt;Approvals follow the execution contract, not the brand shown in a wallet interface: Market uses the Augustus spender, Delta orders use the Delta spender, and bilateral OTC uses AugustusRFQ. Verify the spender returned for the selected flow and approve the amount needed. Resting limit and TWAP orders need an on-chain allowance that remains usable when a later fill occurs; a short-lived permit is not a substitute for that schedule.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Treasury Workflow Needs a Quote-to-Settlement Rule
&lt;/h2&gt;

&lt;p&gt;The common payout mistake is to use &lt;em&gt;SELL&lt;/em&gt; when the recipient must receive an exact amount. Selling, say, 50,000 USDC might quote 49,800 USDT before the allowed slippage; it does not promise a 50,000 USDT payout. Use &lt;em&gt;BUY&lt;/em&gt; to fix 50,000 USDT as the destination and cap the USDC spend, then reject a route that exceeds the treasury budget.&lt;/p&gt;

&lt;p&gt;Set slippage from the pair’s depth and the cost of a failed transfer, rather than leaving one setting across every token. For example, 50 basis points permits a 0.5% move between quote and execution; a tighter limit increases reverts on volatile or thin routes. For a TWAP, quote one slice, approve the total source amount, and leave enough time before expiry for every interval. The schedule requires at least two slices and intervals of at least 60 seconds.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three Questions Clarify the Choice
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How does a route become a completed trade?
&lt;/h3&gt;

&lt;p&gt;A Market route becomes a completed trade only after its transaction confirms on-chain. A Delta quote becomes an order after build, signature, and submission; it completes only when a solver settles it. Record the transaction receipt or terminal order status against the treasury instruction. A quote, approval, or accepted signature is evidence of an earlier step, not proof that the recipient received tokens.&lt;/p&gt;

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

&lt;p&gt;Market timing follows transaction inclusion and chain confirmation; its cost includes gas and the price embedded in the selected route. Delta adds solver competition and can expire without a fill. Limit orders may rest until their price is met, while a TWAP lasts across its chosen intervals. Compare delivered tokens and operational timing together, especially when a payout has a cutoff.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which limits decide whether a type fits?
&lt;/h3&gt;

&lt;p&gt;Check token support, chain support, available routes, allowance, and the team’s maximum spend or minimum receipt. Then check whether the workflow can tolerate a resting order, partial progress across TWAP slices, or crosschain refund timing. An OTC trade also requires the named taker to act. If any of those conditions conflicts with the payment obligation, choose a different trade type before signing.&lt;/p&gt;

&lt;p&gt;ParaSwap is most useful as a set of execution choices. Match the trade type to the amount, price constraint, chain, and settlement deadline, then reconcile the actual fill before marking a treasury transfer complete.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Check a Token Pair for Farming Incentives</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Thu, 29 Oct 2026 06:14:11 +0000</pubDate>
      <link>https://dev.to/mack_schneider/check-a-token-pair-for-farming-incentives-59b5</link>
      <guid>https://dev.to/mack_schneider/check-a-token-pair-for-farming-incentives-59b5</guid>
      <description>&lt;p&gt;A token pair qualifies for farming incentives only when the exact pool has an active reward program on the same chain and pool version. For a treasury team scheduling regular transfers, the useful question is not whether the tokens are popular or available to trade; it is whether your position can earn the stated rewards for the period you plan to hold it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Match the incentive to the exact pool
&lt;/h2&gt;

&lt;p&gt;Start with the chain, both token contract addresses, and the pool implementation. A pair can have several pools with different fee tiers or versions, and an incentive attached to one does not automatically cover the others.&lt;/p&gt;

&lt;p&gt;On SushiSwap, for example, a treasury looking at the &lt;a href="https://paragraph.com/@jifoteg692/sushiswap-aggregator-swaps-explained" rel="noopener noreferrer"&gt;SushiSwap exchange&lt;/a&gt; should verify the chain and pool details before treating a displayed reward as applicable to its position. A V2 pool commonly issues fungible LP tokens; a concentrated-liquidity pool may represent each position as an NFT, and its incentive rules can depend on where liquidity sits within the price range.&lt;/p&gt;

&lt;p&gt;Compare two cases: a treasury’s USDC/WETH position matches the chain, contracts, and fee tier specified by an active program; its USDC/WETH position on another fee tier does not qualify just because the pair name is identical. I would treat the pool contract address and incentive contract as the decisive identifiers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check that rewards are active and reachable
&lt;/h2&gt;

&lt;p&gt;A listed pair is eligible only while its program is live, funded, and accepting the position type you hold. Check the start and end times or blocks, reward token, remaining reward budget, claim conditions, and any minimum liquidity or position requirements.&lt;/p&gt;

&lt;p&gt;In a typical V2 staking farm, the contract tracks each account’s deposited LP-token balance and allocates emissions by pool weight. A common accounting pattern updates accumulated rewards per LP share and subtracts each user’s reward debt; depositing LP tokens in the pool alone may therefore be insufficient if the program requires staking them in a separate contract.&lt;/p&gt;

&lt;p&gt;For concentrated liquidity, eligibility may additionally require that the position’s range overlaps the active price range or satisfies the program’s liquidity rules. A position can remain open yet earn little or nothing if it is out of range, deposited after the end time, or not registered with the incentive contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  Estimate the reward against treasury costs
&lt;/h2&gt;

&lt;p&gt;Estimate rewards from the program’s remaining emission and your expected share of eligible liquidity, then compare that amount with transaction costs and the risks of holding the pair. For a time-based program, a rough calculation is reward tokens distributed over your holding period multiplied by your share of eligible liquidity; pool weights, changing deposits, and reward caps can make the realized amount differ.&lt;/p&gt;

&lt;p&gt;For example, suppose a program distributes 1,000 reward tokens over a week and your position represents 10% of eligible liquidity throughout that week: a rough estimate is 100 tokens before changes in liquidity or program rules. If another pool offers a larger headline APR but has thin liquidity and a volatile reward token, I would favor the lower estimate only when its expected value after price impact, impermanent loss, and operating costs is better for the treasury.&lt;/p&gt;

&lt;p&gt;Include the costs of entry, staking, claiming, and exit, plus the need to rebalance a concentrated position. On Arbitrum, the Arbitrum One explorer can help confirm contract addresses, emitted events, and reward-token transfers; those records are stronger evidence of live distribution than an old APR screenshot.&lt;/p&gt;

&lt;h2&gt;
  
  
  Record the eligibility decision before funding
&lt;/h2&gt;

&lt;p&gt;Before moving treasury assets, save the pool address, chain, program contract, reward token, schedule, and eligibility conditions with the approval record. Recheck those fields before each scheduled deposit or rebalance, since programs can end, exhaust their budget, or change allocation without changing the pool itself.&lt;/p&gt;

&lt;p&gt;SushiSwap can be one venue in that review, but the qualification test is the same: verify the exact pool and position against the active program, then decide whether the expected net reward justifies the exposure and operational work.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Match chain, token contracts, pool version, and fee tier.&lt;/li&gt;
&lt;li&gt;Confirm the incentive is live, funded, and accepts your position type.&lt;/li&gt;
&lt;li&gt;Estimate net rewards after trading, gas, claim, and exit costs.&lt;/li&gt;
&lt;li&gt;Save the evidence and recheck before the next transfer.&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>What Happens When You Use a Permit to Deposit Tokens?</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Sat, 24 Oct 2026 10:46:29 +0000</pubDate>
      <link>https://dev.to/mack_schneider/what-happens-when-you-use-a-permit-to-deposit-tokens-3ghj</link>
      <guid>https://dev.to/mack_schneider/what-happens-when-you-use-a-permit-to-deposit-tokens-3ghj</guid>
      <description>&lt;p&gt;If you are depositing an ERC-20 and want fewer wallet transactions, a permit can authorize the spend with a signature, but only when the token and deposit flow support it. For an Ethereum-to-Mantle deposit, &lt;a href="https://chainbrief.org/mantle-bridge-routes-split-at-the-withdrawal/" rel="noopener noreferrer"&gt;Mantle Bridge&lt;/a&gt; lets you choose a supported asset and amount; whether a permit saves an approval transaction depends on the token and the deposit flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a permit approve?
&lt;/h2&gt;

&lt;p&gt;A permit is a signed token allowance: it lets a named spender use up to a stated amount of your tokens. Under the common ERC-2612 standard, your wallet signs typed data containing the token, owner, spender, amount, nonce and deadline. The token contract checks the signature and records the allowance on-chain when someone submits it.&lt;/p&gt;

&lt;p&gt;The signature is not the deposit itself. A bridge still needs a transaction that transfers the tokens and starts the cross-chain deposit. If the deposit contract accepts a permit and uses it in that same transaction, the approval and deposit can happen together; the signature alone does not move funds or pay the transaction fee.&lt;/p&gt;

&lt;p&gt;The ERC-2612 specification and OpenZeppelin’s implementation notes explain the key limit: the token must implement the permit interface. A wallet signing an approval message does not add permit support to a token, and a bridge interface must also be built to use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  When can it replace a separate approval?
&lt;/h2&gt;

&lt;p&gt;A permit can replace the separate on-chain approval transaction when three things line up: the exact token contract supports the permit format, the deposit flow accepts its signature, and the signature matches the spender and amount required for that deposit. If any one is missing, you will need the usual on-chain approval first.&lt;/p&gt;

&lt;p&gt;For example, suppose you want to deposit 100 units of a supported ERC-20 from Ethereum. With a compatible permit flow, you could sign an allowance for 100 units, then confirm one Ethereum transaction that submits the permit and initiates the deposit. Without that flow, you first send an approval transaction, wait for confirmation, and then send the deposit transaction.&lt;/p&gt;

&lt;p&gt;Check the wallet prompt carefully: the token, network, spender and amount should match the deposit you intend to make. For a one-off transfer, I prefer an allowance limited to the deposit amount over an unlimited allowance. A permit signature may be submitted by someone other than you, so its deadline should be short enough for the task, while still leaving time to complete it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can make the signature fail?
&lt;/h2&gt;

&lt;p&gt;A permit is specific to its token contract and chain, and it uses a nonce to prevent the same signature being used twice. A signature can fail if its deadline has passed, the token’s nonce has changed, or the wallet signs data for the wrong token, network, spender or amount. If the wallet shows unfamiliar fields or an unexpected spender, stop and return to the deposit flow.&lt;/p&gt;

&lt;p&gt;Permit support varies by token, even among familiar ERC-20 assets. Check the selected token’s contract and the deposit interface rather than assuming a ticker or symbol tells you enough. Some tokens also have different permit formats; a signature made for one format will not automatically work with another.&lt;/p&gt;

&lt;p&gt;Smart contract wallets can be another edge case: some cannot produce standard ERC-2612 signatures. If the permit option is unavailable or fails, use the deposit flow’s regular approval route, if offered. For tokens that require an allowance to be reset before it is raised, follow the wallet’s requested approval steps and confirm each transaction before continuing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How should you complete the deposit?
&lt;/h2&gt;

&lt;p&gt;First, select Ethereum as the source network, the supported token and the amount. Check the destination address and keep enough ETH in your wallet for the Ethereum transaction fee; a permit can remove an approval transaction, but it does not make the deposit transaction free.&lt;/p&gt;

&lt;p&gt;Next, use a permit only if the interface offers it for that exact token and deposit. Review the signature details, then confirm the transaction that submits the permit and starts the deposit. If the interface instead asks for an approval transaction, approve only the needed amount where possible, wait for confirmation, and then submit the deposit.&lt;/p&gt;

&lt;p&gt;After submitting, use the transaction status shown by the bridge and wait for the deposit to complete before treating the funds as available on Mantle. In my place, I’d use a permit when the token and deposit flow clearly support it and the signed amount is limited to the transfer; otherwise, I’d use the standard approval flow and check each wallet prompt.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to Prepare Mantle ETH for an Ethereum Validator</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Fri, 23 Oct 2026 07:41:15 +0000</pubDate>
      <link>https://dev.to/mack_schneider/how-to-prepare-mantle-eth-for-an-ethereum-validator-lhp</link>
      <guid>https://dev.to/mack_schneider/how-to-prepare-mantle-eth-for-an-ethereum-validator-lhp</guid>
      <description>&lt;p&gt;If your 32 ETH is on Mantle, withdraw it to Ethereum before you make a validator deposit. You need ETH on Ethereum for the deposit, and the bridge withdrawal and validator setup each take time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the amount and prepare your validator
&lt;/h2&gt;

&lt;p&gt;A solo Ethereum validator needs at least 32 ETH, plus ETH for transaction fees. A validator also needs software to run it, so prepare your node and validator keys before moving funds.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check where your funds are.&lt;/strong&gt; Confirm that you hold ETH on Mantle and that you control the wallet receiving funds on Ethereum. If you already have 32 ETH on Ethereum, you can skip the bridge steps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prepare the validator deposit details.&lt;/strong&gt; Use the Ethereum Staking Launchpad to create your validator keys and set a withdrawal address you control. Keep the signing key private, and save your setup information securely; the deposit cannot be used to start a validator without its matching key details.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Withdraw ETH to Ethereum
&lt;/h2&gt;

&lt;p&gt;Funds on Mantle must return to Ethereum before they can fund the Ethereum validator deposit. A Mantle balance is not an Ethereum balance: &lt;a href="https://ameblo.jp/monnes-web3/entry-12982275225.html" rel="noopener noreferrer"&gt;Mantle Bridge&lt;/a&gt; is the canonical route for withdrawing assets to Ethereum, while the validator deposit happens on Ethereum itself.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Keep gas for both networks.&lt;/strong&gt; Have MNT on Mantle to pay for the withdrawal transaction, and keep ETH on Ethereum for the later claim and deposit transactions. The bridge screen shows the amount you will receive and the estimated network fees before you sign.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start a withdrawal of ETH.&lt;/strong&gt; In the bridge, select Mantle as the source, Ethereum as the destination, and ETH as the asset. Check the receiving address carefully, then sign the withdrawal in your wallet. A withdrawal request does not mean the ETH is already available on Ethereum.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wait, then claim the funds.&lt;/strong&gt; Allow up to around 12 hours for the canonical withdrawal, according to Mantle’s current FAQ; timing can vary. Check the Mantle Bridge status or history for the next action. When the withdrawal is ready, use your Ethereum wallet to claim it, paying the Ethereum gas fee, then confirm the ETH appears in your Ethereum balance.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Make the validator deposit and check its status
&lt;/h2&gt;

&lt;p&gt;The deposit transaction is the final on-chain step, but the validator may not become active immediately.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Deposit the prepared amount.&lt;/strong&gt; Follow the Launchpad instructions and verify the validator public key, withdrawal address, and 32 ETH amount before signing. Leave extra ETH in the wallet to pay the transaction fee.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Track activation.&lt;/strong&gt; After the deposit is recognized, the validator enters Ethereum’s activation queue. The wait depends on how many validators are ahead of it and can range from hours to weeks; keep the validator software running and monitor its status.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In short, prepare the validator first, withdraw Mantle ETH to Ethereum, claim it, then deposit 32 ETH and wait for activation.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Wrapped Assets for Wallet Beginners: Why They Exist</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Thu, 22 Oct 2026 15:10:13 +0000</pubDate>
      <link>https://dev.to/mack_schneider/wrapped-assets-for-wallet-beginners-why-they-exist-kkd</link>
      <guid>https://dev.to/mack_schneider/wrapped-assets-for-wallet-beginners-why-they-exist-kkd</guid>
      <description>&lt;p&gt;If you are moving a token to a chain where it has no native version, use a wrapped asset after checking its origin and destination contract. A wrapped asset is a token made on the destination chain to represent a token held or burned elsewhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  A wrapped token gives another chain a usable version
&lt;/h2&gt;

&lt;p&gt;Blockchains keep separate records, so a token on one chain cannot simply appear on another. A wrapped token is a separate asset contract on the destination chain, with its own address and balance records.&lt;/p&gt;

&lt;p&gt;For example, imagine you hold 10 units of a token on Ethereum and want to use them on Solana. If that token has no native Solana version, a bridge can lock the 10 units on Ethereum and create 10 wrapped units on Solana. The wrapped units represent the original; they are not the original Ethereum tokens moved across.&lt;/p&gt;

&lt;p&gt;This is why a token’s name and logo are not enough to identify it. On the destination chain, check the token contract address and the stated origin chain. Two assets can share a ticker while having different backing or issuers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bridge locks, proves, and then creates the representation
&lt;/h2&gt;

&lt;p&gt;In a typical Wormhole bridge transfer, you approve and send tokens to the source chain’s bridge contract. That contract locks the original tokens and publishes a message describing the amount, destination, and recipient.&lt;/p&gt;

&lt;p&gt;The Guardian Network observes that message and signs a proof called a VAA, short for Verified Action Approval. A supermajority of Guardians must sign it; the destination contract checks those signatures before minting wrapped tokens to the recipient’s wallet.&lt;/p&gt;

&lt;p&gt;That sequence explains why the transfer has two chain transactions in a manual flow: one to start it and another to claim the tokens. With automatic delivery, a relayer submits the destination transaction for you. The convenience and any delivery fee depend on the route shown in the transfer screen; check the &lt;a href="https://telegra.ph/How-to-Compare-Wormhole-Bridge-Route-Liquidity-10-21" rel="noopener noreferrer"&gt;wormhole bridge fees&lt;/a&gt; before confirming.&lt;/p&gt;

&lt;h2&gt;
  
  
  The representation changes when you send it back
&lt;/h2&gt;

&lt;p&gt;When wrapped tokens return to their origin chain, the destination bridge usually burns the wrapped units and releases the same amount from escrow. Burning means removing those units from circulation, so the claim on the locked original is not duplicated.&lt;/p&gt;

&lt;p&gt;If you send the wrapped version from one non-origin chain to another, the first chain burns its wrapped units and the next chain mints a new representation. The original remains locked at its origin. This keeps the total claim tied to the original supply, though each step still needs a valid message and destination transaction.&lt;/p&gt;

&lt;p&gt;One useful edge case: the destination may already have an official native version of the asset. Some transfer routes can release that native token instead of minting a wrapped one. The transfer screen’s asset details and origin label tell you which version you will receive.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the asset and the costs before confirming
&lt;/h2&gt;

&lt;p&gt;Before sending, confirm that the route supports both chains and that the receiving wallet address belongs to the destination chain. Check the exact token you will receive, including its origin and contract address, rather than relying on its symbol.&lt;/p&gt;

&lt;p&gt;Keep enough source-chain currency to pay the transaction fee, called gas. A manual transfer may also require destination-chain gas to claim the tokens. Automatic delivery can include a relayer charge, and some routes let you request a small amount of destination gas; the quote can change with chain conditions and the requested service.&lt;/p&gt;

&lt;p&gt;For instance, if you are used to buying a token on an exchange and withdrawing it to a network, wallet-to-wallet bridging adds a choice: you must accept a specific destination-chain representation. If the transfer is still pending, check its status before retrying or sending again. Once it completes, you can swap or use the wrapped asset on that chain, but it may not be accepted everywhere the original is.&lt;/p&gt;

&lt;p&gt;Wormhole bridge is one route that uses signed cross-chain messages to support these transfers, but the key decision is the asset you receive. Before acting, ask yourself: am I comfortable holding this exact wrapped token on this exact chain?&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to Estimate Refundable Rent Before an LP Position</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Thu, 22 Oct 2026 05:46:25 +0000</pubDate>
      <link>https://dev.to/mack_schneider/how-to-estimate-refundable-rent-before-an-lp-position-42c2</link>
      <guid>https://dev.to/mack_schneider/how-to-estimate-refundable-rent-before-an-lp-position-42c2</guid>
      <description>&lt;p&gt;Add the position-account deposits and any missing token accounts; keep fees separate. On Byreal, your liquidity position uses on-chain accounts that hold SOL as a refundable storage deposit, often called rent. Use the app’s transaction preview for the current amount, since Solana rent levels can change.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does “refundable rent” cover?
&lt;/h2&gt;

&lt;p&gt;It is SOL held in accounts to pay for storing their data on Solana. When an account is closed, its remaining balance can be returned; transaction fees and some setup charges cannot.&lt;/p&gt;

&lt;p&gt;A concentrated liquidity position, which puts funds inside a price range you choose, needs a position account and a position NFT. An NFT is a unique token that represents ownership of that position. The NFT also needs a token account to sit in your wallet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which amounts should I add?
&lt;/h2&gt;

&lt;p&gt;Start with the position account, position NFT, and the NFT’s token account. Then add token accounts only for the pool tokens you do not already hold in your wallet.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check the pool and your wallet.&lt;/strong&gt; Choose the pool and price range you plan to use. Check whether your wallet already has token accounts for both pool assets; a token account is the on-chain place where one type of token is held.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add the position deposits.&lt;/strong&gt; Byreal’s fee guide lists typical amounts of 0.00284664 SOL for the personal position account, 0.00277008 SOL for the position NFT, and 0.00207408 SOL for its token account. Together, that is 0.0076908 SOL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add missing token accounts.&lt;/strong&gt; The same guide lists 0.0020393 SOL as a typical refundable deposit for each new token account. If neither pool token account exists, add 0.0040786 SOL, bringing the estimate to 0.0117694 SOL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare with the wallet preview.&lt;/strong&gt; Treat those figures as a starting estimate, not a quote. Rent levels can change, and the transaction preview shows what this particular opening transaction asks your wallet to fund.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What could make the amount higher?
&lt;/h2&gt;

&lt;p&gt;A new price range can require a tick array, a small on-chain record for price levels used by the pool. Byreal’s guide says initializing one can cost about 0.00117 to 0.00356 SOL, depending on what already exists; this charge is not refundable.&lt;/p&gt;

&lt;p&gt;Network and priority fees are also separate from rent. They pay to process the transaction, so do not count them as money you expect to recover. For a broader task-to-feature comparison, &lt;a href="https://web3newsnetwork.github.io/byreal-features-serve-different-treasury-jobs/" rel="noopener noreferrer"&gt;which Byreal feature fits each job&lt;/a&gt; answers a different question from this position-cost estimate.&lt;/p&gt;

&lt;h2&gt;
  
  
  When do you get the deposit back?
&lt;/h2&gt;

&lt;p&gt;You can recover rent only when the relevant account is closed, and closure may happen as part of removing a position or through a separate step. Closing an account returns its balance to the destination in the close instruction, so check the wallet’s transaction details and resulting balance.&lt;/p&gt;

&lt;p&gt;For a quick estimate, budget about 0.00769 SOL for the three position-related accounts, then add roughly 0.00204 SOL for each missing pool-token account. Use the current wallet preview as the final figure, and keep non-refundable fees outside your rent total.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What Is Manta Bridge and How Does It Work From a Wallet?</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Wed, 21 Oct 2026 12:20:25 +0000</pubDate>
      <link>https://dev.to/mack_schneider/what-is-manta-bridge-and-how-does-it-work-from-a-wallet-9l2</link>
      <guid>https://dev.to/mack_schneider/what-is-manta-bridge-and-how-does-it-work-from-a-wallet-9l2</guid>
      <description>&lt;p&gt;Manta Bridge is the native route for moving ETH and supported Ethereum tokens between Ethereum Mainnet and Manta Pacific. A bridge to Manta Pacific requires the asset to be in your wallet on the supported source chain, with enough ETH there to pay gas. For that Ethereum-to-Pacific transfer, &lt;a href="https://mantabridge.dev" rel="noopener noreferrer"&gt;Manta Bridge&lt;/a&gt; moves the value between chains without a centralised exchange.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Does a Transfer Between Ethereum and Manta Pacific Work?
&lt;/h2&gt;

&lt;p&gt;A deposit starts with a transaction on Ethereum and ends with the corresponding asset becoming available on Manta Pacific. Your wallet keeps the same address on both networks, but the balances are recorded on different chains. Switching the network shown in your wallet changes which balance you see; it does not move funds.&lt;/p&gt;

&lt;p&gt;For ETH, the bridge receives your deposit on Ethereum, then the Manta Pacific side credits ETH to your address. For an ERC-20 token, the Ethereum token is held by the bridge contract while its corresponding token is issued on Pacific. When you withdraw through the native route, that process reverses: the Pacific balance is removed and the asset is released on Ethereum after the withdrawal is finalised.&lt;/p&gt;

&lt;p&gt;This is why a completed source-chain transaction and an arrived destination balance are two separate checks. Manta Pacific is an Ethereum layer 2 that uses Celestia for data availability, but Celestia is not a destination you select for this transfer. The route you check in your wallet is Ethereum Mainnet to Manta Pacific, or the reverse.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Assets Can You Move?
&lt;/h2&gt;

&lt;p&gt;You can move ETH and ERC-20 tokens offered by the bridge’s live asset picker for your chosen direction. Examples associated with the Ethereum-to-Pacific route include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;ETH:&lt;/strong&gt; the simplest first deposit, because ETH also pays gas on Manta Pacific.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;USDC:&lt;/strong&gt; a dollar-denominated ERC-20 token; check its contract and the version shown on each chain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;USDT:&lt;/strong&gt; another ERC-20 stablecoin whose ticker alone does not identify its contract.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DAI:&lt;/strong&gt; an example classified as a canonical bridged token in the Manta Pacific token list.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That list is illustrative, not a promise that every token is available for every route today. The Manta Network bridge asset picker and the token’s contract address decide what you can actually send. Manta Pacific’s token list distinguishes canonical bridged tokens from tokens brought in by external bridges; two assets with the same ticker can therefore have different origins and contracts.&lt;/p&gt;

&lt;p&gt;If a token is absent from the picker, do not send it directly to a bridge contract. You also need the asset on &lt;em&gt;Ethereum Mainnet&lt;/em&gt; before using this deposit route. An exchange balance or the same ticker on another network is not an Ethereum wallet balance.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Do You Deposit From Your Wallet and Withdraw Again?
&lt;/h2&gt;

&lt;p&gt;To deposit, connect your self-custody wallet, select Ethereum Mainnet as the source and Manta Pacific as the destination, then confirm the asset and amount. I would bridge a small amount of ETH first if I were new to the route: it tests the destination and leaves me with Pacific gas for a later transaction.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Check that your wallet is on Ethereum Mainnet and holds both the asset and enough ETH for Ethereum gas. If funds are still at an exchange, withdraw them to your own wallet using the Ethereum network first.&lt;/li&gt;
&lt;li&gt;Add Manta Pacific to your wallet and check its chain ID is &lt;strong&gt;169&lt;/strong&gt;. Review the source, destination, token and amount shown before signing.&lt;/li&gt;
&lt;li&gt;For an ERC-20 token, approve the bridge’s allowance if prompted, then submit the separate deposit transaction. ETH deposits normally need only the deposit transaction.&lt;/li&gt;
&lt;li&gt;Keep the transaction hash. After the Ethereum transaction succeeds, switch your wallet to Manta Pacific and check the received balance there.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Say your Ethereum wallet holds 0.10 ETH and you deposit 0.08 ETH. You must leave some of the remaining 0.02 ETH for Ethereum gas; entering the full 0.10 ETH may make the transaction impossible to submit. Once the deposit arrives, the 0.08 ETH on Pacific can pay for activity there, subject to any amount deducted or displayed by the route.&lt;/p&gt;

&lt;p&gt;To return, choose Withdraw, select Manta Pacific as the source, and initiate the transaction with ETH available on Pacific for gas. Then follow its History status through any proof, waiting and finalisation steps the interface presents. You will need ETH on Ethereum for a final Ethereum transaction if the route asks you to complete one; Pacific ETH cannot pay Ethereum gas before it arrives.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does It Cost, and How Long Does It Take?
&lt;/h2&gt;

&lt;p&gt;The cost is chiefly network gas, and the return trip can take much longer than the deposit. An Ethereum deposit incurs Ethereum gas; an ERC-20 may require a separately paid approval. A withdrawal starts with Pacific gas and may require another Ethereum transaction to finalise. Review the wallet’s gas estimate and the bridge’s displayed amount to receive before confirming.&lt;/p&gt;

&lt;p&gt;Gas is measured in ETH, not as a fixed percentage of the amount bridged. For example, a transaction using 100,000 gas at 10 gwei per gas costs 0.001 ETH. That calculation is illustrative: the gas used and Ethereum gas price change, so a small transfer can be expensive relative to its value even when the token amount is unchanged.&lt;/p&gt;

&lt;p&gt;Deposits commonly arrive in minutes after Ethereum confirmation and processing on Pacific. Native withdrawals have a different timetable because the layer 2 state must be accepted on Ethereum. Manta Network has described a &lt;strong&gt;three-day&lt;/strong&gt; standard challenge period for its optimistic withdrawal path; check the current estimate shown for your specific withdrawal, since the route and finality process can change.&lt;/p&gt;

&lt;p&gt;If timing matters, compare the complete amount received, all gas payments, supported token version and stated arrival time before choosing a route. A faster independent liquidity bridge may quote a different fee or token representation. I would use the native route when preserving the canonical Ethereum-to-Pacific token path matters more than a quick exit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Is My Manta Bridge Transfer Pending?
&lt;/h2&gt;

&lt;p&gt;A pending Manta Bridge transfer usually means one stage has finished while the next has not. First check the source transaction hash on the appropriate chain: a wallet request that was never confirmed is different from a successful deposit awaiting credit on Pacific. If the source transaction failed, the asset has not crossed.&lt;/p&gt;

&lt;p&gt;For a withdrawal, “waiting for state root” or a similar status can reflect the withdrawal finality process rather than a lost balance. Check History for a proof or finalisation action and whether the waiting period has elapsed. If the source transaction succeeded but the expected next step remains unavailable beyond the displayed estimate, keep the hash and contact the route’s support; do not start a duplicate transfer merely because the wallet balance changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is Manta Bridge the Official Way to Move Assets to Manta Pacific?
&lt;/h2&gt;

&lt;p&gt;Yes. Manta Bridge is Manta Network’s native Ethereum Mainnet–Manta Pacific route. Manta Network also displays independent bridge providers, but their routes, fees, arrival times and token versions can differ. “Official” identifies who operates the native route; it does not make every available transfer equally suitable for your asset and deadline.&lt;/p&gt;

&lt;p&gt;Before connecting a wallet, reach the native bridge through Manta Network’s own site and check the requested networks and contract permissions in your wallet. The ERC-20 standard, EIP-20, makes an approval a permission for a contract to spend tokens; read the allowance amount instead of treating that prompt as the transfer itself. The practical sequence is to verify the route and token, budget gas on each chain, then track the transfer through to its destination balance.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>When Your Swap Returns Less, Find the Cause</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Tue, 20 Oct 2026 14:58:49 +0000</pubDate>
      <link>https://dev.to/mack_schneider/when-your-swap-returns-less-find-the-cause-c1o</link>
      <guid>https://dev.to/mack_schneider/when-your-swap-returns-less-find-the-cause-c1o</guid>
      <description>&lt;p&gt;If you received fewer tokens than the first quote showed, the pool price may have moved before your trade completed. &lt;a href="https://cryptoassetwire.pages.dev/quickswaps-first-swap-and-liquidity-position-explained/" rel="noopener noreferrer"&gt;How QuickSwap swaps tokens and adds liquidity&lt;/a&gt; explains where that quote comes from; here, you’ll learn what can change it. The key is to separate the pool’s price effect from a price move while your transaction waits.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pool size and trading fee shape your quote
&lt;/h2&gt;

&lt;p&gt;A swap quote already accounts for the pool’s trading fee and the effect your trade has on the pool price. A liquidity pool is a shared supply of two tokens that traders exchange. In a common automated market maker, or AMM, the pool adjusts its price as its token balances change.&lt;/p&gt;

&lt;p&gt;Imagine a pool with 1,000 Token A and 100,000 Token B. Before fees, its balance ratio suggests 100 B for each A. But a trade of 10 A takes a noticeable share of the smaller reserve. The pool’s pricing rule means each extra A gets slightly fewer B, so the average rate across the trade is worse than 100 to 1.&lt;/p&gt;

&lt;p&gt;This built-in difference between the pool’s starting rate and your average rate is called &lt;strong&gt;price impact&lt;/strong&gt;. A deeper pool has more tokens available, so the same trade usually has less impact. On QuickSwap, compare the quote for your chosen amount with a smaller amount: if the smaller trade gives a better rate, the pool may be shallow for your order.&lt;/p&gt;

&lt;p&gt;The trading fee is another part of the quote. Fees vary by pool and version; common V2 pools are often around 0.25%–0.30%, but check the fee shown for your selected pool. The network fee, often called &lt;strong&gt;gas&lt;/strong&gt;, pays for processing your transaction. It is usually paid separately in the network’s native token, so it can add to your total cost without changing the token amount shown in the quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  Waiting can change the amount you receive
&lt;/h2&gt;

&lt;p&gt;A quote is an estimate based on the pool’s state when you request it. Other trades can change that state before yours is confirmed. The difference caused by movement between the quote and execution is often called &lt;strong&gt;slippage&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;When you set a slippage tolerance, you set how far the final amount may fall below your quoted amount before the trade fails. For example, if the quote is 1,000 tokens and tolerance is 0.5%, the transaction generally requires at least 995. If the pool moves past that limit, the swap should revert instead of completing below your minimum. A reverted swap can still cost gas because the network processed the failed attempt.&lt;/p&gt;

&lt;p&gt;Try this when a quote looks worse than expected: enter a smaller amount and compare the rate; check the displayed fee and minimum received; then check whether the transaction is still pending. If the quote changes while it waits, a tighter tolerance may protect your minimum but make failure more likely. Raising tolerance can let a trade complete after a bigger move, but it also accepts a worse minimum. It does not improve the price.&lt;/p&gt;

&lt;p&gt;Before confirming, check the token names, amount, network, fee, and minimum received in your wallet. If the minimum is lower than you are willing to accept, cancel the attempt or adjust the trade before signing. A practical habit is to compare the rate for half your intended amount first; that quickly shows whether pool depth is driving the poor quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions traders check after a quote changes
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does slippage tolerance reduce the trading fee?
&lt;/h3&gt;

&lt;p&gt;No. The pool fee is charged under the pool’s rules and is already reflected in the quote. Slippage tolerance sets the lowest output you will accept if the pool changes before execution. Lowering tolerance does not make the trade cheaper; it only makes the swap more likely to fail when the price moves beyond your limit.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why did my swap fail but still cost gas?
&lt;/h3&gt;

&lt;p&gt;The network still had to process the transaction and its checks. If the output fell below your minimum, the swap could revert, meaning the token exchange was undone. The network fee may still be charged for that work. Check the transaction status in your wallet or a block explorer before trying again, so you do not accidentally repeat a completed swap.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I raise slippage to make the swap go through?
&lt;/h3&gt;

&lt;p&gt;Only raise it if you are comfortable accepting a lower minimum output. A higher setting can help a trade complete when prices move quickly, but it does not fix a shallow pool or improve your rate. First check the amount, pool fee, and minimum received. If the rate still looks poor, try a smaller trade or wait for a better quote.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Wallet Signing Is Slow? Handle Expiring Swap Quotes</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Sat, 17 Oct 2026 09:36:59 +0000</pubDate>
      <link>https://dev.to/mack_schneider/wallet-signing-is-slow-handle-expiring-swap-quotes-1cfj</link>
      <guid>https://dev.to/mack_schneider/wallet-signing-is-slow-handle-expiring-swap-quotes-1cfj</guid>
      <description>&lt;p&gt;If you are moving crypto from your own wallet and signing takes a minute, check whether the route quote is still current before you submit it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What expires while you sign?
&lt;/h2&gt;

&lt;p&gt;A route quote is a time-limited estimate of what a cross-chain transfer may deliver. It combines the source-chain transaction, any swaps, and the planned transfer to the destination chain. Unlike a centralised exchange order, it usually does not reserve a price while you review it.&lt;/p&gt;

&lt;p&gt;The expiry window depends on the service and route; there is no standard duration. When a quote expires, its estimated output may no longer be reliable. LI.FI’s quote documentation describes routes as transfer plans, while Ethereum’s EIP-1559 specification explains why network fees can change from block to block.&lt;/p&gt;

&lt;p&gt;Quote expiry and an on-chain deadline are different. Expiry may mean the service will no longer stand behind the estimate; a transaction deadline is a condition written into a transaction that can make it fail after a set time. Some transactions also enforce a minimum output, the least amount you agree to receive. Check the wallet details for those conditions when available.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can signing time change the result?
&lt;/h2&gt;

&lt;p&gt;Signing time matters because prices and available liquidity can move while you review the wallet request. Signing approves a transaction; it does not freeze the quoted price or guarantee that the transaction will succeed. Some tokens also need an approval, which lets a contract spend a set amount of your token, before the transfer can proceed.&lt;/p&gt;

&lt;p&gt;Say a route estimates 995 destination tokens for 1,000 USDC and expires after 60 seconds. If you spend a minute checking the chain and fee details, the new quote might estimate 989 tokens. Refreshing gives you a current estimate; it does not move your funds by itself. For acrossbridge users making a cross-chain move and swap in one flow, &lt;a href="https://jesseowji514250.isblog.net/how-to-use-acrossbridge-to-move-crypto-between-chains-60890048" rel="noopener noreferrer"&gt;acrossbridge crypto&lt;/a&gt; handles that combined transfer task.&lt;/p&gt;

&lt;p&gt;Before signing, compare the destination amount and any minimum output with the fresh quote. If the older request is still open in your wallet, review it again rather than assuming the service’s displayed quote still applies. A lower minimum output allows more price movement, but it also means you could receive less.&lt;/p&gt;

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

&lt;p&gt;Get a fresh quote if the old one has expired, the wallet request sat open, or the displayed amount changed. Then check that the source token, source network, destination token, and destination network match your intention. A correct amount sent on the wrong network can create a difficult recovery.&lt;/p&gt;

&lt;p&gt;Review the wallet’s network fee separately from the route’s estimated output. The fee pays the source network to process your transaction, and congestion can change it while you wait. If the fee or output no longer suits you, reject the request and review a fresh quote instead of rushing to sign.&lt;/p&gt;

&lt;p&gt;Allow time to read the wallet prompt, then act on the current quote: it is an estimate with a clock, not a reserved exchange order.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Do I Move Crypto Before Network Rewards Expire?</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Fri, 16 Oct 2026 23:55:30 +0000</pubDate>
      <link>https://dev.to/mack_schneider/how-do-i-move-crypto-before-network-rewards-expire-51g4</link>
      <guid>https://dev.to/mack_schneider/how-do-i-move-crypto-before-network-rewards-expire-51g4</guid>
      <description>&lt;p&gt;To move crypto before network rewards expire, check the program’s cutoff and eligibility rules, then allow time for the bridge and any required swap to finish. A transfer that starts before a deadline may arrive too late to qualify. Leave time for delays, destination-chain fees, and the action that earns the reward.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does “rewards expire” mean?
&lt;/h2&gt;

&lt;p&gt;A rewards deadline can stop new rewards, end a campaign, or close the window to claim tokens already earned. These are different dates, so check which one applies before moving funds.&lt;/p&gt;

&lt;p&gt;Look for the exact cutoff time and time zone, eligible assets and actions, and how the program records activity. Some programs count a balance at a snapshot, a recorded check at a set time; others count completed actions. A pending transfer may not count.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much time should I allow for a cross-chain move?
&lt;/h2&gt;

&lt;p&gt;A bridge moves assets between blockchains, which are separate networks with their own records. In a typical transfer, the source-chain transaction is confirmed, a bridge verifies it, and the destination chain releases or creates the corresponding asset. The wait depends on the chains and bridge. Ethereum.org’s bridge primer and Chainlink’s finality notes explain why transfers can involve more than one confirmation step.&lt;/p&gt;

&lt;p&gt;For a reward on a destination chain, the assets usually need to arrive there before you can take the qualifying action. If the program rewards lending a token, for example, simply sending it across may not qualify; the program may require the token to be deposited in an eligible lending pool.&lt;/p&gt;

&lt;p&gt;When a bridge and swap can happen in one cross-chain flow, &lt;a href="https://crypto-today.news/how-businesses-can-use-paraswap-for-cross-chain-transfers/" rel="noopener noreferrer"&gt;ParaSwap&lt;/a&gt; can move crypto to the destination chain and swap it into an asset there. That can help when the asset you hold differs from the one the reward program requires, but the final action still has to meet that program’s rules.&lt;/p&gt;

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

&lt;p&gt;First, work backward from the deadline. If a program closes at 20:00 UTC and you want to act by 18:00, treat 18:00 as your personal cutoff. A delay or failed transaction could otherwise leave too little time.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the qualifying action.&lt;/strong&gt; Check whether you must hold, swap, lend, stake, or provide liquidity. “Stake” means locking tokens to support a network or service. “Liquidity” means tokens placed in a trading pool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the destination asset and chain.&lt;/strong&gt; A token with the same name can exist on multiple networks. Confirm that the program accepts the version arriving on the destination chain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep fee money available.&lt;/strong&gt; Each chain may charge a transaction fee, usually paid in its own native token. You may need fee money on the source chain to send funds and on the destination chain to complete the qualifying action.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare the reward with the cost and risk.&lt;/strong&gt; Include bridge and swap costs, token price changes, and the chance of a delay. A small reward may not justify moving funds in a rush.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How does the timing work in practice?
&lt;/h2&gt;

&lt;p&gt;Say you have $500 in a stablecoin, a token designed to stay near one dollar, on one chain. A program on Arbitrum ends at 20:00 UTC and rewards deposits of a different token. You need the transfer and swap to finish, then must deposit the qualifying token before the program’s cutoff.&lt;/p&gt;

&lt;p&gt;If the move takes longer than expected, the deposit may miss the deadline even if you sent the funds earlier. I would leave several hours of slack when the rules do not say exactly which transaction time counts. For a slow route or a short deadline, I would skip it rather than risk funds for a reward that may not arrive.&lt;/p&gt;

&lt;p&gt;After the deadline, check whether earned rewards need a separate claim and whether that claim has its own end date. ParaSwap can handle the cross-chain move and swap; the reward program decides whether your completed action qualifies.&lt;/p&gt;

&lt;p&gt;The answer changes if the rules explicitly count a source-chain transaction started before the cutoff, or if the program has no fixed end date. Follow that program’s stated eligibility test, since it determines whether moving now is useful.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Cross-Chain Treasury Test Transfers in 2026</title>
      <dc:creator>Mack Schneider</dc:creator>
      <pubDate>Fri, 16 Oct 2026 14:57:25 +0000</pubDate>
      <link>https://dev.to/mack_schneider/cross-chain-treasury-test-transfers-in-2026-4h55</link>
      <guid>https://dev.to/mack_schneider/cross-chain-treasury-test-transfers-in-2026-4h55</guid>
      <description>&lt;p&gt;If you are moving treasury funds between chains a few times a year, send a small test first, then check what arrives before moving the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a test transfer tell you?
&lt;/h2&gt;

&lt;p&gt;A test checks that the whole route works for your specific assets and destination. It can reveal a wrong destination address, an unsupported asset, or a delay before you commit the larger amount.&lt;/p&gt;

&lt;p&gt;A cross-chain transfer can involve more than one step. Your source chain records the outgoing transaction; a bridge then arranges the asset on the destination chain, sometimes through a liquidity pool, which is a shared reserve used to exchange assets. If you also change assets, a swap adds another exchange to the route.&lt;/p&gt;

&lt;p&gt;For a transfer that needs both a chain move and an asset change, the &lt;a href="https://www.tumblr.com/intrepidserpentastronaut/830401305844613120/when-is-a-native-asset-bridge-the-right-route" rel="noopener noreferrer"&gt;Biswap crypto bridge&lt;/a&gt; moves and swaps assets across chains in one flow. Biswap fits when the treasury needs the destination asset, rather than the same asset on another chain.&lt;/p&gt;

&lt;h2&gt;
  
  
  How small should the test be?
&lt;/h2&gt;

&lt;p&gt;Choose an amount large enough to clear the route’s minimums and fixed costs, but small enough to limit your exposure if something goes wrong. A tiny test can mislead you if fees take a large share or the route rejects amounts below its minimum.&lt;/p&gt;

&lt;p&gt;For example, if you plan to move 10,000 units, you might test with 100 units first. Treat that as an illustration, not a rule: network fees, service minimums, and the asset’s value should set your actual test size.&lt;/p&gt;

&lt;p&gt;Before sending, estimate the full cost. You may pay a source-chain transaction fee, a bridge fee, a swap cost if you change assets, and a destination-chain fee to use the funds. Some costs are fixed, so sending ten times more may not make the test ten times more expensive.&lt;/p&gt;

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

&lt;p&gt;Check the destination network and address, then confirm that the receiving wallet or treasury system can use the exact asset arriving there. Similar asset names can refer to different tokens, and an exchange may not credit a token on every network.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the source and destination networks.&lt;/li&gt;
&lt;li&gt;Check the destination address and asset contract, if shown.&lt;/li&gt;
&lt;li&gt;Estimate fees and the amount expected to arrive.&lt;/li&gt;
&lt;li&gt;Make sure you can pay the destination network’s fee after arrival.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After the test, compare the destination balance with the expected amount and confirm the asset and network. A transfer can arrive successfully while still delivering less than expected because a swap price changed. Slippage means the difference between the expected swap price and the final one.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is it safe to send the main amount?
&lt;/h2&gt;

&lt;p&gt;Send the larger transfer only after the test arrives as the expected asset, on the intended network, at the intended address. Also check that the destination funds are usable, not merely visible in a wallet.&lt;/p&gt;

&lt;p&gt;A common mistake is to test with one asset and then send another through a different route. That test does not prove the larger transfer will behave the same way. Keep the source asset, destination asset, networks, and route consistent; if any changes, run a new test.&lt;/p&gt;

&lt;p&gt;For a large treasury movement, split the main transfer into planned portions if the route’s available liquidity or price impact could change as the amount grows. Price impact is the way a large swap can move its own exchange price. I would use a test to confirm the route, then review the expected received amount again before each portion.&lt;/p&gt;

&lt;p&gt;In short, make the test representative, verify the destination asset and usable balance, and only then move the main funds. That small check can catch costly setup mistakes before they affect the treasury.&lt;/p&gt;

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