Bitcoin Forum
May 11, 2024, 11:29:32 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Economics / Feeling McTroubled? on: May 10, 2024, 09:23:56 AM
Have you looked at the menu recently?  Bitcoin fixes this: https://www.youtube.com/watch?v=6OasCaT2qTA

I tracked this inflation from Twitter/X by simply searching for the keyword "Mcdouble costs". Having the data fed straight from primary sources is a much more revealing truth than any "official" graph the government puts out.
2  Bitcoin / Bitcoin Discussion / Jeremy Rubin coming out of retirement - "You can't deny it's Jeremy Season" on: May 04, 2024, 03:38:41 PM
Jeremy Rubin, Bitcoin developer & author of BIP119/OP_CHECKTEMPLATEVERIFY is done fucking around after the announcement of Wasabi Wallet's default coordinator shutting down: https://twitter.com/JeremyRubin/status/1786094898636042623



He's announced he's back with a vengeance: https://twitter.com/JeremyRubin/status/1786516361587400925

3  Bitcoin / Pools / Braiins pool now supports Lightning payouts on: April 21, 2024, 02:54:34 PM
Braiins pool (formerly known as Slush Pool) now offers the ability to collect your mining rewards using the Lightning Network: https://twitter.com/BraiinsMining/status/1780975851737072085

Now miners can just collect fees from others without having to pay any themselves  Wink
4  Bitcoin / Development & Technical Discussion / Can Coinjoin transactions be traced? Busting Bitcoin privacy myths! on: January 24, 2024, 06:15:29 PM
- Public payments made private?
See https://bitcoin.org/en/bitcoin-paper

Transactions on the Bitcoin blockchain have infamously bad privacy. Every historical transfer of coins is recorded publicly and permanently, providing a link between the public keys used as inputs and outputs. Satoshi noted this in section 10 of the whitepaper titled “Privacy”:

Quote from: satoshi
As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner. Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner. The risk is that if the owner of a key is revealed, linking could reveal other transactions that belonged to the same owner.

Consolidating inputs indicates common ownership when you spend your coins alone, but it’s not necessarily revealing since a multiparty transaction can be constructed containing inputs (and outputs) from others. This type of transaction is called a “Coinjoin”.

Different types of coinjoins provide different privacy guarantees, but they are all inherently non custodial. Various specifications and protocols have been designed to facilitate coinjoins depending on the scenario. Please note that these descriptions target the protocol level, wallet level implementation details are not applicable to these explanations:

- Payjoin
See https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-August/021868.html

A payjoin is a coinjoin that a sender and recipient construct together. This provides marginal privacy gains to each participant by combining their histories while also saving on the receiver’s future cost of block space. Since an output is already being created for the merchant receiving funds, the receiver can opportunistically consolidate their inputs at the same time. A notable advantage of payjoins is that they blend in with regular on chain transactions, as opposed to equal output coinjoins which have a distinct footprint. Another advantage is that the value of the payment is obscured since neither output created matches the amount of value transferred between participants.

In the context of Lightning, this two party interaction is known as “Dual Funding”, where two peers can open a payment channel using inputs from each user. Additionally, new funds can be “spliced in” to the channel without indicating which peer consolidated the input. On chain payments can be “spliced out” that could have been sent by either channel participant while leaving the channel open as the change output.

- Can payjoins be traced?

Not from the outside. However, the disadvantage of payjoins compared to other coinjoins is that the sender and receiver are completely aware of the coins owned by the other participant, which introduces a trusted single point of failure. In theory, a payjoin could be composed with inputs from more than two parties, however, this introduces a time element since some parties must pause their transaction and wait for others to join instead of paying instantaneously.

- JoinMarket Coinjoins
See https://nixbitcoin.org/orderbook/

JoinMarket is a peer to peer marketplace for coordinating coinjoins using “Makers” and “Takers”. Instead of a payjoin where the sender collaborates directly with the recipient who provides their own liquidity, senders using JoinMarket collaborate with anonymous strangers on the marketplace and buy their liquidity.

The privacy of JoinMarket coinjoins is produced by having each peer create an output of equal value, making it unattributable to their originating inputs. There is a minimum of 0.00027300 BTC required to participate, and no maximum. JoinMarket is the most flexible coinjoin protocol since private payments can be made on demand by takers, and privacy can be gained passively on the coins sitting in the wallets of makers.

- Can JoinMarket be traced?

Not as a taker. Since takers choose the equal value output size, they can make coins from incoming payments anonymous or anonymize their change at any time without trusting anyone. Fidelity bonds help protect takers against makers performing Sybil attacks.

However, makers trust their information with the taker of any individual transaction, the coinjoin only provides privacy from outside observers. Makers generally only gain privacy on the equal value output, producing change. Makers reveal the ownership of their UTXOs to takers who propose an offer, but ring signatures are used to help protect makers from revealing their funds to malicious takers that do not complete the offer.

- WabiSabi Coinjoins
See https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020202.html

WabiSabi is a centrally coordinated coinjoin protocol that utilizes keyed verified anonymous credentials and a timed round for gathering liquidity. Each user can register multiple inputs directly to the coinjoin transaction anonymously without indicating common ownership, and change outputs are not created (if there is sufficient liquidity). This model allows a “smart client” to choose matching output amounts based on the input amounts registered in the start of the round instead of having the coordinator dictate the values allowed to “dumb clients”.

