Second Signatures for Bridged Tokens Explained
A second signature usually authorizes a separate on-chain claim. A bridge may first lock or burn tokens on one network, then require a later transaction to release them on another. The extra confirmation is about completing that cross-chain process; it is not a request for the recipient to prove they own the wallet.
Why can receiving tokens take two transactions?
Some bridges split a transfer into a source-chain transaction and a destination-chain transaction. The first records the deposit or withdrawal; the second completes delivery after the bridge has enough evidence that the first transaction is valid. That evidence can include a checkpoint, a record committing to a batch of blocks, and a cryptographic proof of the transfer.
Polygon’s official Portal uses Polygon PoS Bridge for transfers between Ethereum and Polygon PoS. If you are comparing that route, the Ethereum to Polygon bridge is one option to consider. Ethereum.org describes Polygon PoS Bridge as a native bridge, while Polygon’s documentation explains the lock-and-mint and burn-and-unlock model behind transfers.
For example, Maya withdraws a token from Polygon PoS to Ethereum. She signs a Polygon transaction that burns the bridged token. Once that burn is included in a checkpoint on Ethereum, a proof can establish that it happened; a separate Ethereum transaction then submits the proof and releases the original token.
What does the second signature authorize?
It authorizes a transaction that changes the destination chain’s state. In Maya’s example, the Ethereum transaction calls the bridge contract’s exit function with proof of the Polygon burn. If MetaMask asks her to confirm it, she is authorizing that contract call and its gas cost, not signing a vague “receipt” of the token.
The signature is not always from the person receiving the tokens. The key question is who submits the transaction and pays its gas: a wallet-controlled account can do it, or a relayer may submit it for the user. The bridge’s rules determine who can complete the claim and where the released asset goes.
When should you expect another confirmation?
Expect a follow-up transaction when the route requires a proof-based claim on the destination network. A Polygon PoS withdrawal to Ethereum is a clear example: the initial burn happens on Polygon, then the exit is finalized on Ethereum after the burn is checkpointed. The delay varies with checkpoint and network conditions, and the final transaction needs ETH for Ethereum gas.
By contrast, an Ethereum-to-Polygon PoS deposit through Polygon Bridge generally uses a source transaction to lock the asset, after which the corresponding token is delivered on Polygon without a separate recipient claim. An approval for an ERC-20 token can add a prior transaction: it grants the bridge contract permission to transfer that token, while the deposit transaction actually moves it. These are distinct authorizations, and the wallet should show which contract and action each one covers.
Before signing, check the network, token, amount, destination address, and whether the wallet request is a message signature or a gas-paying transaction. A missing token display can simply mean the wallet needs to show that token on the destination network; adding it does not itself claim funds. Polygon Bridge’s two-chain flow is easier to assess once you identify whether the pending request approves spending, starts the transfer, or finalizes delivery.
Comments
Post a Comment