Skip to content

Instantly share code, notes, and snippets.

@AdamISZ
Created February 1, 2021 12:55
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save AdamISZ/325716a66c7be7dd3fc4acdfce449fb1 to your computer and use it in GitHub Desktop.
Save AdamISZ/325716a66c7be7dd3fc4acdfce449fb1 to your computer and use it in GitHub Desktop.
Concise instructions on setting up Joinmarket for testing on signet

Concise instructions on setting up Joinmarket for testing on signet

  • Install Bitcoin Core v0.21.0+ from bitcoincore.org/en/download
  • Edit the bitcoin.conf file (create a new version/back up normal conf file), and put a [signet] section, in which your rpc wallet file is set using a line wallet=..
  • Start bitcoind: ./bitcoind -signet
  • To check when it's synced you can tail -f ~/.bitcoin/signet/debug.log to watch the sync happen. It should be fast; only took perhaps a couple of minutes for me, even though I have a slow internet connection.
  • Once synced configure Joinmarket. As with bitcoind, create a new config file to use by copying an existing mainnet or testnet config file joinmarket.cfg. Settings:
    • rpc_port = 38332
    • network = signet
    • everything else is unchanged except for any rpc_wallet_file name as per the above setting in bitcoin.conf

Note: the IRC settings needn't change; your bot will communicate on #joinmarket-pit-sig instead of #joinmarket-pit or #joinmarket-pit-test, so you can go there if you want to monitor it.

At this point you're ready to run, but you'll want coins. The faucet at https://signet.bc-2.jp/ will give out up to 0.1 coins per request.

The rest is no different from mainnet operation; create the wallet with wallet-tool.py method generate, after you have addresses use the above to get some coins, then run taker/maker bots.

Minor notes on signet

Signet is essentially just "reliable testnet3, with taproot support", though there are doubtless more details. See BIP325 for technical details (e.g. version bytes); p2p port is 38333 corresponding to above-mentioned rpc port 38332; the blocks come in randomly with an average of 10 minutes and poisson distributed, I'm led to believe, and finally, the block explorer you can use to check txs and blocks: https://explorer.bc-2.jp/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment