> For the complete documentation index, see [llms.txt](https://docs.onym.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onym.foundation/seats/courier/courier-nostr.md).

# Nostr/Blossom implementation

The current implementation, and the only one with running code: Nostr relays for small messages, Blossom servers for media blobs. Two off-the-shelf servers under pinned configuration — there is no Onym-written courier, and replaceability is the point, so the interesting code is entirely on the client side.

**Status:** Running alpha implementation with known interoperability, verification, payment, and replication gaps.

**Profiles:** [`message/UI-Message-Nostr.md`](https://github.com/onymchat/onym-system/blob/main/message/UI-Message-Nostr.md) (implements [`message/UI-Message.md`](https://github.com/onymchat/onym-system/blob/main/message/UI-Message.md)) · [`blob/UI-Blob-Blossom.md`](https://github.com/onymchat/onym-system/blob/main/blob/UI-Blob-Blossom.md) (implements [`blob/UI-Blob.md`](https://github.com/onymchat/onym-system/blob/main/blob/UI-Blob.md)) **Servers:** `dockurr/strfry` · `ghcr.io/hzrd149/blossom-server` **Live:** `wss://nostr.onym.app` · `https://blossom.onym.app` **Client code:** `onym-ios`, `onym-android`

## Relay configuration

[`onym-infra/strfry/strfry.conf`](https://github.com/onymchat/onym-infra/blob/main/strfry/strfry.conf) is the deployed policy:

```
maxEventSize            65536
maxWebsocketPayloadSize 131072
maxNumTags              2000       maxTagValSize  1024
maxFilterLimit          500        maxSubsPerConnection 20
rejectEventsNewerThanSeconds  900  (older than) 94608000
ephemeralEventsLifetimeSeconds 300
```

Blossom runs with `DATA_DIR=/app/data`, `PORT=3000`, behind Caddy. Neither container publishes a host port.

## Fan-out rules

The two manifests differ deliberately (see [Discovery — Static Snapshot / Ed25519](/seats/discovery/discovery-static-ed25519.md)):

* **Nostr** — clients connect to **every** listed relay.
* **Blossom** — clients upload and download via the **first** listed server, so order matters.

Clients seed a hardcoded default at first launch (offline-proof), refresh from the manifests in the background, and never overwrite a user's own custom entries.

## Gaps

Both profiles carry long, explicit gap lists. The load-bearing ones:

**Nostr** — receipts expose only `messageId` and aggregate `acceptedBy`, not per-relay outcomes; publish success is inferred from a local socket send or a five-second `OK` timeout rather than `OK true`; `OK` reasons are discarded and `AUTH`/`CLOSED` ignored, so authentication and payment refusal cannot reach the UI; clients recompute event IDs but do not consistently perform full Schnorr verification. iOS and Android diverge in subscription and reconnect behavior.

**Blossom** — each app uses only the first configured server instead of a replicated `BlobRoute`; the seam exposes only upload and complete download; uploads omit `X-SHA-256`, use padded rather than URL-safe Base64, and send the plaintext MIME type for encrypted objects; returned descriptors are not fully verified.

**Both** — `PaymentRequired`, `SeatEntitlement`, quota accounting, renewal, revocation and broker registration are unimplemented. Signed operator manifests for both couriers now exist — `discovery.onym.app` hosts and indexes `onym-courier` and `onym-blossom` manifests declaring the operator key, size limits, retention class, and privacy profile (see [Discovery — Static Snapshot / Ed25519](/seats/discovery/discovery-static-ed25519.md)) — but the legacy lists the shipping clients actually read still bind no operator, limits, retention, or privacy terms. Conformance rests on mirrored app tests rather than one fixture suite.

These are interoperability and security gaps, not alternate wire semantics a third party should copy.

## Next steps

* [Courier](/seats/courier.md) — the technology-free contract this implementation answers to on both the message and blob side.
* [Classical (planned)](/seats/courier/courier-classical.md) — the sibling profile that would let an operator run a courier without a Nostr relay or a Blossom server at all.
* [Discovery](/seats/discovery.md) — the signed manifests, and the fan-out rule each one declares.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.onym.foundation/seats/courier/courier-nostr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.