- Running a Node
- Installing a Node
- Getting Actual Blockchain
- Already a Node Owner
- Upgrade Your Node
- Dealing with Forks
Get to understand what is a Waves full node, Nodes are a critical part of Waves ecosystem. By Running a Waves node, you help in processing transactions and you will increase your profit for securing the network if users start leasing their funds to your node (The more WAVES you lease to a node, the more rewards you will receive, you can lease any sum from 0.002 WAVES).
The WAVES you own (or that have been leased to you) reflect your mining power, the more you own, the higher your chances of processing the next block and receiving the transaction fees as a reward. The final amount will also depend on overall network activity and the level of fees generated.
The Waves full node serves two critical roles:
- To relay blocks and transactions to miners
- To answer queries for end users about the state of the blockchain.
There're different options when you want to deal with Waves full node and you will need to check the node configuration before following any option. The balance of the node can be empty until there are enough people wishing to lease to it by reaching together the generating balance of 1000 WAVES(the minimum balance) and create together a pool.
- The easiest way to run a Waves Node is by using the new Waves Docker container. It requires just one command to enable everything or to change the settings of the node.
- The another way is to download the latest version of
waves.jarand the required
.confconfiguration file (for mainnet or testnet) to any folder, for example
~/waves. You can follow these steps of installing a node depending on your operating system.
Getting actual blockchain
After installing a node, you will have different ways to get the blockchain. follow the getting blockchain guide.
If you're already a node owner, you will need to check the new updates and then go for one of these two options:
Basically, the node should be upgraded by following the upgrading instructions.
You can check the blockchain height or the last 100 signatures of blocks to understand if your node is on fork or not.
Your node can be in one of two possibilities: your node on fork with height less than 2000 blocks or more than 2000 blocks.
In case that your node is on fork with a height less than 2000 blocks, here you can implement rollback through rollback instructions. Otherwise, you need to choose an option for Getting Actual Blockchain.