Bridge Deposit Speed-Ups and Same-Nonce Replacement
A new transaction hash after speeding up a bridge deposit reflects changed signed fees; cBridge still tracks the same deposit by transferId when calldata stays unchanged.
The Chainvane Desk5 min read

A bridge deposit speed-up creates a new transaction hash but can leave the deposit itself unchanged. The wallet signs a replacement with the same account nonce and higher fees; because the signed fee fields change, the hash changes too. When the replacement carries the same deposit call, cBridge identifies the transfer by its transferId.
What changes when you speed up a deposit?
A pending deposit starts as a signed transaction sent to Ethereum. Its nonce sets its place in the sender’s transaction sequence, while its calldata carries the call that requests the bridge transfer. Under EIP-1559, the signed payload also contains fee fields, including max fee and priority fee.
A speed-up signs another transaction at the same nonce, usually with higher fees so a node or wallet can replace the pending version. Geth’s txpool uses a 10% price bump by default; other node settings may differ. Since the fee fields are part of the signed payload, changing them creates a different transaction hash even when the nonce and calldata stay the same.
That distinction matters for cBridge: the transaction hash identifies a particular signed transaction, while the transferId identifies the bridge transfer. The cbridge cross-chain context changes what you should monitor: for a deposit with unchanged calldata, cBridge’s transferId stays the useful status identifier even when the wallet shows a replacement hash.
Why can the bridge still find the deposit?
cBridge derives a transferId from the sender, receiver, token, amount, destination chain, send nonce and source chain. The transaction’s gas fee fields are not among those inputs. So when a speed-up changes only the fees and resends the same deposit call, the transferId remains the same.
Say you submit a cBridge send() call with a 2 gwei priority fee, then speed it up to 4 gwei at the same nonce. The signed transactions have different hashes because their fee fields differ. But if the sender, receiver, token, amount, destination chain and send nonce are unchanged, the bridge transfer has the same transferId. A status lookup using that transferId can still find the transfer.
The wallet may show the original and replacement as separate entries. That view reflects two signed attempts to use one account nonce. On the canonical chain, only one transaction at that nonce can take effect. If the replacement is mined, it carries out the deposit call; the original pending transaction is superseded for that nonce. The bridge can then process the transfer represented by the call.
A cancellation is different from a speed-up. A wallet commonly creates a zero-value self-transfer at the same nonce, with higher fees, to replace the pending transaction. If that cancellation is mined, it sends no deposit call, so no cBridge transferId exists for that attempt. A new hash alone therefore does not tell you whether you sped up the deposit or replaced it with a cancellation.
What should you check?
Open the replacement transaction and compare its destination and calldata with the original. A fee-only speed-up should preserve the deposit call; a self-transfer cancellation will not contain that call. Then use the transferId to follow the bridge transfer, rather than treating the newest transaction hash as the bridge’s permanent identifier.
If the replacement is still pending, the bridge has no mined deposit to act on yet. Once the transaction is included, the transferId links the call to the bridge’s record. For day-to-day tracking, keep both identifiers: the hash helps inspect the on-chain attempt, while the transferId helps look up the cross-chain transfer.
The deciding change is in the signed fees: they produce a new hash, while identical deposit calldata preserves the transferId. For a fee-only speed-up, track the transferId and use the replacement hash to inspect the transaction that was mined.
Common questions
Can a sped-up bridge deposit be paid out twice?
A same-nonce replacement does not create two canonical deposits on Ethereum: only one transaction at that nonce can be included on the canonical chain. cBridge tracks the transfer using its transferId, which remains unchanged when the replacement resends the same call. A chain reorganisation can change which transaction is included, so check the settled transaction and transfer status if the chain reorganises.
What happens if both the original and replacement are mined on a reorg?
They cannot both take effect in the same canonical account history at the same nonce. A reorganisation can remove one inclusion and expose another version of the nonce in the replacement chain history. Check the canonical transaction after the chain settles, then follow the transferId associated with the deposit call.
How do I find a cBridge transferId from a transaction?
Use the transaction’s deposit call data or the bridge’s transfer details to identify the sender, receiver, token, amount, destination chain, send nonce and source chain used in the transferId derivation. A hash alone identifies the signed transaction, so a fee-only replacement can have a new hash while the transferId stays the same.