merkl
A no_std + alloc sparse Merkle tree with a pluggable, namespaced key-value storage backend.
How it works
Each leaf is addressed by a key (a 32-byte hash). The key's bits, read MSB-first,
determine the path from root to leaf: bit 0 selects left (0) or right (1) at the root,
bit 1 at the next level, and so on. Internal nodes are stored in the backend keyed by
their own hash, holding a 64-byte serialised Node (left ‖ right child hashes).
The root lives outside the tree. MerkleTree holds no state beyond its backend and
hash-function marker. Every operation receives a root Hash and returns a new root —
making historical roots and independent sub-trees free.
root ──► Node{ left, right }
│ │
Node{…} leaf_hash ← terminal: no backend entry
│
leaf_hash ← terminal
An all-zero Hash (Hash::default()) is the canonical empty root.
Three ways to insert a leaf:
| Method | Key derivation | Use when |
|---|---|---|
insert(ns, root, data) |
H::hash(data) |
Natural content-addressing |
insert_indexed(ns, root, i, data) |
H::hash(i.to_le_bytes()) |
Array-like stable positions |
insert_keyed(ns, root, key, data) |
caller-supplied key | Complete control |
Feature flags
| Feature | Default | Description |
|---|---|---|
std |
yes | Enables std-backed errors and the sha2 crate's std feature. Disable for no_std targets. |
sha2 |
no | Enables Sha256Hasher and the Sha256MerkleTree<B> alias. |
redb |
no | Enables RedbBackend and RedbMerkleTree<H> backed by redb (requires std). |
fjall |
no | Enables FjallBackend backed by fjall (requires std). |
Quick start
Custom hasher, in-memory backend
use ;
;
let tree = new;
// Insert leaves — each call returns a new root without mutating the old one.
let root1 = tree.insert.unwrap;
let root2 = tree.insert.unwrap;
// Retrieve the stored leaf hash (key = H::hash(data) for plain insert).
let key_alice = hash;
assert_eq!;
// root1 is still valid and does not contain "bob".
let key_bob = hash;
assert_eq!;
// Insertion order does not affect the root.
let tree2 = new;
let r = tree2.insert.unwrap;
let root_ba = tree2.insert.unwrap;
assert_eq!;
SHA-256 hasher (sha2 feature)
[]
= { = "0.2", = ["sha2"] }
use ;
let tree = new;
let root =
.iter
.fold;
Index-keyed inserts
Useful for append-like structures where each element has a stable numeric position:
let root = tree.insert_indexed.unwrap;
let root = tree.insert_indexed.unwrap;
The key for index i is H::hash(i.to_le_bytes()), giving each index a
stable, uniformly-distributed position in the tree.
redb backend (redb feature)
[]
= { = "0.2", = ["redb", "sha2"] }
use ;
// Ephemeral in-memory database — no files created.
let backend = in_memory.unwrap;
let tree = new;
let root = tree.insert.unwrap;
For a persistent file-backed database:
let backend = create.unwrap;
Cloning a RedbBackend is cheap — all clones share the same underlying Database
via Arc (or Rc on targets without atomics).
Each set call opens, writes, and commits its own write transaction. For bulk
tree construction, wrapping a single redb::WriteTransaction in a custom backend
will give better throughput.
fjall backend (fjall feature)
[]
= { = "0.2", = ["fjall"] }
use FjallBackend;
let db = new.open.unwrap;
let backend = from;
Membership proofs
get_opening collects sibling hashes bottom-up. Verification is a pure hash
computation — it never touches the backend:
let proof = tree.get_opening.unwrap;
assert_eq!; // membership verified
// For indexed inserts:
let proof = tree.get_indexed_opening.unwrap;
assert_eq!;
Non-membership proofs
A sparse Merkle tree can also prove that a position is empty:
// "carol" was never inserted; the path leads to an empty slot.
let proof = tree.get_opening.unwrap;
assert_eq!; // non-membership verified
Traversal directions are derived from the key at verification time — never stored in the proof — so the proof cannot be forged by manipulating direction bits.
Implementing KvsBackend
The KvsBackend trait is the only integration point:
use KvsBackend;
use Result;
Key facts:
- All methods take
&self— use interior mutability (RefCell,Mutex, etc.) for the write path. nsis used by the tree to separate node storage (ns) from its internal key-mapping namespace ("{ns}-key"). Your backend only needs to use it as an extra scope for isolation.- Tree node keys are 32-byte parent hashes; values are 64-byte
Nodeencodings (left ‖ right).
For bare-metal targets, wrap your store in RefCell (single-core) or a
critical_section::Mutex (multi-core / interrupt-driven):
use RefCell;
use KvsBackend;
/// Fixed-capacity store backed by a statically allocated array.
/// Each slot: 4 bytes ns_len + ns bytes + 32-byte key + 64-byte value.
/// For simplicity this example uses a flat linear scan.
no_std usage
Disable the default std feature and ensure a global allocator is provided:
[]
= { = "0.2", = false }
The redb and fjall backend features always require std.
License
MIT — see LICENSE.