> For the complete documentation index, see [llms.txt](https://docs.thorchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thorchain.org/thornodes/overview.md). # THORNode Overview Overview of THORNodes ## Overview THORNodes service the THORChain network. Each THORNode is comprised of several independent servers in a cluster. All THORNodes communicate and operate in cooperation to create a cross-chain swapping network. Running a node is a serious undertaking. While Node Operators are well [compensated](/thornodes/overview/risks-costs-and-rewards.md#compensation) for running a node, there are also [risks](/thornodes/overview/risks-costs-and-rewards.md), [skills required](#skillsets) and [costs](/thornodes/overview/risks-costs-and-rewards.md#costs). See the [Node Operator 101 Video](https://youtu.be/XXYXNAolPEU) to learn more before running a node. {% embed url="" %} To understand more about running a THORNode, see the below links: {% content-ref url="/pages/aU3za5gCtrmKi5YlXZAq" %} [Risks, Costs and Rewards](/thornodes/overview/risks-costs-and-rewards.md) {% endcontent-ref %} {% content-ref url="/pages/IRWx6jeWmJEDbnFltsuh" %} [THORNode Stack](/thornodes/overview/thornode-stack.md) {% endcontent-ref %} {% content-ref url="/pages/L4KiOVBHdgKtPMLYDBmk" %} [Node Operations](/thornodes/overview/node-operations.md) {% endcontent-ref %} ## THORNode Dashboards THORNode information can be viewed at the following dashboards: 1. [THORNode API (Liquify)](https://gateway.liquify.com/chain/thorchain_api/thorchain/nodes) - Live THORNode data 2. [thorchain.net](https://thorchain.net/nodes) - THORNode information and network statistics 3. [runescan.io](https://runescan.io/nodes) - THORNode information within the block explorer 4. [thorcharts.org](https://thorcharts.org/thorchain_earnings_distribution) - Earning distribution and other historical data ## Skillsets Running a THORNode is no simple task. As an operator, you will need to run/maintain multiple linux servers with extremely high uptime. It is encouraged that only professional systems engineers run nodes to maintain the highest quality reliability and security of the network. The simple question to know if you have the skillsets to run a THORNode is: > *Have you used pagerduty before?* If the answer is no, it’s probably best that you do not run a node and participate in the network in other ways, such as a [RUNEPool participant](/technical-documentation/thorchain-finance/runepool.md)or a [bond provider.](/thornodes/pooled-thornodes.md) The following skill sets are required to be an effective node operator. * Advanced knowledge of Linux server administration and security * Advanced knowledge of Kubernetes * Advanced experience running a host of nodes on a hosted platform such as AWS, Google Cloud, Digital Ocean, etc * Knowledge of running full nodes for other chains such as Bitcoin and Ethereum. * Willingness to be “on call” at all times to respond to issues when/if your node becomes unavailable ## Creating a Node To set up a node, you have two choices: 1. Set up manually (not recommended unless you are an expert) 2. Set up via Kubernetes (recommended) You can create a bare metal node with your own hardware or use the cluster launcher section for step by step guides using a host provider: {% embed url="" %} {% content-ref url="/pages/KOVyvL9C028BNKA5rxlw" %} [Cluster Launcher](/thornodes/kubernetes.md) {% endcontent-ref %} Once created, follow the [Deploying](/thornodes/deploying.md), [Joining](/thornodes/joining.md) and [Managing](/thornodes/managing.md) pages. ## Node Voting THORNodes have the ability to vote on [Mimir](https://gateway.liquify.com/chain/thorchain_api/thorchain/mimir) settings. This is important when voting for [ADRs](https://dev.thorchain.org/architecture/index.html) and for [network governance](/technical-documentation/technical-deep-dive/governance.md#mimir-network-settings). Mimir settings have specific [abilities](https://dev.thorchain.org/mimir.html). Mimir keys and values are listed in the [Mimir endpoint](https://gateway.liquify.com/chain/thorchain_api/thorchain/mimir). The process for voting from a node is: ```cmd Make mimir => Enter THORNode Mimir key: => Enter THORNode Mimir value: ``` 1. Only an active node can vote, and each active node has one vote on a Mimir. 2. A node can vote at any time on any key, and can change that vote at any time. 3. A node's vote counts only while that node is active. 4. The number of votes needed depends on the Mimir type, described in [Mimir Types](/technical-documentation/technical-deep-dive/governance.md#mimir-types). 5. If that count is not reached, the stored value stays as it is. Where no Mimir value is set, the constant applies. 6. A node can delete their vote by using a -1 value. That removes the node's vote and leaves the stored value as it is. 7. Voting costs one native transaction fee, which is deducted from their bond. The fee is taken even when the stored value does not change. An Operational Mimir vote stays until that node changes it, deletes it with -1, or the active set gains or loses a node. When the active set changes, those votes are deleted and the stored value stays. A churn that does not change the active set leaves the votes in place. An economic vote stays through that change, and it counts only while that node is active. With `OperationalVotesMin` at 3, three active nodes voting the same value, since the last chrun, set an Operational Mimir.