Not going to cave to this trend of jumping on things like Zaps early and sacrificing custody of my Lightning sats for it.
Let's move a little more slowly and push for non-custodial wallet and Lightning Address support to be added more broadly and do this right from the start.
We have a chance to build something immensely powerful, self-sovereign, and decentralized with Nostr + Lightning.
I'm using @ZEUS with #[2] hoping that positions me well for when Umbrel/Start9 add the proper functionality to allow for Lightning Addresses. hopefully in a couple of years we'll have bolt12.org so that DNS becomes unecessary.
💯
Zapped you from my own node via Zeus 🤙
Sending Zaps from Zeus works well!
It's just receiving them with proper Nostr support that isn't possible in a non-custodial way yet.
By proper Nostr support I assume you mean NIP57? All others you can do if you’re using a Btcpayserver like we both are.
There are options to connect your non-custodial wallet / own node in Alby.
You can get an LNaddress from something like sats.pm which you can also self-host on an own domain.
But yeah, it's generally a bit of a hassle, and too easy to just go for a custodial solution 😑
Actually not sure. I know I received Zaps in my wallet.. and I didn't concern myself too deeply with all the NIP-57 fuzz on Bitcoin Nostr..
need to check. probably not..
Yeah, right now LN addresses work to receive but don't properly "Zap".
Damn, another thing to sort out 😞
FWIW, #[4] has a zapper script for CLN
Any tips for running this alongside CLN, #[4]?
you just run it
The only other thing you need is an lnurl server for creating zap invoices on your node. I use a custom fork of https://github.com/jb55/lnurl-commando that adds this. I haven’t released it yet though.
So I'm really new to all this
What is this pertaining too? 😅
I'd love to understand this space better so I can help on-board new people from my Twitter
Yes, there needs to be an easier solution as many wouldn't set up lnd just for zaps.
Plus many simply may not have the knowledge
Well, that's what being self-sovereign means. If you can't run your own node, then, yes, you have to rely on third parties custodying your funds for you. Install WoS and be done with it.
I guess our point is that it's even too much of a hassle for the people willing to go the extra mile and run their own node.
Does that have proper NIP-57 support when using your own node?
For those running BTCPay Server, it's a WIP addition:
https://github.com/btcpayserver/btcpayserver/discussions/4642
Amen. I jumped on already but I hope to see non-custodial easier for this use case.
I'm almost done with this. Self hosted Lightning Address provider, with support for Zaps, connected to my own LND.
https://github.com/Dolu89/ligess/issues/8
Currently handling zaps on #[2].
🔥
I agree but I also don't agree. I'm not setting up LNURL and pointing at my node. Also I'm not putting my node's pub key in my nostr profile.
Well, that's the other core issue -- LN's receive privacy is broken AF right now due to this and people should actually be wary of publicly linking their node.
Wish that wasn't the case but until Bolt12 etc. it's problematic.
Can you quickly bulletpoint how bolt12 remedies this?
BOLT-12 + alias SCIDs would allow you to not reveal your pubkey in each invoice, allowing you to do Zaps without linking Nostr to a single node.
Still has to be reachable via network, but can use VPN/Tor for your node to remedy that issue.
Does Bolt12 even really solve the privacy issue? It solves the 'need to create an invoice, or need post a node ID with keysend enabled, or setup a lnurl contraption issue'
Core caveat here is that doing this non-custodially right now necessarily reveals your Lightning node's address(es) and ties it to your Nostr profile.
Fine for public nodes that people aren't worried about, but the issues with receive privacy in Lightning create some core privacy issues around Zaps etc., sadly...
zaps work for my alby/zeus wallet integrations on BTCPay, which are non-custodial, seeing as they are both linked to my own node
And they properly show in Nostr clients? Receiving sats via Zap works for BTCPay through LN addresses, but doesn't show on Nostr as there's no pubkey in the invoice.
I was just able to zap 1000 sats you from alby with my own node, in Iris.to. Sorry for the crappy pic, took a laptop screenshot from my phone
zap from Zeus?
Zapping *from* wallets is pretty widely supported these days, was more referring to receiving Zaps as it requires LN address + NIP-57 support, which is not easily done in a non-custodial way!
Most people are relying on WoS or similar for this instead of waiting a week or two for proper support in apps like Zeus, BTCPay, etc.
that makes more sense