The advantage of WabiSabi is that the coinjoin structure completely eliminates the links between your addresses when sending or receiving transactions without needing to pay attention to the labels or values of your inputs. WabiSabi is highly block space efficient since input consolidation, mixing, and payment batching can all be performed in the same transaction without premixing or postmixing.

- Can WabiSabi be traced?

Not unless you are the biggest whale in a coinjoin round with insufficient liquidity. Even outputs that do not have matching amounts cannot be traced to an owner on the input side - it’s even possible that the output changed hands as a payment to someone who did not own any funds on the input side at all:

you don't need to be a "whale" at all in order to receive absolutely zero privacy from a Wasabi coinjoin.

Okay then, I'll call your bluff again- Here's 20 non whale non matching outputs from WabiSabi coinjoins, try to identify the inputs owned by even a single one of the 20 outputs (which would be 5%):

01 bc1q032caguldmlrrztmrwhv5wqveyywdu2rtmd740
02 bc1q6vgwhsfkg343mmh27vc6prg3clsd4xu3p68vyd
03 bc1qre8jjpu8p9taw8j44r39z56vfr4sw64d4wyaj4
04 bc1qarharg76gfcrvskfw46f67vtqzd6hxa9pnspp5
05 bc1q4sexgt2p96x3ytnjjttp59w6mkj00kedal3xze
06 bc1qwrf50wpjws5mhdg2rhdu5hy7nqdtl8z94lp75n
07 bc1qz0tal2udfpr20x793fdw6v8lzp2qze7z5zje64
08 bc1qqw2h7fa3n8vyxgqru664fmft2trl9sqh9kz3fp
09 bc1qsud748whmum4gpt2qu52z8gqlgzcjyvhd5w2a5
10 bc1qctvxddyvxupjj8w82m8w5grzn59arstlrnaauw
11 bc1qq2fl05cmmhkr3pzg8elyr859v2fpcltynrk2j5
12 bc1qvwkrd3aecrvql5j8mqkmketvw6g6qwzt4juprq
13 bc1qhc2565fac4lrgyfq6n0mzc0l86jeptfnv2um9x
14 bc1qat6445gutyl3qdz3zhmdng9cdt92mevjlvaljs
15 bc1qk5f3mz0fetccey4nyyjedlrmqstkz2hmun96ha
16 bc1q4tpvm378a9d4n0xcnjtwfwujtr8eatjzvru8dx
17 bc1qd5epyjpj6vuejdppj24wew5n4n5rzepjx2xnay
18 bc1qgafud63me5mffn00g90ch08jjn5h20umzwxd62
19 bc1q5u3f2ldrtqa7ea79a8hcd8kssgw2gmalk4uej9
20 bc1qa6n7g7r4j3nv78gzgzmuvg56em4guppckqpz7r

- Whirlpool Coinjoins
See https://bitcoinmagazine.com/technical/how-bitcoin-anonymity-sets-work

Whirlpool is a centrally coordinated coinjoin that implements the ZeroLink coinjoin protocol with a privacy restriction that limits the anonymity you can gain. This restriction is called “tx0”, it is a self spend transaction prior to the coinjoin that allows the trusted coordinator to custody the fee they charge in order to prevent DoS attacks from being costless. Once the coordinator’s fee is confirmed, they allow the outputs created from the premix tx0 to be added to their liquidity pools. There are 4 different liquidity pools with fixed output values:

0.5 BTC
0.05 BTC
0.01 BTC
0.001 BTC

The coordinator then chooses between 5 and 8 participants for a coinjoin round who use blind signatures to create an equal sized output whose origin input is anonymous to all parties. In order to incentivize liquidity, these participants are composed of new entrants (takers of liquidity) and remixers (makers of liquidity). The mining fee for the block space used by remixers is paid for by the new entrants, so the value a user receives from their first round does not change after they are selected to remix in future rounds.

- Can Whirlpool be traced?

Yes, the common input ownership heuristic and change output heuristics are revealed by the premix tx0, creating a 100% link between a Whirlpool user’s addresses. Any UTXO that does not precisely add up to a multiple of 0.5, 0.05, 0.01, or 0.001 (+fees) cannot gain complete privacy. There are no advanced calculations required to determine these links between addresses, they are visible to the naked eye:

Post the tx ID of any Whirlpool transaction and I will show you the tx0 transaction that was created by each of the new entrants.
Ok, here's one: https://mempool.space/tx/ed3131b544fbf00a71709942e483b55e629312ecb181e6e819409f419ee0d226

Where exactly is the privacy loss for new entrants, splitting a single UTXO in to multiple UTXOs to join the pool?

Okay, here's all the payments that can be tracked from the two new participants of the Whirlpool coinjoin transaction:

Entrant 1: bc1q03c0443ausjjdxl2h6ud5m8c0dux0zyg3dqdj7 created 0.00170417 BTC in unmixed change sent to bc1q3fduld0l3r8nclyt5p3r7ak675tekurstn55tl.  Since this UTXO is not private, the sats were marked as unspendable and have not been recovered by the wallet owner  Cry Cry Cry

