Expose Chatelet over the LNbits nostr-transport (register_rpc) #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Chatelet currently registers nothing on the core LNbits nostr-transport dispatcher (
aiolabs/lnbits#4, kind-21000 NIP-44 RPC over relays), so all operator/booking CRUD is HTTP-only. To make the extension drivable over Nostr the waylnurlpis, mirror its pattern.Reference
lnurlp/__init__.pylnurlp_start()+lnurlp/transport_rpcs.py:register_rpc("lnurlp_create", handler, AUTH_WALLET)etc. fromlnbits.core.services.nostr_transport.dispatcherregister_link_owner_resolver("lnurlp", resolve_lnurlp_owner)from...nostr_transport.subscriptionsWork
chatelet/transport_rpcs.pywith handlers that reuse the same crud paths asviews_api.py(do not duplicate booking logic).chatelet_room_create/_get/_list/_update/_publish(AUTH_WALLET / AUTH_ACCOUNT)chatelet_availability(public-ish read)chatelet_booking_request(guest write) /chatelet_booking_getchatelet_block_createchatelet_start(),try: import ...nostr_transport.dispatcherand register RPCs;except ImportError: return(no-op on pre-#4 lnbits) — same graceful degrade as lnurlp.extra["booking_id"](already done) and map it to the room's wallet.Acceptance
An HTTP-allergic client can create a room, check availability, and request a booking entirely over kind-21000 RPC, with no HTTP call.
Depends on the relay plumbing groundwork in the sibling issue (app-event publish/subscribe).
Shipped in PR #8 (booking flow over the LNbits nostr-transport,
register_rpc) and released in catalog v0.1.0. Closing — the PR's "Closes the code portion of #1" phrasing never matched Forgejo's auto-close parser, so this lingered open.