Avatar
OT
86c79e5aa8c41f68c9a238858b08c4d63c1b0ce6d4fa96d32a90df25bd83b072
A Bitcoin guy.
Replying to Avatar The Nostr Report

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

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!

I've been waiting for a long form nostr client. I'd like to have one for short posts & news, another for long form. Sometimes you click 'more' on a Lyn Alden post & a book scrolls down.

https://geyser.fund/project/payjoin

This is one project well worth supporting. I'd love to see more wallets adopting payjoin to keep transacting on chain private.

It would make things simple. After an initial conjoin there would be no need for any postmix gymnastics. Just a simple obfuscation with a few inputs.

Replying to Avatar MAHDOOD

Check it the liquid fees at the moment

Love the fee on liquid!

Its lower than lightning

Replying to Avatar Dan Gould

What is Payjoin V2, why do we need it now, and how does it make payjoin so much easier to support?

Basic #bitcoin transactions are non-interactive. An address is all a sender needs to send bitcoin.

The trade off is that only the sender can contribute inputs that the receiver must consolidate later, and third parties assume all transaction inputs come from just one sender.

Payjoin peers instead interact before they broadcast a transaction. That way they both can spend inputs in a batch. Batch transactions share fixed fees and save money. They break probability analysis used to track bitcoin.

However, V1 receivers must host a server online.

Payjoin V2 peers may go on and offline and still make a payjoin. V2 lets even web wallets receive payjoin any time to optimize for fees and default to better privacy.

An oblivious third-party directory hosts a server instead. The directory can't steal or even see peer IP addresses.

Oblivious HTTP keeps IP addresses private. It works like Tor with just 2 hops on a pre-defined route.

The OHTTP Relay just sees encapsulated requests.

The Payjoin Directory sees requests without Client IPs.

The Directory can't see request PSBT contents. They're encrypted too.

Payjoin V2 keeps message contents private between sender and receiver without involving a certificate authority. The Payjoin Directory cannot see transaction details.

Hybrid Public Key Encryption makes end-to-end authenticated encryption with tools already native to Bitcoin.

Payjoin only works when we choose to support it. Join me by paying this knowledge forward.

Special thanks to BitDevs NYC for giving these slides their first audience.

What phase are we in? Still testing?

This is perfect for on chain TX post coin join.

No

That's the coinbase

Replying to Avatar UNCLE ROCKSTAR

Amidst what's going on lately, I thought it might be a good time to remind everyone that nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg supports both PayJoin and CoinJoin.

So if you're running a BTCPay instance, you can:

1. Withdraw Bitcoin from exchanges with PayJoin, obscuring the amount to outside observers.

2. Auto-initiate CoinJoin when certain conditions are met (desired Bitcoin amount and fee market).

Bonus: You can easily run your own coordinator, mixing your Bitcoin without using mainstream services and coordinators.

This could be a great asset for local communities with regular Bitcoin flows (e.g., DCA of members) to boost privacy collectively.

The best part? It takes about 20 minutes to set up. I'm considering creating a video guide - would you watch it if I did?

Payjoin from an exchange?