2.3 KiB
NIP-24
Extra metadata fields and tags
draft
optional
This NIP keeps track of extra optional fields that can added to events which are not defined anywhere else but have become de facto standards and other minor implementation possibilities that do not deserve their own NIP and do not have a place in other NIPs.
kind 0
These are extra fields not specified in NIP-01 that may be present in the tags of metadata events:
display_name
: an alternative, bigger name with richer characters thanname
.name
should always be set regardless of the presence ofdisplay_name
in the metadata.website
: a web URL related in any way to the event author.banner
: an URL to a wide (~1024x768) picture to be optionally displayed in the background of a profile screen.bot
: a stringified boolean of "true" or "false" (case insensitive) to clarify that the content is entirely or partially the result of automation, such as with chatbots or newsfeeds.
Deprecated fields
These are fields that should be ignored or removed when found in the wild:
displayName
: usedisplay_name
instead.username
: usename
instead.
The content
field has been used to store the stringified JSON of metadata fields. It has been deprecated in favor of using tags. Clients SHOULD write metadata as both tags and legacy stringified JSON until a reasonable number of SDKs and popular clients on each platform have adopted using tags on the user metadata event to avoid introducing breaking changes.
kind 3
These are extra fields not specified in NIP-02 that may be present in the stringified JSON of follow events:
Deprecated fields
{<relay-url>: {"read": <true|false>, "write": <true|false>}, ...}
: an object of relays used by a user to read/write. NIP-65 should be used instead.
tags
These tags may be present in multiple event kinds. Whenever a different meaning is not specified by some more specific NIP, they have the following meanings: