1/ Today, we are excited to propose the Polygon 2.0 architecture, designed to provide unlimited scalability and unified liquidity, thus transforming Polygon into the Value Layer of the Internet!

Read the blog 👇🏽 or keep scrolling 🧵

go.polygon.technology/3NQmEtV

2/ The Polygon 2.0 architecture consists of four protocol layers, each enabling an important process within the network:

→ Staking Layer
→ Interop Layer
→ Execution Layer
→ Proving Layer

What are these layers and what is their role? Let's dive in...

3/ The Staking Layer is a PoS-based protocol which leverages Polygon’s native token to provide "out-of-the-box" decentralization to participating Polygon chains.

It achieves that via a common, highly decentralized validator pool and an in-built restaking model.

4/ This allows Polygon chains to focus on their use cases and communities rather than infrastructure.

To validators, it offers rewards in Polygon tokens, as well as an opportunity for additional revenue streams via collecting transaction fees/rewards from chains they validate.

5/ The Interop Layer facilitates cross-chain messaging within the ecosystem.

It abstracts the complexity of cross-chain transactions and makes the whole Polygon network feel like a single chain, by enabling:

- Shared access to native Ethereum assets
- Seamless composability

7/ The Execution Layer enables any Polygon chain to produce sequenced batches of transactions, aka blocks.

It has multiple components, commonly observed in most blockchain networks (Bitcoin, Ethereum, etc):

- P2P
- Consensus
- Database
- Syncing
- Mempool etc.

8/ This protocol layer is pretty commoditized, i.e. used in a similar format by most blockchain networks, yet relatively complex to implement.

For this reason, existing performant implementations (e.g. Erigon) should be reused to the maximum extent possible.

9/ The Proving Layer is a performant, flexible proving protocol. It proves all transactions for every Polygon chain.

It has three components:
→ Common prover - proves transactions
→ State machine constructor - defines state machines
→ State machine - interprets transactions

10/ Its novel design offers several major benefits, namely:

- Efficient proof generation and verification
- Straightforward and efficient proof aggregation
- Definition of different ZK state machines
- Safe cross-chain communication between those state machines

11/ In the coming days and weeks, we will be sharing deep dives into individual protocol layers.

As always, we invite the community to review this proposal and upcoming deep dives and provide feedback. Let’s make Polygon 2.0 happen! 💫

6/ It is based on the LxLy protocol (used by Polygon zkEVM) and its concept of Message Queues, coupled with corresponding ZK proofs to ensure secure message passing.

On top of this foundation, we introduce the concept of Aggregator, which makes cross-chain messages seamless.