Skip to main content
Blockchain Today

Crypto markets, protocols and policy

Why Did I Pay Gas Twice Bridging an ERC-20?

Why did I pay gas twice when bridging an ERC-20 token? One charge may approve spending; the next deposits tokens, with each transaction using ETH for gas.

By Blockchain Today Editorial4 min read

Why Did I Pay Gas Twice Bridging an ERC-20?

An ERC-20 bridge deposit usually costs gas twice because one Ethereum transaction approves token spending and a second submits the deposit; an existing sufficient allowance can remove the first transaction.

The two charges pay for separate contract operations, not two versions of the same transfer. Ethereum gas is paid in ETH for transaction execution, so both the approval and the deposit can have their own gas charge. Ethereum’s gas documentation explains how gas pays for work on the network.

Approval and deposit are separate transactions

An approval gives a particular spender permission to use some of your tokens. The deposit then calls the bridge operation that takes those tokens into custody. The ERC-20 standard defines approve, which sets the allowance, and transferFrom, which lets an authorized spender move tokens on your behalf. The ERC-20 standard describes both operations.

For a WETH transfer through Suibridge, the first transaction can approve the bridge spender to use WETH. After that transaction succeeds, a second transaction submits the bridge deposit. Each execution changes contract state on Ethereum and uses gas; the approval charge is for authorization, while the deposit charge is for carrying out the token transfer into bridge custody.

That permission step is separate from how Suibridge holds ETH, the subject of a related article. Suibridge uses a lock-and-mint process to move supported assets from Ethereum to Sui, so understanding the custody side helps explain what happens to assets after the deposit. The allowance itself only records permission for a spender to use tokens under the token contract’s rules.

A sufficient allowance can avoid another approval

An allowance is the amount a spender is still permitted to withdraw from an owner’s balance. It belongs to the owner–spender pair recorded by that token contract. The ERC-20 standard’s allowance function returns the remaining amount, and a later approve call sets the allowance value for that spender.

Take a user who approves a bridge spender to use 40 WETH, then deposits 10 WETH. If the token contract still records at least the needed amount for that same owner and spender, the user may be able to deposit again without sending a new approval transaction. That saves the approval execution and its gas; the new deposit still requires its own transaction.

The amount matters. If the remaining allowance is below the amount the deposit needs, another approval may be required. Some users approve only what they expect to spend, which limits the permission granted but can mean repeating the approval for a later deposit. Others set a larger allowance to reuse it, which can avoid repeat approval transactions while leaving a broader permission in place.

A different spender can mean a fresh approval

A sufficient allowance for one spender does not automatically authorize another. If a bridge deposit uses a different spender address, the old allowance may not cover it, even when the token and wallet are unchanged. A change in spender therefore can bring back the approval transaction and its gas charge.

This is why an approval that worked for an earlier bridge interaction may not apply to a later one. The token contract tracks authorization for each owner–spender pair, rather than one universal permission for all bridges. Before approving again, the useful detail to compare is the spender named in the approval request with the one already associated with the existing allowance.

Some permit-based flows handle authorization differently, so they may not require the same standalone on-chain approval transaction. The exact flow depends on the token and the bridge’s implementation; the basic two-transaction explanation applies when the user submits a regular ERC-20 approval followed by a deposit transaction.

Before confirming, identify whether the pending transaction is an approval or a deposit, and check whether the allowance covers the intended amount for that spender. Those details explain the two charges and indicate whether a later deposit may need another approval.

Questions readers ask

What spending limit should I approve?

Approve an amount that matches your comfort with the spender’s permission. A smaller allowance limits how much that spender can use but may require another approval later; a larger allowance can be reused while enough remains. The ERC-20 standard defines approval as a spender’s permission up to the approved value.

How can I revoke an unused approval?

Use a wallet or token-approval tool that lets you submit a new allowance for the same token and spender, commonly setting it to zero. That update is an on-chain transaction and uses gas. The ERC-20 standard says a new approve call overwrites the existing allowance value.