Crate file_mst 

File-Backed Merkle Search Tree (MST) Map

A high-performance, persistent, and authenticated Key-Value store implementation in Rust. This library combines the structural properties of Merkle Trees (cryptographic verification) with Search Trees (efficient lookups) and creates a flat-file storage engine capable of handling large datasets with efficient I/O.

Features

• Disk-Backed Persistence: Operates directly on a file-backed store with page-aligned writes (4KB).
• Cryptographic Verification: Every node maintains a cryptographic hash (blake3) of its contents (keys and values) and children, allowing for O(1) root hash retrieval.
• Efficient Caching: Implements an in-memory RwLock-guarded cache to minimize disk reads for frequently accessed nodes.
• Lazy Loading: Nodes are only loaded from disk when traversed. Pointers to children are stored as “Links” which can be either loaded in memory or pointing to a disk offset.
• Probabilistic Balancing: Uses the Merkle Search Tree algorithm (hashing keys to determine levels) to maintain balance without complex rotation logic.
• Serialization: efficient binary serialization using postcard.

Usage

1. Basic In-Memory Operation

For temporary usage (e.g., testing or transient cache), you can create a tree backed by a temporary file that is deleted upon drop.

use file_mst::{MerkleSearchTree, MerkleKey};
use std::borrow::Cow;
use serde::{Serialize, Deserialize};

fn main() -> std::io::Result<()> {
    // 2. Create a temporary tree (Key: String, Value: i32)
    let mut tree: MerkleSearchTree<String, i32> = MerkleSearchTree::new_temporary()?;

    // 3. Insert data (Key, Value)
    tree.insert("Alice".to_string(), 100)?;
    tree.insert("Bob".to_string(), 200)?;

    // 4. Query data
    if tree.contains(&"Alice".to_string())? {
        println!("Alice exists!");
    }

    // Retrieve value
    match tree.get(&"Bob".to_string())? {
        Some(val) => println!("Bob's value is: {}", val),
        None => println!("Bob not found"),
    }
    
    // 5. Get Root Hash
    println!("Root Hash: {:?}", tree.root_hash());

    Ok(())
}

2. Persistent Storage

To persist data between runs, use open and flush.

use file_mst::MerkleSearchTree;
use std::path::Path;

fn run_persistence() -> std::io::Result<()> {
    let path = Path::new("./db.mst");
    
    // Open (or create) the file. We use String keys and String values here.
    let mut tree: MerkleSearchTree<String, String> = MerkleSearchTree::open(path)?;
    
    tree.insert("config_key".to_string(), "production_v1".to_string())?;

    // Flush to disk. This returns the Offset and Hash of the new root.
    // You must save these (e.g., in a separate metadata file) to reload the tree later.
    let (root_offset, root_hash) = tree.flush()?;
    
    println!("Saved root at offset {} with hash {:?}", root_offset, root_hash);
    
    Ok(())
}

3. Loading from a Previous State

To load a tree, you need the filepath, the root offset, and the root hash returned by the last flush().

use file_mst::MerkleSearchTree;

fn load_db(offset: u64, hash: [u8; 32]) -> std::io::Result<()> {
    let tree: MerkleSearchTree<String, String> = MerkleSearchTree::load_from_root("./db.mst", offset, hash)?;
    
    // Retrieve value from loaded tree
    if let Some(val) = tree.get(&"config_key".to_string())? {
        println!("Config value found: {}", val);
    }
    
    Ok(())
}

Architecture

The Store

The Store manages a BufWriter<File> and a HashMap cache.

• Writing: Nodes are serialized via postcard and written to the end of the file. Writes are padded to ensure alignment with 4KB pages where possible to optimize OS-level paging.
• Reading: When a Link::Disk is accessed, the store seeks to the offset, reads the length header, and deserializes the node.

The Node

Nodes contain:

• Level: Determined by the hash of the keys (probabilistic).
• Keys: A sorted vector of user keys.
• Values: A parallel vector of user values.
• Children: A vector of Link enums (either Loaded(Arc<Node>) or Disk { offset, hash }).
• Hash: A blake3 hash covering the node’s level, keys, values, and children hashes.

Deterministic Levels

The tree uses a deterministic algorithm to calculate node levels based on the key’s hash. This ensures that regardless of insertion order, the resulting tree structure and root hash remain identical for the same set of keys and values.

Benchmarks

The project includes a suite of benchmarks using the test nightly feature.

To run benchmarks:

cargo bench

Testing

The library includes comprehensive tests covering:

• Basic CRUD (Create, Read, Update, Delete).
• Idempotency (inserting duplicates).
• Value Updates (changing value for existing key).
• Persistence (save/load cycles).
• Fuzzing/Interleaved operations (randomized insert/delete sequences).

To run tests:

cargo test

Reference

This implementation is based on the data structure described in:

Alex Auvolat, François Taïani. Merkle Search Trees: Efficient State-Based CRDTs in Open Networks. SRDS 2019 - 38th IEEE International Symposium on Reliable Distributed Systems, Oct 2019, Lyon, France. pp.1-10, 10.1109/SRDS.2019.00032. hal-02303490

Structs

MerkleSearchTree

Traits

MerkleKey

A trait for types that can serve as keys in a Merkle Search Tree.

MerkleValue

A trait for types that can serve as values. They must be cloneable and serializable.

Type Aliases

Hash