Difference between revisions of "Command line options"
Plebeian9000 (talk | contribs) (list notable command line options) |
Plebeian9000 (talk | contribs) m |
||
| Line 1: | Line 1: | ||
| − | Specifying '''command line options''' can enable additional non-default settings when running Bisq. | + | Specifying '''command line options''' can enable additional non-default settings when [[Running_from_the_command_line|running Bisq from the command line]]. |
See a full list of available options [https://github.com/bisq-network/bisq/blob/master/common/src/main/java/bisq/common/config/Config.java#L57 in the code]. This article covers more notable ones for typical use cases. | See a full list of available options [https://github.com/bisq-network/bisq/blob/master/common/src/main/java/bisq/common/config/Config.java#L57 in the code]. This article covers more notable ones for typical use cases. | ||
Revision as of 19:36, 17 June 2020
Specifying command line options can enable additional non-default settings when running Bisq from the command line.
See a full list of available options in the code. This article covers more notable ones for typical use cases.
Contents
Specify a different data directory
The default data directory Bisq uses is called "Bisq". All Bisq data is fully contained in it.
But you can specify a different data directory with --appData=BisqTest (change "BisqTest" to whatever you want) and Bisq will create a brand new data directory with a new wallet, keys, onion address, etc (or use the existing data directory with that name if it's already there).
You can use this option to run more than one instance of Bisq at once. This can be helpful to send funds from one Bisq instance to another when switching to a new data directory.
Dump delayed payout transactions
Add the --dumpDelayedPayoutTxs=true option to dump delayed payout transactions in the following files in your data directory:
- delayed_payout_txs_closed.json
- delayed_payout_txs_pending.json
- delayed_payout_txs_failed.json
Specify a Bitcoin node
Sometimes Bisq cannot connect to the node specified in the interface at Settings > Network Info, so starting Bisq with --btcNodes=<node address> can help.
See all Bisq trades
See all Bisq trades by running the --dumpStatistics=true option. Then check out the btc_mainnet/db/trade_statistics.json.
