All specifications
Page 11 of 20

BUD-07: Paid upload and download
How a server charges for an endpoint: a 402 response carrying the payment terms, for uploads, downloads or media processing.
draft#blossom#bud
BUD-06: Upload requirements
Defines HEAD /upload, a preflight request telling a client whether an upload would be accepted before it sends the bytes.
draft#blossom#bud
BUD-02: Blob upload
Defines PUT /upload and the blob descriptor, the JSON object describing a stored blob: its url, hash, size, mime type and upload time.
draft#blossom#bud
Fallback Display Name
When a user has no name or display_name in their kind 0 metadata, clients SHOULD display:
covers0
Software Applications
This NIP defines kind 32267 to describe a software application, kind 30063 for a software release and kind 3063 for a software asset.
covers32267
BUD-01: Server requirements and blob retrieval
The base every Blossom server implements: the CORS headers, the error reporting, and the GET and HEAD endpoints that serve a blob by its hash.
draft#blossom#bud
BUD-05: Media optimization endpoints
Defines PUT /media, where a server transcodes and optimises what it is given rather than storing the bytes untouched.
draft#blossom#bud
NIP-DOMINION: Epoch-Based Encrypted Content Access
Authors: decented
covers30480
BUD-04: Mirroring blobs
Defines PUT /mirror, which asks a server to fetch a blob from a URL itself instead of having the client upload the same bytes twice.
draft#blossom#bud
NIP-GRAPEVINE-API
This NIP defines a standard HTTP API for relays to expose trust-weighted influence scores computed using the GrapeVine algorithm. These scores enable clients...

BUD-12: Blob management endpoints
Defines the management endpoints: listing what a pubkey uploaded, and deleting a blob by its hash.
draft#blossom#bud
BUD-11: Nostr Authorization
Defines the kind 24242 event a user signs to prove to a server that they allowed an application to act on their behalf.
draftcovers24242Blossom authorization#blossom#bud
NIP-MACHINE-HANDLERS: Machine Application Handlers
Authors: forgesworn
covers31990
NIP-IDENTITY-TREES: Purpose-Tagged Identity Derivation (nsec-tree)
Nostr users who want to maintain separate identities — one for social posting, one for commerce, one for a specific application — must today manage multiple...

NIP-30: Custom Emoji
The emoji tag, which maps a shortcode written in the content to an image URL.
draft#nostr#nip
Personal Letters
Existing encrypted messaging on Nostr (NIP-04, NIP-17) is designed for chat-style conversations: fast, ephemeral, back-and-forth. This NIP defines a different...
covers8211
NIP-SIGNET: Progressive Identity Verification
Authors: forgesworn

NIP-VEIL: Anonymous Trust Assertions
Authors: forgesworn
coverscomposition-guide
NIP-VA: Verifiable Attestations
This NIP defines kind 31000, an addressable event for attestations between Nostr identities. One kind serves credentials, endorsements, reviews, access grants...
covers31000
NIP-ORACLE: Oracle Dispute Resolution
Four addressable event kinds for challenging and resolving oracle-reported outcomes on Nostr: outcome reporting, challenges, stake-weighted voting, and...
covers30543305473054830549