How to Use Alby to Receive Zaps to your own LND Node

-------------------------------------------------------------------------------------------------------------------

The vast majority of users that utilize LN address for receiving bitcoin as tips or zaps appear to be using custodial wallets (most commonly I see Wallet of Satoshi and Alby, but there are others too such as ln.tips or stacker.news). I'm not here to make a judgment on that usage, but there may be users out there that would prefer to cut out the middle man and reduce their counter-party risk. Problem is, hosting a domain and setting up an ln address to receive sats to one's own node is outside of the capabilities or time allowance of most (including this writer). And with that said, I'll present a decent compromise to this issue.

For my very first write-up, I'm going to walk you through the latest thing I've been toying around with. Alby has this cool feature where you can update your Alby ln address to forward sats directly to your LND node. This means any zaps or tips one receives to their Alby ln address are not sitting in your custodial Alby account and are paid directly to your LND node. Disclaimer: Receiving zaps in this fashion can come with some privacy concerns, so if that is a concern of yours then you should probably not use this tool.

As will be the case with most write-ups I do, I am going to walk you through this setup with an LND node running in start9 OS. So, it will likely benefit users of Start 9 OS but I think people will be able to infer where to get the appropriate info from their respective node interfaces as well.

Without further delay, here are the steps to get all set up to receive zaps directly to your node using your @getalby ln address:

1. I'm going to assume you have Alby as a web browser extension all set-up and also have an Alby ln address (xxxxx@getalby.com). If you don't, I'm sure their website (getalby.com) has easy instructions on how to do so. First, you will want to click the 'Manage your web account' link from the web browser extension.

2. Then, you are going to click 'Wallet', and scroll down to 'Update your LND node settings', section looks like this:

3. We need to add the correct macaroon (hex). Don't close out your Alby wallet page as we will be returning to it to input info. As the instructions outline in the image above, we are going to want a macaroon that gives just the permissions necessary for the purposes of this ln address. In order to create the macaroon, I am going to use the Thunderhub service via Start9 OS. Once logged into Thunderhub, go to the 'Tools' page and click 'Bake' in the Macaroon Bakery section.

4. Once you click 'Bake', you will be presented with many options to choose from for the macaroon that you create. Again, we want to only grant the minimum access necessary, so just switch 'Create Invoices' to Yes.

Scroll down and click 'Bake New Macaroon'. A pop-up will appear that displays the macaroon coding. We are going to copy the Hex encoded option for our purposes. Once copied, paste that Hex encoded macaroon into the Macaroon (Hex) field on the getalby wallet page.

5. Next, we are going to grab our Certificate (Hex). Using start9 OS, I am going to go to my LND service, and select 'Properties'

In the properties section, click the eye next to LND Connect REST URL to display the relevant text string. You will see an extremely long string on characters. For our purposes, we need to pull out the cert from this string. Right after the '.onion:8080' portion of the string it says 'cert='. We want to copy the entire string starting right after this = symbol, and copy all the way to right before the Macaroon string starts (include the & symbol right before 'macaroon=...' begins).

Take this copied text and paste into the Certificate (Hex) field found on the Alby wallet page.

6. Finally, we need to obtain the 'REST API host and port or TOR onion URL' info from the Alby wallet page. Using start9 OS, you will return to the LND properties page. Click the eye for the LND Connect REST URL. Copy starting from the beginning of the string of text to '.onion:8080'

Paste the string of text into 'REST API host and port or TOR onion URL' field on the Alby wallet page. Before saving the page, erase the 'lndconnect' portion of the string and replace with 'https'. So the string should be 'https://xxxxxx.onion:8080.

7. Click 'Update Connection' at the bottom of the Alby wallet page. After a few seconds, the page should update with a green bar that displays the following text: 'Successfully updated your connection details.' You should be good to go now!

8. Test out your new feature. Send sats to your getalby address (cannot be from your LND node). Once successfully sent, check your LND node and confirm that the payment was received. You should be set now to receive zaps or sat tips form an LN address directly to your LND node :)

Reply to this note

