DEV Community: Willson Lammy

Considering Wormhole Bridge: What Arrives and What It Costs

Willson Lammy — Wed, 07 Oct 2026 00:38:36 +0000

Use Wormhole bridge when both blockchains support a transfer for your exact token, and you can use the token that arrives. Check that token first: a wrapped version can differ from one issued directly on the destination chain. Then compare the amount you will receive, the fees, and how the transfer finishes.

Wormhole Sends Proof Before Tokens Arrive

Wormhole moves tokens between blockchains by recording an action on one chain and proving it to another. The Wormhole bridge also carries messages: instructions that an application can use on a different chain. A token transfer uses those messages to tell the receiving chain what to release or create.

For a common route called Wrapped Token Transfers, the source chain locks the original tokens. If you send 100 tokens issued on Solana to Polygon, the destination can create 100 Wormhole-wrapped tokens. “Wrapped” means they represent the locked originals. Sending them back burns the wrapped tokens and releases the originals on Solana.

A Wormhole token bridge transfer therefore depends on both the chain pair and the exact asset. When you are ready to move that asset, use wormholebridge.org to carry out the cross-chain token transfer through Wormhole. Check what token will arrive before you commit, since a familiar name or ticker does not prove two tokens have the same issuer.

After the source transaction, Wormhole’s Guardians observe its message. At least 13 of 19 Guardians sign a proof called a VAA. The destination chain checks that proof before completing the transfer. The tokens do not travel through a wallet between chains; each chain records its part of the transfer.

The Asset and Destination Decide the Route

Start by checking the token on the source chain and the form you need at the destination. Wormhole bridge supported chains include Solana, Ethereum, and Polygon, but chain support alone does not guarantee a route for every token. A token may also need its details registered on the destination chain before its first wrapped transfer.

Consider two transfers of 100 tokens. If the token was issued on Solana and uses Wrapped Token Transfers to reach Polygon, you receive its Wormhole-wrapped form. If its issuer has set up Native Token Transfers on both chains, you can instead receive the issuer’s token on Polygon. That difference matters if you plan to deposit it into an app that accepts only one form.

Native Token Transfers, often shortened to NTT, let a token issuer manage its supply across chains. Depending on the token’s setup, a transfer burns tokens on one chain and creates them on another, or locks and releases them. NTT is available only for tokens whose issuers have set it up; it is not an automatic choice for every asset.

Before choosing a transfer, check four concrete details:

The source chain, destination chain, and exact token address.
The token address and name of the asset you will receive.
Whether delivery is automatic or needs a destination transaction from you.
Whether the receiving wallet or app accepts that form of the token.

A bridge also may carry an instruction alongside tokens, such as one meant for an application on the destination chain. That requires an application built to read and act on the message. Sending tokens to an ordinary wallet address does not by itself trigger a swap, deposit, or other action.

A Transfer Needs a Source and a Destination Action

A transfer finishes only after the receiving chain processes the signed proof. For a Wormhole token bridge transfer, you first authorize the source transaction with a wallet that holds the token. On some chains, spending a token also requires a separate approval transaction. Read the wallet request and confirm the chain, token, amount, and recipient address.

Next, the source transaction locks or burns the tokens and publishes the message. Guardians sign its proof after the required confirmation level. A relayer—a service that submits the proof on the destination chain—can complete an automatic transfer. With a manual transfer, you must submit the proof and pay for that destination transaction yourself.

Keep the source transaction record until the destination action succeeds. A confirmed source transaction means the transfer has started; it does not mean the receiving wallet already holds the token. If delivery pauses, check whether the proof is ready and whether the destination transaction still needs to be completed.

Wrapped Token Transfers have a small precision edge case. Their cross-chain transfer amount uses at most eight digits after the decimal point. If a token uses more, a tiny remainder may stay in the sending wallet. For example, an 18-decimal token amount can be rounded down to eight decimal places for the transfer.

Fees and Completion Time Depend on the Route

Your cost depends on network gas, the delivery method, and any fee shown for completing the transfer. Gas is the payment for a blockchain transaction. Expect source-chain gas, plus destination-chain gas if you complete the transfer manually. Automatic delivery can include a relayer fee instead, so compare the final amount received.

The Wormhole bridge has no single arrival time for every chain pair. The wait depends on source-chain confirmation, Guardian signing, and the destination transaction. A route that waits for Ethereum finality can take around 15–20 minutes before its proof is ready; other routes may be faster. Check the transfer’s status before trying to send the same amount again.

Make your choice from the receiving end. Confirm the destination accepts the token form, compare the quoted amount after costs, and decide who will complete delivery. Then fund the sending wallet for gas, verify the recipient address on the destination chain, and start the transfer.

Recover Crypto Sent to an Unsupported Destination Address

