The wallet uses a nwc string to be setup. I assume that means the wallet communicates with the relay for everything (get balance, get txs, create invoice, pay invoice, etc). Am i wrong about this?
Ah, I see what you’re saying. Then yes, there’s a dependency on the relay. I was thinking of the LNDhub connection. Let’s ask for some clarification on this.
The reason i bring this up is because i had nwc working as a custom node in @btcpayserver and then it suddenly stopped working. No changes to btcpay, reverted to previous versions of alby hub, but still no luck. The only other piece of the equation is the relay and i don't know if they changed anything there. Reached out on discord where they're usually helpful but didn't get a reply https://discord.com/channels/1257746232353230930/1258739896063889470/1284136031976685569
We don’t need discord when the team
Is here.
So just tag them, like @saunter @roland @bumi ? I'm not sure of i should
I can not speak for BTCPay but I know that there was some debugging going on in regards to how BTCPay subscribes to events.
To answer the question about the relay:
if the Alby relay is going away you just use a different relay. in that case you will have to reconnect the app (btcpay) to the wallet that you use again. (because the relay is set as part of the connection secret and the app and wallet need to know through which relay they have to communicate)
but that’s the beauty of NWC, it uses the default Nostr infrastructure and no special setup would be needed in that case.
What other nip47 relays are out there?
I just remembered the only other nip47 relay ive seen was @OpenSecret. Checking their github now to see what they shared...
any relay works.
we do some more special stuff in the relay for validation and protection and optimizing for NIP47 but ultimately any relay works.
Oddbean new post about login | logout