crypto-database
The database that can prove it never lied.
One version across npm · PyPI · crates.io — every release ships aligned.
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_bylinks every record to the facts that produced it;TRACEwalks the graph. Audit why, not just what. - 🔐 Encrypted at rest (AES-256-GCM), RESP2 wire protocol, SQL / Redis / Mongo adapters, a
nedbd-v2server 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-databasewas already taken on PyPI by an unrelated project, so the Python distribution keeps the originalcryptodbname there. npm and crates.io publish ascrypto-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.
1 maintainer
Metadata
1 maintainer
Release files for cryptodb 11.12.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cryptodb-11.12.14.tar.gz | 88.1 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryptodb-11.12.14-py3-none-any.whl | Python 3 | none | any | Details |
| cryptodb-11.12.14-cp38-abi3-macosx_11_0_arm64.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64 | Details |
| cryptodb-11.12.14-cp38-abi3-macosx_10_12_x86_64.whl | CPython 3.8 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 3.1 MB
Release files / cryptodb-11.12.14.tar.gz
| Download URL | cryptodb-11.12.14.tar.gz |
|---|---|
| Size | 88.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eba12b75a165b1d930676b0221a889bd202f77b166c51d92664b14e52b3e8c5c
|
|
BLAKE2b-256 checksum How to use checksums |
951ec409ae472b303988162c92828f2c001833ba5789e6c8bc371c8a14d6d817
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / cryptodb-11.12.14-py3-none-any.whl
| Download URL | cryptodb-11.12.14-py3-none-any.whl |
|---|---|
| Size | 96.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c5101bcb5aea91e6b2fb06831d247003a0e20ce9673e9c860c1dfb56a209805
|
|
BLAKE2b-256 checksum How to use checksums |
8aac344864b57c6578a22b261feb179d51f71170379ed3f40a3cd0a16ae7598e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / cryptodb-11.12.14-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | cryptodb-11.12.14-cp38-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.8 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b920cc02d1e7276e78c5f0424e80b029a9fcfcefa08b92ffaef9d95bf0f17cc2
|
|
BLAKE2b-256 checksum How to use checksums |
957c9b70ec96ad57f52fd32d85f2924b58d62e6199ec2d16f89debb4070b0cce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Release files / cryptodb-11.12.14-cp38-abi3-macosx_10_12_x86_64.whl
| Download URL | cryptodb-11.12.14-cp38-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.8 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
86289efd565d6b26473ac669b75376d84469b7ee1da9fb029f3f5c38518afc7f
|
|
BLAKE2b-256 checksum How to use checksums |
58f490266b2682bfa387e58f1bf0d888b36309007ff756fa5f292be1d284ded2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
