GHOST's avatar
GHOST
ghost@nostrplebs.com
npub18dlu...h8x3
Operational privacy for real people.
I took a HP T630 Thin Client I picked up used for $30 and turned it into a #tor only WiFi access network device. A RT5370 usb antenna dongle gives me decent WiFi coverage. Will do a how to guide on the ZeroSentinel Shadow in a week or so. Tested on a iPhone for compatibility. image
Cold Root Identity update The spec and reference implementations just hit a stable point. • v0.1.0-vectors is published • Python, Go, and JS all reproduce the same deterministic test vectors • HKDF parameters, epoch labels, and lineage format are now frozen • CI verifies every implementation against the canonical vector set Everything you need to experiment with rotation is now stable. If you’re a client developer, the full spec and examples are here:
Cold Root Identity update The spec and reference implementations are at a stable point. - v0.1.0-vectors is published - Python, Go, and JS all reproduce the same deterministic test vectors - HKDF parameters, epoch labels, and lineage format are now frozen - CI verifies every implementation against the canonical vector set Everything you need to experiment with rotation is now stable. If you’re a client developer, the full spec and examples are here:
Cold Root Identity update The spec and reference implementations are at a stable point. - v0.1.0-vectors is published - Python, Go, and JS all reproduce the same deterministic test vectors - HKDF parameters, epoch labels, and lineage format are now frozen - CI verifies every implementation against the canonical vector set Everything you need to experiment with rotation is now stable. If you’re a client developer, the full spec and examples are here:
Cold Root Identity milestone Python and Go now produce identical deterministic vectors for derivation and lineage. The model is stable. Canonical test vectors are frozen in: tests/vectors/cold_root_identity.v1.json CRI requires no protocol changes. Clients just follow standard kind 30001 lineage events signed by an offline root. Repo and spec: If you maintain a client or SDK, you can now test against the vectors and confirm compatibility.
Cold Root Identity v0.1.0 Cold Root Identity is a simple model for survivable Nostr identities. No protocol changes, no new relay behavior, and no delegation logic. The idea is straightforward: - A root key stays offline as the authority - Epoch keys are derived deterministically for actual daily use - A signed lineage event proves each new epoch key is legitimate - Clients treat the newest valid epoch as the user’s active identity - Old posts stay under old keys; new posts use the fresh one This gives users safe key rotation without burning their entire account. A compromise only affects a single window instead of the whole identity. The Python reference implementation, test vectors, and spec are here: If you’re a client dev, this is everything needed to implement rotation cleanly today.
Cold Root Identity v0.1.0 is live. Nostr was never meant to run long term identities off a hot private key sitting inside a mobile app. This repo ships a clean model that fixes it without changing the protocol: offline root key -> deterministic epoch keys -> signed lineage event -> clients follow rotations safely All using standard NIP-01 events and ed25519 signatures. No relay changes. No NIP changes. Just better key hygiene. Spec, docs, test vectors, and a working Python CLI are here: If you’re a client dev, this gives you everything you need to support safe identity rotation today.