# Polygon PoS versus a rollup: different security and bridge assumptions Polygon PoS is a separate proof-of-stake network whose validators and Ethereum checkpoint contracts play specific roles. Posting checkpoints to Ethereum is not the same as Ethereum checking a rollup proof of execution. Compare the actual network architecture, bridge and validator assumptions; a shared brand or Ethereum connection does not make every Polygon system an Ethereum rollup. Evidence: [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/); [Ethereum layer 2](https://ethereum.org/en/layer-2/) Canonical: https://degreesofsatoshi.com/encyclopedia/polygon-pos-and-rollups/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Production:** Bor is the block-production layer described in Polygon PoS documentation. ([Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/)) - **Consensus:** Heimdall-v2 coordinates PoS validation and checkpoints. ([Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/)) - **Checkpoints:** Ethereum contracts receive commitments to Polygon PoS block information. ([Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/)) ## Follow what each component actually verifies Polygon PoS documentation separates Ethereum contracts for staking and checkpoints, Heimdall-v2 consensus and Bor execution. Its validators agree on blocks and produce checkpoint commitments that are submitted to Ethereum. An Ethereum record of a commitment does not by itself establish that Ethereum executed or independently proved all the committed transactions. The verification design behind that commitment matters. Evidence: [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/) ## Two Ethereum-connected networks can have different assumptions Imagine Network A publishes a PoS checkpoint and Network B publishes rollup data with a validity proof checked by an Ethereum contract. Both interact with Ethereum, but the roles of validators, data and verification differ. Calling both “Ethereum-connected” does not make their failure modes equivalent. For a deposit, inspect the bridge’s authorization and release rules for the exact network rather than transferring assumptions from another product name. Evidence: [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/); [Ethereum layer 2](https://ethereum.org/en/layer-2/) ## Treat the product name as a starting point This article describes Polygon PoS’s architecture in the documentation retrieved on 2 October 2026. It does not rate every Polygon-related chain or assert a permanent configuration for every product. Before use, confirm network identity, current asset support and withdrawal behavior. Familiar EVM tooling helps interaction but does not replace understanding the network’s settlement and custody assumptions. Evidence: [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/) ## Questions ### Does publishing a checkpoint on Ethereum make a chain a rollup? No. A checkpoint alone is not the rollup combination of data availability and state-verification mechanisms. Inspect what Ethereum contracts actually verify. Evidence: [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/); [Ethereum layer 2](https://ethereum.org/en/layer-2/) ### Can two Polygon-branded systems use different security models? Yes. Evaluate the named network and its documented architecture. A common brand is not a protocol-level security guarantee. Evidence: [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/); [Ethereum layer 2](https://ethereum.org/en/layer-2/) ## Claims and scope ### polygon-pos-and-rollups-quick-answer Polygon PoS is a separate proof-of-stake network whose validators and Ethereum checkpoint contracts play specific roles. Posting checkpoints to Ethereum is not the same as Ethereum checking a rollup proof of execution. Compare the actual network architecture, bridge and validator assumptions; a shared brand or Ethereum connection does not make every Polygon system an Ethereum rollup. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### polygon-pos-and-rollups-fact-production Production: Bor is the block-production layer described in Polygon PoS documentation. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### polygon-pos-and-rollups-fact-consensus Consensus: Heimdall-v2 coordinates PoS validation and checkpoints. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### polygon-pos-and-rollups-fact-checkpoints Checkpoints: Ethereum contracts receive commitments to Polygon PoS block information. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Polygon PoS architecture](https://docs.polygon.technology/pos/architecture/overview/) — Polygon Labs. PoS validator/consensus and bridge checkpoint assumptions differ from Ethereum rollup proofs. Locator: Bor; Heimdall; checkpoints; Ethereum contracts. Retrieved: 2026-10-02T18:55:28.218Z. - [Ethereum layer 2](https://ethereum.org/en/layer-2/) — ethereum.org contributors. Rollup comparison dimensions and limits of transferring broad labels to a named deployment. Locator: Rollups; sidechains; bridges; considerations. Retrieved: 2026-10-02T18:55:27.801Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Polygon PoS versus a rollup: different security and bridge assumptions.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/polygon-pos-and-rollups/