Let's try some lightning addresses in the decoder: Starting with the most basic to the most complex ⬇️ https://m.stacker.news/34961
Alby Lightning Addresses - SimpleAlby Lightning Addresses - Simple
Starting simple, here's an Alby lightning address from one of our dedicated liquidity sellers, HodlmeTight1337: https://amboss.space/lightning-decoder?request=hakuna%40getalby.com The response now includes specific lightning address details like the user, the domain, and callback info. https://m.stacker.news/34962
In the LNURL section, there's even more information, including the min & max spendable, a Nostr npub belonging to Alby Zapper, and additional Metadata. https://m.stacker.news/34963
Obviously, any payments made to this custodial wallet will go to the http://getalby.com node, as confirmed in the Payee pubkey field. https://amboss.space/node/030a58b8653d32b99200a2334cfe913e51dc7d155aa0116c176657a4f1722677a3 https://m.stacker.news/34964
Lightning Tip Bot Addresses - IntermediateLightning Tip Bot Addresses - Intermediate
Now more advanced: LightningTipB0t ! https://amboss.space/lightning-decoder?request=LightningTipBot%40ln.tips This Lightning Address includes an image, which is the user telegram profile pic. That's all included in the metadata field.
Lightning address makes it easy to pack in lots of extra data outside the invoice. https://m.stacker.news/34965
Similar to Alby, there's a Nostr npub included, which provides zap receipts.
Thanks @calle for your help understanding these functions! https://m.stacker.news/34966
In addition to the image metadata and the Nostr zap receipts, the LightningTipB0t includes a route hint that goes through Boltzhq.
Despite the tipbot being a public node, the route hint exposes a private channel. https://m.stacker.news/34967 According to @calle, this is fine; it's just for routing. https://m.stacker.news/34968
Ghost Addresses - AdvancedGhost Addresses - Advanced
More complex: Ghost addresses!
These are special addresses that allow payments to be intercepted by a node operator, bypassing the need for them to run an LNURL server. https://amboss.space/lightning-decoder?request=jesse%40ghst.to https://m.stacker.news/34969
To enable this, the Payee pubkey field looks just like a private node. In reality, it's a randomly generated pubkey that's non-existent.
Instead, the actual payment destination is included in the route hints. https://m.stacker.news/34971
In this design, the route hint is intercepting the lightning payment, actually arriving at the Satbase node. https://amboss.space/node/0390cc12f782259427bdc45a283705f4c20ccbdff064ed43f6b74fefcafe9eb1f7 When Satbase sees the payment attempting a route to a predefined, nonexistent channel, it will request the preimage, enabling an intercept.
To find out more about ghost addresses, you can check out http://ghst.to and get your own via Thunderhub.
Thanks for reading!
What other lightning addresses have interesting setups?
What other innovations should we dive deeper into?
Who is next to add lightning addresses?
Can the node that receives the payment identify who paid the invoice? What details do the nodes receiving the invoice get to see? thanks
Identifying the payer of an invoice is nearly impossible in lightning unless the payer reveals that fact themselves.
Anyone with access to the lightning address or invoice is able to see this information, including the payer or the payee (they are usually the ones that made it after all, except for Ghost Addresses).
Neat!
Would be great to see this implemented in the different wallets so you could click "show more"when you pay the invoice / send sats to address
We'd love to help a wallet add these features. Be sure to let them know this is a feature you want!
Nice article!
Thanks! This stuff is fascinating ⚡
One thing I want to learn how to do with lightning is how to have a perpetual lightning invoice. All lightning invoices I create only last an hour, I want one that lasts for a long time! Like a year or two