DEV Community: Angus Schimmel

Cosmos Transfers vs EVM Routes From Your Wallet

Angus Schimmel — Wed, 30 Sep 2026 14:24:13 +0000

Use a Cosmos IBC transfer when both chains have a direct IBC path for the asset; choose an EVM bridge route when the destination or token requires a different bridge or a swap. From your own wallet, you authorize transactions on the source chain, and sometimes the destination chain too, so the key difference is what carries the asset and who completes the cross-chain step.

IBC sends a packet between connected chains, with a relayer carrying proofs and acknowledgements.
EVM routes can lock and mint, burn and mint, or use destination-side liquidity; the bridge design determines what you receive.
Check the destination token and final amount, not only the token name and network.

IBC transfers use packets between connected chains

A Cosmos IBC transfer uses a protocol connection between two chains, rather than a general-purpose path across any networks. You sign a source-chain transaction that sends the transfer packet; a relayer submits the packet and its proof to the destination chain, which processes it and returns an acknowledgement.

For example, if you send 100 ATOM from Cosmos Hub to Osmosis over an established IBC channel, the source chain escrows the ATOM and the destination chain credits a voucher representing it. The voucher’s denomination records its path through IBC; it may look unfamiliar, even when it represents the asset you meant to transfer. Sending it back along the matching path can release the original asset from escrow.

The IBC specifications describe the packet, proof, acknowledgement, and timeout flow. A timeout matters because a packet that is not received before its deadline can be refunded on the source chain; it does not mean that every delayed transfer has failed. Check the transfer’s status and transaction details before trying again, since a retry could send a second transfer.

EVM bridge routes depend on the bridge design

An EVM route is a path between compatible smart-contract networks, but there is no single asset-transfer mechanism shared by all bridges. One bridge may lock tokens on the source chain and mint a representation on the destination; another may burn and mint a token, or release destination tokens from available liquidity.

For instance, moving a token from Ethereum to an EVM chain could mean locking the original token and receiving a wrapped version there. A route that also swaps the asset may deliver a different token altogether. Messaging protocols such as LayerZero and Wormhole can carry cross-chain instructions, but the applications using them determine what those instructions do and what asset you receive.

This changes the wallet work as well. An ERC-20 transfer can require an approval transaction before the bridge transaction, and the destination chain may need a separate transaction for the next action you want to take. Your costs can include source-chain gas, any destination execution cost, and swap price impact; the amounts vary with network demand, route design, liquidity, and trade size.

Choose by destination asset and completion conditions

Compare the asset you hold with the asset you need at the destination, including whether it is native, escrow-backed, or a wrapped representation. Then check the destination chain, receiving address, estimated amount after any swap, and whether the route requires another transaction once funds arrive.

If you are comparing routes across networks, Rango Exchange is a cross-chain DEX and bridge aggregator that can route swaps across EVM chains, Solana, Cosmos, and Bitcoin. For the full explanation of what Rango Bridge does, see the article focused on how its swaps work; this comparison is about choosing between Cosmos IBC transfers and EVM routes.

For a first self-custody transfer, try a small amount when practical and confirm the recipient address belongs to the intended chain. An address format that looks familiar does not prove that the destination network or asset is correct, and transactions may be difficult or impossible to reverse once completed.

Use the route that matches the transfer you need

In practice, I’d pick direct IBC when it delivers the right asset over a connected Cosmos path, and use Rango Bridge when a cross-chain route or swap is needed to reach the intended destination. The decision rule is simple: choose the path by the asset you will actually control after completion, not by the number of networks it can reach.

How to fund TRON contract calls from small USDT balances

Angus Schimmel — Wed, 30 Sep 2026 01:30:12 +0000

You can use a small USDT balance to obtain the TRX a contract call needs, if the wallet has enough TRX to pay for the swap transaction itself or a sponsor covers that cost. Estimate the call’s Energy first, then swap only enough USDT to cover the shortfall and a reserve.

Why can’t USDT pay for a contract call?

USDT is a TRC-20 token, while TRX pays the TRON network’s resource costs. A contract call consumes Energy for computation and Bandwidth for transaction data; if the caller lacks Energy, TRON can burn TRX to cover it. Holding USDT does not automatically provide either resource.

That creates a bootstrap problem for a wallet with zero TRX: swapping USDT for TRX is itself an on-chain transaction, so it also needs resources. The swap can work if the wallet has enough TRX for its transaction cost, has delegated resources, or the transaction is sponsored. Check which condition applies before designing a flow that promises gas from a token-only balance.

