IMO this is a bit outdated now, it started as experiment years ago, but overall crypto progress is not sitting at one place, I think solution should be serverless to stay competitive at this field e.g. with btc’s payjoin upcoming serverless solution. Time passed, we can accept this loss and move on as we have not so much time at our lifes to sit at one place for years while everything else is moving forward.
is that btc solution interactive or non-interactive? also what does it actually do?
A wallet that creates a self-spend doesn’t have to run a server, they only do one “fire and forget” request to the first coinswap service in the noninteractive variant i.e. when you’re not a mixnode. While the coinswaps mixnodes are static servers, any group of people/friends could set up their own mwixnet if they wanted with the requirement of only one of them being honest. I don’t see it as outdated, it’s still a simple shuffle protocol that can run in noninteractive setting and it’s as good as it was when proposed which is better than anything else we have. The real question is who would run the noniteractive mwixnet, but that’s a question for any such service.
V2 is async: Serverless Payjoin - Receive surveillance-busting bitcoin transfers without hosting a secure endpoint · GitHub
More to come after this bounty: Bounty for payjoin development on Bitcoin
Just wanted to check in and see if there were any new developments here
@navie We are now in the testing phase. All community members are invited to test MWixnet CoinSwap.
Be warned though, it does require some minimal command line experience and requires testers to do their own compiling. So no point and click testing yet.
https://forum.grin.mw/t/mwixnet-testing-by-community/
Not yet implemented:
- Reorg protection
These milestone 3 tasks were completed some time ago, and I’ve since added a new pull request that adds
- reorg protection
- tor support using the Arti rust client
- async/await support
- new e2e test framework
Code reviewers and testers are very much welcome and appreciated!
EDIT: created Github issue for the problem I was having compiling with cargo.
Build and all test passed on Windows
For whoever wants to test MWixnet themselves:
On Windowss or Linux
git clone https://github.com/scilio/mwixnet-1/
cd mwixnet-1
git checkout reorg
rustup update
cargo update
cargo test
Additionally on Linux/Ubuntu you might need to install the following dependenciess, CC and openSSL
sudo apt-get install gcc
sudo apt install openssl -y
sudo apt install pkg-config
Documentation to understand how to use MWixnet
can be found here, in the README.md @noobvie:
@trab @Trinitron @Neo @renzokuken @Cobragrin
Please test if you are able to, or confirm that it is OK to approve Milestone 3 and release funds.
Voting to release funds for Milstone 3 will be in the public Telegram channel:
After the threshold of 4 is met (assuming there are no votes), funds calculation (£25,000 in BTC 1 month average) and Signing will proceed in the Private Grin CC channel as usual.
oh yea some good development