Pharos Docs
  • Introduction
    • About Pharos Network
    • Vision & Mision
    • Why Pharos Network
    • Concepts
      • Degree of Parallelism (DP)
  • Architecture
    • Pharos Modular Stack
    • Node Architecture
      • About Pharos Nodes
  • Core Technologies
    • Pharos Consensus
    • Pharos Execution
      • Why A New Blockchain Compute Model
      • Pharos VM
    • Pharos Pipelining
    • Pharos Store
      • Why We Need a Blockchain-Native Store
    • Pharos SPNs
  • Network Overview
    • Pharos Networks
      • Pharos Testnet Information
    • Pharos Gas Model
    • FAQ
  • Node & Validator Guide
    • Validator Requirements
    • Validator Node Deployment
      • Using Docker (Devnet)
      • Using Docker (Testnet)
    • Node Management
    • Rapid Node Initialization
      • Rapid Node Initialization(Testnet)
      • Rapid Node Initialization(Devnet)
    • Pharos Network Snapshots
    • Node Debugging & Configuration
  • 🛠️ Pharos Testnet: Rebuild Node with Preserved Node Info
  • Pharos Node Monitoring
  • Developer Guide
    • Foundry
      • Write Your First dApp
      • Write Your First Token
      • Write Your First NFT
      • Write Your First Uniswap Contract
    • Hardhat
      • Write Your First dApp
      • Write Your First Token
      • Write Your First NFT
      • Write Your First Uniswap Contract
    • Rust
    • Interoperability
      • Call EVM From WASM
  • API & SDK
    • JSON-RPC API Methods
  • Resources
    • EVM
    • Solidity
Powered by GitBook
On this page
  • Pharos Store Architecture
  • Innovations 1: Authenticated Data Structure (ADS) Pushdown
  • Innovations 2: Version-Based Addressing
  • Innovations 3: Minimizing "State Bloat" through Internal Compactions, Page Storage, and Delta Encoding
  • Conclusion
Export as PDF
  1. Core Technologies

Pharos Store

The Future of Blockchain Storage

PreviousPharos PipeliningNextWhy We Need a Blockchain-Native Store

Last updated 25 days ago

Pharos Store Architecture

To address the limitations posed by state bloat, Pharos Store was developed as the first blockchain-native, verifiable storage solution, offering high-performance read/write capabilities and efficient merklization. Compared to traditional blockchain storage solutions, Pharos Store achieves up to 15.8× throughput and 80.3% storage cost savings [1].

Innovations 1: Authenticated Data Structure (ADS) Pushdown

Pharos Store integrates the Authenticated Data Structure (ADS) directly into the storage engine, eliminating the boundary between ADS and backend storage to enable fine-grained I/O optimization. This is achieved through three core components:

  • DMM-Tree (Delta-encoded Multi-version Merkle Tree): A built-in multi-version Merkle tree that supports dictionary trees, B-trees, and other tree structures.

  • LSVPS (Log-Structured Versioned Page Store): Provides a page index abstraction between memory and secondary storage for the DMM-Tree.

  • VDLS (Versioned Data Logging Stream): Stores user metadata in an append-only manner.

By integrating ADS with the storage engine, Pharos Store eliminates the Long I/O Path problem that plagues traditional two-layer architectures (e.g., Merkle Tree + KVDB), becoming the first Blockchain Native ADS Store.

Innovations 2: Version-Based Addressing

Pharos Store replaces hash-based addressing with version-based addressing, which eliminates the need for file compaction by ordering data according to version numbers.

Both logically and physically, each leaf node in a DMM-Trie records the block number corresponding to its child nodes, unlike hash-based addressing methods (e.g., MPT, IAVL, ZKTrie). DMM-Trie uses V (the most recent version) + NodeIndex to locate internal nodes and leaf nodes in sequence. Each node and page in the DMM-Trie retains V and the V of its children.

Innovations 3: Minimizing "State Bloat" through Internal Compactions, Page Storage, and Delta Encoding

To mitigate the impact of State Bloat, Pharos Store adopts the following techniques:

  1. Internal Compactions to reduce node path length.

  2. Persistent storage at the subtree level, where pages are used as the minimal persistence unit written to storage.

  3. Delta Encoding: Persists tree nodes using delta encoding, storing only modified data to reduce I/O and space amplification.

By employing these techniques, Pharos Store reduces ADS storage space and bandwidth consumption to less than 20% of traditional models.

Conclusion

As the first blockchain-native ADS storage solution, Pharos Store is compatible with MPT, JMT, and ZKTrie, significantly improving single-node performance, especially in large-scale data environments and complex contract scenarios. More detailed information will be released soon, and we welcome more teams and projects to join us!

In the article , we discuss the three main challenges facing blockchain storage today: Long I/O Paths, Hash-Based Addressing, and State Bloat. Pharos Store tackles these issues through several key design innovations:

Why We Need a Blockchain-Native Store
Figure 1: Pharos Store Architecture