Wasabi Wallet, formerly known as HiddenWallet is a ZeroLink compliant Bitcoin wallet. We are dedicated to restore Bitcoin's fungibility and provide the highest possible privacy for our users.
HiddenWallet's code is archived in the hiddenwallet-v0.6 branch of this repository.

Code Quality	Windows Tests	Linux Tests	OSX Tests	License

1. Get .NET Core.
2. Download the Tor Experd Bundle. (Not the Tor Browser.) https://www.torproject.org/download/download
3. Run tor.exe.
4. Fire up command line:

git clone https://github.com/zkSNACKs/WalletWasabi
cd WalletWasabi
dotnet restore && dotnet build
cd WalletWasabi.Tests
dotnet test

1. dotnet test takes about 3 minutes, the first time it'll take 1-2 minutes longer, because it downloads bitcoind. This daemon is used by the tests in regression test mode to simulate the Bitcoin network.

2. If you'd happen to terminate the tests immaturely, make sure you also terminate the bitcoind daemon process from the Task Manager, otherwise next time your tests would fail.

3. Tests are using %appdata%\WalletWasabi folder to log and for other things, so you can delete it after you no longer wish to do anything with the software anymore.

Goal: Stability, feature minimalization.

It is expected for the proposed timeline to take roughly 1.5 times longer.

• 1. Wallet Back End. 2 weeks. NBitcoin, Bitcoin Core RPC, ASP.NET. Build back end.

• 2. Small Tor Library. 1 week. Tor, .NET Core, cross platform. Build a small Tor library based on DotNetTor, that removes features those are unrelated to the wallet and makes the rest more stable.

• 3. Key Manager. 1 week. NBitcoin. Build a new, high performance key manager with accounts, labelling, etc...

• 4. Wallet Client. 1 month. NBitcoin. Build a high performance client that can work with the new back end, which is built for client side filtering.

  Depends on:

  • ALL previous items

• 5. ZeroLink Research. 1 month. Bitcoin privacy, cryptography. Research ZeroLink, based on technological advancements.

• 6. ZeroLink Coordinator. 2 weeks. NBitcoin, Bitcoin Core RPC. Revise the ZeroLink Coordinator code based on ZeroLink v2 Revision.

  Depends on:

  • ZeroLink Research

• 7. ZeroLink Client. 2 weeks. NBitcoin. Revise the ZeroLink Client code based on ZeroLink v2 Revision.

  Depends on:

  • ZeroLink Research
  • ZeroLink Coordinator

• 8. Design GUI. 1 week. Paper and pen.

• 8. Build GUI. 1 month. Electron, front end, Bitcoin. Redesign the user experience and build it.

  Depends on:

  • ALL previous items

• 9. Documentation. 1 week. Bitcoin. Create documentation.

  Depends on:

  • ALL previous items

• 10. Internal Testing. 2 weeks. Bitcoin or .NET or front end. Test the software and fix the bugs (if there is any haha).

  Depends on:

  • ALL previous items, except Documentation

• 11. Deploy To Mainnet. 2 weeks. .NET Core, ASP.NET Core deployment. Deploy the software to Bitcoin Mainnet.

  Depends on:

  • ALL previous items, except Documentation

• 12. Mainnet Beta Testing. 2 weeks. It's rather a marketing phase. The goal is to get at least 1 round done with > 100 user.

  Depends on:

  • ALL previous items