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.
1 maintainer
Metadata
1 maintainer
Release files for cryptodb 3.3.1
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.3.1.tar.gz | 81.7 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryptodb-3.3.1-py3-none-any.whl | Python 3 | none | any | Details |
| cryptodb-3.3.1-cp38-abi3-macosx_11_0_arm64.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64 | Details |
| cryptodb-3.3.1-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.3.1.tar.gz
| Download URL | cryptodb-3.3.1.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5d0b2ae124a24e789a988215a47cbddb70d3fb2d424d75d2846f948d42695ae
|
|
BLAKE2b-256 checksum How to use checksums |
5d2940cace0a0bb1595a530332f9caaff026358315e025f8307b5d52e4ab53af
|
| 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.3.1-py3-none-any.whl
| Download URL | cryptodb-3.3.1-py3-none-any.whl |
|---|---|
| Size | 86.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
adaa67f9fe68ea919a89297b9681c6d983c81891bc058267210134c73863ff81
|
|
BLAKE2b-256 checksum How to use checksums |
eab6d18e3b4a5c41c276bb4e01694efd71ba58908a188f7b73030c2680f42701
|
| 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.3.1-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | cryptodb-3.3.1-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 |
2db8aeee119e0001cc4677055adf0258bd134f32be6c7a20040a380307242fb5
|
|
BLAKE2b-256 checksum How to use checksums |
f00255dded26ef612d47748224db893e3fbbdb35c888a5dd9de42c4690e64cf0
|
| 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.3.1-cp38-abi3-macosx_10_12_x86_64.whl
| Download URL | cryptodb-3.3.1-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 |
9d4d3d2fa59ac613b19533d8fd4e488ef8207020fafee2e78a7789b0d148759a
|
|
BLAKE2b-256 checksum How to use checksums |
ec68b2c0494a17041ea7abf5ab0f429877c2669e4df25c43a0475a1b41f8771d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