Entrant 2: bc1qzc8zku26ej337huw5dlt390cy2r9kgnq7dhtys created 0.00191247 BTC in unmixed change sent to bc1qjlltxr443uy236wl4xhpxlr6dgsu0zltlv3m44. This UTXO was used in a second tx0 transaction, creating a huge trail of transactions that could be traced to each other  Shocked Shocked Shocked

The 2nd tx0 transaction created 0.00076348 BTC unmixed change which was sent to bc1qehd7gy8rza9mnzm9wnfjhgw82rp47wmqt7vpgy

Since this unmixed change is below the .001 pool minimum, it was consolidated in a 3rd tx0 with 3 other addresses owned by the same wallet:
31x8GPqrhzdaxiBJa9N5UisuoxbX1rAnHa
16Gw5WKjbxZmg1zhZQs19Sf61fbV2xGujx
3LZtsJfUjiV5EZkkG1fwGEpTe2QEa7CNeY

The 3rd tx0 transaction created .00200317 in unmixed change which was sent to bc1q2p7gdtyahct8rdjs2khwf0sffl64qe896ya2y5
This was spent in a 0.00190000 payment to 3B8cRYc3W5jHeS3pkepwDePUmePBoEwyp1 (a reused address)

That payment left .00008553 in change that was tracked to 3Dh7R7xoKMVfLCcAtVDyhJ66se82twyZSn and consolidated with two other inputs in a 4th tx0 transaction:
bc1qeuh6sds8exm54yscrupdk03jxphw8qwzdtxgde
3ByChGBFshzGUE5oip8YYVEZDaCP2bcBmZ

This 4th tx0 created .00533406 in unmixed change which was sent to bc1qzh699s75smwukg9jcanwnlkmkn38r79ataagd9 which was consolidated with 3 more addresses into a 5th tx0:
3F2qiWQJKQjF7XFjEo8FUYP3AU5AC6RqX8
3HAYYVKUpYbr2ARMdZJr9yVu8xi8UcxtPz
3GQtwwRK31wwCc22q6WS5sCgixUHsG5KaT

The 5th tx0 created 0.00058494 BTC in unmixed change that was sent to bc1qvh2zjcwwkj9y70xulla2semvlav3lty0p3l3w3
This was spent in a .00047290 payment to bc1qvzg8jq6wqtr5navn4e3ps4qrkk9r6n4h98gjck

That payment left .00008411 in change that was tracked to bc1qg6j0f0wfhpktt2l8uzdn48ct3um2xyur40eyzd and consolidated with another input into a 6th tx0 transaction:
31iZLXWfoywhuMZTPGxTkpzphzh2NXshpP

The 6th tx0 created .00753775 in unmixed change that was tracked to bc1qgfll2apc27yct6h2c8r8wq4kqhxjsfrudhhn5q
This was spent in a .00737000 payment to bc1q5emzer2t0sq5dez0zsrqgh6scvwn0n24xsladp (a reused address)

This payment left 0.00010896 BTC in change which has not been spent yet, but the payment only took place 11 days ago, so I assume it will eventually be spent, allowing the Whirlpool user to be tracked even further.

Postmix transactions can be traced to premix funds when outputs from child rounds of the same premix transaction are consolidated. Consolidation of mixed outputs from the initial round may be unavoidable since users do not have control over whether or not they remix:

The first is the fee to Whirlpool itself, which is a flat fee depending on the pool you are joining.

The flat pool entry fee structure is designed to incentivize worst privacy practices.  Since fees are not collected directly based on volume, it is cheaper to participate in a smaller pool and create more outputs than participate in a larger pool and create less outputs. Additionally, it incentivizes revealing common inputs ownership of premix UTXOs since it is cheaper to consolidate them to enter the pool once than to enter the pool with each UTXO individually.  Samourai has never explained why they purposely chose a fee structure that heavily penalizes the most private usage of their protocol.

Because of this backwards design, you can easily link premix inputs to postmix outputs in many cases.  Notice how this Whirlpool tx0 premix creates 70 outputs for 0.05 BTC - https://mempool.space/tx/63679c9ec82f246811acbab0c04cc0fc77ba050e1b6c23661d78afcfc13cf8aa

Notice how every single input of this Whirlpool exit transaction is a direct descendant of rounds created by the aforementioned premix transaction: https://mempool.space/tx/ce2f84f7c5ff74fb1da103acb7b279bd34f02f5e9e3a2e1b6417ce8b9b7392db

When many inputs used in the postmix exit transaction are created directly from a round that the premix transaction entered, it makes it trivial to trace the user through Whirlpool.  Fortunately, the user abandoned Whirlpool and upgraded to using the WabiSabi coinjoin protocol instead, which made him completely untraceable: https://mempool.space/address/bc1qjjw5gaglkycu2lm5fskl7qhktk0hec4a5me3da
5  Economy / Reputation / Re: Farewell on: January 18, 2024, 11:03:00 AM
Edit: This thread was created from staff splitting the posts from the original "Farewell" thread posted by o_e_l_e_o.
_________________________________________________________________________