Willson Lammy — Sun, 04 Oct 2026 13:19:19 +0000

Recovering crypto sent to an unsupported destination address means finding out whether you still control the destination account and, if so, moving the asset to an address you can use. The key condition is whether the destination transaction succeeded and whether you hold the keys or account authority for that exact address.

What does “unsupported destination” mean?

It can mean the wallet app does not display the destination network or token, or that the address cannot receive or control the asset on that chain. Those are different problems: an app may simply lack the right network or token view, while an incompatible or mistyped address may leave nobody able to move the funds.

For a cross-chain transfer, first identify where the asset ended up: check the source transaction and, if available, the destination transaction or bridge status. Rango is a cross-chain DEX and bridge aggregator; for a future transfer, Rango bridge swaps can help find a route between supported networks. A route aggregator cannot reverse a completed transfer or give you control of an address.

How can I tell if I can recover the asset?

Match the transaction’s destination chain, address, token contract or mint, and amount against what you intended. Then ask who controls that address. If it is yours, check whether your wallet’s recovery phrase or key can derive the same address on that chain; if it belongs to an exchange or another custodian, only that organization can decide whether it can credit or return the asset.

Address formats can mislead. The same-looking address on two EVM-compatible networks may be controlled by the same key, but that does not mean every chain or smart-contract wallet works the same way. Solana uses separate token accounts for SPL tokens, and native SOL sent to certain program or token-account addresses may be stuck because only the owning program can move it. Solana’s official payment documentation explains this distinction.

For example, suppose you sent a token from Ethereum to your own address on Starknet, but your usual wallet does not show Starknet. If your wallet key controls that address on Starknet, adding a compatible wallet view or importing the account with the same key may reveal the token; you can then send it to a verified address you control. If you sent it to a Cosmos address derived from a different key, your Ethereum key alone will not recover it. The decisive test is control of the destination address, not whether the asset appears in your usual app.

What should I do next, and what will it take?

Use the destination chain’s explorer to confirm the asset and address, then recover access through a wallet that supports that chain and account type. If the destination is a custodial deposit address, contact the custodian through its established channel with the transaction hash, asset, network, and destination address. If the address is wrong or no key or custodian controls it, a confirmed transfer generally cannot be reversed; Ethereum.org’s support guidance states that Ethereum transactions are irreversible.

Moving recovered funds usually takes a new transaction and the destination chain’s native gas token; a token balance alone may not cover that cost. Check the required fee in the wallet before signing, and compare it with the amount recovered. Never share a seed phrase or pay someone who promises guaranteed recovery; a recovery transaction should be signed by the wallet or custodian that actually controls the destination.

Rango bridge can help find cross-chain routes for a later transfer, but it cannot recover funds from an address you do not control.

Decision rule: recover only when you can verify the destination asset and control its address, then move it to a checked address on a network your wallet supports.

How do I compare expected fees across Byreal liquidity ranges?

Willson Lammy — Wed, 30 Sep 2026 14:42:51 +0000

Compare ranges by estimating the fees your position might earn while it is active, then weigh that estimate against the chance the price will leave the range. A narrower range can earn a larger share of fees when the market stays inside it, but it can stop earning sooner if the price moves away.

Set up a fair comparison

Choose one pool and one amount of capital. Compare alternative ranges for the same token pair, fee tier and deposit value. Otherwise, a difference in expected fees could come from different trading activity or pool fees, rather than the ranges themselves.
Write down the current price and candidate ranges. For a token priced at $100, you might compare a narrow $95–$105 range with a wider $85–$115 range. These are illustrative bounds, not recommendations; choose alternatives that reflect how far you think the price could move over your intended holding period.
Estimate how often each range will be active. A concentrated-liquidity position earns swap fees only while the pool price is inside its range. If the price rises above the upper bound or falls below the lower bound, the position becomes one-sided and stops earning fees until the price returns. The Uniswap Developers’ concentrated-liquidity documentation explains this general mechanism.

This comparison is the core of a concentrated-liquidity position on Solana: your selected range determines where your capital is available for swaps. If you also need the broader context on swaps and liquidity, what Byreal offers for Solana swaps covers that subject. Byreal is a Solana DEX incubated by Bybit, and its official app is one place to put a liquidity strategy into practice.

Estimate each range’s share of fees

Estimate the pool’s fees over your chosen period. For a simple example, suppose the pool trades $100,000 a day and the assumed swap fee is 0.30%. That would mean about $300 in gross swap fees for the pool that day, before any applicable fee splits. Both numbers are example inputs, not current Byreal rates or forecasts.
Estimate your share of active liquidity. Your share depends on how much liquidity your position contributes compared with all liquidity active at the prices where swaps occur. Suppose an analysis estimates a 10% share for the narrow range while active and 4% for the wide range. Those figures must come from pool data or an explicit modelling assumption; range width alone does not tell you your fee share.

