pull down to refresh
0 sats \ 9 replies \ @JesseJames 21 Oct \ parent \ on: SN elects to go noncustodial on Nov. 5th - FAQ & AMA meta
it does support LN by default using it now where NWC comes into play? Not clear on that... wallet is connected why to receive only?
reply
yeah, there is but if I reconnect through alby I'm getting this:
"Connection to the Lightning node successful, but no public address has been configured"
which is weird since I see them in there.... anyone experienced the same? (latest BTCpayserver version) Not sure even how to test if after is allegedly configured, any ideas?
reply
reply
My alby browser plugin is linked to my LN/BTC node on which BTCpay also runs... just not sure which connection string to put as "receiving" and which as "sending" in self hosted alby hub. my node and email can send/receive.... just having issues wrapping my head around NWC. I'm logging in to SN with my zeus that runs off of my node... is there "an idiot instructions" anywhere...lol
reply
reply
Awesome, that worked... even "this cowboy" could understand that... I appreciate your help...!!!
reply
Alby Browser Extension is just a wallet interface in your browser and a signing device, here it can be useful in paying webLN invoices, when sending sats over the web, zapping someone on Stacker.News
NWC can be used for both sending and receiving, it's basically giving SN a permission to use your node (like Alby Hub) to create and pay invoices. Much more convenient than through the extension.
Why do you need to use BTCPay here?
What kind of node are you running?
reply
I think I got it. I have a full BTC node and LN (LND), was thinking that BTCPayServer will fit the bill since is used in retail but I used your AlbyHub instead, was slightly confused about connection string for sending and receiving but the guide above (by @supratic #698497) cleared everything. All good now, thanks for reaching out.
reply