Please Login to reply.

Discussion

Hi, I've started to write about my various tinkerings I've done with lightnings. For this post, users of nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll & nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm will likely find it most relevant. Cheers!

nostr:nevent1qqsq9lw5zcrfuls849scv5j9e2909jgrvps57suhv3wrcgjrgd6rs4cpp4mhxue69uhkummn9ekx7mqzyqfykglj7e64gq420q2trpwv6yrxl0c0nc4hu43ks0rc8kczg4v5wqcyqqqqqqgvyzvaz

Very cool but I’m sick of this attidude towards custodial lightning. I contribute sats towards the v4v model while I am still locked into the fiat mines for work, I’m zapping everything instead of likes and I’m not looking to be some meme lord who can run a positive income and withdraw sats from y’all.

Get all the normies to withdraw their on-coins from binance then we can complain about Alby or WoS.

Sorry it touched a nerve. As I mentioned in the post, not a judgment on custodial lightning usage.

Nice write up!

Thank you!

nostr:npub1qd6zcgzukmydscp3eyauf2dn6xzgfsevsetrls8zrzgs5t0e4fws7re0mj

nostr:npub1a8wreeghu0j8g4zqgzex53sq38gjwjdp5czxnu3rfydnz8n8yu2spqkavy

nostr:npub1z8huw7etk7l5a2k5u8n99vsz2uvtjtrusnz05e7j7ptgfcpqnyfsvpq70x

nostr:npub1r27yp3vmr53gx9z2ltzxt8pah07p5xext2u7eeeg5zs5cmxkpeqst2hxu8

nostr:npub1vm0kq43djwdd4psjgdjgn9z6fm836c35dv7eg7x74z3n3ueq83jqhkxp8e

That’s interesting 🤩

I wonder does it work with Umbrel 🤔

That's why we should try

Introducing the "poor man's" wrapped lightning invoice receiver for your zapper node. This will be a more private way to receive zaps to your own lightning node with nostr:

Going to be most appealing for users of nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct and nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll or other node in a box products.

Step 1:

fire up an lnd or cln lightning node.. open a private channel with Stacker News.. use boltz to swap out 50% of the channel or so for easy sending or receiving balance.

Step 2:

Link your node with an ln address. a few examples for the less technical of how to do so:

- link your lnd node up with the amboss ghst. to ln address via thunderhub.

- follow my guide to link lnd with alby ln address here: nostr:nevent1qqsq9lw5zcrfuls849scv5j9e2909jgrvps57suhv3wrcgjrgd6rs4cpvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c330fnrj63cw45xkae5xfcnjvnwvdax5cmrw3h8svm3v45x6dmjw5mnjerv89mxgdtjvvmhqcttw94rjapewfehx7n3x5mxs0mzwfhkzerrv9ehg0t5wf6k2q3qzf9j8uhkw42q92nczjcctnx3qehm7ru79dl9vd5rc7pakqj9t9rsxpqqqqqqz6kwjtm

- follow my guide here to use lnbits to link up cln or lnd with ln address here: nostr:naddr1qqrrywfjxy6nvq3qzf9j8uhkw42q92nczjcctnx3qehm7ru79dl9vd5rc7pakqj9t9rsxpqqqp65ws33x97

Step 3: create a stacker news account. in the wallet, attach your ln address and set it up to send sats from the stacker news wallet to your ln address from step 2 automatically.

Step 4: use the stacker news ln address to receive zaps in your nostr profile. Congratulation, you are now receiving zaps to your custodial stacker news acct, and those zaps are fwded to your node automatically, and much more privately than exposing your at home node on nostr.. thus, the poor man's wrapped invoice.

#bitcoin

#lightning

I saved this to get back and give it a go. The only issue I'm having is that in the LND Properties in Start9 the LND Connect REST URL goes straight from "...onion:8080" to the "macaroon=..." With the cert hex nowhere to be seen. Do you know where else I could find that hex?

lol, LND properties

the configuration system of LND doesn't work properly, got bugs that have been there for over 5 years still, who knows what the trick is