Nostr
This is a shipped config-backed outbound surface. Nostr relay subscriber runtime is not implemented yetAt A Glance
| Field | Value |
|---|---|
| Catalog id | nostr |
| Config key | nostr |
| Implementation status | config_backed |
| Transport | nostr_relays |
| Aliases | none |
| Default send target kind | address |
Minimal Config
Smoke Test
Command Surface
| Operation | Command | Usage or status |
|---|---|---|
| relay publish | nostr-send | Usage: loong nostr-send [OPTIONS] —text <TEXT> |
| relay subscriber | nostr-serve | nostr relay subscriber runtime is not implemented yet |
Required Fields For Send
| Requirement | Config paths | Env pointer paths | Default env |
|---|---|---|---|
| channel enabled | nostr.enablednostr.accounts.<account>.enabled | none | none |
| relay urls | nostr.relay_urlsnostr.accounts.<account>.relay_urls | nostr.relay_urls_envnostr.accounts.<account>.relay_urls_env | NOSTR_RELAY_URLS |
| private key | nostr.private_keynostr.accounts.<account>.private_key | nostr.private_key_envnostr.accounts.<account>.private_key_env | NOSTR_PRIVATE_KEY |
Gateway And Ownership
This surface is a direct-send delivery lane. It does not joinmulti-channel-serve or the gateway-owned reply-loop contract today.
Operator Notes
- Nostr send publishes signed notes to one or more relays. The relay-subscriber serve contract remains planned.
Related Docs
- Continue to Channel Guides for the full shipped channel matrix.
- Continue to Channels for the conceptual surface model.
- Continue to Channel Setup for the shared public setup contract.