You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
AdamISZ d7a2b6b5a8
regtest: fix wallet load in Qt
7 years ago
docs regtest: fix wallet load in Qt 7 years ago
jmbase Convert jmclient to py3 style 7 years ago
jmbitcoin Convert jmclient to py3 style 7 years ago
jmclient Convert JoinmarketQt to PySide2 7 years ago
jmdaemon Convert jmclient to py3 style 7 years ago
pubkeys add undeath's pgp key 7 years ago
scripts regtest: fix wallet load in Qt 7 years ago
test Convert jmclient to py3 style 7 years ago
.coveragerc remove slowaes 7 years ago
.gitignore Convert jmclient to py3 style 7 years ago
.travis.yml Convert jmclient to py3 style 7 years ago
LICENSE Initial commit 9 years ago
README.md update install instructions in README for new JoinmarketQT install 7 years ago
conftest.py Revert "Revert "Python 3 style conversion"" 7 years ago
install.sh Convert jmclient to py3 style 7 years ago
requirements-dev.txt add flake8 config and enable in travis 7 years ago
setup.cfg remove slowaes 7 years ago
setupall.py add setupall.py --all mode 7 years ago

README.md

joinmarket-clientserver

Joinmarket refactored to separate client and backend operations

The latest release uses segwit wallets by default, you are strongly recommended not to change this, but you can use a non-segwit wallet by setting segwit = false in joinmarket.cfg.

Quickstart

For good quality privacy, performance and reliability, Bitcoin Core is required for Makers (yield generators), and recommended for takers (doing coinjoins). Use version 0.15+ ideally; 0.13.1+ required.

For doing coinjoins (Taker side), you can also run without Bitcoin Core, connecting to Electrum servers.

Once you've downloaded this repo, either as a zip file, and extracted it, or via git clone:

./install.sh -p python3
(follow instructions on screen; provide sudo password when prompted)
source jmvenv/bin/activate
cd scripts

(You can omit -p python3 if you want to use Python2)

You should now be able to run the scripts like python wallet-tool.py etc., just as you did in the previous Joinmarket version.

Alternative to this "quickstart" (including for MacOS): follow the install guide.

Upgrade for segwit

See the segwit upgrade guide if you need to update your wallet.

Usage

If you are new, follow and read the links in the usage guide.

If you are running Joinmarket-Qt, you can instead use the walkthrough to start.

If you are not new to Joinmarket, the notes in the scripts readme help to understand what has and hasn't changed about the scripts.

Joinmarket-Qt

Provides single join and multi-join/tumbler functionality (i.e. "Taker") only, in a GUI. NOTE: This is currently only available for Python3, not Python2 (due to bugs in the PySide2 Python2 implementation). It's possible but unlikely that the Python2 version will be fixed, but in any case Python2 will be deprecated at some point.

If binaries are built, they will be gpg signed and announced on the Releases page.

To run the script joinmarket-qt.py from the command line, you need to install two more packages: use these 2 commands:

pip install PySide2
pip install git+git://github.com/sunu/qt5reactor.git@58410aaead2185e9917ae9cac9c50fe7b70e4a60

After this, the command python joinmarket-qt.py from within the scripts subdirectory should work. There is a walkthrough for what to do next.

Notes on architectural changes (can be ignored)

Motivation: By separating the code which manages conversation with other Joinmarket participants from the code which manages this participant's Bitcoin wallet actions, we get a considerable gain at a minor cost of an additional layer: code dependencies for each part are much reduced, security requirements of the server/daemon layer are massively reduced (which can have several advantages such as it being more acceptable to distribute this layer as a binary), and client code can be written, implementing application-level logic (do join with coins X under condition X) using other Bitcoin libraries, or wallets, without knowing anything about Joinmarket's inter-participant protocol. An example is my work on the Joinmarket electrum plugin.

It also means that updates to the Bitcoin element of Joinmarket, such as P2SH and segwit, should have extremely minimal to no impact on the backend code, since the latter just implements communication of a set of formatted messages, and allows the client to decide on their validity beyond simply syntax.

Joinmarket's own messaging protocol is thus enforced only in the server/daemon.

The client and server currently communicate using twisted.protocol.amp, see AMP, and the specification of the communication between the client and server is isolated to this module. Currently the messaging layer of Joinmarket is IRC-only (but easily extensible, see here. The IRC layer is also implemented here using Twisted, reducing the complexity required with threading.

The "server" is just a daemon service that can be run as a separate process (see scripts/joinmarketd.py), or for convenience in the same process (the default for command line scripts).

TESTING

Instructions for developers for testing here. If you want to help improve the project, please have a read of this todo list.