All specifications
Page 5 of 20

Web of Trust
My attempt to add Nostr authentication to #bitcoin-otc web of trust, making it so nostriches can authenticate into a legacy web of trust/orderbook on Libera...
covers30078P2P order book30017Merchant Stalls30018Merchant Stalls1985Trust Ratings30382WoT Assertions
RFP/RFC: Turning a Nostr Nsec Into a Hardened Non-Taproot Address... for on-chain zaps & CRQC resistance
Preface: I put the kinds Gemini suggested, but maybe need to define a new kind, as IIRC Vitor had criticized Kind 0 bloat.
covers0profile metadata for bitcoin9734Zap Request9735Zap Receipt30017marketplace orders
RFP/RFC: Turning a Nostr Nsec Into a Hardened Non-Taproot Address... for on-chain zaps & CRQC resistance
Preface: I put the kinds Gemini suggested, but maybe need to define a new kind, as IIRC Vitor had criticized Kind 0 bloat.
covers0profile metadata for bitcoin9734Zap Request9735Zap Receipt30017marketplace orders
NIP-54
This NIP defines kind:30818 (an addressable event) for descriptions (or encyclopedia entries) of particular subjects, and it's expected that multiple people...
covers30818threads30819redirects818merge request819merge acceptanceIssue #2330: N0..N3 Namecoin RFC track
This issue is a recreation, on this mirror, of the broader N0..N3 RFC track originally filed upstream at nostr-protocol/nips#2330. The companion PR on this...
PR #2337: NIP-11 nip9b pointer (companion to NIP-9B)
Adds an optional "nip9b": "34551::" field to the NIP-11 Relay Information Document, as the machine-readable companion to the existing termsofservice...
PR #2331: NIP-9B Verifiable Community Rules
Adds a new NIP defining kind:34551 — a machine-readable, signed rules document for communities. Clients fetch this event before drafting a post, locally...
covers3455034551PR #2349: NIP-05 verification via Namecoin (.bit)
Adds a new NIP specifying how clients verify, and publishers publish, a NIP-05 identifier whose right-hand side is anchored in the Namecoin blockchain rather...
covers0
NIP-44: Encrypted Payloads (Versioned)
The versioned encryption format the rest of Nostr builds on: secp256k1 ECDH, HKDF, padding, ChaCha20 and HMAC-SHA256.
#nostr#nip
Custom Constellations
This NIP defines a user-drawn constellation in the stars.
covers30621Custom Constellation
Profile Themes
This NIP defines custom profile themes as seen in Ditto. It includes shareable theme events (kind 36767) as well as the user's current profile theme (kind...
covers16767Active Profile Theme36767Shareable Profile Theme
Bird Detection & Birdex
This NIP describes birding events on Nostr.
covers2473Bird Detection12473Birdex
NIP-BC: Onchain Zaps
A Nostr pubkey is also a Bitcoin Taproot address: both are 32-byte x-only secp256k1 keys, so any Nostr user can receive Bitcoin directly to their Nostr...
covers8333Onchain Zap
NUT-14: Hashed Timelock Contracts (HTLCs)
Ecash locked to the hash of a preimage and a deadline, which makes atomic swaps between users possible.
optional#cashu#ecash#nut
NUT-28: Pay to Blinded Key (P2BK)
Blinding the receiver's public key on each payment, so the mint cannot link several of them to the same person.
optional#cashu#ecash#nut
[NIP-5D] Nostr Web Applets (napplets)
This NIP defines a web projection for sandboxed web applications ("napplets") running in iframes to communicate with a hosting application ("shell"). Shells...
covers5129napplet snapshot15129root napplet35129named napplet
Unlock the Benefits of Using Invoice Templates for Your Business
Invoice templates streamline billing, reduce errors, save time, and enhance professionalism for your business.

Slash Commands
A slash command manifest is a kind 33318 which defines a command. Its name tag is the name of the command.
covers33318Slash Command Manifest
NIP-7D
A thread is a kind 11 event. Threads SHOULD include a title.
covers11threads1111comments
NUT-24: HTTP 402 Payment Required
How an HTTP server demands payment with a 402 response carrying a Cashu payment request.
optional#cashu#ecash#nut