How much TRX should the wallet obtain?

Calculate the call’s likely TRX shortfall, then add a reserve for the swap and for variation in execution. Energy depends on the contract path and state; a token transfer to a fresh recipient, for example, can cost more than one to an existing token holder. Bandwidth depends on the transaction’s serialized size.

Simulate the exact contract call from the intended sender and inspect the returned Energy estimate. For an on-chain call, set fee_limit in sun as a cap on the caller’s Energy exposure; it is not a fixed fee or a guarantee that the call will succeed. Query the current Energy price and resource parameters instead of assuming a fixed rate.

As an illustrative example, suppose the estimate and live resource balances imply that the call needs 2 TRX of additional Energy coverage, and the wallet has 0.4 TRX available. The shortfall is 1.6 TRX before the swap’s own resource cost and a reserve; it is not necessarily the amount of USDT to exchange, because the quote determines how much TRX that USDT buys.

How do you stage the swap and contract call?

Use this sequence to turn a small token balance into a funded call without treating the swap quote as a gas estimate. A TRON swap solution is one way to exchange USDT for TRX from the wallet; the integration still needs to account for the resources required to perform that exchange.

Read the wallet’s starting state. Check its TRX balance, available Energy, available Bandwidth, and relevant token balance. Include delegated resources and any contract-level Energy sharing in the calculation, since they can reduce the TRX the caller must supply.
Estimate the target call. Simulate the same function, sender, recipient, and amount that the application will submit. Record Energy used, check whether the call succeeds in simulation, and choose a fee_limit that allows for reasonable execution variation while capping caller exposure.
Check the bootstrap path. Determine how the wallet can pay for the USDT-to-TRX swap transaction. If its existing TRX and resources cannot cover that step, arrange a small TRX seed, delegated resources, or a sponsor before asking the user to swap. Do not assume the USDT balance can pay this first network cost.
Size a conservative top-up. Convert the TRX shortfall into a USDT amount using the available quote, then add a reserve for the swap’s Energy and Bandwidth costs and a modest change in the target call estimate. Keep the reserve explicit in the interface so the user can see why the requested amount exceeds the estimated shortfall.
Swap, then recheck. After the exchange confirms, read the wallet’s updated TRX and resource balances. Re-simulate the target call if state or parameters changed, then submit it with the selected fee_limit and confirm the result from the transaction receipt.

What can still make the call fail?

A simulation is an estimate, not a reservation: contract state can change before broadcast, and execution may take a different path. A small reserve helps, but if the receipt reports OUT_OF_ENERGY, inspect actual Energy consumption and the contract’s caller-versus-deployer resource split before raising the cap. Otherwise, a larger cap may simply expose the wallet to more TRX burn.

For a production integration, make the balance check part of the call flow and explain the bootstrap requirement before a user reaches a zero-TRX state. My practical tip: preserve a small TRX reserve after each successful call, sized from observed receipts, so the next top-up transaction does not depend on a sponsor being available.

DEX Protocol Fee Switches: Compare Costs Before You Swap

Angus Schimmel — Tue, 29 Sep 2026 17:32:52 +0000

A DEX protocol fee switch determines whether part of a swap’s trading fee goes to the protocol instead of liquidity providers. To trade efficiently, check what the switch changes, separate it from other costs, and compare the final amount you receive across routes.

What does the switch change?

A protocol fee switch changes how a decentralized exchange (DEX) distributes trading fees. When it is off, the swap fee may go entirely to liquidity providers (LPs); when it is on, the protocol redirects a defined share to a treasury, governance program, or another recipient. The exact rule depends on the protocol.

Keep four separate questions in mind when checking a swap:

Trading fee: the charge applied to the swap, often expressed as a percentage of the trade.
Protocol share: the portion of that trading fee redirected when the switch is active.
Network cost: the blockchain transaction fee, which is separate from the DEX’s fee.
Execution price: the amount you receive after price impact, routing, and any token-level transfer fee.

These costs can appear together in a quote but have different causes. A protocol fee may reduce the LP share without changing the headline trading-fee rate; another design may add a separate charge. Read the fee rule before comparing percentages.

For example, on a hypothetical $10,000 swap with a 0.30% trading fee, the total trading fee is $30. If an active switch redirects one-sixth of that fee, $5 goes to the protocol and $25 to LPs; the user still pays $30 in trading fees. This is an illustrative split, not a rate for any named exchange.

How does a switch affect the swap you make?

