We have recently disabled the ability to zap nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 wallet users from Mutiny. You may still pay their invoices or LN addresses normally but a big problem we were seeing was force closed channels due to stuck payments to Zeus due to their work arounds with locked payments. Which harm both the user experience and other lightning nodes on the network.
Since nostr users are mostly unaware if they're zapping Zeus users or not, we are taking this step proactively to protect users from having a 10 sat zap costing them serious on chain channel closing (and reopening) fees.
The approach we are working on for solving lightning addresses on mobile wallets is a fedimint hybrid approach where the sats end up at a federation if you are offline but get swept to your self custodial channel when you come online. Payments will settle instantly with the federation and it won't lock up unnecessary HTLCs on the network.
Ideally we get the ability to do offline receives normally on LN but that future is looking really grim with LND's continued priorities on shitcoins instead of features, and offline receives depends on a network wide upgrade.
We petition Zeus to move to a more responsible node implementation like LDK unless their plan is to add shitcoins or break LN further.
Re: LND's continued priorities on shitcoins
I think post author is referring to LND's Taproot Assets (a.k.a Taro)
Here is from Lightning Labs recent newsletter (August 2023):
"""
Over the next year we will also probably see more APIs added to support the Taproot Assets project because that will be built on top of LND but not be tightly integrated internal to LND, similar to the Faraday, Aperture, Loop, and Pool projects that are part of the extended release bundle. A new PR adds a new signing API needed by that project:
"add schnorr_sig_single_tweak option to msg signing"
- Github issue 7898
The Taproot Assets integration is also expected to have a heavy impact on the Taproot channels implementation so that the asset control can be handled by an external daemon. These APIs will allow for a clean separation and conceptually there could even be multiple competing Taproot Asset daemon implementations that would all leverage the same API interface.
"""
nostr:npub15n94rarp3n7dz6edx9cugeshn0kcuxtugwu9nzprkpx7yekw7ygqplqru4 that hash price looks like something is wrong with the metric
grafana (i set it up on my local network, but using nostr to share it with the world)
Using NOSTR from your iPhone? Can't zap anyone? NOW YOU CAN!
Here's a tutorial on how to set up nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan so that you can zap anyone simply by replying with an emoji of your choice. Shoutout nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm for Nostr Wallet Connect (Alby wallet also used in demo). Extra shoutout to nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg which I recommend as a non-custodial wallet option, and to nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 which is mentioned in the context of viewing your Alby wallet on mobile.
Enjoy and please share!
https://www.youtube.com/watch?v=NF2uGXkoBrc
Don't forget to sub for free weekly tutorials!
how does the post author receive the zaps?
Mining Difficulty +3.5% but hashrate drop is under 1% (from 461 to 457 EH/s), so miners just carry on even if they are paid less?
spot on!now i get it, since i'm on UTC and there was a daylight savings change in US my snapshot was taken 1h too early
8 blocks behind, for next one i'll change the cron job to take the snapshot 1 hour later 
Still off by 6 blocks between what I captured and what's in the Morning Coffee Report nostr post. Nostr post is 6 blocks ahead. It's strange because i'm taking the data from https://bitcoin.clarkmoody.com/dashboard/ at the same time as nostr post comes out, i suspect I'm capturing a cached version that's 1 hour old
my snapshot is off by 4 blocks today (about 40 min), not sure why 
my snapshot of Clark Moody Dashboard taken 1 hour too early because I use UTC while Morning Coffee is on PDT which had daylight savings adjustment today
