How alpenlabs/strata works
Main Components (Top Level)
• Bitcoin Layer (Base Layer)
• Strata Core Layer (Rollup)
• Application Layer (EVM Compatible)
Core Components
a) Client Components:
• Bridge Client (bin/bridge-client/)
• Prover Client (bin/prover-client/)
• Strata Client (bin/strata-client/)
• Strata CLI (bin/strata-cli/)
b) Execution Components:
• EVM Execution Engine (crates/eectl/, crates/evmexec/)
• Bridge Execution (crates/bridge-exec/)
• Consensus Logic (crates/consensus-logic/)
c) Storage & State:
• RocksDB Store (crates/rocksdb-store/)
• State Management (crates/state/)
• Database Layer (crates/db/)
d) Proof System:
• RISC0 Prover (provers/risc0/)
• SP1 Prover (provers/sp1/)
• ZK Verification (crates/zkvm/)
Data Flow Connections
• Bitcoin data flow through BTC I/O (crates/btcio/)
• Bridge operations flow through Bridge Relay (crates/bridge-relay/)
• Transaction processing through TX Parser (crates/tx-parser/)
• State transitions through State Management
• Proof generation and verification paths
Key Subsystems
a) Bridge System:
• Bridge TX Builder
• Bridge Sig Manager
• Bridge Relay
• Bridge Operations
b) Proof System:
• Different proof types (BTC blockspace, checkpoint, CL aggregation, etc.)
• Proof verification flow
• Proof generation pipeline
c) Execution Environment:
• EVM compatibility layer
• State transition function
• Block execution
External Interfaces
Connections to:
• Bitcoin network
• RPC interfaces (crates/rpc/)
• Client applications
• External services
The client interaction points
Remember to include version or phase indicators, as the README mentions this is a work-in-progress project with different phases (devnet, mainnet) having different characteristics.