State sync carries a deposit instruction from Ethereum to Polygon PoS so the matching token can be credited on Polygon. If your deposit is pending, the key distinction is whether Ethereum accepted the lock and emitted a message, and whether Polygon has relayed and executed that message.
A state-sync message is a queued instruction, not a cross-chain transaction
Ethereum and Polygon PoS keep separate state, so a contract call on Ethereum cannot directly call a contract on Polygon. Instead, the deposit contract records a state-sync message that Polygon’s validator infrastructure relays; a Polygon contract then interprets the message and performs the local action.
For an ERC-20 deposit, the Ethereum-side bridge locks the tokens and emits data identifying the recipient, root token and deposit amount. Polygon’s ChildChainManager receives the relayed data and calls the mapped child token’s deposit function. The result is a mint or credit on Polygon, while the original tokens remain locked on Ethereum.
Polygon bridge supported tokens helps you check whether the root token has a corresponding child token mapping, which determines whether the receiver can process its deposit instruction. A successful lock alone does not guarantee that a usable Polygon token exists for every asset address or token variant.
The message passes through relay and execution stages
The deposit proceeds in stages: the Ethereum transaction creates the message, Polygon’s relay includes it in state-sync data, and Polygon’s state receiver invokes the destination handler. Each stage has a different observable signal, so “pending” does not identify the cause by itself.
- Ethereum transaction: Check its receipt. A reverted transaction did not complete the lock or create a usable deposit message.
- Message creation: For a successful deposit, inspect the receipt logs for the bridge’s state-sync event and its sync ID.
- Polygon relay: The message must be picked up and included in Polygon’s state-sync processing.
- Destination execution: The ChildChainManager decodes the message, checks the token mapping, and calls the child token.
The relay is not a second transaction you submit from your wallet. Polygon validators relay the message; Polygon execution then applies it through the state receiver, commonly identified as the state-sync system contract at address 0x0000000000000000000000000000000000001001. A wallet may show no destination transaction that resembles a normal user-signed transfer, so use the bridge’s status view or a Polygon explorer that can expose the sync ID and destination processing.
Timing and fees depend on different parts of the path
A normal Ethereum-to-Polygon PoS deposit is often credited around 7–8 minutes after the Ethereum transaction is confirmed, though congestion or relay backlog can extend that wait. The bridge does not charge a separate user gas transaction on Polygon for the automatic mint; you pay Ethereum gas for the deposit, and need POL later to transact with the asset on Polygon.
The wait is a trade-off: state sync automates the destination credit, but your balance is not spendable on Polygon until the relay and execution finish. Polygon Bridge uses this mechanism for deposits, whereas returning assets to Ethereum follows a different path involving a Polygon burn, a checkpoint and an Ethereum claim. Do not apply a withdrawal’s checkpoint wait to a pending deposit.
For example, if an Ethereum receipt shows a successful lock and state-sync event, but your Polygon balance is unchanged after 10 minutes, the lock is evidence that the source step completed; it is not proof that destination execution succeeded. Check whether the sync ID has been relayed, then check whether the destination handler succeeded. If the message is still queued, the likely issue is relay delay; if execution failed, the token mapping or token contract is a relevant place to investigate.
Diagnose the failed stage before taking action
Start with the Ethereum receipt, not a fresh deposit. If the receipt reverted, there is no completed bridge deposit to recover; address the wallet or transaction error before submitting again. If it succeeded, note the transaction hash, amount, recipient and sync ID, then compare those details with the bridge status and Polygon-side records.
A missing token display can also be a wallet configuration issue: verify the receiving address and the Polygon token contract shown for the mapped asset. If the message has not appeared on Polygon, wait and monitor it rather than repeating the deposit, since a second successful Ethereum transaction can lock a second amount. If destination execution reports a mapping or contract error, preserve both transaction hashes and the sync ID for support; do not try to manually call the token’s deposit function.
State sync can stall at network level as well as fail for a particular deposit: a relay backlog can delay many messages, while an unmapped token can cause one message’s destination call to revert. When several deposits are delayed together, check for a broader relay incident before treating yours as an isolated failure. The practical tip: save the Ethereum hash and sync ID as soon as the deposit confirms, so you can locate the exact handoff stage without paying to submit it again.