The switch affects where fee value goes, while your immediate cost depends on the fee charged to your trade and the execution price. Compare two otherwise identical pools: Case A has no protocol share, so the full $30 hypothetical fee goes to LPs; Case B redirects $5 to the protocol and leaves $25 for LPs. If both charge the same total fee and give the same execution price, the switch alone does not make Case B’s swap more expensive.

In practice, the pools may not remain identical. LPs can move capital in response to lower net fee income, changing available depth and price impact. For an active trader, the useful comparison is the net token output now—not the protocol’s revenue destination or the advertised fee tier by itself.

Compare the same input amount and token pair across candidate routes, using the same slippage tolerance and a fresh quote. Include any extra route hop or transaction required, then check the estimated output and minimum output after slippage. A route with a lower trading fee can still deliver less if its liquidity is thinner or its price impact is greater.

What costs sit outside the switch?

Solana’s transaction fee is separate from a DEX protocol fee. Solana documentation describes a base fee and an optional priority fee; the latter can help prioritize a transaction during congestion. These are paid for transaction processing, not as a share of a pool’s swap fee, and they can matter more when a trade requires extra on-chain instructions.

Token mechanics can add another distinct cost. Solana’s Token-2022 documentation describes transfer-fee settings attached to a token mint, with fees withheld during transfers under that token’s rules. Such a fee is not the DEX protocol switch, and a route quote may depend on whether the swap path handles the token’s transfer behavior correctly.

Byreal is a Solana DEX example to consider when researching token swaps and concentrated liquidity. With concentrated liquidity, LPs place capital within selected price ranges, which can create more depth near the active price but less depth elsewhere; that depth influences execution and price impact. The Byreal concentrated liquidity article can add context on that liquidity model, while a swap comparison should still use current route quotes.

What should you check before repeating a trade?

For frequent swaps, focus on the marginal cost of the whole route. A few basis points (one basis point is 0.01 percentage point) matter on large or repeated trades, but a small difference in quoted fee can be outweighed by price impact, a priority fee, or an extra transaction. If you use a wallet such as Phantom or a routing tool, verify the final output and transaction details there before signing.

For a deeper technical workflow, the Byreal SDK and RFQ routing are names worth recognizing when evaluating how quotes or routes may be assembled; their mention does not establish any current fee setting. A switch’s status and split are protocol-specific and can change through governance or configuration, so verify the active rule from the protocol’s own current information rather than assuming an old post or cached quote still applies.

Before you submit a recurring swap, check:

Is the protocol share on, and what portion of the trading fee does it redirect?
What is the net output for the same size across viable routes?
Are network, token-transfer, and extra-instruction costs included?
Does the quote remain acceptable at your minimum-output setting?

How to Remove Liquidity on ArbSwap

Angus Schimmel — Fri, 21 Aug 2026 15:07:42 +0000

ArbSwap liquidity is useful while your tokens work in a pool, but there comes a point where you may want those tokens back in your wallet instead of locked as LP tokens on ArbSwap. Maybe you want to rebalance, reduce exposure, or stop farming.

Removing liquidity is not hard, but it is a real on-chain action. You are not just clicking “withdraw” from a normal account. You are redeeming your share of an AMM liquidity pool, receiving the underlying tokens back, and paying gas on the network you use.

This guide shows what you need, how to remove liquidity, what happens to LP tokens, and the mistakes that cost beginners money.

What You'll Need Before Removing Liquidity

Before you touch the remove button, make sure the basics are ready:

A non-custodial wallet such as MetaMask.
The Arbitrum network added and selected in your wallet.
A little ETH on Arbitrum for gas fees.
The wallet that originally provided the liquidity.
LP tokens unstaked from farming, if needed.
A clear idea of which trading pair you want to exit.

Liquidity is tied to a pair, not one token. If you added liquidity to an ETH and stablecoin pool, for example, you usually withdraw your share of both sides. The amounts may not match your original deposit because the pool ratio changes as people trade.

How ArbSwap Liquidity Removal Works

When you provide liquidity to an AMM, you deposit assets into a liquidity pool and receive LP tokens. Those LP tokens are your claim on a percentage of the pool.

When you remove liquidity on ArbSwap, you give back the LP tokens and receive the underlying pool assets. If the pool earned swap fees, your share is reflected in the pool value. If token prices moved against your position, impermanent loss may also show up in what you receive.

In plain English: removing liquidity turns your LP position back into wallet tokens.

Step 1: Connect Your Wallet

