I added nostr zaps to go-host-lnaddr, everyone's welcome to review and comment:

GitHub

Add nostr zap support by rkfg · Pull Request #27 · hieblmi/go-host-lnaddr

Closes #17. Testing this is harder than I expected because lnd doesn't allow settling an invoice made by itself, Primal asks to connect a walle...

I couldn't find any other such solutions except the reference implementation which is in JS. go-host-lnaddr allows hosting your own Lightning address/LNURL pay/Nostr name, and now it also lets you receive zaps to your own LND node. I haven't tested it much, just followed the spec and used the mainstream libraries. It's effectively a small addition to the existing functionality that parses zap request and posts zap receipt + puts the request to the invoice description. Still, there could be quirks I missed. I currently run this patch myself.

The biggest problem in nostr is... following people apparently. I've seen too many clients where this basic feature is either missing or unavailable because of adblock hiding it for some reason or it's buried so deep I can't find it. On primal it's the former I think: Non-working zap button, a menu... Add user feed? Is that following? Nope, it's something else completely. Ah, there it is: Very convenient, just open any post and you can find the follow button if you're lucky. No wonder engagement is so bad on nostr if you can't even follow people in one click.

Great DoS potential! Since pushing an event doesn't mean you're able to sign, just pick whatever events of other people and push them to this relay, get a bunch of such messages that *those* people receive, not you, lmao!

Eldorado just fucking collapsed:

Amboss Space

Eldorado - Lightning Network Node | Amboss

Eldorado is a Lightning Network node with 38 channels and a capacity of 81,535,101 sats. Pubkey: 02e20cd7de8385128138b82b8364693a66766b8fc60c00aaec...

from my logs they probably restored an outdated backup and all channels were force closed because the height on their side was lower than on the peer side, a few hundred updates off but not 0 (which usually indicates channel recovery request). But what's even worse is that they had one penalty tx:

Amboss Space

Amboss Space - Lightning Network Explorer

Lightning Network Explorer and Analytics Tools. Search for nodes and channels on the Lightning Network and get detailed information on them.

3M sats just found a new home, whoosh! Poor node, but a good lesson for everyone: don't backup your channel database, make a static backup instead. If you lose your state you _have_ to force close _all_ channels (or, to be precise, ask your peers to do so), there's no other way. It's cheaper than losing everything to penalties.

This unknown tx type stuff keeps happening... is anyone paying attention? Is this an elaborate UTXO spam?

The Mempool Open Source Project®

Explore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.

#[0] opening events on nostr.com is currently broken on anigma because they changed the site completely. It runs a fork of Branle now.

Need to add npub-style address support to Branle

BTW this anigma wallet (which is LNBits actually) supports Lightning Addresses so try that too!

Also if you save your profile on anigma, it adds a LUD06 field with your wallet here which enables the tip button in your profile

Hey lnbc210n1p3emhmfsp58tzh903wtmklg7q8suw7g5frd8ylfw02ea4tkgulfr077uv8zweqpp56ghhnnf2rjrms729khh25jh2gjr3306qh4kzaqtn2y4ktg0qn9jqdq2f38xy6t5wvxqyjw5qcqpjrzjqfs23nl63fcpdkurxl2cfcvjewpfqdtpdsxnjy39h9qhkjw5unkk5zagj5qqymgqqyqqqqqqqqqqqugqvv9qyysgqqwt3a245x805xjgspuvh833klyctuyajf4dkldekmyq6eke5mkzr0g4h0k6cm3rvf8q539xxrucgs93ets4y969ckqfpfv3w7jtafmqpuwkh4y

In this time and age it's so much more important to define what your project/protocol is NOT than what it IS. And then follow these limitations strictly. Knowing the boundaries is extremely useful as then you can carefully plan and build within them not inflating the purpose.