Oddbean new post about | logout
 As the guy who made the spec that Zeus Pay is using to enable async payments, I support Mutiny's decision. I think disabling payments to destinations that are known to use hodl invoices is the right move for mobile nodes until some method for mobile nodes to safely pay them is discovered.

Right now a mobile node cannot safely pay a hodl invoice without risking an expensive force closure. But this also exposes a griefing vulnerability that mobile nodes are susceptible to. Nodes simply cannot tell the difference between a hodl invoice and a normal invoice. But if they do pay a hodl invoice, and then go offline for more than a day, they are likely to get force closed, which costs them money.

Since these "dangerous payments" are indistinguishable from safe ones, it is easy to grief someone if you suspect they are running a mobile node and are`on a regular zapper: get them to zap you, hodl their payment for about 10 hours or so, and then settle it. There's a good chance you'll put them in a force closure state at no cost to you. Which means *all* mobile nodes are dangerous to use for zapping right now. You can easily get burned.

I am grateful that Zeus exposed this problem and I look forward to thinking of more/better mitigations than trying to block all hodl invoices whack-a-mole style. That might work fine in a non-hostile environment, but I suspect we're heading into dangerous waters on lightning. Here there be trolls. Watch yourself.

nostr:nevent1qqsthlsymdheuj8tdcxwzxdz5y5y7aqhdedw7jzkw7rh6m3s5x05mtsppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qywhwumn8ghj7mn0wd68ytndw46xjmnewaskcmr9wshxxmmd9uq3samnwvaz7tmjv4kxz7fwvd6hyun9de6zuenedyhszymhwden5te0danxvcmgv95kutnsw43z7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcwne7ch 
 👇👇👇
nostr:nevent1qqs2d5q8f9c4tmzvrzg47d0gn7pdhhzjtc45d7dpp5x22v8zesf8pcgpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqgvra9r4sjqapufyl0vnc4kv4fz70e29em4c655y37vz206f0wt4qvzqqqqqqywaj8kk 
 @talej 👀 
 growing pains as we build the freedom. dust will settle progress will continue tick tock like a block.

in the end there will be only bitcoin 

nostr:note15mgqwjt32hkycxy3tu6738uzm0w9yh3tgmu6zrgv55cw9nqjwrssthazhg 
 Thanks for your work @Super Testnet. Since the BitVM paper I'm following as many interviews and posts of you as I can and I'm glad that such a calm, eloquent, focused and bright mind is part of the Bitcoin ecosystem. Thanks for your efforts!  
 The're just trying to protect their users.

Also:

nostr:nevent1qqs2d5q8f9c4tmzvrzg47d0gn7pdhhzjtc45d7dpp5x22v8zesf8pcgpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqgvra9r4sjqapufyl0vnc4kv4fz70e29em4c655y37vz206f0wt4qvzqqqqqqywaj8kk 
 That's what FED and SEC are also claiming  
 How I understand this is that that there is a bug in the sw. Until they figure out how to prevent it they just don't support this feature.

btw. "classic" invoices and all still work