hzrd149andClaude Opus 5 c0b479b86c Document differences from the source proposals
Adds changes-from-source-proposals.md summarizing how this specification
set diverges from PRs #104-#107, and links it from the README's Source
Material section, which previously compressed the entire delta into a
single sentence about excluded compatibility forms.

Calls out the wire-breaking changes separately: the versioned key grew
from 32 to 33 bytes, nhash TLV type 5 grew with it, the blossom: URI
encryption parameters were removed, three legacy read-paths were dropped,
and the replaceable-event tie-break reversed. Notes that the MessagePack
wire format itself is unchanged, with all manifest test vectors carrying
over byte-identical.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015UJK2viVichZctCtyz9zWu
2026-09-09 15:15:04 -05:00
2024-04-12 15:41:53 -05:00
2026-04-16 10:36:39 -05:00

🌸 Blossom - Blobs stored simply on mediaservers

Blossom uses nostr public / private keys for users identities.

What is it?

Blossom is a specification for a set of HTTP endpoints that allow users to store blobs of data on publicly accessible servers

What are blobs

Blobs are packs of binary data addressed by their sha256 hash

Protocol specification (BUDs)

BUDs or Blossom Upgrade Documents are short documents that outline an additional feature that a blossom server may implement.

BUDs

Endpoints

Blossom Servers expose a few endpoints for managing blobs

Event kinds

kind description BUD
24242 Authorization token 11
10063 User Server List 03

License

Public domain.

S
Description
Blobs stored simply on mediaservers
Readme
647 KiB
Languages
Markdown 100%