🛡️Run Node
Use the gitshockd command with the required command line options to start a node. Alternatively, use the launcher to start gitshockd interactively with the most common options. (comingsoon)
Configure and run an Gitshock node
Run the local node by running the gitshockd script in the base directory of the repository.
Nodes can connect to Ethereum Mainnet and public testnets.
Use the gitshockd
command with the required command line options to start a node.
Validator Specification Hosting
Determine public network system requirements by checking CPU and disk space requirements using Prometheus. Grafana provides a sample dashboard for Besu.
CPU requirements are highest when syncing to the network and typically reduce after the node is synchronized to the chain head.
Service configuration
gitshockd
binary needs to run as a system service automatically upon established network connectivity and have start / stop / restart functionalities. We recommend using a service manager like systemd.
Example systemd
system configuration file:
Start Node
start node and join validator using command line
Download genesis block Gitshock Chain, sync block and join validators
< Coming Soon Genesis Block>
if your node cannot connect peers, you can add manual by using this command and start again your node :
Setup Log Files
If configured without log rotation, log files could use up all the available disk space which could disrupt the validator uptime.
Log files need to be rotated on a daily basis (with a tool like logrotate).
Example logrotate
configuration:
Finished
Now that you've launched your Gitshock node, what should you do next?
Your Gitshock node will perform consensus on its own, but it is not yet a validator on the network. This means that the rest of the network will not query your node when sampling the network during consensus.
Last updated