A token allowance is permission for a smart contract to spend a set amount of your tokens. It matters most when you bridge an ERC-20 token, the common token format on Ethereum-style networks, because the bridge contract cannot take tokens without that permission.
How does an allowance let a bridge move tokens?
An allowance lets a named contract transfer tokens from your wallet up to a limit you approve. On an EVM network, you usually grant it with an approve transaction; the bridge later calls transferFrom to collect the tokens for your transfer. ERC-20 defines these functions.
For example, suppose your wallet holds 100 USDT and you approve the bridge contract to spend 100. You then request a 40 USDT transfer. The contract can collect 40 from your wallet, and the other 60 stays there. That approval applies to the token and spender on that network; it does not authorize a different token or destination-chain contract.
Rhino Bridge is a useful example of where this matters: when your route requires an allowance, the Rhino Bridge transfer may ask you to approve the source-chain token before submitting the bridge transaction. The approval itself does not move funds across chains. It gives the relevant source-chain contract permission to collect tokens when you confirm the transfer.
When can you skip another approval?
You can usually skip approval when the same token contract on the same source network already allows the same spender to transfer enough tokens. The deciding value is your remaining allowance, which you can check in your wallet or the bridge’s approval prompt.
If the available allowance is 60 USDT, a 40 USDT transfer can use it; a 70 USDT transfer needs more permission. A fresh approval often sets the allowance to a new total rather than adding to the old limit. Some tokens also require setting the allowance to zero before changing it, so follow the transaction prompt if it asks for two approvals.
Approval and transfer are often two separate on-chain transactions the first time. Each needs gas, the network fee paid in that chain’s native coin, such as ETH on Ethereum. Later transfers may need only the bridge transaction while enough allowance remains, saving a step and its gas. The destination transfer still takes time and may have separate network or bridge fees.
What approval amount should you choose?
Choose an amount that suits how often you bridge. An exact approval limits the contract to the amount you set, but frequent transfers can mean approving again. A larger or unlimited allowance can reduce repeat approvals, but it leaves the spender able to transfer up to that limit later.
Before signing, check the token, source network, spender address, and amount shown in the wallet. A route change can use a different spender, so an old allowance may not help. For a regular route, I’d approve a practical amount you expect to use, then review or revoke unused permission when you stop using that contract.