NIP Support
Nostr is defined by its NIPs — Nostr
Implementation Possibilities. Here’s where zig-nostr stands. Every “done” NIP
is covered by tests, and the cryptographic ones are verified against their
official specification vectors.
| NIP | Title | Status |
|---|---|---|
| 01 | Basic protocol: events, signatures, subscriptions | ✅ done |
| 06 | Key derivation from mnemonic seed | ✅ done |
| 09 | Event deletion (ingestion) | ✅ done |
| 19 | bech32-encoded entities | ✅ done |
| 21 | nostr: URI scheme | ✅ done |
| 42 | Client-to-relay authentication | ✅ done |
| 44 | Encrypted payloads (v2) | ✅ done |
| 46 | Nostr Connect — remote signing | ✅ done |
| 49 | Private key encryption (ncryptsec) | ✅ done |
| 65 | Relay list metadata (outbox) | ✅ done |
| 17 | Private direct messages | 🚧 planned (A6) |
| 59 | Gift wrap | 🚧 planned (A6) |
| 10 | Reply threading | 🚧 planned (A7) |
The planned NIPs land with the showcase apps — a NIP-17 private messenger (A6) and a read-only outbox client (A7).
Last updated on