There's a tool in Keybase you can use or for Openkeychain I had to save the key and import as an .asc file.
Decentralized Whirlpool was nearly ready to activate before the SW devs were arrested. The vision is still there.
The .onion site is working fine in Tor browser for me too 🤷
My new PayNym in Ashigaru is outrageoushuman41 🤣
Samourai Wallet has been forked. Some brave souls have picked up where Samourai Wallet left off and the fight for privacy lives on.
Excellent work in reigniting this flame in the darkest hour. Running your own Dojo now required.
http://ashigaruprvm4u263aoj6wxnipc4jrhb2avjll4nnk255jkdmj2obqqd.onion/
That's the neat part about open-source, will be both.
GM miners are going to have free & open-source hash boards, control boards, & firmware; complete and fully customizable mining systems that out-perform Bitmain products.
It's the 5G towers
Big announcement this week, HRF has thrown their support behind The 256 Foundation's mission to make Bitcoin mining free & open.
Hear all about it and more with our special guest Skot9000 on our first episode recorded in front of a live audience.
First nostr:npub1p0d256yljvn3pl82gpkmdyfqlxcmu6px63msrpmuauzha8yq4eeqprfpqe being recorded in front of a live audience happening soon.
Tomorrow marks the beginning of the end for the DOJ's campaign against privacy & open-source devs.
All the best to the Samourai Wallet team. Kick the tires and light the fires, guys 👊
Support their legal defense fund: https://p2prights.org/donate.html
Monday Mining Meetup #1 tonight, 9/16 doors open at 16:30, runs until 19:00. nostr:npub1p0d256yljvn3pl82gpkmdyfqlxcmu6px63msrpmuauzha8yq4eeqprfpqe episode #56 will be recorded in front of a live audience with special guest nostr:npub1ql2zzp3g6yndgz05js7wdc4qkr88wkyne5nw2cc7csrtzqs0yeesgwrxya
Join us for special 256 Foundation announcements, Socratic style QnA, food/drinks, & more.
https://www.meetup.com/bitcoinpark/events/302996672/?eventOrigin=group_events_list
I hate to be that guy but Ryan Routh seems a little rude.
>First of all, you have failed to demonstrate any Samourai Wallet "address reuse bugs" that can be equivalently compared to the systemic & symmetric address re-use vulnerabilities in Wasabi although you claimed them to be equivalent on Vlad's podcast.
Why can't they be compared? I just compared them didn't I? Your comment that Whirlpool's toxic change outputs and coordinator fee outputs already have such terrible privacy that it doesn't make any difference whether or not the addresses are reused doesn't help your argument, it hurts your argument.
>As for Ergo's tweet, when he says "unmixed" change, he's talking about change that comes out of a Wasabi CoinJoin tx
Okay, and when I say "unmixed" change I'm talking about the change that comes out of a Whirlpool tx0.
Now that we are both on the same page, please explain why you wouldn't just solve the problem of unmixed change like Ergo suggested by never creating it in the first place? I even opened a Gitlab issue in Samourai's wallet for doing this: https://web.archive.org/web/20231025112756/https://code.samourai.io/wallet/samourai-wallet-android/-/issues/461
You could also compare apples to oranges but you would still look like a fool.
So since you are aware of all of Samourai's address reuse bugs, then please explain to me why anyone would want to create "toxic change" instead of becoming fully untraceable? The WabiSabi protocol solves the "peeling chain" privacy leak that is produced by the Whirlpool protocol: https://x.com/ErgoBTC/status/1181573118810361856
First of all, you have failed to demonstrate any Samourai Wallet "address reuse bugs" that can be equivalently compared to the systemic & symmetric address re-use vulnerabilities in Wasabi although you claimed them to be equivalent on Vlad's podcast. Second, I do not claim to be "aware of all", I have merely responded to your shitty and misleading examples.
Doxxic change in Samourai Wallet is not part of the CoinJoin tx, it comes from the setup tx (tx0) and is separated afterwards, never entering a CoinJoin round.
As for Ergo's tweet, when he says "unmixed" change, he's talking about change that comes out of a Wasabi CoinJoin tx, change that doesn't match the mixed like-amount outputs. These change outputs are far from untraceable and have been the downfall of many users. Take for example, this video where Samourai Wallet demonstrates how easy it is to unwind a Wasabi CoinJoin transaction featuring a systemic case of address re-use. Take special note of the keywords "unmixed change" in the video's caption, which sates: "The 25 BTC unmixed change went to the same address as a 0.401 BTC mixed output. User didn't do this address reuse, the client did."
Says the guy publishing podcasts about an inactive CoinJoin implementation 🙃
I can reply to your wall of text, but it seems you are confused. Here's 3 different instances of address reuse in Samourai:
Samourai coordinator address reuse: https://x.com/Kruwed/status/1735129375001968838
Samourai toxic change address reuse: https://x.com/brian_trollz/status/1559018534675644418
Samourai postmix address reuse: https://x.com/SamouraiWallet/status/1283145015124996098
If you could then you would have but you can't because you're out of your depth. None of your examples are the result of address re-use in the CoinJoin. Unlike Wasabi's systemic & symmetric address re-use vulnerabilities which both occur in the CoinJoin transaction.
To clarify further: in your first example above, the coordinator fee is provided during the tx0 transaction while the wallet is setting up for and prior to the CoinJoin transaction. Tx0 transactions have obvious on-chain fingerprints and I fail to see how identifying the address used by the coordinator to collect the fee has any bearing on the anonymity of the user.
In your second example, the re-used address was also re-used in a Wasabi CoinJoin tx so that doesn't help your case but more importantly, when it was re-used by Samourai, it was in the tx0 - not the CoinJoin transaction. Additionally, based on the comments in that thread, the wallet was imported to Samourai and admittedly wasn't fully synced.
Finally in your third example and like the others, this was not a case of address re-use in the CoinJoin transaction (unlike Wasabi) but rather limited occurrences of address re-use in post-mix spending tools like Stowaway, Stonewall, & Stonewallx2. As explained in Samourai Wallet's write up of their investigation into the reported issue: not nearly as many addresses were effected as originally claimed and for good measure Samourai Wallet introduced Strict Mode after this report to mitigate unintentional address re-use by the users when transacting with post-mix spending tools.
Despite your efforts to equate Wasabi's address re-use vulnerabilities to Samourai Wallet, you have come up short yet again.