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.
Metadata
Release files for cryptodb 15.15.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cryptodb-15.15.15.tar.gz | 88.1 kB | Without provenance | Details for cryptodb-15.15.15.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cryptodb-15.15.15-py3-none-any.whl | Python 3 | none | any | Details for cryptodb-15.15.15-py3-none-any.whl |
| cryptodb-15.15.15-cp38-abi3-macosx_11_0_arm64.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64 | Details for cryptodb-15.15.15-cp38-abi3-macosx_11_0_arm64.whl |
| cryptodb-15.15.15-cp38-abi3-macosx_10_12_x86_64.whl | CPython 3.8 | abi3 | macOS 10.12+ x86-64 | Details for cryptodb-15.15.15-cp38-abi3-macosx_10_12_x86_64.whl |
Total release size: 3.1 MB
Release files / cryptodb-15.15.15.tar.gz
| Download URL | cryptodb-15.15.15.tar.gz |
|---|---|
| Size | 88.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e54f7da690e3fcc1956d6d4bdb39e84d22fbc1680ea853feacfe5a753da26b78
|
|
BLAKE2b-256 checksum How to use checksums |
a369380f19ff1e25018d8cacd0fba6fe8e930bc66dc92ae56a0677baf2654e35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / cryptodb-15.15.15-py3-none-any.whl
| Download URL | cryptodb-15.15.15-py3-none-any.whl |
|---|---|
| Size | 96.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d178d5b533528afadb196a81ab1b1cf5aa9b2533d0c0c804480e8c1d367b500
|
|
BLAKE2b-256 checksum How to use checksums |
2a0ffd2307ebb00535c9ab34f8a76cd34263ce378d8638dd35cfd8ceffc8051e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / cryptodb-15.15.15-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | cryptodb-15.15.15-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 |
c03a4075fe8064e933298d2e959d18c965fde0afb4e5937ba70df190a265b02a
|
|
BLAKE2b-256 checksum How to use checksums |
db9e4885033a18cf11e63f3b4496e6dca040e3786712a91bcd9dceecb695467f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Release files / cryptodb-15.15.15-cp38-abi3-macosx_10_12_x86_64.whl
| Download URL | cryptodb-15.15.15-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 |
016fa26b120fb7567465d66821e1904da1ed5080c56eb937f3dbf3326fb1877c
|
|
BLAKE2b-256 checksum How to use checksums |
4881d6fd49d6f191110f6e31afa44e5338884990d3ffc02756eaf644485d48ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Security for cryptodb 15.15.15
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.