Hemi
DiscordGithub
  • 🏠Main
    • Welcome to the Hemi Docs
    • Getting Started
      • Developer Quickstart
      • Enthusiast Quickstart
      • Miner Quickstart
    • Network Details
  • ⛰️Foundational Topics
    • The Architecture
      • Consensus and Security Protocols
      • Ethereum Rollups
        • Pros & Cons
        • Decentralized Rollups
      • Sequencer Consensus
        • Proof-of-Stake (PoS)
        • PoS-Only Pitfalls
        • PoS Solutions
      • Proof-of-Proof (PoP)
        • Proof-of-Proof Consensus & Bitcoin Finality
        • Proof-of-Proof vs. Merged Mining
        • Running a PoP Mining
      • Tunnels
        • Ethereum Tunnel
        • Bitcoin Tunnel
      • Ethereum Virtual Machine (EVM)
      • Blocks
      • Transactions
      • Gas
    • Nodes & Clients
      • Node Guides
    • Wallet Support
  • 📖How-To Tutorials
    • Using Hemi
      • Wallet Setup
        • EVM Wallet Setup
        • BTC Wallet Setup
          • Switch Bitcoin Networks
      • Tunnel from Ethereum
        • Tunnel ERC20s via Native Tunnel
        • Tunnel ERC20s via 3rd Party
          • Tunnel via Stargate
      • Tunnel from Bitcoin
        • Tunnel BTC via Native Tunnel
        • Tunnel BTC via 3rd Party
      • Stake
      • Developer Tooling
        • Set Up a Safe Wallet
        • Create a Capsule
      • PoP Mining
        • CLI PoP Miner
          • (Testnet) Add tHEMI to MetaMask
          • (Mainnet) Add PoPPoints to Metamask
        • Web PoP Miner (deprecated)
    • Developing on Hemi
      • General
        • HelloWorld.sol
        • Deploy an ERC-20 Token
      • hVM & hBK
        • Using the hBK Demo App
        • Get Bitcoin Balance with Remix
  • ⚙️Building Bitcoin Apps
    • Introduction
    • Hemi Virtual Machine (hVM)
      • Motivation
      • Feature Summary
      • Deploy on hVM
    • Hemi Bitcoin Kit (hBK)
      • Overview
      • hBK Smart Contract
  • ⚙️Tooling
    • viem
    • Contract Addresses
    • Contract Verification
    • Data Indexing
    • Oracles
  • 📝Incentives
    • Points
    • Grants
    • Retroactive Funding
    • One-Off Spends
  • ⚡Additional Resources
    • Partners
    • FAQ
    • Official Links
    • Brand Kit
  • 📨Send Feedback
    • Bug Report
    • Contact Us
Powered by GitBook
On this page
  • 🌀 Conventional Rollups
  • 💭 Things to Consider
  • Centralized Influence in a Decentralized Sequencing World
  • 🟩 Verifiers and Challenges
  • ✋ Denial-of-Service Risks

Was this helpful?

Edit on GitHub
Export as PDF
  1. Foundational Topics
  2. The Architecture
  3. Ethereum Rollups

Pros & Cons

PreviousEthereum RollupsNextDecentralized Rollups

Last updated 9 months ago

Was this helpful?

📜 TL;DR:

  • Optimistic Rollups: Faster, presumed valid until proven otherwise; has delays, user fraud detection, relies on centralization.

  • Zero-knowledge Rollups: Prior validation is needed, enhanced privacy; complex vulnerabilities, trusted setup, reliance on centralization.

  • Centralized Influence: Centralized proposers could disrupt decentralized frameworks.

  • Verifiers and Challenges: Vulnerabilities demand verifiers, lack of incentives leads to centralization.

  • Denial-of-Service Risks: Centralized "batchers" in L2 networks risk refusing to publish transactions back to Ethereum, potentially causing service denial.


🌀 Conventional Rollups


💭 Things to Consider

Centralized Influence in a Decentralized Sequencing World

Within frameworks aiming for decentralized sequencing, the presence of a centralized proposer could wield significant influence, potentially disrupting their intended decentralized nature.

Such control might result in the withholding of valid state rollups from Ethereum, leading to coercion of decentralized sequencers into potential censorship or halting communication of specific chain segments back to Ethereum for settlement.


🟩 Verifiers and Challenges

Vulnerabilities in optimistic rollup networks pose risks of asset theft through forged L2 states. To address this, rollups introduce verifiers, but the lack of proper incentives for this role presents challenges.

These lack of incentives can lead to difficulties such as:

  • 🔒 Securing a sufficient number of verifiers to perform the complex and expensive verification process required.

  • 👥 Relying heavily on users or nodes funded by development teams resulting in centralization.

  • 📣 Potential bias or influence.

  • 🌎 Sustainability and scalability issues.


✋ Denial-of-Service Risks

L2 networks' reliance on centralized "batchers" can expose them to denial-of-service risks if batchers refuse to publish transactions back to Ethereum for data availability.

⛰️

Optimistic Rollups

✅ Pros:

  • Allow faster transaction processing on Layer 2

  • Presume transactions are valid unless disputed within a specific period.

  • Reduce congestion on the main chain (L1)

❌ Cons:

  • Introduce finalization delays due to the challenge period for dispute resolution

  • Place the responsibility of fraud detection on users

  • Rely on centralized sequencers and proposers, causing hidden transaction queues (mempools) and centralized chain state communication

Zero-knowledge Rollups

✅ Pros:

  • Validate transactions before confirming them on the main chain (L1)

  • Potentially enable privacy features by leveraging zk proofs (although current implementations like ZKsync do not currently incorporate significant privacy features)

  • Reduce congestion on the main chain (L1).

❌ Cons:

  • Introduce potential vulnerabilities due to complex cryptographic systems

  • Often require a trusted setup for implementation.

  • Rely on centralized sequencers and proposers, causing hidden transaction queues (mempools) and centralized chain state communication