Skip to content

Latest commit

 

History

History
64 lines (49 loc) · 2.67 KB

README.md

File metadata and controls

64 lines (49 loc) · 2.67 KB
Raw

coinjoin-backend

Docker image running multiple services: bitcoind, blockbook, wasabi-wallet and wasabi-backend

Building

The command make

  • clones the WasabiWallet,
  • builds a docker image called coinjoin-backend-image,
  • creates a docker container called coinjoin-backend-container.

Running

The docker container is started with make start and stopped with make stop. The container doesn't discard its state when stopped.

The container runs a RegTest with the following services on the address 127.0.0.1:

Server Protocol Port User Password
Bitcoin knots P2P 18444
Bitcoin knots RPC 18443 rpc rpc
Blockbook HTTP 19121
Blockbook Websocket 19121
Faucet HTTP 8080
Wabisabi proxy HTTP 8081
WalletWasabi backend REST API 37127
WalletWasabi client REST API 37128

The command make create-container rebuilds the container which resets the network.

Connecting to WasabiWallet GUI

  • Run the WasabiWallet GUI.
  • Go to settings of the GUI and
    • turn off network encryption (TOR),
    • set network to RegTest,
    • set bitcoin P2P Endpoint to 127.0.0.1:18444.
  • Restart the GUI.
  • Open http://127.0.0.1:8080 in your browser.
  • Send yourself money.

Running WasabiWallet GUI from docker

Use command make run-wallet to start WasabiWallet GUI with already preloaded accounts (no password). For convenience also Trezor accounts with all all seed (no passphrase) are preloaded.

Using custom WabiSabiClientLibrary (middleware)

Download artifacts from github action unzip files and make them executable.

unzip ~/Downloads/WabiSabiClientLibrary-bin.zip -d ~/Downloads/WabiSabiClientLibrary
chmod +x ~/Downloads/WabiSabiClientLibrary/*/publish/WalletWasabi.WabiSabiClientLibrary

Start coinjoin-backend image with mounted middleware:

docker run -d --net host -v ~/Downloads/WabiSabiClientLibrary/linux-x64/publish:/mnt/middleware coinjoin-backend-image

Proxy

For development in browser environment proxy accepts preflight OPTIONS requests and overrides Access-Control-Allow-Origin header

Proxy endpoints: