Topic: CoinJoin: Bitcoin privacy for the real world - page 4. (Read 294672 times)

I think nopara73 deserves this bounty for the CoinJoin implementation he did in Wasabi Wallet.

With the addition of TOR integration and Full node use this wallet has come a long way. In some aspects IMHO it has exceeded the expectations of the bounty because the UX is developed leading to better usability for non technical individuals. It would be appreciated if someone would clarify any shortcomings if need be but IMHO nopara deserves the award.

In my world, and soon to be yours, most governments will no longer exist, because bitcoin transactions are made anonymously so they can not tax on citizens at all. The biggest success of bitcoin is that it has become an effective way to cover the government's wealth. This is one of the few bitcoin secrets, hoping to help you understand more about the role of bitcoins in today's world.

Pay the man.

You have my vote as well.  I wonder why there is a lack of communication?

nopara73 you have my vote.

I've used Wasabi wallet a few times now and I think it's awesome. The fact that it has made nearly 23,000 BTC ($114,300,000) fungible, using CoinJoin, seems like it's definitely entitled to (some of) the bounty.

I will test Wasabi Wallet for sure. Thank you!

Since I did not receive a reply to my previous application[1] for the coinjoin bounty, which I submitted half a year ago, with the exception of Pieter Wuille, who to my knowledge did not succeed to discuss this with the rest of the keyholders, I will consider this as a rejection. So in this post I would like to report a status update and ask you to reconsider the application with the new developments to Wasabi Wallet[2,9] in mind.

- Half a year ago Wasabi created 110 BTC equal coinjoin outputs in total[1], today this number is 22941 BTC.[2]
- Wasabi now does P2P communication over Tor, too.[3]
- Wasabi now broadcasts transactions over Tor to a peer. Previously transaction broadcasting happened to the backend over Tor.[3]
- Wasabi now provides .dmg[4] and .deb[5] packages.
- Wasabi now mixes on the changes, resulting in more efficient mixes.[6]
- Wasabi now partially integrates full nodes: If a full node is running in the background, block fetching happens from it by default instead of connected peers.[5]
- Wasabi now comes with a daemon that can be used for mixing.[7]
- Wasabi have deterministic builds.[8]

Thank you for considering my reapplication!
Cheers, nopara73



References.

• [1] Wasabi Wallet CoinJoin Bounty Application: https://bitcointalksearch.org/topic/m.46988492
• [2] Wasabi Wallet: https://wasabiwallet.io/
• [3] Bitcoin Core vs Wasabi Wallet — Network Level Privacy: https://medium.com/@nopara73/bitcoin-core-vs-wasabi-wallet-network-level-privacy-bdca1d501387
• [4] Wasabi v1.0.4: https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.0.4
• [5] Wasabi v1.1.1: https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.1.1
• [6] Upcoming Wasabi Wallet Hard Fork: https://medium.com/@nopara73/upcoming-wasabi-wallet-hard-fork-609f271d9c41
• [7] Wasabi v1.1.3: https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.1.3
• [8] Wasabi Deterministic Build Guide: https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/Guides/DeterministicBuildGuide.md
• [9] WalletWasabi GitHub: https://github.com/zkSNACKs/WalletWasabi/

I support this demand too. Bustapay is a good effort to help in the privacy aspect and I think that not using the funds is worst than using them to provide willingness to participate.

I think Maxwell Theymos and Pieter still have access to the funds as they moved them for consolidation but it would be great to have some confirmation.

As some of you know, I authored: bustapay (bip79) and published a reference implementation of it along with onboarded a major service.


I believe that bustapay itself has the most potential to further the goal of "practical bitcoin privacy", where even the smallest penetration of bustapay payments results in outsized privacy gains for both participants and the bitcoin system at large. Unfortunately bustapay itself suffers from a pretty big "chicken and egg" problem: No one wants to implement support for receiving bustapayments when wallets don't support it. Wallets don't want to support it when no one supports receiving it.


I also believe that the best way to incentivize development is offering by offering concrete rewards for concrete work. So I propose (some of) the coinjoin bounty fund is used to offer compensation to a bunch of wallets for implementing support. Something like offering 2 or 3 bitcoin to each "major" wallet that implements full support.

