tBTC v2 Node Setup
This document explains the basic installation and configuration for the tBTC v2 staking client.
This document is intended for members of the community who would like to run their own tBTC v2 node.
Please be aware that running a node is not an easy task and requires technical skill and commitment to maintaining node uptime and availability.
Please review this document in its entirety prior to beginning setup of your node to familiarize yourself with the general setup process.
The Threshold Network expects certain capabilities for each node running on the network. To help attain these capabilities consider the following criteria:
- It is paramount that tBTC v2 nodes remain available to the Network. We strongly encourage a stable and redundant internet connection.
- Equally important is machine uptime and reliability. A VPS is strongly recommended.
- A connection to a production grade self-hosted or third party Ethereum node deployment.
- Persistent and redundant storage that will survive a VM or container rotation, and a disk failure.
- Each node running on the network requires a unique Ethereum Operator Account. The account has to maintain a positive Ether balance at all times.
- Each node running on the network requires a unique IP address or a unique application port running under the same IP.
While it is possible to run the client on a local machine, this is not recommended.
Your operating environment will ultimately dictate what machine type to go with. This is particularly relevant if you’re running a containerized solution where multiple applications are sharing VM resources. The below types are sufficient for running one instance of the tBTC v2 Node.
The preferred OS is Ubuntu.
2 vCPU / 2 GB RAM / 1 GiB Persistent Storage
The client expects configuration options to be passed as CLI flags or specified in a config file. If you specify an option by using a parameter on the command line, it will override the value read from the configuration file.