Here is the proof of o_e_l_e_o's attacks against non custodial open source projects over the past 2 years (BTCPay Server, Trezor, and Wasabi).  While he was spreading these false accusations against trustless privacy tools, he was simultaneously luring users into depositing their coins into custodial "mixing sites" that robbed depositors of their coins and turned over user data to the government:

TIMELINE

March 14 2022 - o_e_l_e_o admits coordinator policy doesn’t affect your inputs, admits to BlackHatCoiner that switching coordinators solves the censorship problem, and admits to BlackHatCoiner that his motivation is simply to fight against Wasabi anyways:

Even if this change from Wasabi won't affect any of your inputs, they are no longer an entity which I can trust to fight for my privacy.

Would it be possible for some to start running coordinators?
Absolutely. The coordinator code is open source, so anyone can download it and spin up their own instance. That would solve the immediate problem if everyone switched to a different coordinator, but it doesn't stop these other coordinators being pressured in to implementing the same restrictions and it doesn't change the fact that Wasabi did this in the first place instead of fighting against it.

March 15 2022 - o_e_l_e_o admits that the data feed is a 1 way street from a blockchain analysis company to the coordinator, and that no data is provided to blockchain analysis:

In fact, they need to cooperate with blockchain analysis to obtain information about "taint" UTXOs.
Well, they only need to cooperate in this sense to have the blockchain analysis entity feed them data about which UTXO's to block. But as I said, if they cooperate like this then it won't be long before that cooperation becomes a two way street, with them feeding data back to the blockchain analysis entity.

March 18 2022 - o_e_l_e_o spreads fake news article claiming that Wasabi's "anonymity has been cracked" because someone reused their Bitcoin address:

Still, it seems that Wasabi has never been as safe as we all think:
Using a capability that is being disclosed here for the first time, Chainalysis de-mixed the Wasabi transactions and tracked their output to four exchanges.
A little bit of expansion on this that I came across today: US government spooks have cracked ‘anonymous’ Bitcoin wallet Wasabi

Seems like if you have any coins in a Wasabi wallet right now then not only do you need to withdraw them before Wasabi decide to start blacklisting them, you'll also need to re-mix them (and do so thoroughly) using a different mixing method.

April 24 2022 - o_e_l_e_o highly recommends the custodian he partnered with that stole everyone’s deposits and turned over their data to the government and then lies about spying on Wasabi users being possible:

ChipMixer easily has the best and longest standing reputation among all bitcoin mixers.

CoinJoin service: Wasabi / Samourai / JoinMarket
Wasabi now spy on their users and censor transactions, so I would no longer recommend them.

April 25 2022 - To further fool this user to lose their funds and data, o_e_l_e_o blatantly lied about the verifiable open source software by falsely claiming that every user and every UTXO stored on a Wasabi wallet will be monitored and surveilled, and that this survelliance applies specifically to Wasabi:

About 6 weeks ago, Wasabi announced on twitter that zkSNACKs, the entity which runs the coordinator for the all the coinjoin transaction which take place through Wasabi wallet, would start censoring some inputs and refusing to allow them to partake in coinjoins. Wasabi then explained on Telegram that they would be hiring a blockchain analysis company, which would monitor and surveil every user of Wasabi and ever UTXO stored on a Wasabi wallet and decide which ones were and were not allowed to partake in coinjoins. They have since revealed that they did this voluntarily to protect their own operations and therefore their own profits, and not because they were forced to because of any government, law, or regulation.

Wasabi is now pro-censorship and anti-privacy. They should be avoided, unless you like seeing your coinjoin fees go straight to a blockchain analysis company which is being paid to spy on you and you specifically.

April 26 2022 – o_e_l_e_o lies about the Wasabi coordinator sharing information:

Keep in mind that in addition to what has been discussed above, the Wasabi coordinator is now working with and sharing information with blockchain analysis companies, who will be drawing on a variety of non-public sources of information.

April 27 2022 - BlackHatCoiner confirms the coordinator knows nothing:

Indeed, the coordinator knows nothing about who owns what. Although, it isn't so simple to comprehend at first sight, the two parties can hide their outputs (hence why "blinded outputs") using blind signature.

May 2 2022 - o_e_l_e_o falsely accuses coordinators of being able to collect data:

Blockchain analysis is ultimately a process of deduction and induction.
A process which becomes much easier when the centralized coordinator is actively working with blockchain analysis companies and handing over all the data they collect.

May 12 2022 - o_e_l_e_o falsely claims that users are required to trust open source software:

No idea, and given how shady Wasabi have been about this whole thing, don't expect them to be honest and tell us. Any "privacy" firm coordinating with blockchain analysis firms is not to be trusted though, and especially not one which is actively using your coinjoin fees to pay blockchain analysis firms.

May 27 2022 – o_e_l_e_o falsely claims using Wasabi provides the same privacy as using a centralized exchange:

It makes no sense to continue using Wasabi, unless you do not care about your privacy at all. Your privacy with Wasabi is now akin to the privacy you get with a centralized exchange - complete surveillance.

June 12 2022 - NotATether emphasizes that the Wasabi Wallet software is “clean and uncompromised” in a thread posted about running the open source coordinator software:

The situation map is currently thus:

