Skip to main content
Aeterna Sol

Crypto markets, protocols and policy

Why a token tax can shrink your cross-chain deposit

A token tax can leave a bridge with less than you sent, disrupting quotes or delivery. Learn where the deduction happens and what to check before signing.

The Aeterna Sol Editors

Why a token tax can shrink your cross-chain deposit

A 5% transfer tax on 100 tokens leaves 95 tokens after the deduction. That means the bridge may receive less than the amount your wallet shows as sent.

A token tax is a rule in the token’s contract that deducts part of certain transfers, often sending it to a tax wallet. A cross-chain deposit usually moves tokens through one or more contracts before the destination chain credits you. If the amount changes along the way, the route’s assumptions may no longer match what arrived.

The route matters because “bridge” can describe different steps: locking or burning tokens on the source chain, relaying a message, then releasing or minting tokens on the destination. For a fuller look at how transfer types affect what arrives, see this portal bridge explainer. Here, the key question is what each contract receives and expects.

Where does the token tax come out?

The tax is deducted wherever the token’s rules apply, and those rules differ by token. Some tax trades but exempt ordinary wallet transfers; others charge on every transfer, including movements between a wallet and a bridge contract.

Consider a route that asks you to send 100 tokens to a deposit contract. If the token charges 5% on that transfer, the contract may receive 95. The wallet can still show that 100 left your balance, while the contract’s balance increases by only 95. The deduction may go to a fee recipient, remain held back, or be handled another way under that token’s design.

A route can involve more than one taxed transfer. If the bridge later moves the tokens to another contract, a tax may apply again. The amount available at the next step could be smaller still. A destination token may also have its own transfer rules when it is released to your wallet.

Why can a smaller amount disrupt the deposit?

A deposit can fail or deliver less when a contract or route uses the requested amount instead of the amount it actually received. For example, a contract might try to process 100 tokens after only 95 arrived. It could reject the transaction, fail during a later swap, or leave the route short of its expected input.

Better designed integrations can measure the balance change at the receiving contract and use that as the deposit amount. This is often called balance-based accounting. It helps the contract work with the tokens that arrived, rather than assuming the transfer delivered the full requested amount.

That approach does not guarantee a successful cross-chain transfer. The route still needs to support the token, and its quote needs to account for any remaining fees, swap costs, minimum output, and destination rules. A token tax can also make the amount received variable if the rate or exemptions change.

Check the route’s stated output against the token’s behavior. A displayed estimate based on the amount you enter may not reflect a tax the route cannot detect. The amount received on the destination chain can also differ from the source amount because of bridge fees, swaps, or destination-chain handling.

What should you check before depositing?

Before signing, establish whether the token taxes the transfer into the bridge and whether the route supports that token’s tax rules. Use the token’s contract details and the bridge’s own route information where available. A token name or ticker alone cannot tell you how its transfer code behaves.

  • Check whether the tax applies to wallet-to-contract transfers, not only buys or sells.
  • Review the quoted output and minimum received, if the route shows them.
  • Look for a clear statement that the route supports transfer-tax tokens.
  • Confirm the destination chain and receiving address before you sign.

If the route gives no clear answer, avoid testing it with a large deposit. First seek confirmation from the route operator or token documentation. A small test can reveal how a route behaves, but it does not prove that larger transfers will work or receive the same treatment.

For most readers, the better choice is a route that explicitly supports the token’s transfer rules and shows a credible output estimate. If no route does, choose a non-taxed asset or another supported path only after checking the conversion costs and destination amount. The key figure is not what left your wallet; it is what the bridge can actually process.