Can someone explain to me how I can make a CoinCoin transaction myself?
Do I understand correctly that when creating a transaction I need to add, say, 15 of my own btc addresses taken inside my Electrum wallet - with random amounts and returning the balance to the original bitcoin address using bc132131exempl, using the function (!)
And before creating a transaction, do I need to make sure that funds are sent to these addresses from 15 btc addresses? That is, I need to distribute the wallet balance into small amounts in advance. It’s just that in this case you will need at least two transactions, one for preparation, the second for CoinJoin.
Topic: Wasabi Wallet - Open Source, Noncustodial Coinjoin Software - page 35. (Read 10963 times)
A mobile version is on the roadmap, but there's no immediate plans to build one.
Hi Kruw !
Thanks for the answers !
I will submit a request for a function to select a folder for installation - it seems to me to be a standard function, for applications.
Portable version is a little bit different, it is not mobile, but "portable", which is installed not through the installer, but conditionally speaking, by unpacking the archive into a folder selected by the user, bypassing the process of classic installation.
Portable version is very nice.
You can put it in a pen drive, or at some cloud service , email, etc... it might be handy when you are aware of the risks.
Even electrum has one.
https://bitcointalksearch.org/topic/warning-about-portable-versions-154451
And now the questions:
1. I once long ago already asked a question, or wanted to ask ... Are there considered variants of release of versions under ARM ? Or the software uses instruction sets of x86/AMD64 architecture?
1. I once long ago already asked a question, or wanted to ask ... Are there considered variants of release of versions under ARM ? Or the software uses instruction sets of x86/AMD64 architecture?
Yes, here's the supported versions: https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-architectures
Here's an issue tracking ARM support: https://github.com/zkSNACKs/WalletWasabi/issues/4051
2. Why is there no folder selection in the installer?
There is an open feature request for this - https://github.com/zkSNACKs/WalletWasabi/issues/3456
3. Is a portable version planned?
A mobile version is on the roadmap, but there's no immediate plans to build one.
Hi Kruw !
Thanks for the answers !
I will submit a request for a function to select a folder for installation - it seems to me to be a standard function, for applications.
Portable version is a little bit different, it is not mobile, but "portable", which is installed not through the installer, but conditionally speaking, by unpacking the archive into a folder selected by the user, bypassing the process of classic installation.
3. Is a portable version planned?
A mobile version is on the roadmap, but there's no immediate plans to build one.
By portable version, i think he actually mean something like AppImage file or single executable file (which open Wasabi when use run it).
And now the questions:
1. I once long ago already asked a question, or wanted to ask ... Are there considered variants of release of versions under ARM ? Or the software uses instruction sets of x86/AMD64 architecture?
1. I once long ago already asked a question, or wanted to ask ... Are there considered variants of release of versions under ARM ? Or the software uses instruction sets of x86/AMD64 architecture?
Yes, here's the supported versions: https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-architectures
Here's an issue tracking ARM support: https://github.com/zkSNACKs/WalletWasabi/issues/4051
2. Why is there no folder selection in the installer?
There is an open feature request for this - https://github.com/zkSNACKs/WalletWasabi/issues/3456
3. Is a portable version planned?
A mobile version is on the roadmap, but there's no immediate plans to build one.
Hi everyone !
I configured a new laptop, at one time put Wasabi-2.0.6
First of all the description of the changes is impressive ! It's not often to find a product whose release is similar to a new minor version in terms of fixes/improvements
And now the questions:
1. I once long ago already asked a question, or wanted to ask ... Are there considered variants of release of versions under ARM ? Or the software uses instruction sets of x86/AMD64 architecture ?
2. Why is there no folder selection in the installer ?
3. Is a portable version planned ?
I configured a new laptop, at one time put Wasabi-2.0.6
First of all the description of the changes is impressive ! It's not often to find a product whose release is similar to a new minor version in terms of fixes/improvements
And now the questions:
1. I once long ago already asked a question, or wanted to ask ... Are there considered variants of release of versions under ARM ? Or the software uses instruction sets of x86/AMD64 architecture ?
2. Why is there no folder selection in the installer ?
3. Is a portable version planned ?
According to the new release of Wasabi Wallet v2.0.6 - Juggernaut, the application has received new features:
1. Now the wallet supports new hardware wallets - Blockstream Jade and BitBox02.
2. The Safety Coinjoin function has appeared, which
4. The overall performance of the application has improved. Reduced wallet loading time by 60%.
5. Improved user interface. You can rename the wallet directly from the interface.
6. New PGP key for secure reporting of software vulnerabilities.
7. Also several other minor improvements.
Releases · zkSNACKs/WalletWasabi (github.com)
1. Now the wallet supports new hardware wallets - Blockstream Jade and BitBox02.
2. The Safety Coinjoin function has appeared, which
Quote
ensures a minimum of two rounds of coinjoin for the first Bitcoin deposit into an empty wallet, preventing common coin consolidation pitfalls.
3. RPC Server Improvements: The RPC Server now offers 11 new calls.4. The overall performance of the application has improved. Reduced wallet loading time by 60%.
5. Improved user interface. You can rename the wallet directly from the interface.
6. New PGP key for secure reporting of software vulnerabilities.
7. Also several other minor improvements.
Releases · zkSNACKs/WalletWasabi (github.com)
Safety coinjoins are a new default behavior in Wasabi 2.0.6 that protect users from spending their coins in a noticeable way. Check out this new blog to learn the details: https://blog.wasabiwallet.io/exploring-secure-coinjoin-protocols/
Then, I learned the real website is https://blog.wasabiwallet.io/
Yes, there are many phishing sites that appear in search results.
Apart from this, there is nothing more precise or a log about what changes the new update brings? "Many more cool improvements" can mean anything
There will be several blog posts explaining the improvements in this version. There's a lot of of subtle behavior changes that make the wallet "smarter" about when to coinjoin and when not to coinjoin, performance improvements so there's less loading and less CPU/GPU consumption, UI polish, and codebase cleanup that will make future development more productive.
I will make an alert for everyone.
I was looking for your blog, and then a found a phising site . Luckily, phantom wallet (browser extension) told me about it.
This was the first Bing result when searching for 'wasabi blog android app"
Then, I learned the real website is https://blog.wasabiwallet.io/
I believe that it will be in the future, but I prefer to see all the changes brought by an update before I accept it. Regardless of the type of software, each new update brings a certain type of risk because it has not been fully tested in live use.
Wasabi v2.0.6 "Juggernaut" just went live! Here's the full changelog... there's 527 PRs merged
Read more about the new update in the announcement post: https://blog.wasabiwallet.io/wasabi-latest-release-2-0-6-is-out/
Download Wasabi: https://wasabiwallet.io/#download
There will be several blog posts explaining the improvements in this version. There's a lot of of subtle behavior changes that make the wallet "smarter" about when to coinjoin and when not to coinjoin, performance improvements so there's less loading and less CPU/GPU consumption, UI polish, and codebase cleanup that will make future development more productive.
I believe that it will be in the future, but I prefer to see all the changes brought by an update before I accept it. Regardless of the type of software, each new update brings a certain type of risk because it has not been fully tested in live use.
Apart from this, there is nothing more precise or a log about what changes the new update brings? "Many more cool improvements" can mean anything
There will be several blog posts explaining the improvements in this version. There's a lot of of subtle behavior changes that make the wallet "smarter" about when to coinjoin and when not to coinjoin, performance improvements so there's less loading and less CPU/GPU consumption, UI polish, and codebase cleanup that will make future development more productive.
The new version of Wasabi Wallet is in the final stages of development, you can test the release candidate here - https://github.com/adamPetho/WalletWasabi/releases/tag/v2.0.6-RC4
Apart from this, there is nothing more precise or a log about what changes the new update brings? "Many more cool improvements" can mean anything
Quote
Release Highlights
Super-fast start up time 🚀
RPC improvements 🤖
UI improvements ✨
Avalonia update 🆙
Bug fixes 🐞
Blockstream Jade integration 🛠️
BitBox implementation 🛠️
Many more cool improvements 😎
Super-fast start up time 🚀
RPC improvements 🤖
UI improvements ✨
Avalonia update 🆙
Bug fixes 🐞
Blockstream Jade integration 🛠️
BitBox implementation 🛠️
Many more cool improvements 😎
The new version of Wasabi Wallet is in the final stages of development, you can test the release candidate here - https://github.com/adamPetho/WalletWasabi/releases/tag/v2.0.6-RC4
It's decent idea, phone usually use more battery when there's no strong mobile signal. I don't know how it can be implemented either, but i believe Wasabi team have sufficient technical skill to do that. Although i wonder how much battery can be saved when you use Wifi rather than mobile internet.
This option exists, but not so much to save the battery, but when it comes to updating applications, and the purpose is to avoid downloading too large files over the mobile Internet because these are often limited by mobile providers with such data consumption.
As far as I know, multimedia is the biggest drainer of the battery, and in the mentioned Wasabi case, it would only be text communication, so that part should not be a problem for battery capacity. For the application, I assume that some kind of customized Tor bridge could do something like this with minimum requirements.
While it's true smartphone hardware become more powerful, it's not the only limitation. Theoretically, Wasabi Wallet need to run in background while connected to the CoinJoin coordinator and doing some stuff (choose input, sign transaction, etc.). And since Wasabi Wallet use Tor by default, Tor also need to run in background. I expect it could drain battery quickly and the OS show warning about it. CMIIW.
What if, when you first launch the application, you can prompt the user to select by default what type of connection will be used to connect (for example, only Wifi). I know that this can be done in the phone settings, but few people worry about it.And the mobile Internet will be used “only when using the application.” My point is that if the mobile Internet is not used to work in the background, then this will not affect the battery drain in any way.
Although, to be honest, I'm not sure how to implement this.
It's decent idea, phone usually use more battery when there's no strong mobile signal. I don't know how it can be implemented either, but i believe Wasabi team have sufficient technical skill to do that. Although i wonder how much battery can be saved when you use Wifi rather than mobile internet.
While it's true smartphone hardware become more powerful, it's not the only limitation. Theoretically, Wasabi Wallet need to run in background while connected to the CoinJoin coordinator and doing some stuff (choose input, sign transaction, etc.). And since Wasabi Wallet use Tor by default, Tor also need to run in background. I expect it could drain battery quickly and the OS show warning about it. CMIIW.
What if, when you first launch the application, you can prompt the user to select by default what type of connection will be used to connect (for example, only Wifi). I know that this can be done in the phone settings, but few people worry about it.And the mobile Internet will be used “only when using the application.” My point is that if the mobile Internet is not used to work in the background, then this will not affect the battery drain in any way.
Although, to be honest, I'm not sure how to implement this.
--snip--
When was that comment about smartphones originally made, and how have smartphones of today have become more powerful since the original announcement? I believe some smartphone hardware might be starting to reach the capability of what some software requires of it to function like a desktop, no?Although the smartphone's OS could be limiting, especially Apple's smartphones.
While it's true smartphone hardware become more powerful, it's not the only limitation. Theoretically, Wasabi Wallet need to run in background while connected to the CoinJoin coordinator and doing some stuff (choose input, sign transaction, etc.). And since Wasabi Wallet use Tor by default, Tor also need to run in background. I expect it could drain battery quickly and the OS show warning about it. CMIIW.
I would certainly use an android app of wasabi wallet.
Is there any release date for a possible mobile app? I think mobile users are many, and allow users to use wasabi in the phone would be very good.
Is there any release date for a possible mobile app? I think mobile users are many, and allow users to use wasabi in the phone would be very good.
A mobile app is on the roadmap, but it's not currently in the building stage yet. A lot of code maintenance was completed to make it easier to implement though.
This FAQ answer your question, although i recall it's created few years ago.
Is there an Android/iOs version?
No, Wasabi and CoinJoin features require considerable computational power, not currently replicable on a smartphone.
No, Wasabi and CoinJoin features require considerable computational power, not currently replicable on a smartphone.
One short term option is to launch a mobile Wasabi app that connects to your Wasabi desktop running at home, similar to how Zeus used to only work as a mobile interface for your remote Lightning node.
When was that comment about smartphones originally made, and how have smartphones of today have become more powerful since the original announcement? I believe some smartphone hardware might be starting to reach the capability of what some software requires of it to function like a desktop, no?
Although the smartphone's OS could be limiting, especially Apple's smartphones.
Jump to: