If your prediction-market deposit is pending or failed, first check whether the Ethereum transaction confirmed and whether you bridged the exact token the market accepts. For a Polygon PoS deposit, a confirmed lock can still need time to reach Polygon; even after it arrives, the market may require a separate collateral token.

  • A confirmed Ethereum transaction and a credited Polygon balance are different stages.
  • Check the destination token contract and the market’s current deposit instructions, not just the ticker.
  • Retry only after identifying which stage failed; a second transfer can create a second deposit.

What does “pending” mean at each stage?

A native Polygon PoS deposit starts when the Ethereum-side RootChainManager locks a mapped token and emits a state-sync message. Polygon’s ChildChainManager processes that message and credits the corresponding child token; those are separate events, so an Ethereum receipt marked successful does not prove the Polygon credit has completed.

Check the transaction hash on an Ethereum explorer first. If it is still pending, the transaction has not been mined; if it reverted, the lock did not complete. If it succeeded, inspect its logs and recipient, then check the receiving address on Polygon for the child-token balance. A token may be present on-chain but hidden in the wallet because the token has not been added to its display list.

How do you get the collateral the market accepts?

Bridge completion and market credit are separate checks. A market can accept only a particular contract on Polygon, even when another token has the same ticker or is also described as USDC. For example, Polymarket’s current collateral is pUSD, an ERC-20 on Polygon backed 1:1 by USDC; follow its current Deposit flow to see which source assets and routes it will convert.

Before sending again, compare the source network, source-token contract, destination network, recipient address, and minimum deposit against the market’s instructions. If you bridged USDC and can see the resulting Polygon token but the market shows no balance, the bridge may have worked while the collateral conversion or platform deposit did not. Keep the transaction hashes for both stages.

What should you do next?

  1. Record the source transaction hash. Confirm its status on Ethereum and verify the token contract, amount, and recipient in the transaction details. A failed transaction needs a new submission; a successful lock should not be repeated just because the market page is still waiting.
  2. Check for the Polygon credit. Search the same address on a Polygon explorer for the corresponding token transfer. If the Ethereum transaction succeeded but no child-token credit appears after the usual processing interval, keep both explorer records and contact bridge support with the hash.
  3. Compare the credited token with the market’s collateral contract. If the market’s Deposit flow accepts that asset, use its specified route or conversion step and wait for the platform credit. If it does not, do not send that token to a deposit address on the assumption that a matching ticker is enough.
  4. Budget for gas at both ends of the task. The Ethereum deposit consumes ETH for L1 gas; later Polygon transactions need POL. Gas varies with network demand, and the market’s conversion or deposit route may have its own costs. Check the quoted amounts before signing rather than relying on an old fee estimate.
  5. Escalate with evidence if both chains show success. Provide the bridge and market deposit hashes, token contract, amount, and receiving address through the relevant support channel. If your case is instead a Polygon-side withdrawal whose burn has already confirmed and you need the Ethereum release stage, Polygon Bridge withdrawals are the relevant next step; that flow requires its own checkpoint and Ethereum claim.

When should you choose a different route?

For example, if you started with USDC on Ethereum and ended with the expected Polygon token but no usable market balance, the missing step is likely the market’s collateral route, not another bridge deposit. If the deposit is time-sensitive, compare the platform’s supported funding routes before bridging: the right choice depends on its current accepted assets, conversion costs, and the time available for Ethereum confirmation and Polygon processing.