Polygon bridge approvals: one deposit or many
A Polygon bridge deposit may need one ERC-20 approval and then a separate deposit; the allowance can cover one transfer or repeated deposits until spent or revoked.
The Finality Desk4 min read#24d305

A polygon bridge deposit of an ERC-20 token from Ethereum usually requires an approval transaction before the deposit transaction. The approval sets how much a contract may spend from your token balance. You can approve only the next deposit or set an allowance large enough for later deposits. The choice changes how often you sign an approval, and how much spending authority remains with the bridge.
That approval is an ERC-20 permission, not a transfer. In the Polygon PoS Bridge flow, the Ethereum-side RootChainManager.depositFor routes the deposit to the token’s predicate. For ERC-20s, the predicate locks tokens by calling transferFrom. The token contract checks that the predicate has enough allowance from the wallet that owns the tokens. The later bridge message causes the corresponding Polygon-side token to be minted for the recipient.
The approved spender matters. For the PoS Bridge’s ERC-20 path, the spender is the ERC20Predicate, not the recipient wallet or the Polygon-side token. A reference to the Polygon bridge deposit path belongs in the context of that contract flow: approval authorizes the Ethereum-side token lock, while the deposit call starts the cross-chain transfer. ETH deposits follow a different path and do not use an ERC-20 allowance.
Does a polygon bridge approval cover every deposit?
It covers deposits only up to the remaining allowance for that token and spender on the source chain. An ERC-20 stores an allowance for a particular owner-and-spender pair. When a deposit calls transferFrom, the predicate can pull tokens only if that allowance is sufficient and the wallet also has enough tokens.
If you approve exactly the amount you plan to deposit, the approval normally authorizes that transfer. After it is spent, another deposit requires another approval. If you approve more than the first deposit, the unused portion can cover later deposits. For example, an allowance of 100 tokens can cover a 30-token deposit and leave allowance for subsequent transfers, subject to the token’s implementation.
An approval does not expire just because you close the bridge interface or switch networks. It remains recorded by the token contract until it is spent, replaced, or revoked. It is also specific to the source-chain token contract and spender. An allowance for one token does not authorize another token, and an approval on Ethereum does not grant permission over a token balance on Polygon.
Should you approve once or before every deposit?
For occasional deposits, an amount-limited approval is usually the clearer choice: it limits the predicate’s spending authority to the amount you intend to move. For frequent deposits, a larger allowance can reduce repeat approval transactions and the associated source-chain gas, but it leaves more authority active between deposits.
The practical choice depends on the token’s approval behavior and how often you bridge:
- One deposit: approve the intended amount, then submit the deposit after the approval confirms.
- Several planned deposits: approve their combined amount, or another limit you are comfortable leaving available.
- Frequent deposits: a high or unlimited allowance avoids repeated approvals, but increases the amount the spender could pull if the approval is misused.
- No further deposits: revoke or reduce the remaining allowance through a wallet or a direct token interaction that supports allowance changes.
“Unlimited” commonly means the maximum integer value accepted by the token’s approve function. Some ERC-20 implementations treat that maximum as effectively non-decreasing when transferFrom spends tokens; other implementations may update allowance differently. Check the token’s behavior rather than assuming every allowance automatically falls by the amount deposited.
What can make an approval or deposit fail?
An approval can succeed while a deposit still fails. The allowance may be too small, the wallet may lack enough source-chain tokens, or the token may not be mapped or enabled for the PoS Bridge. The deposit transaction also needs to reach RootChainManager.depositFor with valid data for the token. The allowance alone does not make an unsupported asset bridgeable.
Some tokens reject a direct change from one nonzero allowance to another. In that case, a wallet or interface may need to set the allowance to zero before setting a new amount. Token implementations can also differ in how they report or update allowance. If an approval appears to be present but the deposit reverts for insufficient allowance, check the token, chain, spender address, and remaining amount shown in the wallet or a block explorer.
The approval transaction and deposit transaction are separate. A confirmed approval does not mean the tokens have moved; the deposit must still be submitted and confirmed on Ethereum. Conversely, a failed deposit generally reverts its token transfer and allowance use along with the transaction, while the earlier approval remains onchain. For a single planned transfer, amount-limited approval keeps this distinction simple. For repeat use, a larger allowance trades fewer approval transactions for longer-lasting permission.