# Ethereum’s scaling options on Polygon

The use of Polygon, an Ethereum scalability solution, will enable you to scale a wide range of Ethereum-compatible blockchains significantly more quickly and affordably than you could before.

1. **PoS polygon**: A layer 2 scaling approach that makes use of side chains for transactional operations, enabling unheard-of transaction speeds at cheaper gas costs. With the help of a strong Plasma chain and a decentralized network of Proof-of-Stake (PoS) validators, polygon PoS secures the protection of assets.
2. **Theodore Hermez**: A payments system built on the Ethereum network that is scalable and uses no knowledge rollups. Through the consolidation of several transfers into a single transaction, it aims to address Ethereum’s scalability issues.
3. **Polygon Avail**: Avail encourages a total change in how blockchain networks are run. The resilient general-purpose scalable data availability layer is how it is referred to.
4. **Polygon Edge**: The main purpose of Polygon Edge is to launch a new blockchain network that is completely compatible with Ethereum smart contracts and transactions.
5. **Polygon Nightfall**: A roll-up that is hopeful about reducing the cost of transactions including the ERC20, ERC721, and ERC115 tokens. Blocks of transactions will be compiled by the proposers and submitted to the optimistic contracts in this case.
6. **Polygon Miden**: The L-2 Ethereum scaling method combines thousands of transactions into a single Ethereum transaction using zero-knowledge technology. As a result, the throughput is greatly increased and the gas fee is decreased.
7. **Polygon Zero**: The fastest L2 zero-knowledge scaling solution for Ethereum. It makes use of Plonky2, a cutting-edge prover system that produces ZK proofs more quickly than any other technique.

<figure><img src="https://642716061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtRUCHaghT8l5YWiv1ADu%2Fuploads%2FPklovaDRXVNf7YcUhuJL%2Fimage.png?alt=media&#x26;token=8d560289-9bc2-4bca-8761-3f077cafbc89" alt=""><figcaption></figcaption></figure>