- The Wasabi wallet itself is still clean and uncompromised.
- But the default CoinJoin server used by Wasabi wallet (zksnacks) is now blacklisting "tainted" coins, an action which is intolerable to the community.
- Ignore the signature campaign for now, it is irrelevant to remedying the situation.


This thread exists to gather open source software on Github/Gitlab/etc. which allows the running of a Wasabi-compatible CJ mixing server. Software that cannot be plugged in to Wasabi should not be listed here. Since this battle is being fought against their main CJ server, and not analysis companies/exchanges/governments, we still have a chance for winning this, even if we are 3 months behind schedule (the announcment for the blacklisting was made last march).

Discussion on how to make such CJ software work for Wasabi (as well as the other way around) is also welcomed. Special attention should be given to getting these to run on low-powered Linux servers (think 8GB of memory or less).

June 12 2022 - o_e_l_e_o emphasizes not to use open privacy software no matter who coordinates the transactions because his feelings are hurt:

I also wouldn't recommend using Wasabi at all, even with a non censoring coordinator. The Wasabi devs have revealed very clearly where their priorities lie: Those priorities are not with their users or protecting privacy, but solely with making profits. Obviously Wasabi is open source, but I'm still not going to use a wallet which is run by a team who are willing to voluntarily sell out their users for profits.

June 15 2022 - o_e_l_e_o falsely accuses Wasabi of sacrificing user privacy:

It's not like Wasabi where they are sacrificing the privacy of the average user to cater to the bigger players.

June 18 2022 - o_e_l_e_o fights against BlackHatCoiner for suggesting that someone fork the open source coordinator on the grounds that centralized services are vulnerable to censorship:

Yes, but the source code is released under the MIT license, wherein you're allowed to modify and distribute, which means it allows you to develop it. However, being hosted by zkSNACKs means you're going to have a hard time forking it and re-releasing it successfully, as far as I understand.
I still don't see the point, though. Why start with a flawed concept (centralized coordinators which have the power to censor you) and then fork and try to modify around it, when there already exist coinjoin implementations with no centralized coordinator in the first place. Anyone with the time and ability to do this would be far better spending their time on making JoinMarket more newbie friendly.

August 9 2022 – o_e_l_e_o falsely claims Wasabi is flawed for “address reuse”:

You sure? Chainanalysis can de-mix Wasabi coinjoins, and Wasabi is pretty much infamous for it's flawed address reuse and combining of coinjoined and uncoinjoined outputs.

August 13 2022 – o_e_l_e_o discourages tens of thousands of people from using open source Bitcoin privacy tools by lying and saying Wasabi compromises privacy:

Such an approach would require encouraging tens of thousands of people to download and use Wasabi and compromise their own privacy in doing so. Not a great approach.

August 23 2022 – o_e_l_e_o lies and says the custodian he partnered with that stole everyone’s deposits and turned over their data to the government has as good or better privacy than Wasabi

If projects such as Samourai, JoinMarket, ChipMixer, Bisq, LocalCryptos, Monero, and anything else which gives users as good or better privacy than Wasabi can continue unencumbered, then Wasabi can too. They simply choose not to.

November 5 2022 – Wasabi enables coinjoining, generates a new address for each payment, and prevents spying using block filters. Yet o_e_l_e_o is lying to encourage people to offboard software that preserves privacy and leak their addresses to the Samourai coinjoin coordinator instead:

One of reason Wasabi Wallet 1.0 become popular is due to user-friendliness while preserving few advance feature (address/UTXO selection).
There are plenty of other user friendly non full node wallets with such features. Granted, most don't provide coinjoins, but when you are also being spied on, censored, and having your addresses reused, then some might say a wallet without any of those features is better than Wasabi. Wink

It could be replacement of JoinMarket-Qt which need full node since Wasabi Wallet 1.0 is one of very few SPV desktop wallet with strong privacy feature (Tor by default and BIP 157 implementation).
If you don't want to run a full node then I would suggest Sparrow wallet as the next best option to access coinjoins.

Novermber 6 2022 – o_e_l_e_o lies about being able to spy on Wasabi users and tells everyone to send their coins to the custodian he partnered with that stole everyone’s deposits and turned their data over to the government:

And if you depend on third parties, then you are subjected to their rules, spying, and censorship, as we have seen in the case of Wasabi.

By using Sparrow you are still depending on third parties, but at least those third parties aren't in cahoots with blockchain analysis companies. But if that is still too complex for the average user to use without compromising their privacy in some manner, then you can just stick to ChipMixer.

February 28 2023 – o_e_l_e_o lies about Wasabi feeding details to a blockchain analysis firm to avoid the truth that you can change coordinators:

People who are using Wasabi aren't generally going to bother changing coordinator, because anyone who actually cares about privacy and not having their details fed directly to a blockchain analysis firm isn't using Wasabi in the first place.

March 5 2023 – o_e_l_e_o lies about Wasabi creating toxic change:

And that's without even touching on Wasabi's mixing of toxic change with coinjoined outputs, defeating the entire purpose in the first place.

March 8 2023 – o_e_l_e_o lies about BTCPay Server, claiming that coordinators can spy on them and claiming that they are “risking address reuse”

It is a mistake for BTCPay to implement this. Even if someone manages to get enough volume on a coordinator which doesn't spy on users and directly fund blockchain analysis, then they are still risking address reuse and therefore complete failure of what they are trying to achieve by coinjoining in the first place.

