#git #leveldb #rocksdb #version #vcs


A stuctured DB with some 'Git-like' features, mainly used in blockchain projects

34 releases (15 breaking)

0.61.1 Oct 10, 2023
0.61.0 Jul 21, 2023
0.60.1 Jun 22, 2023
0.54.0 Mar 27, 2023
0.45.1 Jun 24, 2022

#288 in Database implementations

Download history 103/week @ 2023-07-31 149/week @ 2023-08-07 138/week @ 2023-08-14 71/week @ 2023-08-21 94/week @ 2023-08-28 101/week @ 2023-09-04 90/week @ 2023-09-11 116/week @ 2023-09-18 89/week @ 2023-09-25 60/week @ 2023-10-02 121/week @ 2023-10-09 69/week @ 2023-10-16 87/week @ 2023-10-23 90/week @ 2023-10-30 104/week @ 2023-11-06 45/week @ 2023-11-13

335 downloads per month
Used in 9 crates (via vsdb)

GPL-3.0 license


Latest Version Rust Documentation Minimum rustc version


The core implementations of vsdb.

Design Principles

Based on the underlying one-dimensional linear storage structure (native kv-database, such as rocksdb, etc.), multiple different namespaces are divided, and then abstract each dimension in the multi-dimensional logical structure based on these divided namespaces.

In the category of kv-database, namespaces can be expressed as different key ranges, or different key prefix.

This is the same as expressing complex data structures in computer memory(the memory itself is just a one-dimensional linear structure).

User data will be divided into two dimensions: 'branch' and 'version', the functions of the 'basic' category are stateless, and the functions of the 'versioned' category are stateful. In the internal implementation, each stateful function is implemented based on its corresponding stateless function, all stateful data has two additional identification dimensions ('branch' and 'version'), somewhat like the logic in Git. Stateless functions do not have the feature of 'version' management, but they have higher performance.


  • MIT for v0.40 and earlier
  • GPL-3.0 for v0.41 and later


~147K SLoC