Avatar
Kruw
0b9de7c5e82d26c285690a13cd164149a5a0ee3131b9912e1c0bb36c66b471ab
Taxes are a scam. Inflation is a stealth tax. Bitcoin fixes this.

If a coordinator refuses to include your UTXO because of a chain analysis company's opinion, you can use a different coordinator or run your own since everything is open source. Wasabi is designed so there is never a risk to the user's data even if the coordinator is malicious.

Replying to Avatar OpenSecret

Just released Mutiny version 0.4.6 for both android and on the web. This release solves two big issues we've been seeing on Mutiny so far, so we appreciate all the testing and patience using the app so far. One area is for multi-device access and the other is on payment reliability.

One area we have solved relates to users that try to run the same wallet in multiple spots at the same time. We had already incorporated VSS to allow for encrypted cloud backups for Lightning data, but some users have been too eager and have ran it at multiple locations, causing force closes to happen. With this release, we use VSS to assign a timestamp lock for 2 minutes so that multiple instances can't use the same wallet.

This makes sure that one instance is closed before another runs. In the future we will allow overrides for this, and in a further away future we will make it safe to simultaneously run any instance of Mutiny across any browser, device, or application.

Another much needed feature is that we have now started shipping a more-updated view of the network to increase payment reliability. Lightning routing is difficult, but many applications solve it by probing the network to find paths. There's about 70k public channels that exist right now and many are either inactive or depleted in one of the directions.

No need for user wallets to aimlessly guess paths that might work, we probe the network ourselves and ship the same state to all. Allowing for more efficiency and reusability for path finding. This will work with any LDK-based wallet too, so it's something we could potentially offer other wallets in the future.

The framework for the remote scorer is now live, but there will be plenty of efficiency and accuracy improvements to make over time on the backend. If there's any particular destinations and amounts you're struggling with for Mutiny after this release, please let us know and we'll be sure to add them to our probing list.

We don't see payments or destinations, so we can only go off of user feedback. With this new probing tool, we should be able to detect problems reaching destinations quicker, and provide suggestions to LSPs for maintaining their channels over time.

Let us know how the new update is working and if there's any other problems you have been seeing! Also, in case you missed it last week, we now have android support that we are testing. Be sure to check it out if you're intested: https://github.com/MutinyWallet/mutiny-web/releases/tag/v0.4.6-1

How do I know if I've upgraded? I can't find the version number in my client.

Having UTXOs of many different sizes is an advantage because you can create combinations of inputs that closely match the amount you are trying to pay without generating a change output. Wasabi Wallet makes your smallest coinjoin outputs flexible this way -

You should try a WabiSabi coinjoin with Trezor, BTCPay Server, or Wasabi Wallet. There's no coordinator fee for inputs under 1 million sats, and less block space/mining fees required.

You should try Wasabi Wallet. UTXO management is even easier since they are consolidated privately in coinjoins. Since there is no "unmixed change", there is no bad bank necessary.

Lots of things are very wrong in that chart. For example, Wasabi doesn't have change outputs at all, has a flat fee, has free remixing, has postmix spending tools, etc.

"Labor and leisure are complimentary human actions that pertain to production and consumption of economic goods" - Eric Voskuil, Cryptoeconomics

Wasabi Wallet (desktop only): It's private by default since it uses compact block filters to mask your xpub address and Tor to mask your IP address. It protects your on chain privacy with coinjoins.

Blixt Wallet (mobile only): Uses compact block filters as well, with optional Tor. It has Lightning (lnd) for making fast/cheap payments off chain.

Sending all 4 UTXOs together is the least private way to spend them since that would give a clue indicating the total amount you registered for that round, but it would not be fully effective since there are many input combinations that add up to that amount. Spending the private UTXOs individually or remixing them before sending your entire balance is the best way to handle them.