Posts

Showing posts from November, 2026

Choosing a Bitcoin Bridge by Its Upgrade Controls

If you are comparing Bitcoin bridge routes that already meet your application’s needs, choose by who can change the wrapped token, how long a change takes, and whether you can exit before it takes effect. Upgradeability can let a team repair a serious contract flaw, but it also makes your holdings depend on whoever controls the upgrade. The right balance depends on how much you trust that decision process and how quickly you can respond to it. Trace who can replace the token’s logic A proxy can keep the same token address while handing calls to a replacement implementation. That means a familiar address and unchanged balance do not guarantee that the rules governing transfers, approvals or other token behavior have stayed the same. The proxy’s upgrade mechanism determines how its implementation can change. OpenZeppelin’s Proxy Upgrade Pattern documentation describes this separation between a proxy and its implementation. When reviewing a route, find the deployed proxy and identify the ...

Monad Bridge: Why Pay Monad Gas Up Front?

If your quote lists a native-token delivery fee, it is prepaying a relayer to execute the transfer on Monad; it is not a second charge for gas on the source chain. You pay in advance, often with a token you already hold, because the delivery transaction must be paid for in MON even if you do not hold any yet. Why is Monad gas charged on the source chain? The source-chain payment funds the person or service that submits your delivery on Monad. On a message-verified route, the source contract records the transfer message and takes a native-token payment; an off-chain relayer watches for the verified message, submits the Monad transaction, and spends MON on its gas. The prepaid fee reimburses that relayer. A prepaid relayer fee is one of what costs to expect from a Monad bridge : it applies when the route needs a relayer to submit delivery on Monad. The payment happens on the source chain because that is where you initiate the transfer, while the gas is spent on the destination chain. Wha...

How Bridge Admin Keys Affect Tokens You Hold on Monad

If the bridge’s admin can change the contracts or verification rules that govern redemption, completing a transfer does not end your exposure: those powers can affect whether and how you redeem tokens you still hold. What can an admin change? Admin powers matter after bridging because your tokens depend on contracts and backing that determine how they can be redeemed. A key may control one function or several; its label alone does not tell you the scope. Look for an upgradeable proxy and identify who can change its implementation. That authority can replace the logic governing transfers or redemption; an immutable contract cannot be changed after deployment. Look for pause and rate-limit controls. A pause can stop transfers during an incident, while a rate limit caps how much can move in a period; either can also delay your exit. Identify who can change the verifier or verification configuration. If an admin can alter how cross-chain messages are accepted, that can change the condition...

Does TeleSwap Need Destination Gas to Receive BTC?

If you hold only BTC and have no balance on your destination chain, you can still receive bridged BTC without first buying that chain’s gas token. A Teleporter submits the minting transaction and pays its gas, with compensation deducted from your BTC deposit; you will need native gas for actions you sign after the funds arrive. Receiving teleBTC does not require your gas balance Your BTC deposit starts a process that a Teleporter completes on the destination chain. Teleporters relay proof of the Bitcoin transaction, then sign and submit the transaction that mints teleBTC to your address. Because the Teleporter pays the destination gas, your empty destination wallet does not make receipt fail. That separation is central to the TeleSwap protocol : the operator handles gas for minting, while the fee deducted from your deposit compensates the operator. In a constructed example, you deposit BTC intending to use it in DeFi on Polygon. Once the mint is complete, teleBTC can appear in your wal...

First-time bridge users: why destination gas raises the base fee

When you bridge to a destination, cBridge’s base fee reflects the gas needed to deliver your tokens there, so it can rise even when your transfer amount stays the same. What does the base fee pay for? The base fee covers the destination-chain transaction that releases or delivers your tokens to you. That transaction uses gas, the resource blockchains charge for processing actions. cBridge estimates the delivery gas cost, converts it into the token you are transferring at its current price, and deducts that amount from what you receive. A useful approximation is: base fee ≈ delivery gas units × destination gas price, converted into the transferred token. The estimate can change if destination gas prices spike or the token’s price changes, even if you keep the same route and amount. Why do destination chains have different base fees? The destination chain’s gas cost is the main driver: a delivery on a high-gas chain such as Ethereum mainnet can cost more than one on a low-gas chain. Hold...

Unwinding a Leveraged DeFi Loan With Flashbots

