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 7.2.0
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-7.2.0.tar.gz | 88.1 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryptodb-7.2.0-py3-none-any.whl | Python 3 | none | any | Details |
| cryptodb-7.2.0-cp38-abi3-macosx_11_0_arm64.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64 | Details |
| cryptodb-7.2.0-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-7.2.0.tar.gz
| Download URL | cryptodb-7.2.0.tar.gz |
|---|---|
| Size | 88.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a692d90c3ccd48b05ac1f97f9d90a21f7a0401caa3e25145071906edbb6eb15f
|
|
BLAKE2b-256 checksum How to use checksums |
4fc142b1f9337893ed79c06749fee492fdc095856ee9ac9a6cffba75fc854e27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / cryptodb-7.2.0-py3-none-any.whl
| Download URL | cryptodb-7.2.0-py3-none-any.whl |
|---|---|
| Size | 95.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e83ce628f37d3f2c4d59dc9b0b3c6c36bb04ee5cff1a7bc897bae94cdecfa236
|
|
BLAKE2b-256 checksum How to use checksums |
de8359e73769fabc255f82a447db55906e92dc203460ab18749ce04806fee15e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / cryptodb-7.2.0-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | cryptodb-7.2.0-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 |
b9c23fdc44f59e69b6af11da239afe8f2e6decdb36caa78b99b95ddd08a7f474
|
|
BLAKE2b-256 checksum How to use checksums |
023b4f65b9d55de2b9889df423116c3b08042c383d3a7892a42561b52c929ab6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Release files / cryptodb-7.2.0-cp38-abi3-macosx_10_12_x86_64.whl
| Download URL | cryptodb-7.2.0-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 |
aa54106642d9a3295519ce08312db68021c405ae74cab6f1f5a14b79abeda2cc
|
|
BLAKE2b-256 checksum How to use checksums |
6b8df46f2d9d8f68af4c555ef14ad8645db9bf97fb0fe08924aff30517736fd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
