cryptodb 2.4.3__tar.gz → 2.4.68__tar.gz

{cryptodb-2.4.3 → cryptodb-2.4.68}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: cryptodb
-Version: 2.4.3
+Version: 2.4.68
 Summary: NEDB — a versioned, self-compressing, time-traveling embedded database (replay-protected, idempotent, relational, searchable) with durable AOF persistence and a server daemon (nedbd).
 Project-URL: Homepage, https://github.com/aiassistsecure/nedb
 Project-URL: Repository, https://github.com/aiassistsecure/nedb
 Author: Eth-Interchained
 License: GPL-3.0-or-later
 License-File: LICENSE
-Keywords: compression,database,dedup,embedded,git,graph,mvcc,persistence,redis,search,server,time-travel,versioning
+Keywords: compression,crypto-database,cryptodb,database,dedup,embedded,git,graph,mvcc,persistence,redis,search,server,time-travel,versioning
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
@@ -19,16 +19,16 @@ Provides-Extra: encryption
 Requires-Dist: cryptography>=41; extra == 'encryption'
 Description-Content-Type: text/markdown
 
-<h1 align="center">CryptoDB</h1>
+<h1 align="center">crypto-database</h1>
 <p align="center"><b>The database that can prove it never lied.</b></p>
 
 ---
 
-CryptoDB 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.
+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* — CryptoDB makes the history itself tamper-evident and replayable.
+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 CryptoDB
+## 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.*
@@ -38,17 +38,19 @@ If your data is evidence — ledgers, audit trails, provenance, anything you may
 ## Install
 
 ```bash
-npm install cryptodb        # Node (native addon)
-pip install cryptodb        # Python
-cargo add cryptodb          # Rust
+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-database` was already taken on PyPI by an unrelated project, so the Python distribution keeps the original `cryptodb` name there. npm and crates.io publish as `crypto-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.
 
 ```js
-import { NedbCore } from "cryptodb";
+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 }));
@@ -58,4 +60,4 @@ db.verify();                               // → true: nothing was tampered
 
 ---
 
-<sub>CryptoDB is a distribution of the **NEDB** engine, tuned for verifiability. Engine development happens upstream at [Eth-Interchained/nedb](https://github.com/Eth-Interchained/nedb). © Interchained LLC.</sub>
+<sub>crypto-database (previously `CryptoDB`) is a distribution of the **NEDB** engine, tuned for verifiability. Engine development happens upstream at [Eth-Interchained/nedb](https://github.com/Eth-Interchained/nedb). © Interchained LLC.</sub>

{cryptodb-2.4.3 → cryptodb-2.4.68}/README.md

@@ -1,13 +1,13 @@
-<h1 align="center">CryptoDB</h1>
+<h1 align="center">crypto-database</h1>
 <p align="center"><b>The database that can prove it never lied.</b></p>
 
 ---
 
-CryptoDB 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.
+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* — CryptoDB makes the history itself tamper-evident and replayable.
+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 CryptoDB
+## 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.*
@@ -17,17 +17,19 @@ If your data is evidence — ledgers, audit trails, provenance, anything you may
 ## Install
 
 ```bash
-npm install cryptodb        # Node (native addon)
-pip install cryptodb        # Python
-cargo add cryptodb          # Rust
+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-database` was already taken on PyPI by an unrelated project, so the Python distribution keeps the original `cryptodb` name there. npm and crates.io publish as `crypto-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.
 
 ```js
-import { NedbCore } from "cryptodb";
+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 }));
@@ -37,4 +39,4 @@ db.verify();                               // → true: nothing was tampered
 
 ---
 
-<sub>CryptoDB is a distribution of the **NEDB** engine, tuned for verifiability. Engine development happens upstream at [Eth-Interchained/nedb](https://github.com/Eth-Interchained/nedb). © Interchained LLC.</sub>
+<sub>crypto-database (previously `CryptoDB`) is a distribution of the **NEDB** engine, tuned for verifiability. Engine development happens upstream at [Eth-Interchained/nedb](https://github.com/Eth-Interchained/nedb). © Interchained LLC.</sub>

{cryptodb-2.4.3 → cryptodb-2.4.68}/pyproject.toml

@@ -4,20 +4,26 @@
 # Rust core (rust/) remains for the napi (npm) addon and future native PyPI
 # acceleration, reintroduced additively; `nedb._native` already imports lazily
 # and the package works identically without it.
+#
+# NOTE: the PyPI distribution name stays `cryptodb` because `crypto-database` is
+# already taken on PyPI by an unrelated third-party project. The npm and crates.io
+# distributions publish as `crypto-database`; PyPI stays `cryptodb`. Same engine,
+# same version, same code — split registry identity by necessity.
 [build-system]
 requires = ["hatchling"]
 build-backend = "hatchling.build"
 
 [project]
 name = "cryptodb"
-version = "2.4.3"
+version = "2.4.68"
 description = "NEDB — a versioned, self-compressing, time-traveling embedded database (replay-protected, idempotent, relational, searchable) with durable AOF persistence and a server daemon (nedbd)."
 readme = "README.md"
 requires-python = ">=3.8"
 license = { text = "GPL-3.0-or-later" }
 authors = [{ name = "Eth-Interchained" }]
 keywords = ["database", "embedded", "mvcc", "time-travel", "versioning",
-            "compression", "dedup", "graph", "search", "redis", "git", "persistence", "server"]
+            "compression", "dedup", "graph", "search", "redis", "git", "persistence", "server",
+            "cryptodb", "crypto-database"]
 classifiers = [
     "Development Status :: 3 - Alpha",
     "Intended Audience :: Developers",

{cryptodb-2.4.3 → cryptodb-2.4.68}/python/nedb/__init__.py

@@ -89,4 +89,4 @@ __all__ = [
     "verify_proof", "fold_head",
     "_native", "__has_native__",
 ]
-__version__ = "2.4.3"
+__version__ = "2.4.68"