Docs
Node Operation
Launch a Quick Node

Tangle Validator Quickstart

Caution: The following guide is only meant as a quickstart for anyone looking to run a tangle node with minimal config, this guide uses automated keys and it is not recommended to run a validator using this setup long term, refer to advanced guide for a more secure long term setup.

Before following this guide you should have already set up your machines environment, installed the dependencies, and compiled the Tangle binary. If you have not done so, please refer to the Requirements (opens in a new tab) page.

Standalone Testnet

1. Fetch the tangle binary

Use the latest release version in the url in place of <VERSION>, you can visit releases (opens in a new tab) page to view the latest info

wget https://github.com/webb-tools/tangle/releases/download/<VERSION>/tangle-testnet-linux-amd64

For example, at the time of writing this document, the latest release is v0.6.1 and the link would be as follows

wget https://github.com/webb-tools/tangle/releases/download/v0.6.1/tangle-testnet-linux-amd64

2. Start the node binary

To start the binary you can run the following command (ensure you are in the same folder where tangle is downloaded)

Make sure to change the following params before executing the command

  1. <BASE_PATH> : This is the path where your chain DB will live
  2. <NODE_NAME> : This is a unique node name for your node, use a unique name here to help identity your node to other validators and telemetry data
./tangle-testnet-linux-amd64 \
  --base-path <BASE_PATH> \
  --name <NODE_NAME> \
  --chain tangle-testnet \
  --port 9944 \
  --validator \
  --auto-insert-keys \
  --telemetry-url "wss://telemetry.polkadot.io/submit/ 1"

If the node is running correctly, you should see an output similar to below:

2023-03-22 14:55:51 Tangle Standalone Node
2023-03-22 14:55:51 ✌️  version 0.1.15-54624e3-aarch64-macos
2023-03-22 14:55:51 ❤️  by Webb Technologies Inc., 2017-2023
2023-03-22 14:55:51 📋 Chain specification: Tangle Testnet
2023-03-22 14:55:51 🏷  Node name: cooing-morning-2891
2023-03-22 14:55:51 👤 Role: FULL
2023-03-22 14:55:51 💾 Database: RocksDb at /Users/local/Library/Application Support/tangle/chains/local_testnet/db/full
2023-03-22 14:55:51 ⛓  Native runtime: tangle-115 (tangle-1.tx1.au1)
2023-03-22 14:55:51 Bn254 x5 w3 params
2023-03-22 14:55:51 [0] 💸 generated 5 npos voters, 5 from validators and 0 nominators
2023-03-22 14:55:51 [0] 💸 generated 5 npos targets
2023-03-22 14:55:51 [0] 💸 generated 5 npos voters, 5 from validators and 0 nominators
2023-03-22 14:55:51 [0] 💸 generated 5 npos targets
2023-03-22 14:55:51 [0] 💸 new validator set of size 5 has been processed for era 1
2023-03-22 14:55:52 🔨 Initializing Genesis block/state (state: 0xfd16…aefd, header-hash: 0x7c05…a27d)
2023-03-22 14:55:52 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
2023-03-22 14:55:53 Using default protocol ID "sup" because none is configured in the chain specs
2023-03-22 14:55:53 🏷  Local node identity is: 12D3KooWDaeXbqokqvEMqpJsKBvjt9BUz41uP9tzRkYuky1Wat7Z
2023-03-22 14:55:53 💻 Operating system: macos
2023-03-22 14:55:53 💻 CPU architecture: aarch64
2023-03-22 14:55:53 📦 Highest known block at #0
2023-03-22 14:55:53 〽️ Prometheus exporter started at 127.0.0.1:9615
2023-03-22 14:55:53 Running JSON-RPC HTTP server: addr=127.0.0.1:9933, allowed origins=["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"]
2023-03-22 14:55:53 Running JSON-RPC WS server: addr=127.0.0.1:9944, allowed origins=["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"]
2023-03-22 14:55:53 discovered: 12D3KooWMr4L3Dun4BUyp23HZtLfxoQjR56dDp9eH42Va5X6Hfgi /ip4/192.168.0.125/tcp/30304
2023-03-22 14:55:53 discovered: 12D3KooWNHhcCUsZTdTkADmDJbSK9YjbtscHHA8R4jvrbGwjPVez /ip4/192.168.0.125/tcp/30305
2023-03-22 14:55:53 discovered: 12D3KooWMr4L3Dun4BUyp23HZtLfxoQjR56dDp9eH42Va5X6Hfgi /ip4/192.168.88.12/tcp/30304
2023-03-22 14:55:53 discovered: 12D3KooWNHhcCUsZTdTkADmDJbSK9YjbtscHHA8R4jvrbGwjPVez /ip4/192.168.88.12/tcp/30305

Note : Since the --auto-insert-keys flag was used the logs will print out the keys automatically generated for you, make sure to note down and keep this safely, in case you need to migrate or restart your node, these keys are essential.

Congratulations! You have officially setup an Tangle Network node. The quickstart is only meant as a quickstart for anyone looking to run a tangle node with minimal config, this guide uses automated keys and it is not recommended to run a validator using this setup long term, refer to Deploy with Systemd (opens in a new tab) guide for a more secure long term setup.

To setup monitoring for your node, please refer to the monitoring (opens in a new tab) page.

TroubleshootingFAQs