We've released Mutiny version v0.5.7 which includes two notable changes.

Payjoin v1 support has been added. Huge credit to nostr:npub1yevrvtp3xl42sq06usztudhleq8pdfsugw5frgaqg6lvfdewfx9q6zqrkl over the last few months, for the improvements to the PDK library and getting it included into Mutiny! Thanks to Ben Allen too for testing.

We're really excited about the privacy gains here and for future improvements such as Payjoin v2. This should allow asynchronous payjoins, making it possible for a mobile user to payjoin with another mobile user.

We've also made some underlying changes to how NWC works in Mutiny. We've switched over all new connections to use our new strfry based relay instead of using the Blastr. This should greatly improve performance and speed, in addition to being able to better support consumer apps.

You may continue using your existing NWC connections, but for better reliability, you can delete existing wallet connections to recreate them on the new relay.

In the coming months, we should have a load of new nostr related features as well. Stay tuned!

Reply to this note

Please Login to reply.

Discussion

Like always, AMAZING NEWS 🔥🚀🤙

nostr:note1xkz6gtymgx76rqd3h2ffyaagym3q3mk4dmrpwn95vac26mkdl37q2nf4y7

Where can I find some information about Payjoin v1 functionality in Mutiny ?

What would you like to know? You can now pay payjoin merchants.

Payjoinってなんだ…?

nostr:note1xkz6gtymgx76rqd3h2ffyaagym3q3mk4dmrpwn95vac26mkdl37q2nf4y7

Payjoin is very important to make on-chain transactions more accessable in the future.

LFG!

Very cool.

Just thought about how we could have automated subscriptions not only for Mutiny but also for donations/support to FOSS third parties like GrapheneOS, or even just to regular anons or devs we want to support. Maybe Mutiny could offer such a service?

You can subscribe to anyone with zapplepay.com

Thanks for the pointer!

Love the progress, looking forward to using mutiny more. At this point there have been too many cool developments to ignore.

Congratulations on your work Mutiny 🤗

Wow nice 🤩

I missed a few updates. Is it possible to receive zaps with Mutiny ?

nope

Hopefully soon ™

Very nice, love what you guys are doing once I watch YouTube videos of smart people explain to me what it is exactly.

so freaking awesome

This is a really cool project! I didn't understand it when it first came out but I am catching on quickly and enjoying using your wallet

Payjoin via lightning?! This was a test from our website, which has payjoin enabled…but from your lightning wallet?! 🤯

nostr:npub1yevrvtp3xl42sq06usztudhleq8pdfsugw5frgaqg6lvfdewfx9q6zqrkl whoa!

That might be a bug. Does your shop show bip21 invoices with the payjoin info and lightning info at the same time?

Yes…it was a unified qr

This is awesome! I am bullish on Bitcoin privacy because of efforts like this.

That's cool 😎

Payjoin is our best hope for on chain privacy. I'm so happy y'all are building this functionality. 🧡

Where can I learn more about the payjoin feature? Is there a good resource that details what is actually going on with a payjoin and what circumstances must be met to make it possible?

Let me know what you think of https://payjoin.org so that it addresses your exact questions

How is a payjoin coordinated between different wallets? Can a payjoin happen between sparrow and mutiny?

Basically, payjoin is a way to coordinate multiple users inputs and outputs into one transaction? Is there a way for participants of payjoins to select inputs and outputs?

Payjoin is coordinated by end to end encrypted messages transmitted over the internet between sender and receiver. The protocol is specified in BIP 78 and BIP 77. Neither sparrow nor Mutiny support receiving payjoin yet (but stay tuned)

Payjoin enables exactly what you’ve described, multiple inputs and outputs from each user may be batched into a single transaction. Input selection depends on the wallet implementation but is not limited by the payjoin protocol itself. What selection do you have in mind?

Okay cool, I think I get it.

As far as selection goes, the more options the better. The use case I have in mind is for transactions at Bitcoin meetups. A large single transaction could be built coordinating many of the transactions taking place at the meetup simultaneously.

For example, I sell maple syrup from one individual and buy coffee from another. This could be one payjoin transaction? Could the participants in the transaction choose to consolidate utxos as well?

How does signing work? Would the users be looking at the same payjoin transaction on each of their wallets and hit send at the same time?

I’m not sure of any UI that yet enables this fine grained queueing and batching you’re describing but it’s certainly possible. sender would propose their batch, receiver would respond with theirs, combined and signed, and the sender would take a final sign off if all looks good. Should be the same flow you’re used to for any other tx in terms of signing, but both would set up queues or batches in their respective wallets beforehand to consolidate or otherwise batch funds beforehand. nostr:npub1yashrajtj3ddn9u2ypzalp4qew4f9u8wls0tpf5kuvqarenqwckql8adnu might have some design input