Open ArbSwap and connect the wallet that holds your LP position. Use the same wallet you used when you added liquidity or staked the LP tokens.

Check the wallet address before approving anything. If you use multiple wallets, it is easy to connect the wrong one and think your liquidity disappeared.

Step 2: Switch to the Correct Network

Switch your wallet to Arbitrum if your liquidity position is on Arbitrum. ArbSwap has expanded to other chains, but each pool still lives on a specific network.

Confirm that you have enough ETH on Arbitrum to pay gas. Arbitrum is an L2, but gas is still required.

Step 3: Unstake LP Tokens From Farming

If you placed your LP tokens into a farm, remove them from the farm first. Farming and liquidity are related, but they are not the same action.

A common beginner flow looks like this:

Provide liquidity to a pool.
Receive LP tokens.
Stake those LP tokens in a farm.
Later, unstake the LP tokens from the farm.
Remove liquidity by redeeming the LP tokens.

If the interface says you have no liquidity to remove, check whether the LP tokens are still deposited in farming or staking.

Step 4: Choose the Liquidity Pair

Go to the liquidity area and select the trading pair you want to withdraw from. Read the pair name carefully because similar token symbols can exist.

If the interface shows your pool share, underlying token amounts, or LP balance, compare those details with what you expected.

If one side of the pair rose or fell sharply, you may receive a different mix of tokens than you imagined. That is not necessarily an error. It is how liquidity pools work.

Step 5: Select How Much Liquidity to Remove

Choose the percentage of liquidity you want to withdraw. You can remove all of it or only part of it.

Removing 100% means you are fully exiting that pool position. Removing less keeps some LP exposure active, including fee potential and impermanent-loss risk.

Before confirming, look at the estimated tokens you will receive. These estimates can shift before the transaction confirms. If there is a slippage or minimum-received setting, do not set it carelessly.

Step 6: Approve the LP Token if Needed

The first time you remove liquidity from a specific LP token, your wallet may ask for an approval. This lets the contract use the LP tokens for the removal transaction.

Read the wallet prompt. You are approving the LP token involved in the pool exit. If the token name, site, or network looks wrong, stop and recheck.

After approval confirms, you may need to click remove again to submit the withdrawal.

Step 7: Confirm the Removal Transaction

Review the transaction in your wallet and confirm it. Wait for the network to process it.

Once confirmed, your LP tokens should decrease or disappear depending on how much you removed. The underlying tokens should return to your wallet.

If the tokens do not appear immediately in MetaMask, the transaction may still be pending, or the token may need to be added to the wallet view.

Common ArbSwap Mistakes That Cost Beginners Money

The most common mistake is using the wrong network. If your pool is on Arbitrum, connect to Arbitrum and keep enough ETH on that L2 for gas.

Another mistake is forgetting farmed LP tokens. If your LP tokens are staked, unstake them before removing liquidity.

Be careful with fake tokens. A DEX lets many assets trade, and similar names can be misleading.

Do not ignore impermanent loss. If token prices moved a lot, your withdrawal may be worth less than simply holding the two tokens separately. Pool fees can help, but they do not guarantee profit.

Watch slippage and price impact too. Removing standard two-sided liquidity is usually about redeeming your pool share, but thin pools and volatile tokens still need care.

Finally, avoid treating yield as guaranteed. Farming rewards, LP fees, and token prices all change.

Ready to Exit Your Liquidity Position?

To remove liquidity cleanly, connect the right wallet, use the right network, unstake any farmed LP tokens, choose the correct pair, review the token amounts, and confirm only when the details make sense.

The simple rule is this: your LP tokens represent your share of the pool, and removing liquidity redeems that share back into the underlying assets. When you are ready to exit your position, open ArbSwap, review your pool carefully, and withdraw at the pace that fits your risk.

How ArbSwap Liquidity Pools Work

Angus Schimmel — Fri, 21 Aug 2026 15:07:20 +0000

ArbSwap liquidity pools are the engine behind swaps on this Arbitrum DEX: users deposit paired tokens, traders swap against those pools, and liquidity providers may earn a share of trading fees. You are not just buying or selling. You are helping supply the market.

A liquidity pool lets a decentralized exchange work without a traditional order book. Instead of waiting for one buyer and one seller to match, an AMM uses tokens already sitting in a smart contract. This guide explains what LP tokens mean and where beginners can lose money if they move too quickly.

What You'll Need

Before you add liquidity, prepare the basics:

