The first thing to do is to initialize your machine. This process will create the necessary directories, files and configurations required to run a MakeOS node.
Open a terminal and run this command:
kit init --v1
init command will set up Kit’s application directory and create the configuration needed to operate a MakeOS node. These data directory of a node can be found in
--v1 applies the network preset that configures your node for the Testnet (v1). Without the flag, your node will be configured for the Mainnet which is not live at the moment.
ls $HOME/.kit1 accounts extensions kit.ymlls $HOME/.kit/configaddrbook.json genesis.json priv_validator_key.json config.toml node_key.json
To get your node to join the public network, run:
kit start --rpc.on
Kit will connect to the network automatically and begin to fetch and execute blocks till it is completely synchronized with the network. Kit connects to seed nodes embedded in the binary and managed by us.
The seed nodes in the binaries we distribute will allow you to quickly and painlessly connect to the network as soon as you start Kit.
However, if you want to connect to a specific node of your choice, use the
--node.addpeer flag to add one or more peer addresses:
kit start --node.addpeer="<id-of-node>@127.0.0.1:9000"
On the console, you can perform query operations, create transactions, execute custom scripts, perform RPC operations and more.
To start a node in console mode, open a new terminal window and run:
kit console --rpc.on
The command above is like
If you already have a node running on the default RPC address and port, you can attach to it using the
However, if the node is running on a remote server, you can specify the remote address of the server using the
kit attach --remote.address="10.45.22.21:9002"
--rpc.password to set RPC username and password.