BitGo Express via Docker

This guide is designed to guide you through the installation of a BitGo Express node using Docker.

• It is a requirement when using CAS to access your BitGo wallets (on the BitGo website).

• BitGo Express is designed and written by BitGo for their BitGo website wallets.

Open

1. Install Docker.

Install the Ubuntu dependencies:

Install the product signatures to verify file integrity:

Install the latest stable version of Docker:

Assuming Docker installation went as planned, this next command should succeed:

Success looks like this:

Open

2. Setup a secure tunnel for encrypted communication.

Your CAS server and this node must have a secure channel. Your passphrase (and other sensitive information) will be passed back & forth. Encrypt (and protect) communication by using a secure SSH tunnel (SSH).

The GB Wallet Tunnel is recommended.

General Bytes has incorporated an open-source SSH client into CAS.

Click here for instructions to install the GB Wallet Tunnel Server on this node.

3. Install & run Bitgo Express.

Navigate to your home directory. The home directory is the default login directory.

Reference: https://developers.bitgo.com/guides/get-started/express/install

Install the latest version of Bitgo Express locally:

Run BitGo Express:

This is an example of a successful start:

• To stop it (interrupt it), merely press Ctrl+C at this point. Do not do that yet - you still need to test it.

4. Test it.

Verify that your node is working properly by sending a command via another terminal window.

1. Open a new/second Terminal window/tab.

2. Login on on that second window (via SSH) to the same Bitgo Express node.

3. Type the following:

You should see something similar to this reply:

• On the first (original) window, you’ll see confirmation that the second window said “hello”:

• This indicates that the server is running as expected, and is listening for commands.

• You’ll also see messages from CAS as you test the Hot Wallet settings.

  • This is a great method to help diagnose any problems with CAS settings.

• You may safely close the second window (the test window) at this point.

5. Ensure continuity.

BitGo Express MUST be running at all times to be available as a Hot Wallet for CAS. If the program terminates for any reason, the Hot Wallet will cease to function. If the server goes down, so does your Hot Wallet. You need the server up & Bitgo Express operating continuously for proper operation.

The best way to ensure that Bitgo Express is always running is to implement Docker’s detached mode:

• This command is only slightly different from that in Step 3; it includes the “-d” detached mode flag.

This is an example of BitGo Express successfully started in the background (detached mode):

• the cryptic reply indicates that Bitgo Express was successfully started, and assigned an identifier. That ID will vary every time - and it’s not very important unless you wish to stop the program. Normally you will only stop the program during maintenance or troubleshooting.

• To stop Bitgo Express, simply re-attach the container (use the first 12 characters of the identifier):

• you can now close Bitgo Express by pressing Ctrl-C, or

• watch incoming test messages from CAS (or from CURL in another window, as described above).

• If you don’t know the container ID, use this command to list all Docker containers: sudo docker ps

6. Firewall the node.

The node only needs to expose ports 22 (SSH) and 22222 (GB Wallet Tunnel).

• Block off all other access to avoid having malicious actors abuse/attack your node.

UFW, or Uncomplicated FireWall, is a simplified firewall management interface. UFW is included (by default) with Ubuntu.

Check to see if UFW is already enabled and running:

If UFW is enabled and working, it will report the active rules of allowed connections to your server - otherwise you'll see something like this:

• Fresh/new systems will normally be inactive (unprotected).

• If it is not installed, install it now using: sudo apt update && sudo apt install ufw

• If UFW is active, then this procedure will erase that previous configuration and rewrite the rules.

Reset & deny all incoming connections by default:

• This will erase any/all previous UFW configuration.

Deny all public access to all ports:

• Now we’re left to specify the exceptions (the “rules”).

Allow incoming TCP connections on ports 22 and 22222:

Finally, enable & reload UFW to apply the new rules:

7. Create a new Crypto Setting for use with this node.

• The “node” is now done, and you can create a new Crypto Setting to access your Bitgo wallets.

• The Crypto Setting will require 2 pieces of information from the procedure you performed in this article.

  • The “host” is typically “http://” + the IP address of this node (e.g. http://123.231.123.231), and

  • the port is “3080” (unless you changed it).

• See: BitGo Express Parameters

Additional references:

https://developers.bitgo.com/guides/get-started/express/install

https://hub.docker.com/r/bitgo/express/tags

More Hot Wallet & Exchange guides: