mirror of
https://github.com/hzrd149/blossom.git
synced 2026-10-05 15:38:22 +00:00
hzrd149andClaude Opus 4.8
2c30864340
The definition restricted BUDs to features a server implements, but BUD-10 (the blossom: URI schema) is already a client-side convention. Broaden the definition to cover client-side conventions and data formats built on Blossom blobs that servers do not implement. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
22 lines
745 B
Markdown
22 lines
745 B
Markdown
# BUD-00
|
|
|
|
## Blossom Upgrade Documents
|
|
|
|
`draft` `mandatory`
|
|
|
|
This document details the common language for all following BUDs
|
|
|
|
## Language
|
|
|
|
All occurences of "MUST", "MUST NOT", "SHOULD", "SHOULD NOT" MUST be interpreted as per [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119)
|
|
|
|
## BUDs
|
|
|
|
BUDs or "Blossom Upgrade Documents" are short documents that outline an additional feature of the Blossom protocol.
|
|
|
|
A BUD MAY define a requirement or feature that a blossom server MUST or MAY implement, or a client-side convention or data format built on top of Blossom blobs that servers do not need to implement (for example the `blossom:` URI schema in [BUD-10](./10.md)).
|
|
|
|
## Blobs
|
|
|
|
Blobs are raw binary data addressed by the sha256 hash of the data.
|