A non-custodial wallet, such as MetaMask.
The Arbitrum network selected in your wallet.
A little ETH on Arbitrum for gas fees.
Both tokens in the trading pair you want to supply.
A reason for choosing the pool beyond a yield number.

If your funds are on another chain, you may need to bridge to Arbitrum first. Check the network carefully before sending funds, approving tokens, or confirming a deposit.

How ArbSwap Liquidity Pools Work

ArbSwap is a decentralized exchange and AMM, not an aggregator. A liquidity pool usually holds two assets, called a trading pair. Traders use that pool when they want to swap between those assets.

Liquidity providers deposit both sides of the pair into the pool. In return, they receive LP tokens. Those LP tokens represent your share of that specific pool. If you own an illustrative 1% of a pool, your LP tokens represent a 1% claim, adjusted as trades happen.

Your deposit does not stay as a fixed amount of each token. As traders swap, the pool balance changes. If one asset rises or falls sharply against the other, your position shifts with the AMM.

Step-by-Step: Add Liquidity

Step 1: Connect your wallet. Open ArbSwap, connect your wallet, and confirm you are using the right account. Do not approve signature requests you do not understand.

Step 2: Switch to Arbitrum. Select Arbitrum in your wallet before you start. If your wallet is on the wrong network, balances may look missing or the transaction may fail. You need ETH on Arbitrum to pay gas fees.

Step 3: Choose a trading pair. Pick a pool you understand. A pair with two established assets behaves differently from a pool involving a thinly traded token. LP fees come from trading, so a quiet pool may not generate much fee income.

Step 4: Deposit both tokens. Most AMM pools require both assets in the correct ratio. Equal value does not always mean equal token counts. If one token is worth more, you may need fewer units of it.

Step 5: Review approvals, slippage, and price impact. You may need to approve each token before depositing. Check the token name, contract, amount, expected pool share, and any warning shown by the interface. Slippage is the difference between the expected result and the final execution. Price impact is how much your action affects the pool price.

Step 6: Receive LP tokens. After the transaction confirms, your position is represented by LP tokens. These are not a bonus reward. They are the receipt for your share of the liquidity pool. When you remove liquidity later, those LP tokens are used to withdraw your share of the underlying assets.

Step 7: Track the position. Watch both assets, trading activity, fees earned, and your pool share. If farming is available, you may be able to stake LP tokens for extra rewards. Farming can add yield, but it does not remove market risk.

LP Fees, Farming, and Yield

The basic return from a liquidity pool comes from LP fees. When traders swap through the pool, liquidity providers may receive a share of fees according to the pool rules. Your share depends on how much of the pool you own.

Farming is separate. A farm may let you stake LP tokens to earn additional rewards. That can make a pool look more attractive, but the yield is variable. Token prices, reward rules, and total liquidity can all change.

Do not treat any displayed yield as guaranteed. A pool can show a strong return and still lose value if the paired assets move against you.

Common Mistakes That Cost Beginners Money

Using the wrong network. ArbSwap is built on Arbitrum and has expanded to other chains, so confirm the network before approving, swapping, or depositing.

Ignoring slippage. A very high slippage setting may help a transaction go through, but it can also give you a worse result than expected, especially in thin pools.

Confusing gas with price impact. Gas is the network fee for the transaction. Price impact is the effect your action has on the pool price. A transaction can have low gas and still be a poor move if the pool is shallow.

Depositing into fake or low-quality tokens. Token names and symbols can be copied. Check the token contract before swapping, approving, or pairing assets.

Forgetting impermanent loss. Impermanent loss happens when your LP position is worth less than simply holding the two tokens separately. It becomes permanent if you withdraw at that point. This is a normal AMM risk, not a platform glitch.

Chasing yield without understanding the pair. If you would not want to hold both assets, think twice before becoming a liquidity provider for that pool.

When a Pool Makes Sense

A liquidity pool can make sense when you understand both tokens, are comfortable holding them, and accept that your position may change as traders use the pool. It is usually a poor fit if you only want exposure to one token or cannot tolerate volatility.

Start small if you are learning. A small test deposit teaches the full workflow: wallet connection, network selection, approvals, gas fees, LP tokens, optional farming, and withdrawal.

Put ArbSwap Pool Mechanics to Work

ArbSwap liquidity pools are straightforward once you separate the parts: paired assets go into a pool, LP tokens represent your share, traders create fee opportunities, and market movement creates real risk. Check the network, review slippage and price impact, and remember that liquidity providing is never risk-free.

When you are ready to try the workflow, use ArbSwap with a small, deliberate first position and treat every approval screen as part of the decision.