Skip to main content
Merkle Street

Protocols, markets, policy, people

Polygon PoS State Sync: How Deposits Get Minted

Why bridged tokens arrive on Polygon without paying gas: Heimdall validators relay the Ethereum event, then Bor mints your deposit by system call.

Merkle Street Newsroom#b421443 min read

Polygon PoS State Sync: How Deposits Get Minted

A Polygon PoS deposit can appear in your wallet without a Polygon gas payment because Bor mints it through a protocol system call, not a transaction signed by you.

From Ethereum deposit to Polygon balance

A Polygon PoS deposit reaches your address through three steps: an Ethereum event, validator agreement, and a Bor system call. The deposit transaction is the only one you sign and pay for.

  1. On Ethereum, your deposit transaction calls RootChainManager. The deposit emits a StateSynced event through the StateSender contract. That event carries the information Polygon needs to process the deposit, including where the tokens should arrive.

  2. Heimdall validators observe the StateSynced event and agree on it. Once a supermajority agrees, Heimdall records the event for Polygon’s block producers to apply. Your wallet does not submit a second transaction to ask for the mint.

  3. At the start of a Bor sprint, Bor makes a system call to the StateReceiver genesis contract at 0x…1001. StateReceiver passes the message to ChildChainManager, which mints the tokens to the destination address on Polygon.

Think of the event as a deposit instruction that validators verify before Bor carries it out. The analogy stops there: the actual work is done by these named contracts and protocol components, not by a person forwarding a message or paying a separate Polygon fee.

This explains the difference between a deposit being included and the tokens arriving. Ethereum inclusion means your paid transaction and its event are on Ethereum. Arrival means Heimdall has recorded that event and Bor has applied it, so the balance appears on Polygon. Treating those as the same moment can make a deposit look stuck when it is simply waiting for the next steps.

Why higher Ethereum gas cannot speed up the mint

Higher Ethereum gas can help your deposit transaction get included sooner, but it cannot buy faster Heimdall agreement or a Bor sprint. Gas affects the first step: inclusion of your transaction on Ethereum. After the StateSynced event exists, Polygon’s own sequence controls when the mint happens.

Say you raise the Ethereum fee to get a supported token deposit included quickly. That can move the event onto Ethereum sooner. It does not make validators record the event sooner once their agreement is needed, or make Bor apply it outside its block production. The wait after Ethereum inclusion is therefore different from a slow Ethereum transaction, and paying more on Ethereum does not remove it.

This is why no Polygon gas is charged to your wallet for the deposit mint. The protocol applies the verified event as part of Bor’s work; your wallet has not sent a Polygon transaction that needs its own gas payment. Withdrawals work differently: you pay Polygon gas to burn tokens, then Ethereum gas to claim them there.

Related

How long does a deposit to Polygon take to arrive?

A deposit arrives after its Ethereum transaction is included, Heimdall validators agree on the StateSynced event, and Bor applies it during a sprint. The wait after Ethereum inclusion depends on those later protocol steps, so a higher Ethereum fee only affects how quickly the first step happens.

Where does a state sync appear on Polygonscan?

On Polygonscan, look for the destination-side token transfer to your address; the StateSynced event itself is emitted on Ethereum. The Polygon bridge is a concrete example of this deposit path because its Polygon PoS deposits use state sync to carry the verified Ethereum event into Bor’s minting process.