* regtest: adapt regtest params for easier testing
* regtest: start two makers in dev setup
* regtest: own bitcoin rpcauth for tertiary jm instance
* docs(regtest): add info about tertiary container
* fix: min confs of preconditions for all utxos instead of single
* fix: i18n phrases of collaborative transaction preconditions
* wip: use new scheduler preconditions in Jam component
* fix: only report utxos without retries of no retry is left within jar
* feat(regtest): set taker_utxo_retries and maker_timeout_sec config vars for improved testability
* test(preconditions): add test for CoinjoinRequirements
* fix: enable starting scheduler even if preconditions are not fulfilled
* review: fix wording
Co-authored-by: Gigi <109058+dergigi@users.noreply.github.com>
* dev(regtest): remove nbxplorer in favor of simpler custom regtest-initializer
* dev(regtest): use jsonrpc 2.0 requests to create and load wallet
* dev(regtest): upgrade bitcoin core from v22 to v23
* fix(regtest): wait-for-bitcoind should wait for at least >=0 blocks
* dev(regtest): use jam-dev-standalone
* dev(regtest): add npm script regtest:build
this command will build the development setup with docker cache
enabled. usually must fast as it will only pull in newer base
images and not download and recompile jm again. this is the
preferred way if you made only a few adaptions to the images
and e.g. not want to fetch the current master of jm.
* regtest: delete wallet lockfiles before startup
* regtest: expose external tor directory to primary regtest container
* dev: adhere to new standalone image changes
* dev: update regtest config for JM v0.9.6 in dev setup
* dev: use jam's 'default' cj_max fee settings in dev setup
* dev: update secondary dev container config
* dev: start directory node in dev setup
dev: start instance 1 with access local directory node
dev: connect primary and secondary instances to local directory node
dev: ability to specify jm branch in primary container
dev: remove symlink for tor in directory-node as #1271 is fixed upstream
dev: inject hs dir in directory-node instance
dev: add script to create onion addresses for regtest setup
dev: add prepare-setup.sh script to write .env.generated file
dev: cleanup directory-node setup and scripts
* cleanup: clarify hs directory handling
* cleanup: fix typos and remove unneeded commands in prepare setup script
* dev: revert changes to regtest fee settings
* dev: use example env file for all other commands than 'up'
* dev: fix directory node setup on restarts
* dev: adapt permissions of hs directory in regtest directory node
* dev: ability to follow logs of directory node via npm script
* fix: directory node scripts compatibility
* Update docker/regtest/dockerfile-deps/joinmarket/directory_node/README.md
Co-authored-by: Daniel <10026790+dnlggr@users.noreply.github.com>
* Update docker/regtest/.gitignore
Co-authored-by: Daniel <10026790+dnlggr@users.noreply.github.com>
* Update docker/regtest/dockerfile-deps/joinmarket/directory_node/README.md
Co-authored-by: Daniel <10026790+dnlggr@users.noreply.github.com>
* review: fix newlines and typos
Co-authored-by: Daniel <10026790+dnlggr@users.noreply.github.com>
* dev: use same fee settings as jam release in regtest setup
* dev: use default value for 'taker_utxo_retries' in regtest setup
* dev: use default value for 'taker_utxo_age' in regtest setup
* fix: move comment to own line in regtest default.cfg
* feat: readd websocket connection
* add WebsocketProvider
* feat: update taker/maker state based on websocket data
* update connection indicator based on websocket state
* reconnect with linear backoff on websocket errors
the backend is not happy with a second instance in another browser tab
that send invalid tokens (e.g. because the previously used wallet was
locked in another tab). This introduces a linear increase to a max
of 10 seconds. Seems to ease the problem in the active tab.
* send keepalive message periodically
some webservers will close connections on inactivity rather
soon by default (e.g. nginx is 60s). this commit contains
sending a keepalive message periodically every 30 seconds.
Co-authored-by: d11n <mail@dennisreimann.de>
* feat: use joinmarket-webui standalone container in regtest setup
* dev: use build flag --docker-install in regtest env
* dev: build first jm instance from master; remove image based on btcpayserver
* dev: fix creating wallets in docker setup 'latest'
* update: use newest dev image from public registry
* review: remove checksum of dev-standalone image
* review: add '--pull' arg to docs for rebuilding regtest setup
* fix: prevent 'config value not set' on cj in regtest env
'max_cj_fee' config values must be present when invoking a
coinjoin via the api. the default config for the regtest env
did not include these values before, hence they could not
be overridden in docker-compose setup file.
* dev: switch irc server from miniirc to ergochat
* dev: start second joinmarket container
In order to successfully perform a CoinJoin, there must be at least one
maker. This commit adds a second JoinMarket container with
jmwalletd accessible on port 29183.
* dev: add helper script to mine a block
* dev: add container switch to regtest-control script
* dev: invoke mine-block in regtest-control script
* dev: add flag '--unmatured' to regtest-control script
Sometimes it is desired that block rewards do not reach maturity
immediately. This is convenient if you want to supply several wallets
with coins, but do not want to generate many blocks all the time.
* dev: add helper script to start maker service
This script helps in providing both JoinMarket containers a wallet with
spendable coins and starting the Maker Service in the secondary
container. Its main goal is to make CoinJoin transactions possible in the
regtest environment.
* dev: move common functions to script common.sh
* fix: use correct irc host in docker setup
* dev: use ergochat image from ghcr.io
* dev: dont lock secondary wallet in setup script
normally the wallet should be locked, but it seems this leads to the
maker service responding very slowly which causes failing coinjoins.
as the secondary instance is never interacted with directly, we can
refrain from unlocking the wallet for now.
* docs: add debug log command to docker readme
* cleanup: rename script 'regtest-control' to 'fund-wallet'
* dev: upgrade joinmarket from v0.9.3 to use current master branch
* review: add more descriptive comments and cleanup files
