Polygon is Ethereum's most diversified scaling suite, running a commit-chain (PoS), a ZK rollup (zkEVM), a chain development kit (CDK), and a shared validity proof layer (AggLayer) under one umbrella. It processes billions of dollars in onchain volume across DeFi, payments, and NFTs each month, and its native token upgraded from MATIC to POL in late 2024.
​

Polygon is a multi-product scaling platform built alongside Ethereum. Rather than a single chain, it is a suite: Polygon PoS handles high-throughput consumer transactions, Polygon zkEVM offers ZK-proven EVM execution, Polygon CDK lets teams launch custom ZK-powered chains, and AggLayer knits those chains together under a shared proof. Every product settles finality back to Ethereum mainnet.
​

The suite grew out of Matic Network, which launched in 2019 as a plasma-based sidechain. The rebranding to Polygon in 2021 signaled a pivot from a single chain to a platform strategy. Today Polygon Labs employs one of the largest ZK research teams in the industry and ships across all four product lines in parallel. For developers, the practical effect is that deploying on "Polygon" means choosing which product fits the application's latency, cost, and trust assumptions, not just pointing at one RPC endpoint.
​

Polygon competes directly with the OP Stack and Arbitrum Orbit ecosystems as a framework for launching application-specific chains. Its differentiator is a ZK-native approach: every CDK chain uses ZK proofs, not optimistic fraud windows, which means faster finality back to Ethereum.
​

External reference: Polygon Labs — About
​

Polygon PoS is the original Polygon chain, live since mid-2020 and still the highest-throughput product in the suite. It runs at chain ID 137, processes roughly 3-4 million transactions per day at sub-cent fees, and uses a validator set staking POL tokens on Ethereum mainnet to commit Merkle roots every checkpoint. Its consensus layer runs Bor for block production and Heimdall for checkpointing, giving it a hybrid architecture that is not a pure rollup but provides Ethereum-anchored finality at each checkpoint.
​

Technically Polygon PoS is a commit-chain rather than a true rollup: validators produce blocks independently, and only Merkle roots are posted to Ethereum. This means trust in Polygon PoS depends partly on the validator set, currently over 100 active validators. The trade-off is high throughput and very low fees. The chain handles 65,000+ transactions per block and has onboarded mass-market applications in gaming, NFTs, and payments precisely because $0.001 fees are viable there where Ethereum mainnet fees are not.
​

The staking token was MATIC for years. The migration to POL (covered below) preserves the staking relationship but expands the token's role to cover CDK chains too, meaning the same token will eventually secure a network of many chains rather than just PoS. Validators on Polygon PoS earn transaction fees plus POL emissions. The checkpoint-based model means users withdrawing assets to Ethereum mainnet through the canonical bridge typically wait for the next Heimdall checkpoint, roughly 30 minutes, before a withdrawal is confirmed at the Ethereum layer.
​

For stablecoin infrastructure, Polygon PoS hosts one of the largest onchain USDC pools outside of Ethereum mainnet itself. Circle deployed native USDC on Polygon PoS via CCTP, meaning USDC minted directly on-chain rather than bridged from Ethereum. Developers building payment flows on PoS can use cross-chain intent protocols to route USDC across networks, including Polygon PoS, without wrapping or bridging overhead.
​

External reference: PolygonScan — Polygon PoS block explorer
​

Polygon zkEVM is a ZK rollup deployed on Ethereum mainnet that executes transactions in an EVM-compatible environment and posts validity proofs to Ethereum L1. It launched in March 2023 and targets EVM equivalence at the bytecode level, meaning Solidity and Vyper contracts deploy without modification. Its proof system is built on polynomial commitments (PLONK-based), and the team has progressively improved the prover to reduce latency and cost.
​

