Skip to content

Latest commit

 

History

History
331 lines (241 loc) · 11 KB

ROADMAP.md

File metadata and controls

331 lines (241 loc) · 11 KB

Stoolap Chain Roadmap

This roadmap outlines the evolution of the Stoolap Chain blockchain SQL database from conception to production.

Current Status: Phase 2 - Zero-Knowledge Proofs ✅

Completed: March 2026

STWO/Cairo integration, compressed proofs, confidential queries, and L2 rollup protocol have been implemented.

Phase 1: Foundation ✅ (COMPLETE)

Goal: Establish core cryptographic and consensus infrastructure

Completed Milestones

Milestone RFC Status Date
Deterministic Value Types RFC-0102 ✅ Complete Feb 2025
Hexary Merkle Proofs RFC-0101 ✅ Complete Feb 2025
Blockchain Consensus RFC-0103 ✅ Complete Feb 2025
SHA-256 Migration - ✅ Complete Feb 2025

Deliverables

  • ✅ DetermValue - Deterministic value types with inline/heap optimization
  • ✅ HexaryProof - Compact bitmap-based Merkle proofs for 16-way tries
  • ✅ RowTrie - Hexary Merkle trie with proof generation
  • ✅ ExecutionContext - Gas-metered transaction execution
  • ✅ Block - Block structure with operations and state commitments
  • ✅ 4,344 passing tests
  • ✅ Comprehensive benchmarks

Performance Achieved

Metric Target Actual
Proof size (typical) <100 bytes ~68 bytes
Verification time <5 μs ~2-3 μs
Batch verification (100) <50 μs single-threaded ~50 μs
Batch verification (100) <15 μs parallel (8 cores) ~15 μs

Phase 2: Zero-Knowledge Proofs ✅ (COMPLETE)

Goal: Integrate STWO/Cairo for proof compression, confidential queries, and L2 scaling

Completed Milestones

Milestone RFC Status Date
STWO and Cairo Integration RFC-0201 ✅ Complete Mar 2026
Compressed Proof Format RFC-0202 ✅ Complete Mar 2026
Confidential Query Operations RFC-0203 ✅ Complete Mar 2026
L2 Rollup Protocol RFC-0204 ✅ Complete Mar 2026
STWO Plugin Architecture RFC-0205 ✅ Complete Mar 2026
STWO Benchmarks RFC-0106 ✅ Complete Mar 2026

Deliverables

  • ✅ stwo-plugin/ - STWO verification plugin (C-compatible FFI)
  • ✅ stwo-bench/ - STWO proof generation benchmarks
  • ✅ cairo/hexary_verify.cairo - Cairo program for hexary proof verification
  • ✅ cairo/state_transition.cairo - Cairo program for state transitions
  • ✅ cairo/merkle_batch.cairo - Cairo program for batch verification
  • ✅ src/zk/ - ZK types, Pedersen commitments, compressed proofs
  • ✅ Plugin architecture for stable Rust compatibility

Key Features Implemented

  • STWO Integration - Circle STARK prover/verifier in Rust
  • Cairo Programs - Full Cairo programs for core operations
  • Proof Compression - Aggregate HexaryProofs into single STARK proof
  • Confidential Queries - Private database operations with ZK proofs
  • L2 Rollup - Off-chain execution with on-chain verification
  • STWO Plugin - Modular verification with plugin architecture

Phase 3: Protocol Enhancement 🔄 (CURRENT)

Goal: Extend consensus mechanism with block production and validation

Planned RFCs

RFC Title Status Priority
RFC-0301 Block Production & Proposer Selection Draft High
RFC-0302 Block Validation & Fork Choice Draft High
RFC-0303 Network Protocol & Gossip Draft Medium
RFC-0304 Signature Schemes & Validator Keys Draft High

Key Features

  • Block Producers - Designated nodes propose blocks
  • Validator Set - Participating nodes validate and sign blocks
  • Fork Choice Rule - Chain selection in case of conflicts
  • Gossip Protocol - Block and transaction propagation
  • Finality - Economic finality for confirmed blocks

Timeline Estimate

Q1-Q2 2026

Phase 4: Advanced Optimizations (FUTURE)

Goal: Further scalability and advanced features

Planned RFCs

RFC Title Status Priority
RFC-0401 State Pruning & Archive Access Draft Low
RFC-0402 Parallel Transaction Execution Draft High
RFC-0403 Database Sharding Draft Low
RFC-0404 Cross-Chain Bridges Draft Medium
RFC-0405 Light Client SPV Mode Draft High

Key Features

  • State Pruning - Archive old state, reduce storage
  • Parallel Execution - Execute non-conflicting transactions in parallel
  • Database Sharding - Horizontal scaling for large datasets
  • Cross-Chain Bridges - Interoperability with other blockchains
  • SPV Mode - Light client verification without full nodes

Timeline Estimate

2026

Implementation Progress

Phase 1: Foundation ✅ (COMPLETE)

Mission Status Mission #
HexaryProof Core Data Structures ✅ Complete 001
Nibble Packing/Unpacking Utilities ✅ Complete 002
Bitmap Sibling Reconstruction ✅ Complete 003
16-Way Child Hashing ✅ Complete 004
HexaryProof Streaming Verification ✅ Complete 005
RowTrie Proof Generation ✅ Complete 006
Solana-Style Serialization ✅ Complete 007
Parallel Batch Verification ✅ Complete 008
Verification Fixes and Refinements ✅ Complete 009
Integration Tests ✅ Complete 010
Benchmarks ✅ Complete 011
Documentation and Cleanup ✅ Complete 012

