Add NIP-52 calendar event publishing via nostrclient #4

New issue

Closed

opened 2026-04-26 20:18:58 +00:00 by padreug · 0 comments

padreug commented

2026-04-26 20:18:58 +00:00

Owner

Summary

Publish NIP-52 calendar events to Nostr relays when events are created/updated in the LNbits events extension, following the nostrmarket bidirectional sync pattern.

Scope

Add nostr/ module to the events extension (scaffolding already excluded in pyproject.toml)
Add event_id and event_created_at columns to the events DB table (same pattern as nostrmarket)
On event creation/update → publish kind 31922 (time-based) or 31923 (date-based) calendar events via nostrclient WebSocket
Map Event model fields to NIP-52 tags:
- name → content
- event_start_date → start tag
- event_end_date → end tag
- info → description tag
- banner → image tag
- price_per_ticket + currency → custom tag or amount tag
Store NIP-52 event's Nostr event_id back in DB for correlation
On event deletion → publish kind 5 (delete) event

Dependencies

nostrclient extension must be installed and configured with relays

References

nostrmarket sync pattern: nostrmarket/services.py lines 144-179 (sign_and_send_to_nostr())
NIP-52 spec: https://github.com/nostr-protocol/nips/blob/master/52.md (always consult for latest tag names and required fields)
Lightning.pub patterns: ~/dev/shocknet/lightning-pub/extension-loader/src/services/nostr/ for event dedup and relay pooling

## Summary Publish NIP-52 calendar events to Nostr relays when events are created/updated in the LNbits events extension, following the nostrmarket bidirectional sync pattern. ## Scope - Add `nostr/` module to the events extension (scaffolding already excluded in pyproject.toml) - Add `event_id` and `event_created_at` columns to the events DB table (same pattern as nostrmarket) - On event creation/update → publish kind 31922 (time-based) or 31923 (date-based) calendar events via nostrclient WebSocket - Map Event model fields to NIP-52 tags: - `name` → content - `event_start_date` → `start` tag - `event_end_date` → `end` tag - `info` → `description` tag - `banner` → `image` tag - `price_per_ticket` + `currency` → custom tag or `amount` tag - Store NIP-52 event's Nostr `event_id` back in DB for correlation - On event deletion → publish kind 5 (delete) event ## Dependencies - nostrclient extension must be installed and configured with relays ## References - nostrmarket sync pattern: `nostrmarket/services.py` lines 144-179 (`sign_and_send_to_nostr()`) - NIP-52 spec: https://github.com/nostr-protocol/nips/blob/master/52.md (always consult for latest tag names and required fields) - Lightning.pub patterns: `~/dev/shocknet/lightning-pub/extension-loader/src/services/nostr/` for event dedup and relay pooling

padreug referenced this issue

2026-04-26 20:24:03 +00:00

Register events extension RPCs with Nostr transport #7

padreug referenced this issue

2026-04-26 20:24:06 +00:00

Add ticket purchase via Nostr DM (NIP-17 preferred) #8

padreug closed this issue

2026-04-27 15:45:01 +00:00

padreug referenced this issue from a pull request that will close it,

2026-04-28 05:36:59 +00:00

feat: event proposal and approval workflow #9