4.1. How to prepare your Bisq source code for regtest mode

Registration of an arbitrator is protected by a key pair. For development environment you can use the pre-defined developer key which gets enabled by a development flag in the source code.

You have to edit DevEnv.java. Set DEV_MODE to true if you want to skip a lot of popups and confirmation dialogs. If you want to test the regular UI leave this option to false and just add the program argument --useDevPrivilegeKeys=true.

This enables a developer key which can be used as well for all other privileged activities which are protected by a key pair (registering arbitrator, sending a private message, sending an alert or update info,...).

For registration of the arbitrator you need to navigate to the Account screen and press Ctrl+R or Cmd+R to reveal the hidden "Arbitrator Registration" tab and select it. Here the user enters his private invitation key. Use the testing key (which is usually commented out in code): 6ac43ea1df2a290c1c8391736aa42e4339c5cb4f110ff0257a13b63211977b7a. Select your preferred language to complete the arbitrator registration.

Take care to not use the version with the modified DevEnv flags in production mode!