Nostr Wire Format¶
The Nostr wire format is the OpenETR interoperability boundary.
It defines how OpenETR control evidence is represented as signed Nostr events, event kinds, and tags.
Event Kinds¶
The current regular-event model uses:
| Kind | Use |
|---|---|
1415 |
Origin event |
1416 |
Control event family |
Legacy prototype events using 31415 and 31416 may exist, but new graph events use regular kinds 1415 and 1416.
Core Tags¶
| Tag | Role |
|---|---|
o |
Controlled object digest. Primary object-centric query anchor. |
e |
Prior event link for graph traversal. |
p |
Action-specific participant. |
action |
Control event subtype. |
enc |
Encumbrance event referenced by a discharge. |
type |
Action-specific subtype. |
ref |
External reference or business reference. |
Structured Metadata¶
OpenETR uses named tags for signed structured metadata that does not need relay indexing.
Examples:
["name", "MLWR001.pdf"]
["size_bytes", "282796"]
["digest_generated_at", "2026-07-10T12:00:00+00:00"]
["domain", "mlwr"]
["document_type", "warehouse_receipt"]
["record_reference", "MLWR001"]
["record_description", "Stored goods described in the receipt"]
Implementations should read structured data from tags after retrieving the event. They should not parse the content field to recover machine data.
Content Field¶
The event content field is for readable narrative, comments, or unstructured context.
The signed tags are the machine interface.