Skip to main content

Running a Node


wasp and wasp-cli binaries installed in $PATH.


  • Cores: At least 2 cores (most modern processors will suffice)
  • RAM: 4GB


  • Access to a Hornet node (with mqtt enabled) for production operation.


You can configure your node/s using the config.json. The minimum needed configuration to run a wasp node is a L1 connection. For more advanced configuration see Node Configuration.

You can set L1 access of the node following the instructions below.


Wasp requires a Hornet node to communicate with the L1 Tangle.

You can use any publicly available node, or set up your own node, or create a private tangle.

Hornet Connection Settings

l1.apiAddress specifies the Hornet API address (default port: 14265)

li.faucetAddress specifies the Hornet faucet address (default port: 8091)

Running the Node

After you have tweaked config.json to your liking, you can start a Wasp node by executing wasp and providing the path to your config.json file with -c. Not providing this flag will cause your config.json file to be ignored and wasp will be started with default configurations.

mkdir wasp-node
cp config.json wasp-node
cd wasp-node
#<edit config.json as desired>
wasp -c config.json

You can verify that your node is running by opening the dashboard with a web browser at (default URL).

Repeat this process to launch as many nodes as you want for your committee.

Accessing Your Node From a Remote Machine

To access the Wasp node from outside its local network, you must add your public IP to the webpi.adminWhitelist. You can add it to your config file or run the node with the webapi.adminWhitelist flag.

wasp --webapi.adminWhitelist=,YOUR_IP

Video Tutorial