Wondering what all the commotion was about yesterday with Mutiny and Zeus? Here’s our summary of what happened.

nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg stirred up some controversy yesterday after announcing their decision to disable the ability to zap nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 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

nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s , 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