To close a leveraged lending position with less risk of sandwich losses, repay some debt first, withdraw only collateral that leaves your health factor safely above the liquidation threshold, then swap it to the debt token through private transaction submission. Why the order matters Keep the position healthy throughout the unwind: withdrawing collateral before repaying debt reduces your safety margin and can bring liquidation closer. A health factor compares your collateral’s borrowing value with your debt under the lending protocol’s rules; below the protocol’s threshold, liquidators can repay part of your debt and claim collateral under its liquidation terms. The ethereum.org entry “Maximal extractable value (MEV)” defines MEV as value extracted by changing transaction inclusion, exclusion, or order in a block. It describes both liquidations and sandwich trading as MEV opportunities, but the mechanisms differ: a sandwich targets the price impact of a swap, while liquidation follows ...

Signed a cBridge Withdrawal? Find the Missing Payout Step

A signed cBridge withdrawal is only a request; tokens arrive after authorization and a successful release transaction, which may be delayed. If your wallet has no payout, identify the withdrawal’s current stage in Liquidity History before deciding whether to wait, confirm, or investigate a failed transaction. Three milestones separate your signature from a payout The initial signature records your request to remove liquidity; it does not send tokens to your wallet. The request must then be authorized by the State Guardian Network (SGN), and the release must complete on the withdrawal chain. Each milestone has different evidence, so a signature in your wallet is not proof that a payout transaction occurred. For a standard signing wallet, cBridge security is relevant at this boundary: your first signature records intent, while a later wallet transaction can authorize the release of tokens. The cBridge LP Guide’s liquidity removal flow describes the initial signing, subsequent confirmati...

No direct token route? Weigh a two-hop transfer

If your token has no supported direct route and no single-transfer alternative can deliver a comparable amount, a two-hop route can get it there; otherwise, I would not add a chain. Each leg is a separate transfer with its own fees, wait and refund risk. That makes the extra hop useful only when the missing connection leaves no practical direct option. What two transfers add A two-hop cBridge route means sending the token to an intermediate chain, then starting a second transfer from there to your destination. Understanding cBridge transfers matters because it helps you judge whether the second leg is a viable transfer in its own right, rather than assuming the first one guarantees the journey. Budget for two base fees, two protocol fees and gas on both source chains. The second source chain is the intermediate chain, so you need its native gas token there to submit the next transfer. The displayed fees can vary by route and conditions; compare the total amount expected at the destina...

Why does one ShibaSwap pair have several fee tiers?

On shiba swap, each listed fee tier is a separate pool that charges that rate on every swap, but a higher rate does not automatically mean higher earnings. Fees go to liquidity providers in that specific pool, and your share depends on your liquidity relative to the pool’s. The practical comparison is the fee rate multiplied by the trading volume the pool attracts, with the pool’s liquidity affecting your share. Each fee tier has its own pool and trading activity Pools for the same token pair operate independently: each has its own price, liquidity and liquidity-provider positions. A position in one tier does not earn fees from swaps through another tier. The Uniswap v3 Core whitepaper by Adams et al. (2021) describes this multiple-pool design, in which a pair can have pools with different fee tiers. That design explains the distinction, but it does not show which tier currently gets the most ShibaSwap volume. Traders tend to route through the pool that gives them the best net price af...

How Do I Sell a Taxed Token on Matcha Swap Without Reverts?

To complete a taxed-token swap, find the tax for the direction you are trading, set slippage slightly above that rate, and test with a small amount. The token’s contract deducts part of a transfer, so the amount that reaches the trade or your wallet can fall below the quote; this approach assumes the contract permits the sale. Which tax applies to this swap direction? Use the buy tax when the taxed token is being bought, and the sell tax when you are selling it. These rates can differ, so a token’s advertised “tax” may not tell you which rate applies to your trade. A token contract can take its fee from the transfer into a pool or router, or from the transfer of tokens to your wallet. That distinction matters when Matcha swap routes a trade: the interface can show an estimated output, but a transfer tax can reduce what reaches the next step. For a sell, less input may reach the route; for a buy, less of the quoted token may arrive in your wallet. The effect depends on where the contra...

Converting a partial liquidity withdrawal to one token

