Write path
- Serialize a JSON record into a NIP-78 kind
30078event. - Tag it with the namespace, table, and record ID.
- Ask the active Applesauce signer for a signature.
- Publish it through Applesauce RelayPool.
- Return per-relay acknowledgements and a signed-event receipt.
Record identity is namespace + table + author + ID. Two authors can use the same ID.
Read path
- Request records and deletion events from the configured relays.
- Verify signatures and the record envelope.
- Resolve each address to its latest valid version.
- Apply field filters, sorting, and selection in the client.
- Return rows with
idand_nostrmetadata.
Namespace, author, and ID narrow relay requests. A relay can limit results or prune history. End of stored events (EOSE) does not prove a complete global table.
Updates and deletes
An update signs a new event at the same address. The highest created_at wins; a timestamp tie uses the lowest event ID. Writes in one client are serialized. Separate devices can overwrite each other.
A delete signs a NIP-09 kind 5 request. The SDK uses tombstones to hide old versions. Relays decide whether to remove their stored copies. A newer event can recreate the record.
What runs where
| Component | Responsibility |
|---|---|
| Your app | UI, trusted-author rules, field queries, validation |
| nostrbase | Record encoding, ownership, version resolution, receipts |
| Applesauce | Signers, relay connections, EventStore, Negentropy |
| Nostr relay | Event storage, queries, delivery, relay policy |
| Blossom server, optional | HTTP file storage |
| IndexedDB, optional | Device cache and signed write queue |
A client-side query runs in the app and can fetch relay data. A cache-only query uses .local() and sends no relay request.
Access and consistency
A signature proves origin. It does not prove truth, app approval, or permission to join a collection. Namespaces label data; they do not restrict access.
Public tables are public. Personal private tables encrypt bodies to the author. Shared private groups use experimental Marmot/MLS membership and encryption. Transactions, global uniqueness, and trusted server functions require more services.
Use native events when interoperability calls for an existing Nostr kind. Use tables for application records. Wire format.