Docs
FAQ

General FAQ: Frequently Asked Questions

Where can I get help?

Our Discord is the best place to get assistance with your node or other questions about the project. See http://webb.tools/community (opens in a new tab) for links to Discord and more.

How do I stay up to date?

All upgrades and important technical information are announced on Discord and Twitter, in the #tangle-network channel. See http://webb.tools/community (opens in a new tab) for links to Discord and more.

What are the hardware requirements?

The following specifications are the ideal or recommended, but nodes can be run with less. Testnet nodes have also been run using AWS t3.Large instances.

ComponentRequirements
CPUIntel(R) Core(TM) i7-7700K CPU @ 4.20GHz
StorageAn NVMe solid state drive of 500 GB (As it should be reasonably sized to deal with blockchain growth).
Memory32GB ECC
FirewallP2P port must be open to incoming traffic:
- Source: Any
- Destination: 30333, 30334 TCP

See Hardware (opens in a new tab) and Getting Started with Validating (opens in a new tab) for more information.

What about backup nodes?

We recommend that you run two machines with the same specifications, in different countries and service providers to decentralize and make your services more robust. If your primary fails you can quickly resume services on your backup and continue to produce blocks and earn rewards. Please refer to the Q&A on failovers below.

What are the different networks?

There are two networks, each will require dedicated hardware. The Tangle TestNet is free and should be used to familiarize yourself with the setup.

Tangle Network - Mainnet, not launched yet.

Tangle Testnet - Launched.

What ports do I allow on my firewall?

As stated before, the standalone nodes will listen on multiple ports. The default Substrate ports are used in the standalone, while the relay chain will listen on the next higher port.

The only ports that need to be open for incoming traffic are those designated for P2P. Collators must not have RPC or WS ports opened.

Default Ports for a Tangle Full-Node:

The standalone nodes will listen on multiple ports. The default Substrate ports are used in the standalone, while the relay chain will listen on the next higher port.

The only ports that need to be open for incoming traffic are those designated for P2P.

Default Ports for a Tangle Full-Node:

DescriptionPort
P2P30333 (TCP)
RPC9933
WS9944
Prometheus9615

Is there a binary?

We're working on this, check back soon!

What are the recommendations for monitoring my node?

Monitoring is critical for success as a node operator. See our full Monitoring guide (opens in a new tab)

What are the KPIs I should be monitoring?

The main key performance indicator for a node operator is the number of blocks produced. The Prometheus metric for this is called substrate_proposer_block_constructed_count.

How should I set up alerting?

Alerting is critical for your success as a node operator, see our full guide to using our recommended AlertManager (https://docs.tangle.tools/docs/node/monitoring/alert-manager/ (opens in a new tab))

What is the failover process if my primary node is down?

When the primary server is down, the best way to perform a failover to the backup server is to perform a key association update. Each server should have a unique set of keys already. Run the setKeys author mapping extrinsic. You can follow the Mapping Extrinsic instructions and modify the instructions to use the setKeys extrinsic.

What should I look for in the logs?

For full support, see our guides on Logging (opens in a new tab).

How much stake do I need to become a validator in the active set?

Per era, the NPoS system selects a certain number of nodes with the most TNT to validate. Therefore, the minimum amount required to become an active nominator and earn rewards may change from era to era. You can check the active validator set's stake at https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftangle-standalone-archive.webb.tools#/staking (opens in a new tab)

How do I set an identity on my account?

Setting an identity on-chain will help to identify your node and attract delegations. You can set an identity by following the instructions on Polkadot's Identity Documentation at https://wiki.polkadot.network/docs/learn-identity (opens in a new tab)