Phase 2: Zero-Knowledge Proofs ✅ (COMPLETE)

Mission Status Mission #
STWO Dependency ✅ Complete 0201-01
Cairo Program Types ✅ Complete 0201-02
Cairo Compiler Integration ✅ Complete 0201-03
STARK Proof Types ✅ Complete 0201-04
Prover Interface ✅ Complete 0201-05
Core Cairo Programs ✅ Complete 0201-06
Integration Tests ✅ Complete 0201-07
Compressed Proof Types ✅ Complete 0202-01
Proof Generation ✅ Complete 0202-02
Proof Verification ✅ Complete 0202-03
Pedersen Commitment Scheme ✅ Complete 0203-01
Confidential Query Types ✅ Complete 0203-02
Query Execution ✅ Complete 0203-03
Result Verification ✅ Complete 0203-04
L2 Rollup Types ✅ Complete 0204-01
Batch Execution ✅ Complete 0204-02
Batch Submission ✅ Complete 0204-03
Fraud Proofs ✅ Complete 0204-04
Withdrawals ✅ Complete 0204-05
STWO Plugin Architecture ✅ Complete 0205-01
STWO Real Benchmarks ✅ Complete 0106-01
Trie Extension Fix ✅ Complete 0105-01

Phase 3: Protocol Enhancement 🔄 (NEXT)

Mission Status Mission #
TBD 📋 Planned -

Use Cases Driving Development

Active Use Cases

  1. Blockchain SQL Database - Primary motivation

    • Enables verifiable SQL database state
    • Trust minimization through cryptographic proofs
    • Gas-metered transaction execution

  2. Verifiable State Proofs - Core technology

    • Lightweight clients without full nodes
    • Efficient proof verification
    • Standard hexary proof format

  3. ZK Proofs for Scalability and Privacy - ✅ COMPLETE

    • Proof compression for bandwidth efficiency
    • Confidential queries for private data operations
    • L2 rollup for high-throughput applications

  4. Protocol Enhancement (Phase 3) - Next phase

    • Block production and validation
    • Network gossip protocol
    • Economic finality

Related RFCs

Accepted RFCs

  • RFC-0101 - Hexary Merkle Proofs (Phase 1)
  • RFC-0102 - Deterministic Value Types (Phase 1)
  • RFC-0103 - Blockchain Consensus (Phase 1)

Implemented RFCs

  • RFC-0106 - STWO Benchmarks (Phase 2)
  • RFC-0201 - STWO/Cairo Integration (Phase 2)
  • RFC-0202 - Compressed Proofs (Phase 2)
  • RFC-0203 - Confidential Queries (Phase 2)
  • RFC-0204 - L2 Rollup (Phase 2)
  • RFC-0205 - STWO Plugin Architecture (Phase 2)

Draft RFCs

  • RFC-0301 - Block Production & Proposer Selection (Phase 3)
  • RFC-0302 - Block Validation & Fork Choice (Phase 3)
  • RFC-0303 - Network Protocol & Gossip (Phase 3)
  • RFC-0304 - Signature Schemes & Validator Keys (Phase 3)

Technology Choices

Why Hexary Tries?

  • Efficiency - 16-way branching reduces tree depth
  • Proximity - Related data stored near each other
  • Industry Standard - Ethereum, Optimism use similar structures

Why SHA-256?

  • Security - Cryptographic hash function
  • Standard - Widely adopted, hardware acceleration
  • Determinism - Same input always produces same output

Why Bitmap Encoding?

  • Compactness - Only store actual siblings, not empty positions
  • Flexibility - Handles sparse trie structures
  • Efficiency - 5-10x smaller than binary proofs

Why STWO and Cairo?

  • STWO - Circle STARK prover/verifier written in Rust
  • Cairo - Turing-complete language for provable programs
  • Native Integration - Direct Rust linking for performance
  • Cairo VM Verification - On-chain verification via Cairo contracts

Success Metrics

Phase 1 Targets (ACHIEVED)

Metric Target Actual Status
Proof size <100 bytes ~68 bytes ✅
Verification time <5 μs ~2-3 μs ✅
Tests passing >4000 4,344 ✅
Benchmarks created Yes Yes ✅

Phase 2 Targets (ACHIEVED)

Metric Target Actual Status
STWO plugin built Yes ✅ Yes ✅
Cairo programs 3 3 ✅
Compressed proof Yes ✅ Yes ✅
Confidential queries Yes ✅ Yes ✅
L2 Rollup Yes ✅ Yes ✅
Benchmarks Yes ✅ Yes ✅

Phase 3 Targets (FUTURE)

Metric Target Status
Block production Yes 📋 Planned
Validator set Yes 📋 Planned
Fork choice Yes 📋 Planned
Gossip protocol Yes 📋 Planned
Finality <1 minute 📋 Planned

Contributing

See BLUEPRINT.md for the governance process.

Quick Start:

  1. Read Use Cases for WHY
  2. Read RFCs for WHAT
  3. Claim a Mission for HOW

Never skip layers. No RFC = No Mission.

Links