reply on: SN elects to go noncustodial on Nov. 5th

pull down to refresh

0 sats \ 4 replies \ @JesseJames 22 Oct \ parent \ on: SN elects to go noncustodial on Nov. 5th - FAQ & AMA meta

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

42 sats \ 1 reply \ @k00b OP 22 Oct

We need to make a "Cowboy's Guide" for these.

For sending, you'll add permissions for paying invoices.

For receiving, you'll add permission for reading/creating invoices.

Supratic made this guide: #698497

150 sats \ 0 replies \ @JesseJames 22 Oct

Awesome, that worked... even "this cowboy" could understand that... I appreciate your help...!!!

21 sats \ 1 reply \ @Alby 23 Oct

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?

21 sats \ 0 replies \ @JesseJames 23 Oct

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.