For everyone that was complaining "Lightning is broken" when on-chain fee rates were high, you can now splice in outgoing or rent inbound liquidity at rock bottom rates.

“Last week, Bitcoin Lightning developer Jordi Montes disrupted the US presidential campaign trail and the largest Bitcoin gathering in the world by trying to hide his cigarette lighter inside a conference hall.” 😅
https://protos.com/bitcoin-lightning-dev-tried-to-outsmart-secret-service-at-trump-speech/
icym 
Time lapse of US Air Traffic during today's Network Outage
https://video.nostr.build/87291a9fd371cdaa81b1a67bfc685205908cb227a4d4fa63c5e71cd2f4540dcc.mp4
Go ahead and check ✅ "IT Mayhem" on your 2024 bingo cards folks.
Vance's questions to Powell on this topic are interesting:
"Now, I know the strong dollar is sort of the “sacred cow” of the Washington consensus, but when I survey the American economy, and I see our mass consumption of mostly useless imports on the one hand, and our hollowed-out industrial base on the other hand, I wonder if the reserve currency status also has some downsides, and not just some upsides as well."
oops, missing example link: https://dns.google/query?name=ben.user._bitcoin-payment.btcsessions.ca&rr_type=TXT&ecs=
Useful discussion on Xitter about how to check if your BIP-353 DNS records have DNSSEC setup correctly:
Almost there! You must enable DNSSEC on your domain.
This should contain "AD":true
Have to say that Phoenix wallet is probably the best lightning wallet right now due to BOLT 12 support and splicing, but I can't wait to see what nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 and MuunWallet are cooking up
Bolt compatible Lightning wallets are stronger together 💪
Curious about this new BIP 353/Human Readable Names thing but don’t have a wallet that supports it yet? Want to see if you set it up right?
Head over to https://satsto.me/ to resolve them to legacy addresses!
It’s not just BOLT12, either, any reusable bitcoin addresses can go in there (but preferably ones that don’t cause on-chain address reuse)!
#dnsmaximalist

"🧪 Phoenix now supports BIP-353 LN addresses
To create your address (must have a channel):
- android: Settings > Experimental features
- ios: soon™
- server: ./phoenix-cli getlnaddress
Phoenix (android/ios/server) can all send to both BIP-353 and LNURL addresses"
https://x.com/PhoenixWallet/status/1811442125801705638
Now we just need nostr zaps support for BIP-353..
I think it's a matter of if you can support the LN address functionality via standardized LN wallet API. Could take awhile but we need something similar to support Ocean mining payouts so could be it happens sooner rather than later.
I took a quick look at https://nostr.how/en/zaps and I think the payer's nostr app needs to pass to the payer's Lightning app via an API call:
- the static invoice of the note's poster
- an ID for the zap that the payer's LN app should include as a note with the payment
- the sats amount the payer selected
The zapper's nostr app can then post a note about the zap with the ID, amount and relays to respond to. This should be possible without nostr specific changes to Lightning clients.
The note lets the zap receiver know what note was zapped. I'm not sure how the zap receiver can confirm the zap though. They would need their Nostr app to query their Lightning app.. or maybe the other way around?
Then they can post the confirmation note to the relays specified by the sender.
Hmm ya maybe it's way harder than it seems, as is most things in Bitcoin 🫣
What happens if a tyrant starts gobbling up these small Lichtensteins? I agree it would be better to have many microstates but history shows you also need a way to prevent forced consolation. Or maybe with Bitcoin you can reduce the incentives to invade?
What's it going to take to add a bolt-12 offer to my nostr profile so that it's used for zaps?
Check out Phoenix or phoenixd - just released bolt-12 support today!
On Android it will wake up your phone to receive the payment, this seems to work well. I assume it will work the same for iOS.
