LogoLogo
English
English
  • Introduction
  • API
  • Methodology
    • Blockspace
    • Fundamentals
      • 🕓Activity
      • ⭐Value Locked
      • 💳Economics
      • 🔀Convenience
  • General Layer 2 Knowledge
    • 📜Data Availability
      • ⚪Light/client and full nodes
      • ❌Fault Proofs
      • 🏄‍♂️Onchain Data Availablity
        • 📄EIP-4844
        • 🧫Data Availability Sampling
      • 🕊️Offchain Data Availability
        • ⚙️General Purpose DACs Mechanism
        • 📚Sources and Extra Material
  • Developer Content
    • ⚖️Which Layer 2 approach is for you?
      • ↔️State Channels
      • ⚡Plasma
      • 🌀Rollups
      • 🔐Validiums
    • ⛽Transaction Costs
      • ⚔️Optimistic vs. Zero Knowledge Rollups
      • 🤝Validium Hybrids
      • 🖼️What EIP 4844 means for Layer 2s
    • ⭐Rollup Performance
      • ⌛General Stats
      • 📨Messaging Latency and Cost
  • OP Chains
    • 🧰OP Stack
    • 🌟Superchain
    • 🛣️Road to Superchain
      • ✅Chain Factories
      • ✅Permissionless Proof System
      • ☑️Configurable Sequencer per OP Chain.
    • ⛓️Chain Knowledge
      • 🔵Base
      • ⚪Zora
      • 🟢Public Goods Network
Powered by GitBook
On this page
  • Bedrock's SystemConfig
  • The Birth of a Chain Factory
  1. OP Chains
  2. Road to Superchain

Chain Factories

Complete

PreviousRoad to SuperchainNextPermissionless Proof System

Last updated 9 months ago

The first step is to turn the Bedrock Bridge into a Chain Factory through the derivation function offered by Bedrock.

How? Let's get digging

Bedrock's SystemConfig

Contract Bedrock has revolutionized the way Layer 2 chains interact with Layer 1 smart contracts through the introduction of the SystemConfig contract. This innovation marks the beginning of defining L2 chains directly within L1 smart contracts.

The potential of this system can be further harnessed by transferring all L2 chain-defining information onto the blockchain. This includes essentials like a unique chain ID, block gas limits, and other key configuration values.

The Birth of a Chain Factory

With all chain data available Onchain, we can create a factory that deploys the configuration and all necessary contracts for each chain.

  • Streamlining efficient chain creation

Deterministic Contract Addresses with CREATE2

By utilizing CREATE2, contract addresses can be made deterministic. Given a chain configuration, all bridge addresses associated with that chain can be predetermined. – Simplifying interactions and enhancing efficiency.

Counterfactual Chain Deployment

This new system allows for counterfactual chain deployment, which is virtually free. Chains can be interacted with without deploying their bridge contracts

  • Inheriting standard security properties.

  • Significantly reducing deployment costs

Deriving OP Chain Data Using the Chain Factory

The L1 chain factory extends Bedrock's capability to derive L2 chain data from an L1 chain. This enables Optimism nodes to sync any OP Chain deterministically using just a single L1 address and a connection to L1.

When an OP Chain is synced, its state is computed locally. This process is fully permissionless and secure, eliminating the need for a proof system for chain derivation. Invalid transactions are automatically disregarded!

Maintaining Proof System for Superchain Withdrawals

Despite the advancements in chain derivation, a proof system remains necessary for enabling Superchain withdrawals, ensuring the security and integrity of cross-chain transactions. Which is coming on Next

Secure and Permissionless Chain State Computation

If you're wondering how they are automatically disregarded this example from works best:

⛏️
🌉
🏭
⛓️
💡
🎉
🔒
@karl_dot_tech
🛣️
✅
Page cover image