Quickstart

Becoming a Public Representative (P-Rep)
P-Reps are the consensus nodes that produce, verify blocks and participate in network policy decisions on the ICON Network. To register and become a P-Rep will consist of the following three steps,
1. Install P-Rep tools (CLI for on-chain P-Rep operations)
2. Register as a P-Rep via P-Rep tools
3. Build MainNet P-Rep node
1. Install P-Rep Tools
Quick Install
1
$ virtualenv venv -p python3    # Create a python 3.6.5+ virtual environment.
2
$ source venv/bin/activate        # Enter the virtual environment.
3
(venv) $ pip install preptools
Manual Install
For manual installation and P-Rep tool commands, see full documentation​
2. Register via P-Rep Tools
(Registration fee is 2,000 ICX)
There are three ways supply P-Rep registration info to P-Rep Tools; using a json configuration file, using optional arguments, or using interactive command line.
1
(venv) $ cat registerPRep.json
2
{
3
 "name": "banana node",
4
 "country": "USA",
5
 "city": "New York",
6
 "email": "[email protected]",
7
 "website": "https://icon.banana.com",
8
 "details": "https://icon.banana.com/json",
9
 "p2pEndpoint": "node.example.com:7100"
10
}
11
​
12
# Using json file
13
(venv) $ preptools registerPRep --prep-json registerPRep.json -k keystore
14
​
15
# Using optional argument and interactive command line
16
(venv) $ preptools registerPRep -k keystore --name "kokoa node" --email "[email protected]"
17
> Password: 
18
 > country : USA
19
 > city : New York
20
 > website : https://icon.kokoa.com
21
 > details : https://icon.kokoa.com/json/details.json
22
 > p2pEndpoint : node.example.com:7100
23
​
24
[Request] ======================================================================
25
{
26
 "from_": "hxef73db5d0ad02eb1fadb37d0041be96bfa56d4e6",
27
 "to": "cx0000000000000000000000000000000000000000",
28
 "value": 2000000000000000000000,
29
 "step_limit": 268435456,
30
 "nid": 3,
31
 "nonce": null,
32
 "version": 3,
33
 "timestamp": null,
34
 "method": "registerPRep",
35
 "data_type": "call",
36
 "params": {
37
 "name": "kokoa node",
38
 "email": "[email protected]",
39
 "country": "USA",
40
 "city": "New York",
41
 "website": "https://icon.kokoa.com",
42
 "details": "https://icon.kokoa.com/json/details.json",
43
 "p2pEndpoint": "node.example.com:7100"
44
 }
45
}
See registerPRep command details​
The "details" parameter is an external json file that holds additional information about the P-Rep. We strongly recommend that you register this information. Example,
1
{
2
 "representative": {
3
 "logo": {
4
 "logo_256": "https://icon.foundation/img/img-256.png",
5
 "logo_1024": "https://icon.foundation/img/img-1024.png",
6
 "logo_svg": "https://icon.foundation/img/img-logo.svg"
7
 },
8
 "media": {
9
 "steemit": "",
10
 "twitter": "",
11
 "youtube": "",
12
 "facebook": "",
13
 "github": "",
14
 "reddit": "",
15
 "keybase": "",
16
 "telegram": "",
17
 "wechat": ""
18
 }
19
 }, "server": {
20
 "location": {
21
 "country": "",
22
 "city": ""
23
 },
24
 "server_type": "",
25
 "api_endpoint": ""
26
 }
27
}
3. Build MainNet P-Rep Node
How to build
Pre-requisites
The specifications below are recommended for main P-Reps (top 22). Sub P-Reps (outside of top 22) can run lower-end specs as they do not produce/validate blocks but only serve as citizen nodes. Current blockchain size is 1.1T as of this update (2021, September 13th).
Hardware considering the node is running on AWS
c5.4xlarge (2TB SSD, gp3, 3000 IOPS, 125MBps)
​https://aws.amazon.com/ec2/instance-types/c5/​
Software
OS Requirement
Linux (CentOS 7 or Ubuntu 16.04+)
Open Ports
TCP 7100: gRPC port used for peer-to-peer connection between peer nodes.
TCP 9000: JSON-RPC or RESTful API port serving application requests.
3.1 Install Docker
Docker 18.x+
1
## Update the apt package index:
2
$ sudo apt-get update
3
​
4
## Install necessary packages:
5
$ sudo apt-get install  -y systemd apt-transport-https ca-certificates curl gnupg-agent software-properties-common 
6
​
7
## Add Docker's official GPG key:
8
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
9
​
10
## Add the apt repository
11
$ add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
12
​
13
## Update the apt package index:
14
$ sudo apt-get update
15
​
16
## Install docker-ce:
17
$ sudo apt-get -y install docker-ce docker-ce-cli containerd.io
18
​
19
## Add your user to the docker group with the following command.
20
$ sudo usermod -aG docker $(whoami)
21
​
22
## Set Docker to start automatically at boot time:
23
$ sudo systemctl enable docker.service
24
​
25
## Finally, start the Docker service:
26
$ sudo systemctl start docker.service
27
​
28
## Then we'll verify docker is installed successfully by checking the version:
29
$ docker version
3.2 Install Docker Compose
1
## Install python-pip
2
$ sudo apt-get install -y python-pip
3
​
4
## Then install Docker Compose:
5
$ sudo pip install docker-compose
6
​
7
## To verify the successful Docker Compose installation, run:
8
$ docker-compose version
3.3 Running a P-Rep Node Container using docker-compose
Pull ICON2 image
1
# docker pull <goloop package image>
Keystore
If you have your own KEYSTORE, store it and the password file in the configuration directory.
1
# cp keystore.json ./config/keystore.json
2
# echo -n "password" > ./config/keysecret
Create docker-compose config
1
version: "3.7"
2
services:
3
    node:
4
        image: iconloop/goloop-icon:latest
5
        volumes:
6
            - ./data:/goloop/data
7
            - ./mainnet:/mainnet
8
            - ./config:/goloop/config
9
        ports:
10
            - "9080:9080"
11
            - "8080:8080"
Start containers
1
# docker-compose up -d
Check the status
1
# docker-compose exec node goloop system info
2
{
3
  "buildVersion": "v0.9.9-338-g19c58f03-dirty",
4
  "buildTags": "darwin/amd64 tags()-2021-09-03-14:35:59",
5
  "setting": {
6
    "address": "hx14637aec2d2941f56d4878557b298bea5460fdaa",
7
    "p2p": "node0:8080",
8
    "p2pListen": "0.0.0.0:8080",
9
    "rpcAddr": ":9080",
10
    "rpcDump": false
11
  },
12
  "config": {
13
    "eeInstances": 1,
14
    "rpcDefaultChannel": "",
15
    "rpcIncludeDebug": false
16
  }
17
}
Citizen Node
Citizen nodes are non-producing nodes on the ICON network. A non-producing node is a node that is not configured to produce blocks, instead it is constantly synchronizing the latest blocks from the network and can be used for on-chain queries. Citizen nodes DO NOT require registration.
ICON node software is identical for P-Rep nodes and Citizen nodes, one can follow the same procedures to set up a P-Rep node, without registration, to operate a Citizen node.
​Experiment on TestNet​
Having Trouble?
For troubleshoots and other questions, please join ICON P-Rep MainNet or ICON P-Rep TestNet Telegram Channels. You can ask for an invite in the main telegram channel.