Wasabi Wallet 1.0 Is Released

[nopara73]

But then, is there any other reason for "why" the address reuse by that particular "participant"? The question not intended as a challenge, but out of curiousity.

Why that strange behavior happened is a great mystery. The only theory I could come up with that actually made sense is that it's Samourai itself, of course I have no idea, nor days or weeks to investigate it.

[1713628126]

1713628126

[1713628126]

1713628126

[Wind_FURY]

But then, is there any other reason for "why" the address reuse by that particular "participant"? The question not intended as a challenge, but out of curiousity.

Why that strange behavior happened is a great mystery. The only theory I could come up with that actually made sense is that it's Samourai itself, of course I have no idea, nor days or weeks to investigate it.

That's a grave accusation that could demolish their standing in the community, be careful. But truly disgusting, if proven true.

[nopara73]

That's a grave accusation that could demolish their standing in the community, be careful. But truly disgusting, if proven true.

Samourai has a long shady history surrounded by extreme incompetence. It'd be perfectly in-character for them to do this.

- https://medium.com/@nopara73/samouraileaks-samouraidevs-sockpuppet-exposed-7ce654b92c0b
- https://medium.com/@nopara73/samouraileaks-part-2-harassment-of-bitcoin-developers-fae3019abd2f
- https://medium.com/@nopara73/samouraileaks-part-3-is-random-org-random-enough-35704796ae93

[buwaytress]

Who'd have thought that these wallets would be battling for supremacy only to bring about mutually assured denouncement?

Been completely unaware of all this background happenings in Samourai, but I wonder if anyone else notice this aggressive response to criticism is something a bit more common in dev-world? I totally get the defensiveness, I'd be all up in arms if someone criticised my work, but then I wouldn't go down warpaths haranguing other devs.

A belated question: but Samourai and Wasabi... any reason for these names? HiddenWallet, DarkWallet... and then this move. A vague link to Nakamoto etymology?

[layer1gfx]

i suggest renaming the wallet to "shinobi" - a real samurai wouldn't act this way.

*adds wasabi*

[Wind_FURY]

Who'd have thought that these wallets would be battling for supremacy only to bring about mutually assured denouncement?

Been completely unaware of all this background happenings in Samourai, but I wonder if anyone else notice this aggressive response to criticism is something a bit more common in dev-world? I totally get the defensiveness, I'd be all up in arms if someone criticised my work, but then I wouldn't go down warpaths haranguing other devs.

A belated question: but Samourai and Wasabi... any reason for these names? HiddenWallet, DarkWallet... and then this move. A vague link to Nakamoto etymology?

While JoinMarket is going along quietly. Maybe they're the bad-actors, making Wasabi and Samourai fight. Haha.

That was a joke.

i suggest renaming the wallet to "shinobi" - a real samurai wouldn't act this way.

*adds wasabi*

Or NinjaAssasin the Honorless Wallet.

[Wind_FURY]

I believe this settles it. Jorge Timon is in the same thread calling them out too. A friend of mine also said that Gregory Maxwell also did.

I was slightly doubting nopara73, honestly. Sorry.

https://twitter.com/lukedashjr/status/1165628234597355520

Samourai likes to advertise features that they don't actually have, and add "features" that don't do what they claim.

Their reaction to me calling them out, has so far been to troll me. I think others calling them out have received the same treatment.

[layer1gfx]

Andreas Antonopoulos Bitcoin Q&A: Samourai, Wasabi, and privacy

https://www.youtube.com/watch?v=k8pjs3bz9-8

[nopara73]

Andreas Antonopoulos Bitcoin Q&A: Samourai, Wasabi, and privacy

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

[layer1gfx]

Andreas Antonopoulos Bitcoin Q&A: Samourai, Wasabi, and privacy

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.

[layer1gfx]

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

[layer1gfx]

If you created your wallet with an empty password, this hotfix is for you!

https://twitter.com/molnardavid84/status/1172420536447586306?s=21

[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

[layer1gfx]

just in case you missed this visual from the 1st birthday of wasabi wallet tweeted on the 31st october.

here it is:

[layer1gfx]

RECAP: Bitcoin Magazine Article: Nopara73 on Wasabi Wallet and the Quest for Bitcoin Privacy

[nopara73]

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/

[mocacinno]

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).

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.<<Start>b__0>d.MoveNext()

[nopara73]

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"

[mocacinno]

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.

[nopara73]

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.

[mocacinno]

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