April 15 2023 – o_e_l_e_o falsely claims that Trezor allows blockchain analysis to monitor outputs in their hardware wallet

Cool, so I can get blockchain analysis entities to specifically monitor the outputs in my hardware wallet now. Just what I've always wanted! Roll Eyes

April 28 2023 – o_e_l_e_o tries to sabotage a user’s privacy by convincing them not to use the coinjoin feature in Trezor, which protects your xpub and IP address from being shared, and protects your on chain data from being tracked:

I regret ever suggesting that anyone should buy a Trezor, and I will never do so again. They have shown themselves to be anti-privacy and anti-fungibility, and are therefore not just selling out their users but are actively working against bitcoin itself, in order to line their own pockets.

As he says, however, if you already have a Trezor device (and no other hardware wallet you can swap to or can afford), you are probably safe to keep using it provided you don't go anywhere near the coinjoin feature. I also don't have a single shred of trust left for Trezor, though, so I would make sure you are using it through something like Electrum or Sparrow pointed at your own node and absolutely not relying on Trezor's servers. And when it comes to the time to upgrade or replace your hardware wallet, obviously do not buy another Trezor.

June 21 2023 – o_e_l_e_o tells people to “steer well clear of ever using Wasabi” by lying about address reuse:

Add in the fact that they suffer from endemic address reuse (https://bitcointalk.org/index.php?topic=5419000.msg61220171#msg61220171, https://bitcointalk.org/index.php?topic=5286821.msg62085316#msg62085316), and I would steer well clear of ever using Wasabi.

August 21 2023: BlackHatCoiner confirms that what a coordinator does with their money isn’t important for the coinjoin user:

I would also say "Service uses the fee you pay to hire a blockchain analysis company to spy on your inputs" is a pretty big con of Wasabi which you've missed.
What the default coordinator does with the money it makes isn't important for the coinjoin user, but for the integrity of their business.

Sure, but it is an objective fact that Wasabi use the fees you pay them to pay blockchain analysis companies for information about your UTXOs. And I would argue that is incredibly important for the coinjoin user.
What's important here is to break down what's user's best courses to accomplish mixing. Even if funding blockchain surveillance is completely contradictory to being proclaimed a pro-privacy service, that doesn't change their coinjoin process. Just as if Samurai announced that they're funding the Ukrainian war, it wouldn't change the effectiveness of the coinjoin. It'd ruin their reputation, and people would stop using it; not because of effectiveness, but ethical concerns.

December 9 2023 – o_e_l_e_o lies about BTCPay Server’s coinjoin implementation being “inferior” because of “address reuse” and lies about the existence of “deterministic links”:

The large group of people outside of Bitcointalk who are interested in coinjoins are predominantly using Samourai/Sparrow/Whirlpool. As I've said 100 times already, even putting the whole mass surveillance thing to one side why would people abandon a better coinjoin implementation in order to bootstrap an inferior one which suffers from address reuse and deterministic links?

_________________________________________________________________________

Original post:
_________________________________________________________________________

This is a pathetic post. I would delete it if I were you. This is just proving the kind of person you are. Someone is ill and you say you are happy. Good luck in your life...

Why should I excuse or forgive o_e_l_e_o's continuous attacks on Bitcoin just because he's mortal?
6  Bitcoin / Wallet software / Updated Coinjoin & Payjoin Guide for BTCPay Server on: January 06, 2024, 09:36:59 PM
I previously created some short video guides on how to use the coinjoin plugin for BTCPay Server developed by Kukks - [1] [2]

Uncle R0ckstar has posted an updated guide for v1.0.67.0 demonstrating payjoin, coinjoin, and mixing to cold storage: https://www.youtube.com/watch?v=Qwo8qcfnZ14
7  Economy / Reputation / Scammer kayirigi posted a fake accusation about Wasabi and self moderated it on: January 06, 2024, 09:09:58 PM
User "kayirigi" has posted a fake accusation of scamming against Wasabi Wallet:  https://bitcointalk.org/index.php?topic=5480440.0

This user, of course, "self moderated" the fake topic in order to prevent anyone from commenting honestly about these blatantly false accusations.

Quote
There have been 5 documented cases of coinjoins being flagged by exchanges and brokers. All have concerned Wasabi. Rather than fix recurring issues with their implementation, Wasabi claimed that the problem was due to an anti-coinjoin campaign by KYC actors despite the fact that only Wasabi coinjoins have ever been targeted https://6102bitcoin.com/coinjoin-flagging/ (Update: now 6 documented cases. See below.)

Do not let these obvious hit job accounts scare you out of using Bitcoin privately.  If someone you are transacting with "flags" your coinjoined funds, it is not due to "an issue with their implementation", it's because that person is requiring your data in order to transact with them.  Defy them, and become anonymous anyway.
8  Bitcoin / Wallet software / Wasabi Wallet - Open Source, Noncustodial Coinjoin Software on: December 01, 2023, 02:51:53 PM


Privacy is your ability to selectively reveal yourself to the world. - [Cyperpunk Manifesto]

Official download  https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.7.1
Onion link http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/
Open source code https://github.com/zkSnacks/WalletWasabi
PGP (software verification guide) 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Wasabi provides network level privacy
Other light wallets sacrifice your privacy in exchange for speed by leaking all of the addresses in your wallet to a third party server. This third party server also is able to see the IP address your wallet connects from, which can provide them even more data to tie your Bitcoin addresses to your identity.  

Quote from: wasabiwallet.io
We live in an Orwellian surveillance society where your information is being used to typecast and manipulate you. Bitcoin projects are being pressured to collect more and more data, if possible. This is why Wasabi Wallet is programmed to be a zero-knowledge software. Developers can't collect any sensitive information about you. What you do with your Bitcoin is your business.

Wasabi innovates on the light wallet design and solves these privacy leaks by masking your wallet addresses with client side block filters, and masking your IP address with Tor. Although combining these two technologies this reduces the privacy footprint for receivers to a single address, the addresses are still visible on a public ledger, so another step must be taken to hide the origin of the coins you received from the destination you send them to, and vice versa. This traceability is broken by coinjoins.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Wasabi provides blockchain level privacy
WabiSabi research paper (Ádám Ficsór, Yuval Kogman, Lucas Ontivero, and István András Seres): https://eprint.iacr.org/2021/206.pdf

Wasabi's most impressive privacy feature is the ability to participate in coinjoin transactions. A coinjoin combines your coins non custodially into a bulk transaction with other users in order to make your Bitcoins untraceable.  The outputs of a coinjoin can't be tracked to the inputs because the outputs created have identical clones with the *exact* same value. Even the coinjoin coordinator themselves cannot determine which inputs and outputs belong to each participant:

Quote from: Lucas Ontivero
The whole WabiSabi protocol is a really complex beast which involves a lot of cryptography from Pedersen commitments, zk-proofs, balance proofs, range proofs, ownership proofs, a strobe construction around Keccak and others that play together to create the credentials system. The protocol involves the construction of http messages that have to be sent to the central coordinator in a randomized schedule under different Tor identities to guarantee the unlinkability of the participants' transactions against the central coordinator.

Here's an example of a Coinjoin transaction on mainnet with 400 inputs and 407 outputs: https://mempool.space/tx/d465033214fd2309dcce5a90c45fcaa788aa4394ee36debe07aad8d8a37907d2




=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

There is a cost tradeoff for using the optional coinjoin feature.  Participating in a coinjoin transaction will always cost a miner transaction fee, and may cost a one-time 0.3% coordinator fee, depending on the value and origin of the input you are registering.  The following inputs do not pay any coordinator fees:

- Any inputs with a value of 1 million sats (0.01 BTC) or lower
- Any outputs from a coinjoin that you remix for additional privacy
- Any change from spending inputs that were already coinjoined
- Any coins sent to you by other Wasabi Wallet users that were already coinjoined

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Cold storage interface
Wasabi also allows you to connect your USB hardware wallet such as BitBox02, Coldcard, Jade, Ledger, or Trezor.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Reputation for innovation
Wasabi Wallet was awarded a share of Bitcointalk's longstanding coinjoin development bounty, along with JoinMarket:

Congratulations to the Wasabi and JoinMarket developers! JoinMarket pioneered a lot of CoinJoin science (and BTW, belcher wrote an excellent & comprehensive wiki article on privacy), while Wasabi is the first wallet that implements CoinJoin in both a highly-usable and sound way. As both a signer and a donor to the CoinJoin bounty fund, I'm thrilled that these two pieces of software exist!

For everyone looking to improve their privacy, I highly recommend checking out Wasabi, especially over centralized "mixers".


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Official Wasabi social network channels:

Quote from: Wasabi Wallet
                                               
9  Bitcoin / Wallet software / 2 New bug reports DELETED from Samourai Wallet's Gitlab Repo on: October 25, 2023, 04:46:08 PM
While doing research, I ran across two bugs taking place in Samourai's Whirlpool coinjoin protocol that could be spotted with the naked eye.  On October 25th, I opened two Gitlab issues describing the bug with links to the addresses and transactions the behavior occurred under. Within hours, both bug reports were deleted without comment. Since Samourai does not want to comment on their existence, I am publicly disclosing them:

https://web.archive.org/web/20231025112756/https://code.samourai.io/wallet/samourai-wallet-android/-/issues/461
https://web.archive.org/web/20231025112815/https://code.samourai.io/wallet/samourai-wallet-android/-/issues/462

Issue 461 is the most straightforward: You are spending 305 sats to yourself and paying 369 sats in mining fees to do it. There is no privacy benefit from creating this output since it is known to belong to the same owner as the inputs of the transaction.

Issue 462 appears even more straightforward at first but is actually more nuanced: The coinjoin coordinator is reusing addresses to collect its fees, with one receiving up to 36 incoming payments. While this might seem like an obvious privacy leak that can be fixed with a debug, it's not effective just to rotate the receive address. It would actually require an upgrade to the coinjoin protocol itself to hide the amount paid the coordinator (and save block space) with participant paying their fee directly in a coinjoin and the coordinator mimicking the participants' output size.
10  Bitcoin / Development & Technical Discussion / Why Bitcoin needs block filters on: October 23, 2023, 05:47:04 AM
A shocking amount of Bitcoin wallets are built such that they forfeit your privacy at step 1 by sharing your addresses with third party servers.  No matter how carefully you label your UTXOs and track your spending, common ownership clusters are revealed simply from the synchronization process.  This article covers the historical attempt to solve light wallet privacy (BIP37 bloom filters) that failed, and the prevailing solution (BIP157/158 compact block filters) for those who have hardware or bandwidth limitations that exclude usage of a full node: https://bitcoinmagazine.com/technical/why-bitcoin-wallets-need-block-filters

Combining compact block filtering with Tor and selectively disconnecting from peers after block download requests prevents any efforts to recombine this data into a traceable wallet history.
11  Bitcoin / Bitcoin Discussion / BIP324 (P2P encryption) was merged on: October 03, 2023, 12:47:31 PM
This is an exciting non consensus level upgrade that makes Bitcoin much more robust against nation state level attacks.  Before, it was transparent to your ISP that you are using Bitcoin because of how it talks to other nodes.  With the new v2 P2P protocol version, your traffic is encrypted and uses a pseudorandom pattern.

Quote from: BIP324 "Goals" Section
This proposal aims to achieve the following properties:

    Confidentiality against passive attacks: A passive attacker having recorded a v2 P2P bytestream (without timing and fragmentation information) must not be able to determine the plaintext being exchanged by the nodes.
    Observability of active attacks: A session ID identifying the encrypted channel uniquely is derived deterministically from a Diffie-Hellman negotiation. An active man-in-the-middle attacker is forced to incur a risk of being detected as peer operators can compare session IDs manually, or using optional authentication methods possibly introduced in future protocol versions.
    Pseudorandom bytestream: A passive attacker having recorded a v2 P2P bytestream (without timing information and fragmentation information) must not be able to distinguish it from a uniformly random bytestream.
    Shapable bytestream: It should be possible to shape the bytestream to increase resistance to traffic analysis (for example, to conceal block propagation), or censorship avoidance.[4]
    Forward secrecy: An eavesdropping attacker who compromises a peer's sessions secrets should not be able to decrypt past session traffic, except for the latest few packets.
    Upgradability: The proposal provides an upgrade path using transport versioning which can be used to add features like authentication, PQC handshake upgrade, etc. in the future.
    Compatibility: v2 clients will allow inbound v1 connections to minimize risk of network partitions.
    Low overhead: the introduction of a new P2P transport protocol should not substantially increase computational cost or bandwidth for nodes that implement it, compared to the current protocol.

https://github.com/bitcoin/bitcoin/pull/28331
12  Bitcoin / Bitcoin Discussion / A Comparison of Coinjoin Protocols and Clients [Open Source] on: September 28, 2023, 08:38:19 PM
CAUTION: Another user has created a self moderated topic about privacy services - remember to never trust "mixing sites" with your coins!

https://www.coinjoins.org/ is a new open source educational project for promoting the use of privacy preserving transactions on Bitcoin, called Coinjoins (a term coined by gmaxwell and Peter Todd). The origins of privacy on Bitcoin go all the way back to... well, Bitcointalk!  The concept arose in 2011 and was a highly demanded and anticipated way for users to separate the history of their funds from the future of their funds in a noncustodial way. There was even a huge bounty awarded to the Wasabi and Joinmarket teams for their development success.

Coinjoin supporting wallets are now fairly commonplace, but it's hard to figure out which one is the best tool for you without a good way to compare them against each other.  Trying to parse the documentation of every project is difficult, especially when teams such as Samourai engage in repeated dishonesty, which is why this community accessible guide was created.

There are three coinjoin protocols popular today:

-JoinMarket - https://mempool.space/tx/c270b84767431eae0aabcd4f99f93f1d299518aebb7529650dbbf41815561d03
-WabiSabi - https://mempool.space/tx/d465033214fd2309dcce5a90c45fcaa788aa4394ee36debe07aad8d8a37907d2
-ZeroLink - https://mempool.space/tx/3cef999a3c006be772f7f63fc87b718cd01146ab593644e0eeb3d61e753f02b8

They are implemented in many different clients:

-JoinMarket CLI/GUI (JoinMarket)
-Jam (JoinMarket)
-Wasabi 2.0 (WabiSabi)
-BTCPay Server (WabiSabi)
-Trezor (WabiSabi)
-Wasabi 1.0 (ZeroLink)
-Samourai (ZeroLink)
-Sparrow (ZeroLink)

Even if the implementation of the coinjoin protocol is correct, there is still a need for the client to protect its privacy against the coinjoin coordinator so that absolutely no one knows which outputs of a coinjoin transaction belong to which inputs.  This requires protecting registering your input and output using separate Tor identities, and protecting your xpub address from being leaked when querying your wallet balance.

In addition to the mining fees paid for coinjoin transactions, there are fees charged by coordinators in WabiSabi and ZeroLink and fees charged by makers in JoinMarket.  This is another aspect to consider when choosing providers within these protocols themselves.

Coinjoins.org is a work in progress, but it's an ambitious project:  It is hard to keep track of documentation and development, so if you see something that needs updating, feel free to create an issue or pull request - https://github.com/CoinjoinsOrg/coinjoins
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!