What the Polygon PoS user is confirming
Bor produces Polygon PoS blocks, Heimdall-v2 coordinates validator consensus and milestones, and checkpoints periodically anchor accepted Polygon state to Ethereum.
Polygon PoS (POL): How Transactions and Checkpoints Work
Polygon PoS is an EVM-compatible proof-of-stake sidechain for Ethereum, and POL is its protocol-native asset used for transaction fees and validator staking. This page focuses on how Polygon PoS Transactions and Checkpoints Work and the checks users need before bridging assets, paying fees or waiting for finality.
Help users understand how Polygon PoS transactions work and make safer bridge and transaction decisions for Polygon PoS.
- Snapshot:
- CoinGecko - USD
- Chart:
- Binance Spot - POL/USDT
- Timezone:
- UTC
Use this page to inspect sourced market references and understand Polygon PoS architecture. It is not an executable quote, price forecast or bridge transaction interface.
Content ownership: BitcoinToolkit Editorial Team
Technical references: Official Polygon PoS architecture, fee, token and bridge documentation.
Review approach: Technical explanations are checked against primary Polygon documentation.
Last content review: Data integration last tested:
How Polygon PoS Transactions and Checkpoints Work
BitcoinToolkit separates CoinGecko USD data from the Binance Spot POL/USDT market and explains Polygon PoS execution, checkpoints, bridge withdrawals, fees and local finality.
POL and transaction costs
Polygon Ecosystem Token (POL) is the asset profiled on this page. POL is the market asset displayed on this page.
Polygon Ecosystem Token (POL) pays the applicable transaction cost. POL pays EVM transaction execution fees on Polygon PoS.
POL Candlestick Chart
POL/USDT · Binance Spot · UTC
Long ranges automatically use a compatible candle interval.
Historical Binance Spot candles are available. JavaScript is required for current-candle updates.
Recent OHLC and volume data
| Time (UTC) | Open (USDT) | High (USDT) | Low (USDT) | Close (USDT) | Volume (POL) |
|---|---|---|---|---|---|
| Aug 25, 2026 11:00:00 UTC | 0.12 USDT | 0.12 USDT | 0.12 USDT | 0.12 USDT | 5,387,680.10 POL |
| Aug 25, 2026 10:00:00 UTC | 0.12 USDT | 0.12 USDT | 0.12 USDT | 0.12 USDT | 3,789,823.00 POL |
| Aug 25, 2026 09:00:00 UTC | 0.12 USDT | 0.12 USDT | 0.12 USDT | 0.12 USDT | 5,122,583.80 POL |
| Aug 25, 2026 08:00:00 UTC | 0.12 USDT | 0.12 USDT | 0.12 USDT | 0.12 USDT | 7,860,152.10 POL |
| Aug 25, 2026 07:00:00 UTC | 0.12 USDT | 0.12 USDT | 0.12 USDT | 0.12 USDT | 10,457,178.40 POL |
Market data: Binance Spot POL/USDT
Charting library: TradingView Lightweight Charts
Polygon PoS Network and POL
Polygon PoS is an EVM-compatible sidechain network, while POL is the protocol-native asset used for fees and validator staking.
Network
Polygon PoS executes EVM transactions with its own validator and consensus systems while maintaining an anchoring relationship with Ethereum.
Primary asset
POL is the native asset used for Polygon PoS transaction fees and validator staking.
Network and asset roles
Polygon PoS is the transaction-processing network; POL is an asset with fee, staking and market roles.
Polygon PoS Sidechain Architecture
Polygon PoS executes EVM transactions independently while checkpoints connect accepted sidechain history to Ethereum.
Parent network
Ethereum
Ethereum relationship
Ethereum receives checkpoint commitments and hosts bridge contracts, but it does not directly order or execute each Polygon PoS transaction.
Execution environment
Bor provides EVM-compatible block production and execution for account state and smart contracts.
Security boundary
Polygon PoS validators provide the immediate network security model, so Ethereum consensus does not automatically secure every sidechain block.
Polygon PoS Accounts
Polygon PoS uses EVM account state with balances, nonces, contract code and storage.
Externally owned accounts
Private keys control externally owned accounts and authorize transactions.
Contract accounts
Deployed bytecode controls contract accounts and executes when called.
Nonce
A sender nonce orders transactions and prevents replay from the same account.
Asset roles
The page entity, transaction fee asset, and primary displayed asset are configured independently.
Native asset: POL
POL is the protocol-native asset on Polygon PoS.
Fee asset: POL
POL pays EVM transaction execution fees on Polygon PoS.
Display asset: POL
POL is the market asset displayed on this page.
POL Fee Units
Polygon PoS represents native POL with 18 decimal places; raw RPC values use wei and gas prices are commonly quoted in gwei.
Unit asset
POL
Native unit
POL
Smallest unit
wei
Fee quote unit
gwei
RPC unit
wei
Conversion factor
1 POL = 10^18 wei; 1 gwei = 10^9 wei
Unit explanation
Wallets display POL, fee interfaces commonly quote gwei, and JSON-RPC values use integer wei.
Polygon PoS Gas and Fees
Polygon PoS meters EVM work in gas and pays execution fees in native POL.
Fee asset
POL
Gas
Gas measures EVM computation and storage work.
Gas limit
The gas limit caps the work a transaction can consume.
Gas used
Gas used records the work consumed during execution.
Base fee
An EIP-1559-style base fee adjusts according to Polygon PoS block utilization.
Priority fee
A priority fee can influence transaction inclusion and ordering.
Execution cost
Execution cost depends on gas used and the effective gas price in POL-denominated wei.
Polygon PoS Transactions
A signed EVM transaction is checked, executed by Bor, included in a sidechain block and finalized under Polygon PoS consensus.
- Transaction creationThe sender sets recipient, value, data, nonce, chain ID and gas parameters.
- SigningThe sender signs the transaction with the account private key.
- Nonce validationNodes validate the sender nonce, signature, balance and transaction rules.
- BroadcastThe signed transaction is submitted to a Polygon PoS RPC endpoint.
- ExecutionBor executes the transaction against the current EVM state.
- Receipt generationExecution produces a receipt with status, logs and gas used.
- Block inclusionA Polygon PoS block producer includes the transaction in a block.
- Local finalityPolygon PoS consensus and milestone rules determine local finality.
Polygon PoS Smart Contracts
Polygon PoS executes EVM-compatible smart contracts through its Bor execution layer.
EVM compatibility
Common EVM bytecode, account, Solidity and JSON-RPC concepts apply.
Contract accounts
Contract accounts execute deployed bytecode and have no private key.
Token contracts
Token contracts maintain balances and allowances independently of native POL.
Ethereum Anchoring and Checkpoints
Polygon PoS checkpoints commit accepted sidechain state to Ethereum without turning each Polygon block into an Ethereum block.
Anchoring relationship
Checkpoint contracts on Ethereum receive commitments produced through the Polygon PoS checkpoint process.
Checkpoint mechanism
Heimdall-v2 aggregates an accepted range of Bor blocks and submits a checkpoint commitment to Ethereum according to protocol rules.
Checkpoint and finality distinction
Local finality is established by Polygon PoS consensus and milestones; Ethereum checkpoint acceptance is a separate anchoring event.
Polygon Bridge and Withdrawals
The official bridge coordinates contracts and proofs across the Ethereum and Polygon PoS boundary.
Bridge relationship
Bridge contracts lock or release assets and coordinate mapped representations across Ethereum and Polygon PoS.
Deposit path
A deposit locks or transfers an asset on Ethereum before the mapped asset becomes available on Polygon PoS.
Withdrawal path
A withdrawal burns or exits the Polygon representation and follows the protocol path back to Ethereum.
Withdrawal limitation
Withdrawal completion depends on checkpoint availability, bridge proof processing and Ethereum confirmation requirements, so it is not immediate.
Polygon PoS Validators and Finality
Polygon PoS validators coordinate Bor block production and Heimdall-v2 consensus, with milestones providing fast deterministic finality.
Consensus model
Polygon PoS uses a proof-of-stake validator system spanning Bor execution and Heimdall-v2 consensus rather than Ethereum consensus ordering each block.
Validator behavior
Validators produce or validate Bor blocks and participate in Heimdall-v2 consensus, checkpoints and milestone commitments.
Independent security model
The Polygon PoS validator and staking system is the immediate security model even though checkpoints are later committed to Ethereum.
Local finality
Heimdall-v2 milestones provide deterministic finality for confirmed Polygon PoS blocks, normally within a short network-dependent interval.
Application limitation
Bridges and applications may require a later checkpoint or Ethereum confirmation beyond local milestone finality.
Polygon PoS Guidance for Holders
Before the next transaction
- Choose network for the current Polygon PoS route.
- Fund fee asset for the current Polygon PoS route.
- Review action for the current Polygon PoS route.
- Execute for the current Polygon PoS route.
- Check finality for the current Polygon PoS route.
Polygon PoS Risks Before Completion
The POL result needs context
A Polygon PoS transaction can execute successfully while the application state, contract permission or later exit remains wrong for the user's goal. POL is the market asset displayed on this page. POL pays EVM transaction execution fees on Polygon PoS.
What Polygon PoS users should verify and why this design differs
CoinGecko USD and Binance Spot POL/USDT are separate datasets and can differ. Bridge completion depends on checkpoints, proofs and Ethereum confirmation requirements.
For Polygon PoS, the practical sequence is Choose network, Fund fee asset, Review action, Execute, Check finality. Confirm the official destination and current network, then inspect the final balance, position, receipt or documented exit state that actually completes the task: Understand how Polygon PoS transactions work and make safer bridge and transaction decisions for Polygon PoS.
Polygon PoS Network use FAQ
What is Polygon PoS?
Polygon PoS is an EVM-compatible proof-of-stake sidechain for Ethereum.
What pays Polygon PoS gas fees?
Native POL pays transaction execution fees.
How do Polygon checkpoints work?
Heimdall-v2 summarizes accepted Polygon block ranges and submits checkpoint commitments to Ethereum.
Are Polygon withdrawals immediate?
No. Withdrawal completion depends on checkpoints, proof processing and Ethereum confirmations.
Known Limitations
- Applications should use current node and bridge documentation for confirmation policies.
Market Data Methodology
The snapshot is CoinGecko aggregated USD data. The chart is Binance Spot POL/USDT data. Providers, venue coverage and quote currencies differ.
- Market Snapshot Source
- CoinGecko aggregated market data (USD)
- Candlestick Source
- Binance Spot market data
- Pair
- POL/USDT
- Venue
- Binance Spot
- Market Type
- Spot
- Timezone
- UTC
- Cache
- Snapshot cache is approximately 60 seconds; historical candle cache varies by interval.
- Failure Handling
- Verified cache is labeled Cached or Delayed. Missing or provider-inconsistent values remain unavailable.
- Snapshot Status
- Delayed
- Chart Status
- Historical Only
- Report Issue
- Report a market-data problem →
Technical Sources
Selected primary sources support the operational explanations. Market-provider attribution remains separate.
Editorial Information
Verified technical content, reviewed sources and update history.
- Published
- Last Review
- Data Verification
- Sources
- Official documentation