The EVM equivalence classification matters for developers and auditors. The Ethereum Foundation uses a spectrum from Type 1 (fully Ethereum-equivalent, slow proofs) to Type 4 (transpiler-based, fast proofs, limited compatibility). Polygon zkEVM launched at Type 3 (mostly EVM-equivalent, minor deviations at the opcode level) with an explicit roadmap to Type 2 (EVM-equivalent, proving the exact EVM state transition). Moving from Type 3 to Type 2 matters because it eliminates edge-case incompatibilities that can affect complex DeFi contracts and reduces audit overhead when porting code from Ethereum.
​

Transaction finality on Polygon zkEVM has two stages. Sequenced transactions reach "trusted finality" within seconds as the sequencer orders them, which is fast enough for UX purposes. Proved finality occurs once a validity proof is generated and verified onchain on Ethereum L1, which historically took 30-60 minutes but has shortened as prover hardware and algorithms improve. This is materially faster than optimistic rollups, which require a 7-day fraud window before finality is fully trustless. For a deeper look at how ZK proofs work in this context, see the explainer on ZK proofs and blockchain verification.
​

Gas fees on Polygon zkEVM are quoted in ETH (the rollup's gas token) and are typically 10x-20x cheaper than Ethereum mainnet for comparable operations. The zkEVM is also one of the two Polygon chains where Circle has deployed native USDC through CCTP, giving payment developers a ZK-proven path for onchain dollar transfers that does not rely on bridged tokens.
​

External reference: Polygon zkEVM — official documentation
​

Polygon CDK is an open-source framework for launching application-specific ZK chains that settle to Ethereum and connect to other CDK chains through AggLayer. It is Polygon's answer to the OP Stack and Arbitrum Orbit: a modular toolkit that lets teams configure their own chain with custom gas tokens, sequencer rules, data availability policies, and permissioning, while inheriting ZK-proven security from Ethereum. Chains built with CDK are called "validiums" or "validchains" depending on their data availability choice.
​

The key architectural decision in a CDK chain is data availability. A team can post transaction data to Ethereum calldata (full rollup mode, highest cost, highest decentralization), to a committee of designated data availability nodes (validium mode, lower cost, trust in committee), or to an external DA layer like Celestia or Avail (middle ground). This modularity makes CDK attractive for enterprise deployments, gaming studios, and financial applications that need throughput or privacy guarantees that a shared public chain cannot provide.
​

Notable CDK deployments include Immutable zkEVM (gaming), Ronin's planned upgrade path, OKX's X Layer, Astar zkEVM, and Manta Pacific at various points in their chain history. The CDK ecosystem is growing because it gives teams a shorter path to production than building a ZK rollup from scratch while retaining the ability to customize economic parameters. From an infrastructure standpoint, CDK chains share Polygon's prover technology, meaning improvements to the core proving stack benefit all CDK chains simultaneously without per-chain engineering work.
​

For developers evaluating whether to build on an existing chain or launch a CDK appchain, the decision typically comes down to whether the application needs dedicated block space. High-frequency onchain games, real-time prediction markets, and private enterprise ledgers are the canonical use cases where dedicated throughput justifies the operational overhead of running a chain. For comparison with other appchain frameworks and how they fit into cross-chain payment flows, the rollup explainer covers the trade-offs in detail.
​

External reference: Polygon CDK documentation
​

The AggLayer is Polygon's aggregated proof layer: a protocol that collects ZK validity proofs from multiple CDK chains, aggregates them into a single combined proof, and submits that proof to Ethereum. The goal is to unify liquidity and state across all CDK chains without requiring each chain to bridge assets through Ethereum mainnet. It is the mechanism that transforms the CDK ecosystem from a collection of isolated chains into a connected network with shared security and near-native cross-chain transfers.
​

The core insight behind AggLayer is that ZK proofs are composable. If Chain A proves its state transition and Chain B proves its state transition, a single aggregated proof can verify both simultaneously at the cost of one Ethereum verification. This dramatically reduces the per-chain cost of L1 settlement and allows the number of connected chains to scale without proportionally increasing Ethereum gas costs. The economic model is that as more CDK chains join AggLayer, the per-chain settlement cost falls, making AggLayer membership increasingly attractive for new chains.
​

The cross-chain transfers enabled by AggLayer are qualitatively different from bridge-based transfers. A traditional bridge locks tokens on the source chain, mints wrapped tokens on the destination, and relies on an off-chain message passing layer to coordinate. AggLayer transfers use unified bridge contracts and shared state proofs, meaning the destination chain can verify the source chain's state directly without an intermediary. The trust model collapses to ZK math rather than multisig operators or optimistic challengers.
​

AggLayer also positions Polygon against the OP Superchain. The OP Stack's shared sequencer model achieves cross-chain atomicity through a common sequencer, while AggLayer achieves it through shared validity proofs. Both approaches are in early deployment as of 2025, and neither has fully solved asynchronous cross-chain composability at the application layer. The competition between these two frameworks will likely define a significant portion of Ethereum's modular future. For context on how Arbitrum's own ecosystem approach compares, that article covers Orbit chains and the Arbitrum stack.
​

External reference: Polygon AggLayer — product page
​

The MATIC to POL migration completed in Q4 2024, replacing MATIC as the native gas and staking token across the Polygon ecosystem. POL was designed to be a "hyperproductive" token that secures not just Polygon PoS but any number of CDK chains through a staking mechanism that allows validators to opt into multiple chains simultaneously. The supply ratio for the migration was 1:1 and existing MATIC holders could migrate via a smart contract deployed on Ethereum mainnet.
​

The economic rationale for the upgrade was that MATIC's role was narrowly scoped to Polygon PoS, which made it a poor fit for a multi-chain ecosystem. POL is designed to scale its security mandate as the CDK ecosystem grows. Validators who stake POL can elect to validate additional CDK chains and earn additional rewards from those chains, creating a marketplace for validator capacity across the ecosystem. This is analogous to how ETH restaking works conceptually, though the implementation is specific to Polygon's architecture.
​

Staking mechanics remained largely continuous through the migration. Validators who were active on Polygon PoS under MATIC continued operating under POL with no interruption to checkpointing or block production. The upgrade also changed the token contract on Ethereum mainnet from the original MATIC ERC-20 to the new POL ERC-20, meaning centralized exchanges, DeFi protocols, and wallets that held MATIC had to update token contract references. Most major exchanges completed the migration automatically on behalf of users.
​

The governance implications of the upgrade are still unfolding. Polygon's governance forum and the Polygon Improvement Proposal (PIP) process use POL as the voting token for protocol changes across the suite. As CDK chains proliferate and AggLayer matures, POL's role as a cross-chain security token will become more concrete. The current staking APR for POL on Polygon PoS sits in the low single digits, funded by a combination of transaction fees and protocol emissions.
​

External reference: Polygon POL — token and migration page
​

USDC on Polygon exists in two forms: native USDC and bridged USDC.e. Native USDC is issued directly by Circle on Polygon PoS and Polygon zkEVM, meaning the token contract is a Circle-controlled mint rather than a lock-and-mint bridge wrapper. Bridged USDC.e is the older form, created when users lock USDC on Ethereum and receive a synthetic representation on Polygon through the PoS bridge. The distinction matters because native USDC can be redeemed directly with Circle, while USDC.e can only be redeemed by reversing the bridge.
​

Circle deployed native USDC on Polygon PoS in late 2023 and on Polygon zkEVM in 2024, both using CCTP (Cross-Chain Transfer Protocol). CCTP is a burn-and-mint mechanism: USDC is burned on the source chain, Circle's attestation service issues a signed message, and USDC is minted on the destination chain. This eliminates bridge custodial risk and ensures that USDC on any CCTP-supported chain is fungible at par with USDC on Ethereum. For applications moving dollars across chains at scale, this matters significantly because it removes the discount that sometimes affects bridged stablecoins when bridge reserves come under stress.
​

The practical liquidity situation on Polygon PoS is that both USDC and USDC.e are widely held and both appear in DeFi protocols. Aave, Uniswap, QuickSwap, and other major protocols on Polygon PoS list both tokens, though native USDC has been gradually displacing USDC.e in terms of preferred reserves and new integrations. Users migrating from USDC.e to native USDC can use Circle's own bridge portal or any DEX with sufficient liquidity. On Polygon zkEVM, native USDC is the primary dollar token given that the chain launched after the CCTP deployment.
​

For developers building multi-chain payment infrastructure, Polygon PoS and zkEVM are both supported destinations for USDC flows. The stablecoin automation platforms comparison covers how platforms like Eco handle routing across chains including Polygon. The combination of low fees on PoS and ZK-proven settlement on zkEVM makes Polygon a common choice for payment flows that need cost efficiency without sacrificing Ethereum-anchored finality.
​

External reference: Circle CCTP — Cross-Chain Transfer Protocol documentation
​

Choosing between these four networks depends on the application's requirements for finality speed, trust assumptions, ecosystem depth, and stablecoin availability. The table below compares five dimensions that matter most for developers and payment infrastructure teams.
​

The finality column deserves elaboration. Optimistic rollups show 7-day trustless finality because anyone can submit a fraud proof during that window. In practice, third-party fast-exit services (Hop, Across, Connext) provide near-instant exits by advancing capital against the pending withdrawal. ZK rollups post proofs rather than waiting for challengers, so the window shrinks to however long the prover takes, currently 30-60 minutes for Polygon zkEVM. Polygon PoS finality is checkpoint-driven and sits between the two at roughly 30 minutes, but it does not have a fraud proof architecture at all, relying instead on the validator set's economic stake.
​

For TVL, Arbitrum One consistently holds the top L2 position across 2024-2025. OP Mainnet and Polygon PoS trade positions in the next tier depending on market conditions and incentive programs. Polygon zkEVM is smaller but growing as DeFi applications port from PoS to get ZK-proven finality. All four chains support native USDC via CCTP as of 2025, removing a key differentiation that previously favored chains with earlier Circle integrations.
​

Technically no. Polygon PoS is a commit-chain, sometimes called a sidechain, because it runs its own validator set rather than deriving security entirely from Ethereum. True L2s inherit Ethereum's security through rollup proofs or fraud windows. PoS posts checkpoints to Ethereum but does not post full transaction data, so it sits in a category between L1 and L2.
​

MATIC migrated to POL in Q4 2024 at a 1:1 ratio. The upgrade expanded the token's role from securing only Polygon PoS to potentially securing any CDK chain that opts into POL staking. Most exchanges and wallets handled the migration automatically. MATIC contracts still exist on Ethereum but the active token for staking and governance is now POL.
​

Native USDC is minted directly by Circle on Polygon via CCTP and can be redeemed directly with Circle. USDC.e is a bridged wrapper created when USDC from Ethereum is locked in the PoS bridge. USDC.e carries bridge custodial risk and can only be unwrapped by reversing the bridge. For new integrations, native USDC is preferred.
​

Both aim to connect multiple appchains with shared security, but through different mechanisms. AggLayer aggregates ZK validity proofs across CDK chains, providing cryptographic finality without shared sequencing. The OP Superchain uses a shared sequencer model that enables atomic cross-chain transactions. AggLayer's approach gives each chain independent sequencing; the OP approach centralizes ordering for composability.
​

In most cases, yes. Polygon zkEVM targets EVM equivalence at the bytecode level (currently Type 3, targeting Type 2), meaning Solidity and Vyper contracts compile and deploy without modification. Edge cases exist around specific precompiles and opcode costs. Complex contracts using low-level assembly should be tested on the zkEVM testnet before mainnet deployment to catch any compatibility gaps.
​

Sources: Polygon Labs documentation, Polygon PoS block explorer (PolygonScan), Circle CCTP documentation, Ethereum Foundation EVM equivalence taxonomy. Published April 2026.
​