How to set up a full node

How to set up a full node

By using, recording, referencing, or downloading (i.e., any “action”) any information contained on this page or in any dYdX Operations Services Ltd. ("dYdX Operations subDAO") database, you hereby and thereby agree to the dYdX Chain Docs Terms of Use governing such information, and you agree that such action establishes a binding agreement between you and dYdX Operations subDAO.


  1. Linux (Ubuntu Server 22.04.3 recommended)
  2. 8-cpu (ARM or x86_64), 64 GB RAM, 500 GB SSD NVME Storage

Get the dydxprotocold binary and initialize the data directory

  1. From (opens in a new tab) | Look for the protocol assets.
  2. For example, as of 10/19/2023, this was the correct binary to use: dYdX Protocol Binary
  3. Download, extract, and rename the binary to dydxprotocold. Move it to a directory in your $PATH. Now, initialize the data directory (create the directory first if it doesn’t exist). Note in the example below, chain-id=dydx-mainnet-1, the data directory=/home/vmware/.dydx-mainnet-1, and the nickname for the full node is mydydxfullnodemainnnet:
dydxprotocold init --chain-id=dydx-mainnet-1 --home=/home/vmware/.dydx-mainnet-1 mydydxfullnodemainnet

Get the latest applicable genesis.json file and install

  1. Use
curl | python3 -c 'import json,sys;print(json.dumps(json.load(sys.stdin)["result"]["genesis"], indent=2))' > genesis.json 

to get the applicable Genesis state of the network.

  1. Copy the applicable genesis.json file to the data directory’s config/ directory
  2. (Alternatives): If the RPC endpoint above does not work, there are these alternatives:

Install Bware’s snapshot (optional but saves days)

  1. From (opens in a new tab)
  2. Download and extract (using lz4 -dc < snapshotfile.tar.lz4 | tar xf -) the snapshot contents in the data directory (make sure you are in the data directory before running the tar command). Important: The data directory (/home/vmware/.dydx-mainnet-1/ in our example) contains another data/ directory.
  3. (Alternatives): If the above is not available, there are these alternatives:

Start the full node

  1. Start the full node. Note that you may need to change the --p2p.seeds parameter depending on the applicable v4 software blockchain network – you can find an example on Resources page under “Seed nodes”
nohup dydxprotocold start --p2p.seeds=",,,,,,,802607c6db8148b0c68c8a9ec1a86fd3ba606af6@,," --home=/home/vmware/.dydx-mainnet-1 --non-validating-full-node=true > /tmp/fullnodemainnet.log 2>&1 &
  1. You can tail the log to see the progress.
tail -f /tmp/fullnodemainnet.log
  1. The full node is now syncing. To determine whether the full node is caught up with the chain head, please check the applicable block explorer to determine when it reaches the current block – an example block explorer is shown on (opens in a new tab)

Things you can do with the full node

GET CURRENT BLOCK: You can get the current block with this program (opens in a new tab)

Run it with the full node IP address and port 26657:

python3 ws://<IPADDRESS>:26657

Where <IPADDRESS> is the IP address of your full node. Full node usage example