Setup Local Node
Download the Inery Local Node Package
To start your local Inery node, follow these steps:
Install Dependencies: Ensure you have all necessary dependencies installed. Refer to the Hardware and Software Requirements for detailed information.
Clone and Navigate the Local Node Repository: Clone the Inery repository from GitHub to your local machine.
git clone https://github.com/inery-blockchain/inery-local.git
cd inery-local/inery.setup
Inside inery-local directory you can find tool/sconfig.json
and ine-local.py
script
inside tool directory you will also have contracts direcoty where system contract and token contracts wasm and abi are
Running locla genesis nod will set those contracts, create system accounts and delegate system resouces.
Before starting protocol ensure you have opend and unlocked wallet, you can do that following wallet guide Open Wallet
Set Up Environment Variables
The binaries within the inery
directory must be accessible from anywhere in your system.
To achieve this, you need to export their path to your local OS environment.
Export and Verify Path of Inery Binnaries
The ine.py
script is used for starting genesis and other local nodes
chmod +x ine.py
Run the ine.py
script with the --export
flag to export the paths of the binaries then refresh OS enviroment
./ine.py --export ; source ~/.bashrc
Confirm that the binary path has been successfully exported, you can check by running:
cline version full
v1.0.1-0d87dff8bee56179aa01472dd00a089b2aa7b9fa-dirty
Start Local Node
To start the Inery Local Node, run the ine.py
script with the --genesis
flag.
./ine.py --genesis
The script will start the local node and create a new local network with the default parameters.
port 8888 and 9010 should be open and not used by any other service
Script will create a new local network with the default parameters, you can modify the parameters by editing tool/config.json
file.
Change keys, add more accounts, modify system contract, token contract, and other parameters.
Verify Local Node
To verify that the local node is running, you can check by running:
cline get info
If the local node is running, you should see the node information in the terminal output.
{
"server_version": "0d87dff8",
"chain_id": "3b891f1a78a7c27cf5dbaa82d2f30f96d0452262a354b4995b88c162ab066eee",
"head_block_num": 12,
"last_irreversible_block_num": 12,
"last_irreversible_block_id": "0107a5ec968c814cd5c83c149fe5ab6e8ee187478fd65d42ea99ef82526886ea",
"head_block_id": "0107a5ef1e891165661f2babe5add616658be44a671856fbeeea89c613b8fa2d",
"head_block_time": "2024-10-17T11:24:44.500",
"head_block_master": "inery",
"virtual_block_cpu_limit": 200000000,
"virtual_block_net_limit": 1048576000,
"block_cpu_limit": 199900,
"block_net_limit": 1048576,
"server_version_string": "v1.0.1",
"server_full_version_string": "v1.0.1-0d87dff8bee56179aa01472dd00a089b2aa7b9fa-dirty"
}
Next Steps
To start integrating with the local node, you can refer to the Command Line API Reference.