If your position still has liquidity after the withdrawal, you can receive proceeds in one chosen token by collecting what the withdrawal releases and swapping the unwanted token separately. A liquidity decrease releases the pair’s current amounts; it does not choose a payout asset. If the withdrawal already yields only your chosen token, no conversion is needed. That distinction matters when using a ShibaSwap-related liquidity position: shiba swap exchange is part of the broader trading and liquidity context, but removing liquidity and exchanging tokens remain separate operations. In the steps below, “position” means the accessible liquidity position you intend to reduce, and the available controls depend on the interface and pool. What does a partial withdrawal release? A partial decrease releases the token amounts represented by the fraction you remove, based on the position’s current state and the pool. It does not guarantee a fixed ratio or let you nominate one of the pair as the...

How do I compare Monad bridge routes by net value?

Image
If you compare several routes for the same transfer, rank them by usable value delivered to Monad after source-chain gas and any extra MON you need to buy. Headline bridge fees leave out costs such as exchange-rate spread, so the displayed fee alone can put the routes in the wrong order. Which number should I compare? Use one net value for each route: the value of the minimum amount the quote says you will receive on Monad, minus the source-chain gas you pay and the cost of any extra MON needed for gas. This makes the routes comparable even when one displays a bridge fee and another emphasizes an exchange rate. Start with the quote’s minimum received amount, rather than the estimated or expected amount. The minimum is the amount the route represents as deliverable under its stated quote conditions; the estimate may be more optimistic. Convert that minimum to a common value, such as the value of the asset you are sending, using the same price basis for every route. Then subtract the so...

Why does my Matcha swap quote change before I confirm?

Image
If the wallet prompt still reflects the route and minimum received you reviewed, a changing receive amount before signing is usually a live quote refresh, not by itself a sign that something is wrong. On Matcha swap, each refresh uses current liquidity, so the amount that matters for your trade is the quote and minimum received attached to the transaction you confirm. Each refresh recalculates the route from live liquidity A receive amount that shifts between refreshes means the quote has been rebuilt using current prices and pool reserves. Those reserves change as other traders buy and sell, and market makers update their prices block by block. The refreshed quote may also use a different route through available pools, so the amount can change even when you have not changed your input. The network affects which liquidity a route can use. Before requesting a quote, make sure you have selected a network where the tokens and route are supported; the Matcha swap supported networks are r...

Before Bridging to a Polygon App, Confirm Its Chain

The Polygon bridge sends supported assets to Polygon PoS only; if your app runs on zkEVM or another chain, you need a bridge for that destination. The app uses Polygon PoS: choose a route that lists Polygon PoS as the destination. The app uses Polygon zkEVM: use a route that lists zkEVM, because a Polygon PoS balance will not appear there. The app names another chain: find a bridge route to that chain before sending funds. Polygon PoS and zkEVM Keep Separate Balances Polygon PoS and Polygon zkEVM are separate networks, each with its own bridge contracts and token records. A token balance is recorded on the network where the transfer arrives; sharing the Polygon name does not make balances visible across both chains. A bridge's destination is the deciding criterion: the Polygon bridge records supported transfers on Polygon PoS. If your app reads balances on zkEVM, that transfer will not fund it, even if the same wallet address is used on both networks. Consider two cases with th...

Why Is One Chainlist RPC Several Blocks Behind?

Image
If one RPC stays several blocks behind across repeated refreshes, it is serving an older chain state, so treat it as stale for live wallet activity; that does not mean its data for the older block is wrong. When comparing RPC rows on Chainlist, a gap of a block or two during a single measurement can be ordinary timing noise. What Does a Lower Block Height Mean? A lower block height means that node has imported fewer blocks than a node reporting the current chain tip. The height is the number of the latest block the node knows about; it is not a score for the RPC or a separate balance of the network. Nodes sync independently. Each receives new blocks, checks them, and makes their transactions available to queries. A node that is overloaded, has weak network peering, or is serving cached responses may fall behind while other nodes continue updating. Its JSON-RPC responses then describe the latest block it has imported, which may be an earlier moment in the same chain. That distinction m...

Upgrade and Pause Controls for EigenLayer Restakes

Image
The core contracts holding an EigenLayer restake can be upgraded by multisig-controlled roles after a timelock, while a separate pauser can halt supported actions sooner. Proxies let authorized upgrades change contract logic after deposit A proxy is a contract address that holds or accounts for a position while directing activity to separate implementation code. If an authorized upgrade changes that implementation, the rules applied to deposits can change without moving the deposits to a new address. The eigen layer protocol is a concrete example of an Ethereum restaking protocol whose core contracts use upgradeable proxies, so reviewing the upgrade path matters even after you have deposited. The upgrade path adds a delay between authorization and effect. A multisig-controlled role queues an upgrade through a timelock, a contract that prevents the queued transaction from executing until its delay has passed. After that window, an authorized party can execute the transaction and apply...

