Canopy Network Docs
  • πŸ‘‹Welcome to Canopy
    • Overview
    • What is Canopy?
      • Introduction
      • Why Canopy?
        • Blockchain 101
        • Background
        • Industry State
        • Seeding the Future
        • Comparables
          • Ethereum
          • Tendermint
          • Polkadot
          • Avalanche
          • Rollups
      • Core Features
        • Peer-To-Peer Security
        • Progressive Sovereignty
        • Capital Efficient Restaking
        • Composable Architecture
        • One-Way Interoperability
        • Built-In Liquidity
        • Chain Halt Rescue
        • NestBFT
          • PoS Is Trusted
          • PoAge Is Trustless
          • VRF Leader Election
        • Checkpoints as a Service
        • United Governance
      • Tokenomics
        • CNPY
        • Staking
        • DAO Treasury Fund
        • Recursive Rewards
        • Subsidies
      • Who is Canopy for?
        • New Blockchains
        • Existing Ecosystems
        • Token Participants
    • How does Canopy work?
      • Utility
      • Consensus
      • P2P
      • State Machine
      • Storage
      • Specifications
        • CLI
        • RPC
        • Config
        • Governance Params
        • Nested Chain IDs
  • βš’οΈBuild
    • Build a new L1
      • Introduction
      • Building
        • Application
        • Governance
        • Testing
        • Upgrading
      • Governance
        • Straw Polling
        • Proposals
    • Connect an external chain
      • Introduction
      • Building
        • Connecting
        • Testing
        • Upgrading
      • Governance
        • Straw Polling
  • πŸ‘¨β€πŸ’»Node Runner
    • Setup
    • Install
    • Configure
    • Manage
    • Debug
    • Validate
      • Get CNPY
      • Plugins Config
      • Stake
      • Manage
      • Slashing
    • Govern
  • πŸ’ͺParticipate
    • How To Get CNPY
    • What to do with CNPY
      • Manage
      • Earn
      • Subsidize
      • Govern
Powered by GitBook
On this page
  • What are Rollups?
  • How does it work?
  • Pros & Cons of building on Rollups
  • Canopy and Rollups Comparison
  1. Welcome to Canopy
  2. What is Canopy?
  3. Why Canopy?
  4. Comparables

Rollups

PreviousAvalancheNextCore Features

Last updated 1 month ago

What are Rollups?

Rollups offer a model that offloads heavy computation and state storage from the host while relying on the host for security guarantees. Rollups achieve this by electing dedicated, often centralized, Sequencers who are responsible for aggregating transactions and producing blocks.

The popularity of Rollups inspired projects like Celestia to champion data availability as an independent service, offering a Tendermint-based storage layer for Rollup deployment.

Critical thinking: Celestia promotes itself as modular - but how does this work with ?

How does it work?

Just like Monoliths - builders deploy app code to 'contract' accounts that the Sequencer and full-nodes store, update state, execute transactions on, and verify. The app code is only the 'state-machine' logic, whereas the Rollup client handles peer-to-peer, and persistence β€” while the host protocol (Ethereum) handles Consensus and finality.

Pros & Cons of building on Rollups

The good:

  • βœ… quick to market

  • βœ… have immediate security

  • βœ… have access to Ethereum's ecosystem and tooling

  • βœ… have an easy framework to build

It's important not to overlook the features that make Ethereum so popular

The bad:

  • ❌ compete for limited resources, favoring the highest bidder

  • ❌ leak economics to Ethereum for life (fees, network effects, ecosystem lock-in)

  • ❌ can't leave without starting over

  • ❌ have limited scalability

  • ❌ are success-capped with historically lower FDV than L1s

  • ❌ can't natively communicate with external ecosystems

  • are not decentralized relying on the host for:

    • ❌ governance

    • ❌ transaction execution

    • ❌ state updates

    • ❌ blockchain storage

  • Which means:

    • ❌ can be by non-stakeholders

    • ❌ are controlled by the host

    • ❌ lack autonomy

    • ❌ have single points of failure

A "not so" decentralized app is just Web2 with an inefficient and complicated architecture

Canopy and Rollups Comparison

_
CANOPY
ROLLUPS

Architecture

βœ… Peer-to-Peer

❌ Layered on a Monolith

Scaling Method

βœ… Every new chain horizontally scales Web3

❌ Semi-centralized layers

Builder Sovereignty

βœ… Progressive

❌ Critical, lifelong reliance on host for security, finality, and blockchain storage

Ecosystem

❌ New

βœ… The best

Long range attack

βœ… Proof of Age

βœ… Checkpoint on Ethereum

Builder Difficulty

βœ… Quick to market

βœ… Quick to market

Builder Economic Security

βœ… Immediate

βœ… Immediate

Builder Framework

βž– Fork & Clone: Golang

βž– Standards with DSL (Solidity)

Chain Resources

βœ… Exponential: Each new chain is additive

❌ Limited: host single chain

Builder Success

βœ… L0 Premium

❌ Typically lower FDV than sovereign L1s

Native Interoperability

βœ… Permissionless

βž–Within Ecosystem

Builder Decentralization

βœ… Full/Progressive

❌ Not decentralized

πŸ‘‹
censored
Blockchain 101