Wondering what all the commotion was about yesterday with Mutiny and Zeus? Here’s our summary of what happened.
@OpenSecret stirred up some controversy yesterday after announcing their decision to disable the ability to zap @ZEUS wallet users. They said the decision had to do with increased forced channel closures due to stuck payments with Zeus’s approach to locked payments, and further said the decision would not affect the ability to pay Zeus invoices or LN addresses.
nostr:note1h0lqfkm0neywkmsvuyv69gfgfa6pwmj6aay9vau804hrpgvlfkhqszvfj9
@Super Testnet , who says he made the spec used by Zeus to enable these async payments, voiced his support for Mutiny’s decision.
nostr:note15mgqwjt32hkycxy3tu6738uzm0w9yh3tgmu6zrgv55cw9nqjwrssthazhg
Meanwhile, Zeus pushed back with their own statement saying, “ZEUS will never block payment to our competitors’ wallets, disparage or belittle anyone trying [to] push Bitcoin adoption forward, or give up on trying to ship self custodial solutions.”
nostr:note1ek4gze5sndaahsrptwpfxtmcpuvyyx998jn9fl04e7q8trjc9t9sfftv29
The news was hotly debated and thoroughly memed among #Nostr users throughout the day, some in favor of Mutiny’s decision, and some decrying it as censorship and a removal of user choice. Ultimately, Mutiny issued a further update that gives users the option to assume the risk if they want to, calling it “Freedom to get rekt.”
nostr:note15zl3g840gtuycmfhdmfdr6ep8str9f0n0h5srrpa5htqh04k8vlszumgtj
The two wallet makers ended the night wishing each other well… well, sort of:
“Night night. Don’t let the force closes bite.” nostr:note1v2h3f4q2uel70te5z7yaplf69lv7aclg9nler5mnecs8mt7xv53qmfzt74
“gn, check your zaplocker before falling asleep” nostr:note1tpnz6jwrrcadkfql39ele2w0kd55yfaazjwhmfyge2asynnnwsxsvynlhg
Giving the “Freedom to get rekt” as an optional opt-in after providing a reasonable warning/education seems like a great way to handle a situation like this.
I don’t know enough about the technical aspects to judge either implementation, but seems like the friction will hopefully drive the developers to better solutions in the long run 🤞
Agreed, I like that there are strong opinions on how it should be built but also maintain respect for the users
Mutiny isn’t even a viable option for iOS users for connecting your node and zapping so they can cry all they want but they are alienating a whole subset of nostr bitcoiners
Good report and summary
nostr:nevent1qqs23qk0vr9d04k4dr39n2umfvxncqpwcyunvza3ezah990wt3a0jhcpzfmhxue69uhk7enxvd5xz6tw9ec82cszyqhdhn4xjngkgc5c2jjjtq693ltdjed3v83ufz6h6whlqx2q2kyggqcyqqqqqqgf3ggdv
Something happened .. 👀 .. something, something, stay humble .. something, something, stack sats
👀
#bitcoin
#lightning
#ticktocknextblock
nostr:nevent1qqs23qk0vr9d04k4dr39n2umfvxncqpwcyunvza3ezah990wt3a0jhcpp4mhxue69uhkummn9ekx7mqzyqhdhn4xjngkgc5c2jjjtq693ltdjed3v83ufz6h6whlqx2q2kyggqcyqqqqqqgxxkuf0
This is how the disputes should be handled! Friendly!
nostr:nevent1qqs23qk0vr9d04k4dr39n2umfvxncqpwcyunvza3ezah990wt3a0jhcpp4mhxue69uhkummn9ekx7mqzyqhdhn4xjngkgc5c2jjjtq693ltdjed3v83ufz6h6whlqx2q2kyggqcyqqqqqqgxxkuf0
Thank you, was curious about this.
Getting forced closed in mutiny creates a bad impression.
I understand why they did it.
Hope this doesn't turn into another Samurai/Wasabi BS soap opera drama.
Figure it out people!
TLDR: Growing pains from building culture and tech at same time. All want same thing but have different perspectives. Creativity cant exist without conflict I dont think. This was pretty healthy all things considered.
-Community now knows about the risk more broadly.
-Projects came to compromise that respects (grudgingly) both perspectives.
-Nostr gets better. Tick tock like a block.
nostr:note14zpv7cx26ltd268ztx4ekjcd8sqzasfexc9mrj9mw227uhr6l90s6h5rap
Oddbean new post about login | logout 