How to Use cBridge to Complete a DeFi Deposit

Image
Use cBridge to move funds to the chain where your DeFi app accepts deposits, then make the app’s deposit transaction separately. The key is whether the delivered token matches the app’s accepted token contract and leaves enough funds for destination gas. If the route cannot deliver an accepted token, plan a swap or choose another route before bridging. What exactly must arrive on the destination chain? The app’s accepted token contract determines what must reach your wallet before you deposit. Find the destination chain and the app’s deposit asset, then verify the token contract the app accepts; matching ticker symbols alone do not establish that two tokens are interchangeable. Knowing that cBridge liquidity pools provide liquidity for transfers is useful background when comparing available routes. For your deposit, though, the decisive question is whether the route delivers the token contract the app accepts, not just a token with a familiar name. Consider two otherwise identical ca...

Monad Bridge Refunds: Expect the Bridge-Step Token

Image
A failed Monad bridge transfer can return a different token when a source swap completed before the bridge failed; the refund depends on where the route stopped and the provider’s recovery rules. If your route swapped ETH to USDC before bridging, a source-side refund may return USDC because that is what the bridge step received. The completed swap does not necessarily reverse itself during recovery. A completed source swap can leave USDC as the refund A cross-chain route can contain several steps: first a swap on the source chain, then a bridge transfer, and sometimes another swap on the destination chain. If the source swap succeeds but the bridge cannot complete, recovery may act on the bridge step alone. It can return that step’s input token without undoing the earlier conversion. For example, a route that starts with ETH may swap it to USDC on the source chain and then attempt to bridge USDC to Monad. If the bridge fails and the provider starts an origin-side refund, the recovery ...

Where Is My Fraxswap Long-Term Order ID?

Image
If you still have the wallet that placed the order, you can find it by returning to the same network and tracing the placement transaction to its pair contract and order ID. The order is stored in that contract under your address, so a different network or wallet can make it look missing even when it still exists. The order is tied to its original network and address A long-term order belongs to the pair contract on the network where you placed it, and its record is associated with the placing address and an order ID. It is not stored in the app or in your wallet. Reconnecting the original address and selecting the original network are both necessary before the app can show the right order. That record tells you what was deposited, when the order is due to end, and what proceeds are available. If you find the order but its execution state is unclear, what a stuck Fraxswap order is doing can help explain what that state means for the proceeds you see. For example, suppose you placed a...

Failed: Decide Before Sending

Image
If the wallet reports that simulation ran and the transaction reverted, do not submit it; fix the cause first. If simulation could not run because the RPC timed out or failed to respond, retry estimation through a validated endpoint. A larger gas limit helps only with a diagnosed estimation limitation, not an unexplained failure. Separate an RPC failure from an execution rejection A failed estimate has two different meanings: the wallet may not have obtained a simulation, or the simulation may have shown that this transaction would fail. Ethereum’s eth_estimateGas call simulates execution without broadcasting the transaction. A timeout or transport error means the wallet lacks a result; an execution-reverted response means the simulated call reached a contract condition that rejected it. That distinction decides what to try next. If the RPC call timed out, retry estimation after confirming the network and endpoint are responsive. If the response reports a revert, inspect the proposed ...
Image
If your funds are on Ethereum and Arbitrum is not yet in your wallet, add the destination network first, then use the bridge’s official site and switch networks after the transfer completes. Chainlist supplies wallet network settings; it does not move funds. Set up the destination network, then send Follow these steps in order so the wallet can query the chain where the bridge will deliver your funds: Find the destination network on Chainlist and compare its chain ID with the ID in the bridge’s official documentation. A chain ID identifies the network, so the values should match. Add the network to your wallet and approve the request. The wallet may ask to add network settings through wallet_addEthereumChain . EIP-3085 defines that request, including fields such as chainId and rpcUrls , which tell the wallet how to identify and query the network. The ethereum-lists/chains GitHub repository is a public source of chain IDs and network metadata used by directories. Open the destination ...