aiolabs/chatelet
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: expose Chatelet over the LNbits nostr transport (#1) #8

Merged
padreug merged 3 commits from feat/nostr-transport-rpcs into main 2026-07-19 14:50:39 +00:00
Conversation 0 Commits 3 Files changed 5 +9 -5
1 changed files with 9 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 1b65890f42 - Show all commits

docs: reframe kind:22000/22001 as retained proposal, not redundant

Prev Next 
Per the client-agnostic doctrine (workspace CLAUDE.md): the availability RPC
is the training wheel, the public kind:22000/22001 is the destination. Keep
the custom kinds as a proposal so a generic Nostr client can one day query
availability without our RPC. Published via the nostrclient relay path (#2).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019VUQCfdqiLSsFS2jcGnaFD
Padreug 2026-07-19 15:37:06 +02:00
commit 1b65890f42

14
docs/event-flow.md
View file

@ -41,11 +41,15 @@ scoped, so the *operator* can stream booking settlements
wallet, so the guest confirms by polling `chatelet_booking_get` until wallet, so the guest confirms by polling `chatelet_booking_get` until
`confirmed` (a guest push would need a NIP-17 DM — issue #5). `confirmed` (a guest push would need a NIP-17 DM — issue #5).
> **Consequence for the custom kinds:** with availability answered by the > **Custom kinds vs the RPC — training wheels, not redundancy:** the
> `chatelet_availability` RPC, the ephemeral `kind:22000/22001` availability > `chatelet_availability` RPC is what ships first, but the ephemeral
> query/response (ADR-0001) is **redundant for RPC clients**. It is only worth > `kind:22000/22001` availability query/response (ADR-0001) is **retained as a
> keeping if we want non-RPC Nostr clients to query availability by publishing > proposal**, not dropped. The RPC is the training wheel; the public event kind
> an event. Revisit when the public-discovery transport is chosen (issue #2). > is the client-agnostic destination — a generic Nostr client must one day be
> able to query availability *without* speaking our private RPC (workspace
> doctrine: extensions aim to be Nostr-client-agnostic). It will be published
> over the nostrclient relay path alongside the NIP-99/52 discovery events
> (issue #2).
## Actors ## Actors