Proposal: New Nostr Kind-0 Metadata Fields
Please share this note for more peer review.
I've drafted a proposal to add three new optional fields to kind-0 user metadata: status, partner, and kin.
— status (integer 0-7): relationship status, from single to married to open relationship. Integer-based for localization across all languages.
— partner (hex pubkey array): link your partner(s) to your profile. First entry is primary.
— kin (tuple array): family connections with optional relationship types — parent, sibling, child, cousin, in-law, and more.
All fields are optional, public, and use hex pubkeys natively. Clients that don't support them simply ignore them. The spec includes relay size analysis, a privacy section, and a comparison to NIP-81 (Contact Cards).
Full proposal: 
GitHub Discussion: 
Feedback welcome. Looking for input from client devs and protocol contributors before drafting a formal NIP.
GitHub
proposals/nostr-kind0-metadata at main · dankswoops/proposals
Protocol and specification proposals for Nostr and the open web. - dankswoops/proposals
GitHub
Proposal: Three new kind-0 metadata fields — status, partner, kin · Issue #2202 · nostr-protocol/nips
I'd like to propose three new optional fields for kind-0 user metadata: status, partner, and kin. status (integer, 0-7) — A standardized relation...