1. the ultimate cyperpunky setup feat. Bisq, raspibolt and wasabi by Stadicus
2. really cool wasabi tshirt designs by andhans
Topic: Wasabi Wallet 1.0 Is Released - page 4. (Read 4066 times)
here is some really cool wasabi stuff i just found on the official twitter account: https://twitter.com/WasabiWallet
1. the ultimate cyperpunky setup feat. Bisq, raspibolt and wasabi by Stadicus
2. really cool wasabi tshirt designs by andhans
1. the ultimate cyperpunky setup feat. Bisq, raspibolt and wasabi by Stadicus
2. really cool wasabi tshirt designs by andhans
Just a quick question to the OP (or anybody else that knows the answer for that matter).
Why does my gut feeling tells me the minimum amount to participate in coinjoins only seems to go up?
In all fairness, i get why you don't want to have 0.001 BTC as minimum amount, you've promoted the coinjoin feature to be very cost-effective, and if you're building giant coinjoin transactions with a huge amount of inputs and outputs that have a value of ~0.001 BTC, you can't say you'll have a fee of 0.003% per anonimity set, and you wouldn't help your enduser nor the blockchain by creating thousands of 0.001-valued unspent outputs.
However, there's a big difference between 0.001 (~$8) and the current ~0.11 (~$850), and the fact that my gut feeling tells me it's just going upwards regardless of the average fee per vbyte or the fiat exchange rate makes me worry what minimum amounts we'll see in the future (i don't think that at this rate it'll take very long before we breach the minimum $1000 equivalent as a minimum amount to participate in a coinjoin).
Could the developers give some extra insight if they plan to make coinjoin more accessible for the broad public (people that don't have 0.11 BTC, or are unwilling to "test" out coinjoining with such a large chunk of money)? I, for one, wouldn't mind paying more than (0.003 * 51)% if that would mean i could participate in a coinjoin with 0.05 BTC instead of 0.11 BTC
I've found discussions on reddit talking about this subject, but i didn't really feel they completely answered my question (for example: https://www.reddit.com/r/WasabiWallet/comments/c2sizh/coinjoin_minimum_of_approximately_1100aud/)
Why does my gut feeling tells me the minimum amount to participate in coinjoins only seems to go up?
- IIRC, the first time i looked at the wallet, the minimum amount was pretty low (my memory tells me it was like ~0.01, but i could be waaaay of).
- The first time i actually wanted to participate in a coinjoin, the minimum amount rose to ~0.05 (IIRC), while at the same time the price also went waaaay up. Since, at that point, i didn't want to risk 0.05, i used a trusted mixer instead
- The first time i actually participated in a coinjoin, the minimum amount was ~0.09
- At this moment, the minimum amount is ~0.11
In all fairness, i get why you don't want to have 0.001 BTC as minimum amount, you've promoted the coinjoin feature to be very cost-effective, and if you're building giant coinjoin transactions with a huge amount of inputs and outputs that have a value of ~0.001 BTC, you can't say you'll have a fee of 0.003% per anonimity set, and you wouldn't help your enduser nor the blockchain by creating thousands of 0.001-valued unspent outputs.
However, there's a big difference between 0.001 (~$8) and the current ~0.11 (~$850), and the fact that my gut feeling tells me it's just going upwards regardless of the average fee per vbyte or the fiat exchange rate makes me worry what minimum amounts we'll see in the future (i don't think that at this rate it'll take very long before we breach the minimum $1000 equivalent as a minimum amount to participate in a coinjoin).
Could the developers give some extra insight if they plan to make coinjoin more accessible for the broad public (people that don't have 0.11 BTC, or are unwilling to "test" out coinjoining with such a large chunk of money)? I, for one, wouldn't mind paying more than (0.003 * 51)% if that would mean i could participate in a coinjoin with 0.05 BTC instead of 0.11 BTC
I've found discussions on reddit talking about this subject, but i didn't really feel they completely answered my question (for example: https://www.reddit.com/r/WasabiWallet/comments/c2sizh/coinjoin_minimum_of_approximately_1100aud/)
I don't understand why I can't run Wasabi wallet via Turkey's internet connection. Is there anyone who has the similar problem here?
Additional information: I have to select obsf4 bridge to run Tor Browser because Tor is censored in my country.
Additional information: I have to select obsf4 bridge to run Tor Browser because Tor is censored in my country.
Do you install Tor on your system? Wasabi Wallet will try to use Tor which is installed on your system, before using Tor which included on Wasabi Wallet.
If not, please try install Tor and configure it to use one of obfs4 bridge you know, then try to run Wasabi wallet again.
Max Hillebrand posted a call to participate in the Merchandise Design Contribution Game #76 on telegram some hours ago:
Telegram:
Github:
Telegram:
Quote
Three questions...
1] want to stack sats?
2] want to contribute to Bitcoin privacy and Wasabi?
3] are You an artist?
then create beautiful designs and earn up to 0.1 bitcoin!
https://github.com/zkSNACKs/Meta/issues/76
1] want to stack sats?
2] want to contribute to Bitcoin privacy and Wasabi?
3] are You an artist?
then create beautiful designs and earn up to 0.1 bitcoin!
https://github.com/zkSNACKs/Meta/issues/76
Github:
Quote
We would like to collaborate with artists to create beautiful merchandise that reflects the values of Bitcoin privacy and the Wasabi brand. In order to reward the peers who craft these, there will be yet another Contribution Game!
The Task
Create a design that is a piece of art, not just the Wasabi logo. It may reflect the topic of privacy in general, Bitcoin and Wasabi specifically. There are no clear guideline, let Your imagination fly.
The art will be displayed on:
T-Shirts
Hoodies
Stickers
Hats
Facemasks
Mugs
whatever else You come up with
We will then print the design in large quantities, and distribute them to other Wasabikas.
The bounty
zkSNACKs has offered a budget of up to 0.1 bitcoin [yes, 10 MILLION coinjoined satoshis!!]. It will be granted to those who provide the most beautiful designs. The exact amount distributed will depend on the quantity of participating artists, and the quality of their work. The jury is the zkSNACKs team and the Wasabi community in a transparent decision-making process.
Who can participate?
Anyone! Simply send us Your design suggestions on Twitter, Reddit, Telegram or under this issue.
The Task
Create a design that is a piece of art, not just the Wasabi logo. It may reflect the topic of privacy in general, Bitcoin and Wasabi specifically. There are no clear guideline, let Your imagination fly.
The art will be displayed on:
T-Shirts
Hoodies
Stickers
Hats
Facemasks
Mugs
whatever else You come up with
We will then print the design in large quantities, and distribute them to other Wasabikas.
The bounty
zkSNACKs has offered a budget of up to 0.1 bitcoin [yes, 10 MILLION coinjoined satoshis!!]. It will be granted to those who provide the most beautiful designs. The exact amount distributed will depend on the quantity of participating artists, and the quality of their work. The jury is the zkSNACKs team and the Wasabi community in a transparent decision-making process.
Who can participate?
Anyone! Simply send us Your design suggestions on Twitter, Reddit, Telegram or under this issue.
I don't understand why I can't run Wasabi wallet via Turkey's internet connection. Is there anyone who has the similar problem here?
Additional information: I have to select obsf4 bridge to run Tor Browser because Tor is censored in my country.
Additional information: I have to select obsf4 bridge to run Tor Browser because Tor is censored in my country.
if you want to contribute your skills and time to improve the wasabi wallet code and documentation check this link to learn how to get involved:
https://docs.wasabiwallet.io/building-wasabi/ContributionChecklist.html
https://docs.wasabiwallet.io/building-wasabi/ContributionChecklist.html
Since you're so responsive, this is the speed the filters are built:
Also note there'll be a power outage here in 15 minutes, so I probably won't see the results of it for a while.
Code:
2020-01-22 13:37:55 INFO IndexBuilderService (295) Created filter for block: 1639200.
2020-01-22 13:39:04 INFO IndexBuilderService (295) Created filter for block: 1639300.
2020-01-22 13:40:13 INFO IndexBuilderService (295) Created filter for block: 1639400.
2020-01-22 13:41:21 INFO IndexBuilderService (295) Created filter for block: 1639500.
2020-01-22 13:42:30 INFO IndexBuilderService (295) Created filter for block: 1639600.
2020-01-22 13:43:41 INFO IndexBuilderService (295) Created filter for block: 1639700.
2020-01-22 13:44:50 INFO IndexBuilderService (295) Created filter for block: 1639800.
2020-01-22 13:39:04 INFO IndexBuilderService (295) Created filter for block: 1639300.
2020-01-22 13:40:13 INFO IndexBuilderService (295) Created filter for block: 1639400.
2020-01-22 13:41:21 INFO IndexBuilderService (295) Created filter for block: 1639500.
2020-01-22 13:42:30 INFO IndexBuilderService (295) Created filter for block: 1639600.
2020-01-22 13:43:41 INFO IndexBuilderService (295) Created filter for block: 1639700.
2020-01-22 13:44:50 INFO IndexBuilderService (295) Created filter for block: 1639800.
Also note there'll be a power outage here in 15 minutes, so I probably won't see the results of it for a while.
Actually I don't need it, as I got the same report from someone else, too. Turns out on the coordinator side the filters on the testnet got stuck at block 1639121. While according to SmartBit the latest block is 1663495. This happened like 2-3 times on the testnet before, as testnet is often acting crazy. I restarted it, it should catch up in a few minutes.
Perfect
Let's do some more testing now!
Thanks
Actually I don't need it, as I got the same report from someone else, too. Turns out on the coordinator side the filters on the testnet got stuck at block 1639121. While according to SmartBit the latest block is 1663495. This happened like 2-3 times on the testnet before, as testnet is often acting crazy. I restarted it, it should catch up in a few minutes.
Since it's a testnet wallet, can you share your extpubkey? With this we can avoid back and forth debugging. In the wallet file there's a line:
Code:
"ExtPubKey": "xpub12234"
No problem, like you say: it's a testnet wallet
Code:
"ExtPubKey": "xpub6DWrfCFdchVSbJ8vTprYwoXwy3Z8rucCS7Kv24WgFdexQWuayE36ARNGNdbc8xktgbn5WnVVoW15qWCSLXcJVnqYz4e6uizNLjX4TSFdJQu",
Like i said: no harm was done, it's all on the testnet, and i can use electrum to recover my unspent outputs (sufficiently large tBTC outputs are hard to come by nowadays), but i tought it would be good if i didn't give up on wasabi, but rather tried to give you the info you need to find the problem.
Since it's a testnet wallet, can you share your extpubkey? With this we can avoid back and forth debugging. In the wallet file there's a line:
Code:
"ExtPubKey": "xpub12234"
I realise this isn't the default support channel, but since i'm not a redditor and the lead dev seems to visit this thread once in a while, i decided to post my question here
I found some strange behaviour on the TESTNET, i didn't lose anything, not even TESTNET coins, but if i weren't on the TESTNET, my heart would have skipped a beat.
The setup:
OS: Ubuntu 16.04.6 LTS
Wasabi version: 1.1.10.2
Tor Disabled
Local node enabled
bitcoin core is sync'ed
backend is connected
I have funded, and moved around a couple addresses with some tBTC, then closed the gui and waited for a clean shutdown.
Afterwards, i restarted wasabi, waited untill the node was up and running again, opened my wallet.... Aaaand.... No funds
I restored the wallet in electrum and see all those transactions funding my addresses... But in wasabi: nothing.
However, when i create a new address, the key path is 84'/0'/0'/0/9. So Wasabi knows it already derived 8 addresses and they were funded, but it decided not to show those transactions funding those first 8 addresses...
If i fund address 84'/0'/0'/0/9 (tb1q57p5taq0dvlpm7url7n2kdh90h5n2mug5aays3), the transaction shows up, but it remains unconfirmed (eventough core is synchronised and the backend is connected, and the transaction IS in fact confirmed)... (i messed up and send 1 mtBTC instead of 1BTC, but this isn't the problem, i funded the other 8 addresses with inputs of up to 5 tBTC)
I used an unspent output funding a previously derived wasabi address to fund address 84'/0'/0'/0/9, and wasabi detected the transaction that funded both 84'/0'/0'/0/9 AND the change address 84'/0'/0'/1/1
Soooo... Basically, i ended up with wasabi telling me i have a wallet with 0.00129791 tBTC, 2 unspent outputs from one transaction... While electrum tells me this wallet is funded with 5.57983242 tBTC, 6 unspent outputs funding 6 addresses (including 2 change addresses).
If i close wasabi and re-open it, i'm sure that wasabi will tell me i have an empty wallet (already tested this a couple times before to confirm the behaviour).
I found some strange behaviour on the TESTNET, i didn't lose anything, not even TESTNET coins, but if i weren't on the TESTNET, my heart would have skipped a beat.
The setup:
OS: Ubuntu 16.04.6 LTS
Wasabi version: 1.1.10.2
Tor Disabled
Local node enabled
bitcoin core is sync'ed
backend is connected
I have funded, and moved around a couple addresses with some tBTC, then closed the gui and waited for a clean shutdown.
Afterwards, i restarted wasabi, waited untill the node was up and running again, opened my wallet.... Aaaand.... No funds
I restored the wallet in electrum and see all those transactions funding my addresses... But in wasabi: nothing.
However, when i create a new address, the key path is 84'/0'/0'/0/9. So Wasabi knows it already derived 8 addresses and they were funded, but it decided not to show those transactions funding those first 8 addresses...
If i fund address 84'/0'/0'/0/9 (tb1q57p5taq0dvlpm7url7n2kdh90h5n2mug5aays3), the transaction shows up, but it remains unconfirmed (eventough core is synchronised and the backend is connected, and the transaction IS in fact confirmed)... (i messed up and send 1 mtBTC instead of 1BTC, but this isn't the problem, i funded the other 8 addresses with inputs of up to 5 tBTC)
I used an unspent output funding a previously derived wasabi address to fund address 84'/0'/0'/0/9, and wasabi detected the transaction that funded both 84'/0'/0'/0/9 AND the change address 84'/0'/0'/1/1
Soooo... Basically, i ended up with wasabi telling me i have a wallet with 0.00129791 tBTC, 2 unspent outputs from one transaction... While electrum tells me this wallet is funded with 5.57983242 tBTC, 6 unspent outputs funding 6 addresses (including 2 change addresses).
If i close wasabi and re-open it, i'm sure that wasabi will tell me i have an empty wallet (already tested this a couple times before to confirm the behaviour).
Code:
2020-01-21 14:21:12 INFO Program (44) Wasabi GUI started (be2de3a6-f9ee-428a-9b05-9aaf0f3a4cf7).
2020-01-21 14:21:15 INFO Global (164) Config is successfully initialized.
2020-01-21 14:21:15 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 4 milliseconds.
2020-01-21 14:21:15 INFO Global (230) TorProcessManager is initialized.
2020-01-21 14:21:15 INFO Global (418) Loaded AddressManager from `/home/wasabi/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat`.
2020-01-21 14:21:15 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2020-01-21 14:21:15 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 384 milliseconds.
2020-01-21 14:21:15 INFO AllTransactionStore (27) InitializeAsync finished in 389 milliseconds.
2020-01-21 14:21:18 INFO IndexStore (43) InitializeAsync finished in 3 seconds.
2020-01-21 14:21:18 INFO BitcoinStore (39) InitializeAsync finished in 3 seconds.
2020-01-21 14:21:19 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Connection refused
2020-01-21 14:21:19 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Verifying wallet(s)...
2020-01-21 14:21:19 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Loading block index...
2020-01-21 14:21:29 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Rewinding blocks...
2020-01-21 14:21:29 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Verifying blocks...
2020-01-21 14:21:31 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Loading wallet...
2020-01-21 14:21:32 INFO BitcoindRpcProcessBridge (52) RPC connection is successfully established.
2020-01-21 14:21:32 INFO CoreNode (164) Started Bitcoin Core.
2020-01-21 14:21:32 INFO CoreNode (48) CreateAsync finished in 13 seconds.
2020-01-21 14:21:32 INFO HostedServices (49) Started Software Update Checker.
2020-01-21 14:21:32 INFO HostedServices (49) Started Block Notifier.
2020-01-21 14:21:32 INFO HostedServices (49) Started RPC Monitor.
2020-01-21 14:21:32 INFO HostedServices (49) Started RPC Fee Provider.
2020-01-21 14:21:32 INFO Global (349) Start connecting to nodes...
2020-01-21 14:21:32 INFO Global (373) Start synchronizing filters...
2020-01-21 14:24:21 INFO Global (722) Wallet loaded: Wallet0.
2020-01-21 14:24:21 INFO ClientState (468) Round (33305) added.
2020-01-21 14:24:21 INFO ClientState (468) Round (33306) added.
2020-01-21 14:24:21 INFO Global (506) Start Chaumian CoinJoin service...
2020-01-21 14:24:21 INFO Global (508) Starting WalletService...
2020-01-21 14:24:21 INFO CoinJoinClient (141) CoinJoinClient is successfully initialized.
2020-01-21 14:24:22 INFO Global (510) WalletService started.
2020-01-21 14:28:46 INFO Global (661) Transaction Notification (Success): Received Replacable Transaction - 0.00129791 BTC - 3b98ecbb7c7fa5db5bb175b7bb883337a814548caa1bf3209651b0cacfa4dc07
2020-01-21 14:29:05 ERROR WasabiSynchronizer (305) Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 1, position 1.
at Newtonsoft.Json.JsonTextReader.ReadStringValue(ReadType readType)
at Newtonsoft.Json.JsonTextReader.ReadAsString()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value)
at System.Net.Http.HttpContentExtensions.ReadAsJsonAsync[T](HttpContent me)
at System.Net.Http.HttpResponseMessageExtensions.ThrowRequestExceptionFromContentAsync(HttpResponseMessage me)
at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<b__0>d.MoveNext()
2020-01-21 14:21:15 INFO Global (164) Config is successfully initialized.
2020-01-21 14:21:15 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 4 milliseconds.
2020-01-21 14:21:15 INFO Global (230) TorProcessManager is initialized.
2020-01-21 14:21:15 INFO Global (418) Loaded AddressManager from `/home/wasabi/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat`.
2020-01-21 14:21:15 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2020-01-21 14:21:15 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 384 milliseconds.
2020-01-21 14:21:15 INFO AllTransactionStore (27) InitializeAsync finished in 389 milliseconds.
2020-01-21 14:21:18 INFO IndexStore (43) InitializeAsync finished in 3 seconds.
2020-01-21 14:21:18 INFO BitcoinStore (39) InitializeAsync finished in 3 seconds.
2020-01-21 14:21:19 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Connection refused
2020-01-21 14:21:19 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Verifying wallet(s)...
2020-01-21 14:21:19 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Loading block index...
2020-01-21 14:21:29 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Rewinding blocks...
2020-01-21 14:21:29 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Verifying blocks...
2020-01-21 14:21:31 INFO BitcoindRpcProcessBridge (58) Bitcoin Core is not yet ready... Reason: Loading wallet...
2020-01-21 14:21:32 INFO BitcoindRpcProcessBridge (52) RPC connection is successfully established.
2020-01-21 14:21:32 INFO CoreNode (164) Started Bitcoin Core.
2020-01-21 14:21:32 INFO CoreNode (48) CreateAsync finished in 13 seconds.
2020-01-21 14:21:32 INFO HostedServices (49) Started Software Update Checker.
2020-01-21 14:21:32 INFO HostedServices (49) Started Block Notifier.
2020-01-21 14:21:32 INFO HostedServices (49) Started RPC Monitor.
2020-01-21 14:21:32 INFO HostedServices (49) Started RPC Fee Provider.
2020-01-21 14:21:32 INFO Global (349) Start connecting to nodes...
2020-01-21 14:21:32 INFO Global (373) Start synchronizing filters...
2020-01-21 14:24:21 INFO Global (722) Wallet loaded: Wallet0.
2020-01-21 14:24:21 INFO ClientState (468) Round (33305) added.
2020-01-21 14:24:21 INFO ClientState (468) Round (33306) added.
2020-01-21 14:24:21 INFO Global (506) Start Chaumian CoinJoin service...
2020-01-21 14:24:21 INFO Global (508) Starting WalletService...
2020-01-21 14:24:21 INFO CoinJoinClient (141) CoinJoinClient is successfully initialized.
2020-01-21 14:24:22 INFO Global (510) WalletService started.
2020-01-21 14:28:46 INFO Global (661) Transaction Notification (Success): Received Replacable Transaction - 0.00129791 BTC - 3b98ecbb7c7fa5db5bb175b7bb883337a814548caa1bf3209651b0cacfa4dc07
2020-01-21 14:29:05 ERROR WasabiSynchronizer (305) Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 1, position 1.
at Newtonsoft.Json.JsonTextReader.ReadStringValue(ReadType readType)
at Newtonsoft.Json.JsonTextReader.ReadAsString()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value)
at System.Net.Http.HttpContentExtensions.ReadAsJsonAsync[T](HttpContent me)
at System.Net.Http.HttpResponseMessageExtensions.ThrowRequestExceptionFromContentAsync(HttpResponseMessage me)
at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<
Is it still as useless as it used to be?
Yes, many of your UX critics are correct, so if that's your criteria of qualifying it as "useless" then it indeed is.
However, regarding merging together mixed UTXOs you are wrong: https://old.reddit.com/r/WasabiWallet/comments/avxbjy/combining_mixed_coins_privacy_megathread/
just in case you missed this visual from the 1st birthday of wasabi wallet tweeted on the 31st october.
here it is:
here it is:
If you created your wallet with an empty password, this hotfix is for you!
https://twitter.com/molnardavid84/status/1172420536447586306?s=21
https://twitter.com/molnardavid84/status/1172420536447586306?s=21
Quote
[RELEASE] Wasabi v1.1.8: Community Edition - Hotfix
https://wasabiwallet.io
With the v1.1.7 release, you could not spend funds if your wallet was created with an empty password. It is fixed in this hotfix.
More details here: https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.1.8
https://wasabiwallet.io
With the v1.1.7 release, you could not spend funds if your wallet was created with an empty password. It is fixed in this hotfix.
More details here: https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.1.8
Image: zkSNACKs founders (left to right) Lucas Ontivero, Balint Harmat, Gergely Hajdu and Adam Ficsor. Courtesy of zkSNACKs
Good news:
+ New CTO prioritizing open source contributions, so far this project is doing unusually well in that regard.
+ @nopara73 focusing on privacy research, including full BTC node features in the wallet (!)
+ # of BTC mixing txs is surging
full article on coindesk: Leadership Shakeup at Wasabi Wallet as Bitcoin Business Surges
Andreas Antonopoulos Bitcoin Q&A: Samourai, Wasabi, and privacy
https://www.youtube.com/watch?v=k8pjs3bz9-8
https://www.youtube.com/watch?v=k8pjs3bz9-8
Middle ground fallacy. "An informal fallacy which asserts that the truth must be found as a compromise between two opposite positions."
https://en.wikipedia.org/wiki/Argument_to_moderation
i posted this because it was nice that andreas mentioned wasabi. but he is rather diplomatic i would say.
Andreas Antonopoulos Bitcoin Q&A: Samourai, Wasabi, and privacy
https://www.youtube.com/watch?v=k8pjs3bz9-8
https://www.youtube.com/watch?v=k8pjs3bz9-8
Middle ground fallacy. "An informal fallacy which asserts that the truth must be found as a compromise between two opposite positions."
https://en.wikipedia.org/wiki/Argument_to_moderation
Jump to: