SGX-enabled Secret Node in Docker

So you don't want to fiddle with the .deb file, and just want to run your node? We got you, with this quick and easy guide to getting a node started without much tinkering.

This guide will help you set up a node, but you will need to maintain it, or change the default setup. We recommend being familiar with Linux, docker, and docker-compose.

The scripts in the guide will be for Linux (tested on Ubuntu 18.04), but you could get this working on Windows if you swing that way too.


Minimum requirements

  • 1GB RAM
  • 100GB HDD
  • 1 dedicated core of any Intel Skylake processor (Intel® 6th generation) or better
  • 2GB RAM
  • 256GB SSD
  • 2 dedicated cores of any Intel Skylake processor (Intel® 6th generation) or better
  • Motherboard with support for SGX in the BIOS

Refer to if unsure if your processor supports SGX


0. Step up SGX on your local machine

See instructions here

1. Make sure you have the SGX device installed

If you're using Linux either /dev/sgx or /dev/isgx should exist depending on the driver and hardware you're using.

2. Install docker & docker-compose

Either install yourself, or use this script for Ubuntu

Run as root

#! /bin/bash

# Run as root

apt update
apt install apt-transport-https ca-certificates curl software-properties-common -y
curl -fsSL | apt-key add -

add-apt-repository "deb [archamd64] bionic stable"
apt update
apt install docker-ce -y

# systemctl status docker
curl -L"$(uname -s)"-"$(uname -m)" -o /usr/local/bin/docker-compose

chmod +x /usr/local/bin/docker-compose

docker-compose --version

3. Set up /tmp/aesmd folder

We use this folder to communicate with the aesm (architectural enclave service manager) service. You can use any other folder you want, just change the paths in the scripts

You may have to run this after a reboot, as well, since the /tmp/ folders are volatile.

#! /bin/bash

# Aesm service relies on this folder and having write permissions
# shellcheck disableSC2174
mkdir -p -m 777 /tmp/aesmd
chmod -R -f 777 /tmp/aesmd || sudo chmod -R -f 777 /tmp/aesmd || true

4. Create the docker-compose file docker-compose.yaml

Edit the path under devices to match to your device from step 1

version: "3.4"

    image: cashmaney/aesm
      - /dev/isgx
      - /tmp/aesmd:/var/run/aesmd
    stdin_open: true
    tty: true

    image: enigmampc/secret-network-node:v0.8.1-mainnet
      - /dev/isgx
      - /tmp/aesmd:/var/run/aesmd
      - /tmp/.secretd:/root/.secretd
      - /tmp/.secretcli:/root/.secretcli
      - /tmp/.sgx_secrets:/root/.sgx_secrets
      - SGX_MODEHW
      - MONIKER
      - RPC_URL
      - CHAINID
      test: ["CMD", "curl", "-f", ""]
      interval: 1m30s
      timeout: 10s
      retries: 3
      start_period: 40s
      - "26656:26656"
      - "26657:26657"

NOTE: If you want to persist the node beyond a reboot, change the paths

      - /tmp/.secretd:/root/.secretd
      - /tmp/.secretcli:/root/.secretcli
      - /tmp/.sgx_secrets:/root/.sgx_secrets

To something persistent (e.g. in your home directory) like:

      - /home/bob/.secretd:/root/.secretd
      - /home/bob/.secretcli:/root/.secretcli
      - /home/bob/.sgx_secrets:/root/.sgx_secrets

Note: If you delete or lose either the .secretd or the .sgx_secrets folder your node will have to reset and resync itself.

5. Set up environment variables

  • MONIKER - your network name
  • RPC_URL - address of a node with an open RPC service (you can use
  • CHAINID - chain-id of the network (for testnet this is enigma-pub-testnet-4)
  • PERSISTENT_PEERS - List of peers to connect to initially (for this testnet use
  • REGISTRATION_SERVICE - Address of registration service (this will help the node start automatically without going through all the manual steps in the other guide) -

You can set an environment variable using the export syntax


6. Start your node

docker-compose up -d

After creating the machine a healthy status of the node will have 2 containers active:

docker ps

CONTAINER ID        IMAGE                                      COMMAND                  CREATED             STATUS                    PORTS                                  NAMES
bf9ba8dd0802        enigmampc/secret-network-node:v0.8.1-mainnet   "/bin/bash"   13 minutes ago      Up 13 minutes (healthy)>26656-26657/tcp   secret-node_node_1
2405b23aa1bd        cashmaney/aesm                             "/bin/sh -c './aesm_…"   13 minutes ago      Up 13 minutes                                                    secret-node_aesm_1

7. Helpful aliases

We recommend setting the following aliases, which will allow you to transparently use the secretd and secretcli commands from the host (rather than having to exec into the container)

echo 'alias secretcli"docker exec -it secret-node_node_1 secretcli"' >> $HOME/.bashrc
echo 'alias secretd"docker exec -it secret-node_node_1 secretd"' >> $HOME/.bashrc

Where secret-node_node_1 should be the name of the node container (but it may be different, you can check with docker ps)

8. Troubleshooting

You can see the logs of the node by checking the docker logs of the node container:

docker logs secret-node_node_1

If you want to debug/do other stuff with your node you can exec into the actual node using

docker exec -it secret-node_node_1 /bin/bash