2022-01-22 17:09:14 +01:00
#!/usr/bin/env bash
###
#
2022-10-13 14:07:48 +02:00
# This script helps initializing the JoinMarket docker containers.
2022-01-22 17:09:14 +01:00
# Its main goal is to make CoinJoin transactions possible in the regtest environment.
#
# It has two responsibilities:
2022-10-13 14:07:48 +02:00
# - funding wallets in all containers with some coins
chore(regtest): initial joinmarket-ng backend for regtest environment (#1240)
* chore(regtest): initial joinmarket-ng backend for regtest environment
Adds jmwalletd, directory servers, makers, and bitcoind to the regtest
docker-compose environment so jam can be developed against the jm-ng
backend end-to-end.
chore(regtest): wire docker compose env and vite dev proxy for jm-ng
Connects the local regtest containers into a single compose network,
adds tor and fund-wallet helpers, and points Vite's dev proxy at the
local jmwalletd instance.
fix(tags): recognize cj-change, used-empty, and flagged UTXO statuses
joinmarket-ng's WalletService emits four statuses jam's JmPlainTagValue
didn't cover: 'cj-change' (deanonymising change from our CJ),
'used-empty' (previously-used address with zero balance), and 'flagged'
(address shared in a CJ that later failed). They fell through to the
generic 'default' badge with no distinguishing styling.
Add them to JmPlainTagValue and the status->variant map. 'used-empty'
maps to the existing 'used' variant, 'flagged' to 'reused' (both signal
a used address the user should avoid reusing). Add a dedicated
'cj-change' badge variant (emerald) next to 'cj-out' so the
deanonymising change output is visually distinct from an equal-amount
CJ output.
fix(send): keep direct send available with maker
Only block collaborative sends while the maker service is running. Direct sends stay enabled and the form explains why the collaborative toggle is unavailable.
Changelog: Allow direct sends while the maker service is running
docs(dev): explain jm-ng backend workflow
fix(auth): only clear auth on invalid_token 401s
Previously every 401 response cleared the session and logged the user out. jm-ng returns 401 for service-state errors (e.g. POST /tumbler/stop when nothing is running), which should never drop the session. Inspect the WWW-Authenticate header and only clear auth when the server signals ``error="invalid_token"``.
Changelog: Non-auth 401 responses no longer log the user out.
fix(dev): proxy /jmws to the jm-ng HTTPS port
jm-ng serves WebSocket on the same port as the HTTPS API. The `jm-ng:dev` script used to override JMWALLETD_WEBSOCKET_PORT to 32283, but the regtest stack exposes that port without a matching listener, so vite proxied WebSocket upgrades into a dead port and the handshake returned empty. Default the env var to JMWALLETD_API_PORT and drop the override.
Changelog: Fix WebSocket proxying in the local jm-ng dev setup.
fix(dev): correct jm-ng websocket port and proxy targets
Update the README and developer docs to reflect that both ports must be
set when overriding for a custom jm-ng setup.
fix(dev): correct jm-ng websocket port (#1237)
chore(dev): distinct server configs for various backends
* chore(regtest): address jm-ng review comments
---------
Co-authored-by: m0wer <m0wer@sgn.space>
Co-authored-by: Parth Bandwal <143504541+parrth20@users.noreply.github.com>
2026-05-05 13:52:41 +02:00
# - starting the maker service in secondary through quinary containers
2022-01-22 17:09:14 +01:00
#
###
set -Eeuo pipefail
script_dir = $( cd " $( dirname " ${ BASH_SOURCE [0] } " ) " & >/dev/null && pwd -P)
2026-06-16 21:14:44 +05:30
# fund wallet in primary JoinMarket NG container
2026-07-26 15:32:15 +02:00
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket --mixdepth 0 --unmatured --blocks 1
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket --mixdepth 1 --unmatured --blocks 2 # outputs should be flagged as "reused"
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket --mixdepth 4 --unmatured --blocks 1
2022-01-22 17:09:14 +01:00
2026-06-16 21:14:44 +05:30
# fund wallet in ng standalone secondary container
2022-05-11 10:05:01 +02:00
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket2 --unmatured --blocks 50
2026-06-16 21:14:44 +05:30
# fund wallet in legacy clientserver native tertiary container
2022-10-13 14:07:48 +02:00
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket3 --unmatured --blocks 50
2022-01-22 17:09:14 +01:00
2026-06-16 21:14:44 +05:30
# fund wallet in legacy clientserver jam-standalone quaternary container
chore(regtest): initial joinmarket-ng backend for regtest environment (#1240)
* chore(regtest): initial joinmarket-ng backend for regtest environment
Adds jmwalletd, directory servers, makers, and bitcoind to the regtest
docker-compose environment so jam can be developed against the jm-ng
backend end-to-end.
chore(regtest): wire docker compose env and vite dev proxy for jm-ng
Connects the local regtest containers into a single compose network,
adds tor and fund-wallet helpers, and points Vite's dev proxy at the
local jmwalletd instance.
fix(tags): recognize cj-change, used-empty, and flagged UTXO statuses
joinmarket-ng's WalletService emits four statuses jam's JmPlainTagValue
didn't cover: 'cj-change' (deanonymising change from our CJ),
'used-empty' (previously-used address with zero balance), and 'flagged'
(address shared in a CJ that later failed). They fell through to the
generic 'default' badge with no distinguishing styling.
Add them to JmPlainTagValue and the status->variant map. 'used-empty'
maps to the existing 'used' variant, 'flagged' to 'reused' (both signal
a used address the user should avoid reusing). Add a dedicated
'cj-change' badge variant (emerald) next to 'cj-out' so the
deanonymising change output is visually distinct from an equal-amount
CJ output.
fix(send): keep direct send available with maker
Only block collaborative sends while the maker service is running. Direct sends stay enabled and the form explains why the collaborative toggle is unavailable.
Changelog: Allow direct sends while the maker service is running
docs(dev): explain jm-ng backend workflow
fix(auth): only clear auth on invalid_token 401s
Previously every 401 response cleared the session and logged the user out. jm-ng returns 401 for service-state errors (e.g. POST /tumbler/stop when nothing is running), which should never drop the session. Inspect the WWW-Authenticate header and only clear auth when the server signals ``error="invalid_token"``.
Changelog: Non-auth 401 responses no longer log the user out.
fix(dev): proxy /jmws to the jm-ng HTTPS port
jm-ng serves WebSocket on the same port as the HTTPS API. The `jm-ng:dev` script used to override JMWALLETD_WEBSOCKET_PORT to 32283, but the regtest stack exposes that port without a matching listener, so vite proxied WebSocket upgrades into a dead port and the handshake returned empty. Default the env var to JMWALLETD_API_PORT and drop the override.
Changelog: Fix WebSocket proxying in the local jm-ng dev setup.
fix(dev): correct jm-ng websocket port and proxy targets
Update the README and developer docs to reflect that both ports must be
set when overriding for a custom jm-ng setup.
fix(dev): correct jm-ng websocket port (#1237)
chore(dev): distinct server configs for various backends
* chore(regtest): address jm-ng review comments
---------
Co-authored-by: m0wer <m0wer@sgn.space>
Co-authored-by: Parth Bandwal <143504541+parrth20@users.noreply.github.com>
2026-05-05 13:52:41 +02:00
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket4 --unmatured --blocks 50
2026-06-16 21:14:44 +05:30
# fund wallet in ng peer quinary container
. " $script_dir /fund-wallet.sh " --container jm_regtest_joinmarket5 --unmatured --blocks 50
2026-06-07 22:07:53 +05:30
2023-09-08 13:26:59 +02:00
# fund addresses of seed 'abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about'
# this is useful if you "import an existing wallet" and verify rescanning the chain works as expected.
dummy_wallet_address1 = 'bcrt1q6rz28mcfaxtmd6v789l9rrlrusdprr9pz3cppk' # 1st address of jar A (m/84'/1'/0'/0/0)
dummy_wallet_address2 = 'bcrt1qt5yxk3xzrx66q9wd5sdyynklqynqcyf7uh74j3' # 8th address of jar C (m/84'/1'/2'/0/7)
dummy_wallet_address3 = 'bcrt1qn8804dw5fahuc5cwqteuq5j4xlhk2cnkq7a8kw' # 21st change address of jar E (m/84'/1'/4'/1/21)
2026-07-23 13:06:40 +02:00
dummy_wallet_address_fb0 = 'bcrt1q7war3lusq3ez633rzzfkp75unfcgrqqcu80sgp0ellhrdvkzxh5swspygk' # 1st fb address (m/84'/1'/0'/2/0)
dummy_wallet_address_fb959 = 'bcrt1q6rlcknptmqhf4w20928tpz6px4y70960gyupd029c7vx7kdjwt0q46nk9c' # 960th fb address (m/84'/1'/0'/2/959)
2026-07-26 15:32:15 +02:00
# make block rewards spendable: 100 + 5 (default of `taker_utxo_age`) + 1 = at least 106 blocks
2023-09-08 13:26:59 +02:00
. " $script_dir /mine-block.sh " 2 " $dummy_wallet_address1 " & >/dev/null
. " $script_dir /mine-block.sh " 2 " $dummy_wallet_address2 " & >/dev/null
. " $script_dir /mine-block.sh " 2 " $dummy_wallet_address3 " & >/dev/null
2026-07-23 13:06:40 +02:00
. " $script_dir /mine-block.sh " 1 " $dummy_wallet_address_fb0 " & >/dev/null
. " $script_dir /mine-block.sh " 1 " $dummy_wallet_address_fb959 " & >/dev/null
2023-09-08 13:26:59 +02:00
. " $script_dir /mine-block.sh " 100 & >/dev/null
2022-01-22 17:09:14 +01:00
2022-10-13 14:07:48 +02:00
start_maker( ) {
local base_url; base_url = ${ 1 :- }
local wallet_name; wallet_name = ${ 2 :- }
local wallet_password; wallet_password = ${ 3 :- }
# Check if maker service is not yet running
verify_no_open_session_or_throw " $base_url "
2022-01-22 17:09:14 +01:00
2022-10-13 14:07:48 +02:00
local maker_running; maker_running = $( is_maker_running " $base_url " )
2022-01-22 17:09:14 +01:00
2022-10-13 14:07:48 +02:00
if [ " $maker_running " != false ] ; then
msg_success "Maker is already running"
2022-01-22 17:09:14 +01:00
else
2022-10-13 14:07:48 +02:00
# Unlock wallet
local unlock_result; unlock_result = $( unlock_wallet " $base_url " " $wallet_name " " $wallet_password " )
local auth_token; auth_token = $( jq -r '.token' <<< " $unlock_result " )
local auth_header; auth_header = " Authorization: Bearer $auth_token "
# --------------------------
# Start maker
# --------------------------
## API: POST /api/v1/wallet/$wallet_name/maker/start
##
## Response:
## 200 OK
## {}
msg " Starting maker service for wallet $wallet_name .. "
2026-06-07 22:07:53 +05:30
local start_maker_request_payload; start_maker_request_payload = "{\"txfee\":\"0\",\"cjfee_a\":\"0\",\"cjfee_r\":\"0.0003\",\"ordertype\":\"sw0absoffer\",\"minsize\":\"1\"}"
2022-10-13 14:07:48 +02:00
chore(regtest): initial joinmarket-ng backend for regtest environment (#1240)
* chore(regtest): initial joinmarket-ng backend for regtest environment
Adds jmwalletd, directory servers, makers, and bitcoind to the regtest
docker-compose environment so jam can be developed against the jm-ng
backend end-to-end.
chore(regtest): wire docker compose env and vite dev proxy for jm-ng
Connects the local regtest containers into a single compose network,
adds tor and fund-wallet helpers, and points Vite's dev proxy at the
local jmwalletd instance.
fix(tags): recognize cj-change, used-empty, and flagged UTXO statuses
joinmarket-ng's WalletService emits four statuses jam's JmPlainTagValue
didn't cover: 'cj-change' (deanonymising change from our CJ),
'used-empty' (previously-used address with zero balance), and 'flagged'
(address shared in a CJ that later failed). They fell through to the
generic 'default' badge with no distinguishing styling.
Add them to JmPlainTagValue and the status->variant map. 'used-empty'
maps to the existing 'used' variant, 'flagged' to 'reused' (both signal
a used address the user should avoid reusing). Add a dedicated
'cj-change' badge variant (emerald) next to 'cj-out' so the
deanonymising change output is visually distinct from an equal-amount
CJ output.
fix(send): keep direct send available with maker
Only block collaborative sends while the maker service is running. Direct sends stay enabled and the form explains why the collaborative toggle is unavailable.
Changelog: Allow direct sends while the maker service is running
docs(dev): explain jm-ng backend workflow
fix(auth): only clear auth on invalid_token 401s
Previously every 401 response cleared the session and logged the user out. jm-ng returns 401 for service-state errors (e.g. POST /tumbler/stop when nothing is running), which should never drop the session. Inspect the WWW-Authenticate header and only clear auth when the server signals ``error="invalid_token"``.
Changelog: Non-auth 401 responses no longer log the user out.
fix(dev): proxy /jmws to the jm-ng HTTPS port
jm-ng serves WebSocket on the same port as the HTTPS API. The `jm-ng:dev` script used to override JMWALLETD_WEBSOCKET_PORT to 32283, but the regtest stack exposes that port without a matching listener, so vite proxied WebSocket upgrades into a dead port and the handshake returned empty. Default the env var to JMWALLETD_API_PORT and drop the override.
Changelog: Fix WebSocket proxying in the local jm-ng dev setup.
fix(dev): correct jm-ng websocket port and proxy targets
Update the README and developer docs to reflect that both ports must be
set when overriding for a custom jm-ng setup.
fix(dev): correct jm-ng websocket port (#1237)
chore(dev): distinct server configs for various backends
* chore(regtest): address jm-ng review comments
---------
Co-authored-by: m0wer <m0wer@sgn.space>
Co-authored-by: Parth Bandwal <143504541+parrth20@users.noreply.github.com>
2026-05-05 13:52:41 +02:00
local start_maker_result; start_maker_result = $( curl " $base_url /api/v1/wallet/ $wallet_name /maker/start " --silent --show-error --insecure -H " $auth_header " -H "Content-Type: application/json" --data " $start_maker_request_payload " | jq "." )
2022-10-13 14:07:48 +02:00
if [ " $start_maker_result " != "{}" ] ; then
msg_warn " There has been a problem starting the maker service: $start_maker_result "
else
msg_success " Successfully started maker for wallet $wallet_name . "
fi
# do not lock the wallet as this will terminate the maker service
msg_warn " Wallet $wallet_name remains unlocked! "
2022-01-22 17:09:14 +01:00
fi
2022-10-13 14:07:48 +02:00
}
2026-06-16 21:14:44 +05:30
msg " Attempt to start maker service for wallet $wallet_name in ng standalone container.. "
2022-10-13 14:07:48 +02:00
start_maker "https://localhost:29183" "Satoshi.jmdat" "test"
2026-06-16 21:14:44 +05:30
msg " Attempt to start maker service for wallet $wallet_name in legacy native container.. "
2022-10-13 14:07:48 +02:00
start_maker "https://localhost:30183" "Satoshi.jmdat" "test"
chore(regtest): initial joinmarket-ng backend for regtest environment (#1240)
* chore(regtest): initial joinmarket-ng backend for regtest environment
Adds jmwalletd, directory servers, makers, and bitcoind to the regtest
docker-compose environment so jam can be developed against the jm-ng
backend end-to-end.
chore(regtest): wire docker compose env and vite dev proxy for jm-ng
Connects the local regtest containers into a single compose network,
adds tor and fund-wallet helpers, and points Vite's dev proxy at the
local jmwalletd instance.
fix(tags): recognize cj-change, used-empty, and flagged UTXO statuses
joinmarket-ng's WalletService emits four statuses jam's JmPlainTagValue
didn't cover: 'cj-change' (deanonymising change from our CJ),
'used-empty' (previously-used address with zero balance), and 'flagged'
(address shared in a CJ that later failed). They fell through to the
generic 'default' badge with no distinguishing styling.
Add them to JmPlainTagValue and the status->variant map. 'used-empty'
maps to the existing 'used' variant, 'flagged' to 'reused' (both signal
a used address the user should avoid reusing). Add a dedicated
'cj-change' badge variant (emerald) next to 'cj-out' so the
deanonymising change output is visually distinct from an equal-amount
CJ output.
fix(send): keep direct send available with maker
Only block collaborative sends while the maker service is running. Direct sends stay enabled and the form explains why the collaborative toggle is unavailable.
Changelog: Allow direct sends while the maker service is running
docs(dev): explain jm-ng backend workflow
fix(auth): only clear auth on invalid_token 401s
Previously every 401 response cleared the session and logged the user out. jm-ng returns 401 for service-state errors (e.g. POST /tumbler/stop when nothing is running), which should never drop the session. Inspect the WWW-Authenticate header and only clear auth when the server signals ``error="invalid_token"``.
Changelog: Non-auth 401 responses no longer log the user out.
fix(dev): proxy /jmws to the jm-ng HTTPS port
jm-ng serves WebSocket on the same port as the HTTPS API. The `jm-ng:dev` script used to override JMWALLETD_WEBSOCKET_PORT to 32283, but the regtest stack exposes that port without a matching listener, so vite proxied WebSocket upgrades into a dead port and the handshake returned empty. Default the env var to JMWALLETD_API_PORT and drop the override.
Changelog: Fix WebSocket proxying in the local jm-ng dev setup.
fix(dev): correct jm-ng websocket port and proxy targets
Update the README and developer docs to reflect that both ports must be
set when overriding for a custom jm-ng setup.
fix(dev): correct jm-ng websocket port (#1237)
chore(dev): distinct server configs for various backends
* chore(regtest): address jm-ng review comments
---------
Co-authored-by: m0wer <m0wer@sgn.space>
Co-authored-by: Parth Bandwal <143504541+parrth20@users.noreply.github.com>
2026-05-05 13:52:41 +02:00
2026-06-16 21:14:44 +05:30
msg " Attempt to start maker service for wallet $wallet_name in legacy standalone container.. "
chore(regtest): initial joinmarket-ng backend for regtest environment (#1240)
* chore(regtest): initial joinmarket-ng backend for regtest environment
Adds jmwalletd, directory servers, makers, and bitcoind to the regtest
docker-compose environment so jam can be developed against the jm-ng
backend end-to-end.
chore(regtest): wire docker compose env and vite dev proxy for jm-ng
Connects the local regtest containers into a single compose network,
adds tor and fund-wallet helpers, and points Vite's dev proxy at the
local jmwalletd instance.
fix(tags): recognize cj-change, used-empty, and flagged UTXO statuses
joinmarket-ng's WalletService emits four statuses jam's JmPlainTagValue
didn't cover: 'cj-change' (deanonymising change from our CJ),
'used-empty' (previously-used address with zero balance), and 'flagged'
(address shared in a CJ that later failed). They fell through to the
generic 'default' badge with no distinguishing styling.
Add them to JmPlainTagValue and the status->variant map. 'used-empty'
maps to the existing 'used' variant, 'flagged' to 'reused' (both signal
a used address the user should avoid reusing). Add a dedicated
'cj-change' badge variant (emerald) next to 'cj-out' so the
deanonymising change output is visually distinct from an equal-amount
CJ output.
fix(send): keep direct send available with maker
Only block collaborative sends while the maker service is running. Direct sends stay enabled and the form explains why the collaborative toggle is unavailable.
Changelog: Allow direct sends while the maker service is running
docs(dev): explain jm-ng backend workflow
fix(auth): only clear auth on invalid_token 401s
Previously every 401 response cleared the session and logged the user out. jm-ng returns 401 for service-state errors (e.g. POST /tumbler/stop when nothing is running), which should never drop the session. Inspect the WWW-Authenticate header and only clear auth when the server signals ``error="invalid_token"``.
Changelog: Non-auth 401 responses no longer log the user out.
fix(dev): proxy /jmws to the jm-ng HTTPS port
jm-ng serves WebSocket on the same port as the HTTPS API. The `jm-ng:dev` script used to override JMWALLETD_WEBSOCKET_PORT to 32283, but the regtest stack exposes that port without a matching listener, so vite proxied WebSocket upgrades into a dead port and the handshake returned empty. Default the env var to JMWALLETD_API_PORT and drop the override.
Changelog: Fix WebSocket proxying in the local jm-ng dev setup.
fix(dev): correct jm-ng websocket port and proxy targets
Update the README and developer docs to reflect that both ports must be
set when overriding for a custom jm-ng setup.
fix(dev): correct jm-ng websocket port (#1237)
chore(dev): distinct server configs for various backends
* chore(regtest): address jm-ng review comments
---------
Co-authored-by: m0wer <m0wer@sgn.space>
Co-authored-by: Parth Bandwal <143504541+parrth20@users.noreply.github.com>
2026-05-05 13:52:41 +02:00
start_maker "https://localhost:31183" "Satoshi.jmdat" "test"
2026-06-16 21:14:44 +05:30
msg " Attempt to start maker service for wallet $wallet_name in ng peer container.. "
chore(regtest): initial joinmarket-ng backend for regtest environment (#1240)
* chore(regtest): initial joinmarket-ng backend for regtest environment
Adds jmwalletd, directory servers, makers, and bitcoind to the regtest
docker-compose environment so jam can be developed against the jm-ng
backend end-to-end.
chore(regtest): wire docker compose env and vite dev proxy for jm-ng
Connects the local regtest containers into a single compose network,
adds tor and fund-wallet helpers, and points Vite's dev proxy at the
local jmwalletd instance.
fix(tags): recognize cj-change, used-empty, and flagged UTXO statuses
joinmarket-ng's WalletService emits four statuses jam's JmPlainTagValue
didn't cover: 'cj-change' (deanonymising change from our CJ),
'used-empty' (previously-used address with zero balance), and 'flagged'
(address shared in a CJ that later failed). They fell through to the
generic 'default' badge with no distinguishing styling.
Add them to JmPlainTagValue and the status->variant map. 'used-empty'
maps to the existing 'used' variant, 'flagged' to 'reused' (both signal
a used address the user should avoid reusing). Add a dedicated
'cj-change' badge variant (emerald) next to 'cj-out' so the
deanonymising change output is visually distinct from an equal-amount
CJ output.
fix(send): keep direct send available with maker
Only block collaborative sends while the maker service is running. Direct sends stay enabled and the form explains why the collaborative toggle is unavailable.
Changelog: Allow direct sends while the maker service is running
docs(dev): explain jm-ng backend workflow
fix(auth): only clear auth on invalid_token 401s
Previously every 401 response cleared the session and logged the user out. jm-ng returns 401 for service-state errors (e.g. POST /tumbler/stop when nothing is running), which should never drop the session. Inspect the WWW-Authenticate header and only clear auth when the server signals ``error="invalid_token"``.
Changelog: Non-auth 401 responses no longer log the user out.
fix(dev): proxy /jmws to the jm-ng HTTPS port
jm-ng serves WebSocket on the same port as the HTTPS API. The `jm-ng:dev` script used to override JMWALLETD_WEBSOCKET_PORT to 32283, but the regtest stack exposes that port without a matching listener, so vite proxied WebSocket upgrades into a dead port and the handshake returned empty. Default the env var to JMWALLETD_API_PORT and drop the override.
Changelog: Fix WebSocket proxying in the local jm-ng dev setup.
fix(dev): correct jm-ng websocket port and proxy targets
Update the README and developer docs to reflect that both ports must be
set when overriding for a custom jm-ng setup.
fix(dev): correct jm-ng websocket port (#1237)
chore(dev): distinct server configs for various backends
* chore(regtest): address jm-ng review comments
---------
Co-authored-by: m0wer <m0wer@sgn.space>
Co-authored-by: Parth Bandwal <143504541+parrth20@users.noreply.github.com>
2026-05-05 13:52:41 +02:00
start_maker "https://localhost:32183" "Satoshi.jmdat" "test"