pull down to refresh

If I understand correctly, these static payment codes requires specific configuration of Lightning Node and requires the user to have a specific wallet to support payments via this protocol. It seems to be quite experimental at the moment.

Any website can display the invoices, there's a sdk for fetching them making it wallet agnostic for paying, but a wallet could implement the sdk to also use the codes directly (enables for webserver-less or trustless lightning addresses with nip05)

The node server has to support it just as it would NWC, but no extra middleware beyond that

Also does debits and remote offer management without preshared secrets

Much more comprehensive and interactive than NWC, which is just a hackathonized version of what Lightning.Pub has been doing much longer (before nostr actually, nostr sprouted from GUN)

There's also no easier nor more powerful node to setup that Lightning.Pub, the nostr offers even have callback triggers

Your NWC-bridge should use it as an interface to enable lightning addresses via NWC so we can add it to the list of tools on the site

Sample bridge: https://GitHub.com/shocknet/bridgelet

Installer v.2
#1196941

Offer builder with callbacks:
https://njump.me/nevent1qqsdzd8pj8654hxn3ym5cnrzg0yclswvlls7n6gtd3lwy3mcz0uad6qppemhxue69uhkummn9ekx7mp0qgsrx9hrd9k7wnfejkgj0wwcgt0400wut5w8479qfudu0tkcpdz9pzqrqsqqqqqp8z43yv

Completely jacked to the NIPs

reply