(And to be clear, I'm not requesting/wanting/needing any of the bounty for myself.)

Hi nopara,

I've interestingly followed your recent talks and blog posts as well as read the future idea plan for Wasabi yesterday and I'm very excited about your work. The last two days I did two CoinJoins with Wasabi in Testnet just out of curiosity.
Today I clicked randomly on the Development subforum and just saw this thread on top with your posting. So it came just in the right time for me.

Your work is amazing, I keep my fingers crossed that you'll succeed. Since I'm not able to contribute to your project on a technical level you would need, expect my donation soon

Hi there,

I am nopara73 and I would like to apply for a part of the CoinJoin bounty.[21]
During the past 3 years I worked tirelessly to improve the privacy of Bitcoin. I wrote over 100 articles on privacy,[22] participated in a privacy workshop[1] and gave privacy presentations on various conferences.[2,3] I designed ZeroLink: Bitcoin Fungibility Framework,[4] within that detailed Chaumian CoinJoin Bitcoin mixing technique[5] and participated in the creation of Pay To EndPoint scheme.[1]
I created the the Tor library for .NET Core,[6,12] I am a maintainer of on NTumbleBit,[7] I participated in the early stages of the creation of Stratis: Breeze wallet,[8] created and deployed the a full block downloading SPV wallet on the mainnet: HiddenWallet.[9] I also lost an impressive amount of weight during the past few months on Ketogenic diet.[10]

The past year I was lucky enough to meet and work together with great people who helped me rewrite and release the latest iteration of HiddenWallet: Wasabi Wallet,[11] which brings me to the CoinJoin bounty.
Wasabi is an open-source, desktop Bitcoin wallet, working on Windows, Linux and OSX, written in .NET Core (C#),[12] which is the cross platform and open source .NET. Wasabi uses NBitcoin[13] as its Bitcoin library, to which Wasabi developers are frequent contributors: @lontivero,[14] @nopara73.[15] Wasabi uses Avalonia[16] library as its UI framework where Wasabi developer @danwalmsley[17] is a maintainer.
Wasabi does not support and does not plan to support other currencies in the future.

Wasabi uses and ships with the Tor anonymity network. In Wasabi we implemented and deployed a BIP157-BIP158-like Golomb-Rice filtering light wallet architecture. To my knowledge Wasabi is the only light wallet that has been deployed on the mainnet and has strong protections in place against network observers, unless we consider Stratis's Breeze wallet[8] a light wallet (it's full block SPV.) (ToDO: what's the state of Neutrino?)
Wasabi have various privacy features, among many, its compulsory coin control feature and a built-in intra-wallet blockchain analysis tool combined with compulsory labeling system to give feedback to the user and guide her to make educated, privacy-aware decisions at spending.
Wasabi's main feature is the built in Chaumian CoinJoin, which has already mixed (created equal outputs) over 110 bitcoins on the mainnet. For real time statistics and last five coinjoin txids, see: http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/



Wasabi's CJ implementation works as it was described in the first post of this forum thread:

For more information, a detailed and up to date description of the inner workings and future plans of Wasabi can be found here:

A Technical Overview of Wasabi Wallet, Future Ideas, Plans and Strategy: https://github.com/zkSNACKs/Meta

The document is not a marketing pitch. In there we honestly detailed the tradeoffs and rationales behind every major design decision we made. I hope it will satisfy all your doubts.

Where does the money go?

A software is not a static, but a living and breathing creature that requires nurturing. Therefore the sustainability of Wasabi is also an important factor, that we did not neglect. There is a (0.003%*anonymity set gained*denomination) per user CoinJoin fee that adds up to 0.3% for a CoinJoin with 100 participants, which is our goal. (Denomination:0.1BTC, only take fee after the denomination, CJ changes doesn't count.) When we reach this number (currently 20) we will let the rounds to happen faster (currently 1/day.) Bootstrapping this system is a balancing act.
The bounty would go to sustain and improve of the wallet and we hope by the time the bounty money runs out project will be able to sustain itself.
Finally, it may also be worth pointing out that I have been accepting donations myself:

Thank you for considering our application!
Cheers, nopara73

References.

• [1] Pay To EndPoint: https://medium.com/@nopara73/pay-to-endpoint-56eb05d3cac6
• [2] Breaking Bitcoin 2017, nopara7 - Roadmap To Anonymous Bitcoin: https://www.youtube.com/watch?v=RY-QQOjycgI&t=0m51s
• [3] Building on Bitcoin 2018, nopara7 - Anonymous Bitcoin: https://www.youtube.com/watch?v=XORDEX-RrAI&t=17m01s
• [4] ZeroLink: https://github.com/nopara73/ZeroLink/
• [5] Chaumian CoinJoin: https://github.com/nopara73/ZeroLink/#ii-chaumian-coinjoin
• [6] DotNetTor: https://github.com/nopara73/DotNetTor/
• [7] NTumbleBit: https://github.com/NTumbleBit/NTumbleBit/
• [8] StratisBitcoinFullNode: https://github.com/stratisproject/StratisBitcoinFullNode
• [9] HiddenWallet: https://github.com/zkSNACKs/WalletWasabi/tree/hiddenwallet-v0.6
• [10] Lyle McDonald - Rapid Fat Loss Handbook: https://store.bodyrecomposition.com/product/rapid-fat-loss-handbook/
• [11] WalletWasabi: https://github.com/zkSNACKs/WalletWasabi
• [12] .NET Core: https://en.wikipedia.org/wiki/.NET_Core
• [13] NBitcoin: https://github.com/MetacoSA/NBitcoin
• [14] lontivero on GitHub: https://github.com/lontivero
• [15] nopara73 on GitHub: https://github.com/nopara73
• [16] Avalonia: https://github.com/AvaloniaUI/Avalonia/
• [17] danwalmsley on GitHub: https://github.com/danwalmsley
• [18] BIP157: https://github.com/bitcoin/bips/blob/master/bip-0157.mediawiki
• [19] BIP158: https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki
• [20] CoinJoin bounty: https://bitcointalksearch.org/topic/m.2983911
• [21] nopara73 blog: https://anonymousbitcoin.com

Did you think building a decentralized currency would be simple? One could argue that current privacy is "good enough" to protect identities from most parties, even as blockchain analysis makes address linkage trival, but there is more. Say the DOJ gets tired of fooling around with bitcoin and starts cracking down on funds with dubious addresses in their past. They could even go so far as to put out a list of verified "good" addresses, and make it illegal to accept coins that have been in contact with any others. Now some coins become worthless, or at least worth less than others, and the system breaks down. There is no fungibility without privacy, and no decentralized currency without fungibility.

Although I think the Lightning Network may have some real benefits in this area, since the creation of a channel will not necessarily signify an actual transaction between the two parties, and connecting to a random node cannot incriminate a user. When the channel is closed and funds are transferred, it's basically like a CoinJoin for all parties involved.

This seems overly complicated

where can I find a comparison of conjoin?
is there a website?

very informative can someone make test QT soon?   

Gmaxwell and his bitcoin devs should realise that the IRS has already mapped out all significant bitcoin addresses to social security numbers, whilst they debate the alpha tech of ring sigs but yet are doing nothing to fix the privacy issue

Yes, the facilitator gains no extra information about the transaction than is observable from the outside, if blind signing is used

Hi All,

Adam Ficsor (@nopara73) and Myself are currently trying to test an implementation of a Chaumian CoinJoin mixer and client wallet using the ZeroLink framework and HiddenWallet. https://github.com/nopara73/ZeroLink

We are aiming for 100 participants in the first scale testnet test and any participation would be appreciated. The mix is ongoing and currently we have about half the required anonymity set to conclude our test. To participate you basically have to download binaries (or compile from source), get some testnet coins, move them into a bech32 address in HiddenWallet and join the mix.

Many thanks to those that than can help.

A guide to participating in the test:

https://github.com/nopara73/HiddenWallet/blob/master/HiddenWallet.Documentation/TestingTheZeroLinkMixer.md