crypto-database

The database that can prove it never lied.

crypto-database is a content-addressed, hash-chained, time-traveling datastore. Every version of every record is an immutable, BLAKE2b-verified object in a Merkle DAG — nothing is ever overwritten, and the store can prove its own integrity on demand.

If your data is evidence — ledgers, audit trails, provenance, anything you may one day have to defend — crypto-database makes the history itself tamper-evident and replayable.

Why crypto-database

🔒 Tamper-evident by construction. verify() re-hashes every object against its content address. Flip a single byte on disk and it's caught — silently impossible to forge history.
⏪ Time-travel is a query. AS OF <seq> returns the exact state at any point. VALID AS OF <time> adds bi-temporal validity — what was true, as of when.
🧬 Causal provenance. caused_by links every record to the facts that produced it; TRACE walks the graph. Audit why, not just what.
🔐 Encrypted at rest (AES-256-GCM), RESP2 wire protocol, SQL / Redis / Mongo adapters, a nedbd-v2 server daemon.

Install

npm install crypto-database   # Node (native addon)
pip install cryptodb          # Python  ← note the PyPI name
cargo add crypto-database     # Rust

Why the split name? crypto-database was already taken on PyPI by an unrelated project, so the Python distribution keeps the original cryptodb name there. npm and crates.io publish as crypto-database. Same engine, same version, same code — only the registry labels differ.

Reach for it when

Audit logs · financial & token ledgers · compliance trails · supply-chain provenance · anything where provable, replayable history is the product, not a nice-to-have.

import { NedbCore } from "crypto-database";
const db = new NedbCore();
db.put("ledger", "acct:alice", JSON.stringify({ balance: 100 }));
db.put("ledger", "acct:alice", JSON.stringify({ balance: 250 }));
db.getAsOf("ledger", "acct:alice", 0n);   // → balance 100, the past, intact
db.verify();                               // → true: nothing was tampered

_{crypto-database (previously CryptoDB) is a distribution of the NEDB engine, tuned for verifiability. Engine development happens upstream at Eth-Interchained/nedb. © Interchained LLC.}

Metadata

Release files for cryptodb 2.8.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cryptodb 2.8.3
File	Size	Uploaded
cryptodb-2.8.3.tar.gz	83.6 kB	Sep 4, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for cryptodb 2.8.3
File	Interpreter	ABI	Platform	Reset
cryptodb-2.8.3-py3-none-any.whl 88.1 kB Sep 4, 2026	Python 3	none	any	Details

Total release size: 171.6 kB

Release files / cryptodb-2.8.3.tar.gz

Download URL	cryptodb-2.8.3.tar.gz
Size	83.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`f8ec23a90d81b25b542606ddfadef72bb488aebb0c40308fe07d1277bcac7e77`
BLAKE2b-256 checksum How to use checksums	`b5c2e9404edde36ec56d7841535fab2f447c34010755c8b8646d92d4ceab78ea`
Upload date	Sep 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.11.16`

Release files / cryptodb-2.8.3-py3-none-any.whl

Download URL	cryptodb-2.8.3-py3-none-any.whl
Size	88.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`178831f24a8e126d5efe8cfe798b3123d7c2f9d2d370b8695190b94248ef568b`
BLAKE2b-256 checksum How to use checksums	`0308d7c3c7c1927975cf541643ce1ba8bbd848607101633f43adb530b04cd27b`
Upload date	Sep 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.11.16`