RTL
RTL copied to clipboard
Ride-The-Lightning
Integrated Nostr chat
Playing with ideas on integrating a Nostr chat client within RTL. The objective is to enable an out of band communication channel between lightning node operators. This communication channel can be used to coordinate on various operational aspects like notifying a peer on an inactive node or notifying channel partners on node maintenance etc.
Initial ideas are for a basic interface, but can evolve much further depending on traction and feedback from users High level requirement is:
- create a
Nostr Chatmenu at the top level - Clicking on the menu takes the user to the chat page where user can perform the following actions
- Add/Create a Nostr prv-pub key pair and save to RTL
- Add Nostr pub keys by associating them with LN pub key and save them as
Contacts - Chat 1:1 with the contacts over Nostr
Hey! Posted this to nostr and someone pointed me to this issue. Happy to see others with similar thoughts.
Upon setup, the lightning node signs the user’s npub, thus creating an attestation. The nostr client publishes a profile update (kind 0) and includes the attestation (signtature) and the lightning node’s pubkey in the content JSON.
The nostr client would then run beside a Lightning Node and automatically attempt to follow new channel partners (and maybe gossip peers).
This could allow node runners to send verified messages to their channel partners at any time, even if their node goes down… All without the use of a 3rd party service.
Thinking it could be used to free up some bandwidth over gossip (liquidity ads, channel negotiations, etc.)
Thoughts?
Add/Create a Nostr prv-pub key pair and save to RTL
Please, support browser extension (nos2x) and/or key delegation in order not to import existing privkeys.
Add Nostr pub keys by associating them with LN pub key and save them as Contacts
Why not getting (and updating) the Contacts List through nostr itself?
Great idea!
FYI: nostr npub keys are the same as taproot addresses with a different prefix, (npub vs bc1p) if that's any help. So if RTL can already create a taproot address, it can be a chat identifier
