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_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.
Metadata
Release files for cryptodb 3.0.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-3.0.0.tar.gz | 81.7 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryptodb-3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
| cryptodb-3.0.0-cp38-abi3-macosx_11_0_arm64.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64 | Details |
| cryptodb-3.0.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-3.0.0.tar.gz
| Download URL | cryptodb-3.0.0.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
764afca2d659edf1ee4e9cacb28e6c3f1051a4929b89d6014052969ecc061f29
|
|
BLAKE2b-256 checksum How to use checksums |
b978836c65e5457c0572b7fdb4fd1fae3b5ff5d24f90c183d2fb51effce3b592
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / cryptodb-3.0.0-py3-none-any.whl
| Download URL | cryptodb-3.0.0-py3-none-any.whl |
|---|---|
| Size | 86.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c8b253e1f304cabec7d53556bc1c3740e311d2d51fcd5af3fab0a68001cd329b
|
|
BLAKE2b-256 checksum How to use checksums |
9290503b82fab348c248eccee7726af599078b3998bf09fe56a54d4325c0e8cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / cryptodb-3.0.0-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | cryptodb-3.0.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 |
4c5408b03d5af0003248b9a90498bb02106c9eef4e1aa5fafd3f98307c92d5c7
|
|
BLAKE2b-256 checksum How to use checksums |
31822d289737a5c5054ba561217638ae41b36c444506dfeabc7d25af7be66989
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Release files / cryptodb-3.0.0-cp38-abi3-macosx_10_12_x86_64.whl
| Download URL | cryptodb-3.0.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 |
353d2ea32b67418cfb2218a5ed1f5590507db35114a0e839ae48c2581d69a128
|
|
BLAKE2b-256 checksum How to use checksums |
6e1d206e8620cc2abf2ffc5ca563f97b111d9c47d9d9059070e76d2c6d547c8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|