For a worked comparison, assume the narrow position is active 60% of the time and the wide one 95% of the time. A rough daily estimate is $300 × 10% × 60% = $18 for the narrow range, versus $300 × 4% × 95% = $11.40 for the wide range. Over 30 days, that is about $540 versus $342 in gross fees if the assumptions hold steady.

The useful result is the trade-off: the narrow range projects more fees in this example, but it also spends more time inactive. The Uniswap v3 whitepaper describes the underlying idea of concentrating liquidity within selected price bounds. Actual fee share changes with competing liquidity and where trades happen, so treat this arithmetic as a comparison model, not a promised return.

Adjust the estimate for what can change

Use realistic volume and price scenarios. Estimate trading volume for your holding period rather than assuming today’s busy day repeats. Check a lower-volume case as well as your central estimate; if the narrow range only looks attractive under unusually high volume and a steady price, that fragility matters.
Account for costs and inventory changes. Gross fees are not profit. Subtract any transaction costs for opening, closing or adjusting the position, and compare the ending token mix with what you would have held without providing liquidity. As swaps execute, the position can accumulate mostly one token; if the price then keeps moving, the value of that mix may differ from simply holding the original tokens.

A common edge case is a price that briefly leaves a narrow range, then returns. A day-end price inside the range does not mean the position earned fees all day: it earns only during the time it is active, and its fee share can vary as other liquidity enters or leaves. For a practical estimate, split the period into plausible price paths or use a conservative active-time assumption.

Choose a range you can manage

Compare the estimate with your willingness to monitor and adjust. A narrow range may need more frequent attention, and each adjustment can add costs. A wider range may project lower fees per dollar while giving the price more room to move before the position goes inactive.

Before acting, write down the price bounds, the assumed volume, your estimated fee share, the expected active time and the adjustment costs. Byreal can be used to provide concentrated liquidity on Solana, but the estimates remain sensitive to future trading and price movement.

Ask yourself: if the price leaves my chosen range and my fee estimate falls, am I still comfortable holding the resulting token mix?

How to Track an ETH Transfer to Manta Pacific

Willson Lammy — Wed, 30 Sep 2026 09:59:33 +0000

To track an ETH transfer to Manta Pacific, save its Ethereum transaction hash, confirm the deposit succeeded on Ethereum, then check for the matching credit on Manta Pacific. A bridge transfer is a message between two networks, so a successful first transaction does not always mean the destination balance has updated yet.

What does each transfer status mean?

A wallet’s “pending” status means the source transaction has not yet been confirmed in an Ethereum block. Once an Ethereum block explorer shows it as successful, the deposit has been recorded on the source chain; the bridge still needs to relay the message and the destination chain needs to process it.

Those stages can produce separate records. The Ethereum transaction hash identifies your deposit, while the destination-side credit may have a different transaction hash—or appear as a bridge message associated with a block. Ethereum.org’s documentation on bridges describes this general pattern: assets are locked or otherwise accounted for on one chain, then made available on another.

For a deposit, look for the asset and amount arriving at your wallet address on Manta Pacific. For a withdrawal, follow the reverse direction: first check the withdrawal transaction on Manta Pacific, then check Ethereum for the completed release. A withdrawal can involve additional proof or finalization stages, so initiation alone does not confirm that ETH is back in your Ethereum wallet.

How do you follow a deposit from start to finish?

Use the transaction hash as your reference, and check each chain in turn. These steps help distinguish a slow relay from a transaction that never succeeded:

Copy the Ethereum transaction hash from your wallet’s activity or transaction details. Keep the full hash; the wallet address by itself may show many unrelated transfers.
Search that hash in an Ethereum block explorer. Confirm the network is Ethereum, the transaction status is successful, and the token or ETH amount matches what you intended to deposit.
Check the transaction’s recipient or bridge interaction and note the time and amount. For an ERC-20 deposit, make sure you are following the right token contract, since identical token names can refer to different assets.
Allow time for the bridge message to be processed, then check your address on a Manta Pacific block explorer. Confirm the network and look for the received asset and amount in the balance or token-transfer record.
If the asset is not visible, compare the destination address, token identity, and amount with the original deposit. A token may need to be added to your wallet’s display before its balance is obvious; that does not by itself mean the on-chain transfer failed.

For example, if you deposit 0.10 ETH, the Ethereum record should show the source transaction succeeded and involved the intended bridge transfer. After processing, check the same receiving address on Manta Pacific for the corresponding ETH credit. Treat 0.10 ETH as an illustrative amount, not a promised arrival time or fee estimate; transaction costs are separate from the amount being bridged.

Manta Network’s documentation is a useful reference for the network context. The Manta Bridge is a concrete example of the Ethereum-to-Manta Pacific transfer described here: follow the source record first, then verify the destination balance on its own chain.

