You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Or supply the dcrdex executable with the pubkey using:
./dcrdex --{network} --regfeexpub={network specific value}
Note: You can specify configurations for different networks in a separate config file e.g ~/.dcrdex/dcrdex-{network}.conf and provide it to the dcrdex executable using the -C flag:
./dcrdex -C ~/.dcrdex/dcrdex-{network}.conf
~/.dcrdex/ is the default app data directory location used by the
DEX server, but can be customized with the --appdata command-line argument.
Run your asset daemons
Only the full node software listed in the client configuration
section are supported for the server. The txindex configuration options must
be set. Be sure to specify the correct network if not using mainnet.
Create the assets and market configuration file
A sample is given at
sample-markets.json. See the
market json section of the wiki for
more information on individual options.
Build and run dcrdex
From a command prompt, navigate to server/cmd/dcrdex. Build the executable
by running go build. The generated executable will be named dcrdex. Run
./dcrdex --help to see configuration options that can be set either as a
command line argument or in the dcrdex.conf file. The
Exchange Variables section of the specification has
additional information on a few key options.