Specifications covering kind 0

NoorNote
NoorNote is a privacy-first Nostr client for desktop (macOS/Linux), Android and web. This is its public capability profile: the Nostr event kinds it can create and/or render. Directories and other clients can read the k-tags below to discover that NoorNote supports a given kind.
covers0Profile Metadata1Short Text Note3Follow List4Encrypted DM (legacy)5Event Deletion6Repost+52 more
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 ordersPR #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-01: Basic protocol flow description
The core protocol: the event object, how its id and signature are computed, what makes a kind regular, replaceable or addressable, and the messages clients and relays exchange.
draftcovers0User Metadata#nostr#nip
Profile Colors
A standard for deriving deterministic, readable colors from Nostr pubkeys. This ensures consistent visual identity across all clients.
covers0
Default picture
This NIP standardizes a deterministic method for deriving avatar from a user's pubkey. This ensures consistent visual identity across all Nostr clients.
covers0
Fallback Display Name
When a user has no name or display_name in their kind 0 metadata, clients SHOULD display:
covers0