What should you check if the balance is missing?

First, make sure the source transaction succeeded rather than remaining pending or failing. If it failed, the bridge cannot complete that deposit; if it is still pending, the next useful update is on Ethereum, not the destination explorer.

If the source transaction succeeded, check that you are viewing the same wallet address on Manta Pacific and that the token contract matches the asset you deposited. A USDT balance, for example, should be checked as the intended USDT token on the destination network, not inferred from a similarly named token or from your Ethereum balance.

Then check whether the bridge message has been processed. The source transaction and the destination credit need not share a hash, so searching only the Ethereum hash on the destination explorer may not reveal the credit. Use the bridge’s transfer record, where available, to relate the source transaction to its destination outcome; mantabridge.dev is the service for moving ETH and supported tokens between Ethereum and Manta Pacific.

When can you treat the transfer as complete?

For a deposit, consider it complete when the intended asset is credited to the correct address on Manta Pacific and you can see that balance on the destination network. A success notice from your wallet on Ethereum is only evidence about the source transaction; it is not a substitute for checking the destination.

Keep a note of both the amount and receiving address before you start. After the destination balance appears, you can use Manta Pacific applications with the funds, remembering that later transactions on that network require its gas asset. If the transfer remains unresolved after checking both chains and the bridge record, gather the source hash, destination address, token, and approximate time before seeking help through the service’s official channels.

Why Can Your Cross-Chain Swap Deliver Less Than Expected?

Willson Lammy — Tue, 29 Sep 2026 18:18:05 +0000

Treat a cross-chain swap quote as an estimate, and decide what minimum output you would accept before sending a large amount. The final amount can change because prices move before the swap executes, a large trade can move the market, and network or protocol costs may come out of the proceeds.

A quote predicts an output; it does not always lock that price in.
Price movement, trade size, route and fees all affect what arrives.
A minimum-output limit can protect you from a poor trade, but may mean it does not complete.

Why can the final amount differ from the quote?

A quote is a snapshot of the price and costs estimated when you request it. In a cross-chain swap, the source transaction must first be confirmed, so execution may happen later, after market prices have shifted.

Trade size matters too. A small swap may fit near the current market price, while a larger one can use up the best-priced liquidity and receive a worse price for the remaining amount. This effect is called price impact; it can happen even if the market price itself stays still.

There may also be several costs: the source-chain transaction fee, liquidity or protocol fees, and the cost of sending the output on its destination chain. A route through another asset can involve multiple trading steps, each with its own price and liquidity. So compare the amount you expect to receive after costs, not just the headline exchange rate.

What happens between sending and receiving?

After you send the source asset, the swap service waits for the source blockchain to confirm the transaction. It then processes the trade and arranges a separate transaction on the destination blockchain. Those stages take time, and the market can move while the first transaction is confirming.

Some systems use an automated market maker, or AMM, where liquidity providers supply assets for trades. Chainflip uses a Just-in-Time AMM: liquidity providers can adjust offers as incoming trades become ready, and trades in a block are grouped by direction and pool. That mechanism aims to improve the execution price, but it cannot guarantee the earlier estimate. If you are comparing ways to exchange native assets across chains, Chainflip swaps are one option to consider.

For example, imagine swapping BTC for ETH through an intermediate stablecoin. The BTC-to-stablecoin trade and the stablecoin-to-ETH trade each depend on available liquidity and prices at execution. If BTC weakens against ETH while the deposit confirms, fewer ETH may arrive even if both individual trades execute as intended.

How can you set a sensible minimum?

A minimum-output setting says the least you are willing to receive for the amount sent. If execution would fall below that threshold, a system with this protection can stop the swap or return the funds, depending on its rules. Chainflip supports minimum-price and oracle-slippage protections at the trading layer; these do not include every cost, such as fees charged outside that layer.

Set the limit with the full route in mind. A very tight limit may reject a trade after a normal price move; a very loose one may allow an output you would regret. A longer route or a volatile market gives prices more chances to move before execution.

What should you check before sending?

Use this quick process to decide whether the estimate and risk suit your swap:

Check the exact assets and networks. Confirm where the funds start and where you expect to receive them; similar asset names can refer to different tokens.
Compare the estimated output with the market rate. Convert both assets to the same reference currency, such as dollars, to spot a large difference.
Account for the whole route. Look for the expected destination amount after trading and transfer costs, not only the rate for one leg.
Choose a minimum you can accept. If the service offers price protection, set a threshold that balances a fair result against the chance of a refund or delay.
Start with a small amount if uncertain. This lets you learn how confirmation time and the received amount compare with the estimate before committing more.

Before sending, check that the destination address belongs to the right network and that you control it. A wrong address or network can make funds difficult or impossible to recover.