- Release Status
- Join MainNet
- Join Mainnet without using Docker
- Join TestNet
- Interact with Blockchain
- Enable Logrotate
- Operate Your Node
- Upgrade Your Node（One Line Upgrader）
- Q&A
Here are the software versions we use:
- MainNet: v1.14.1
To start and run a testnet node, please click Join Testnet
This is the recommended way to start an IoTeX node
- Pull the docker image:
docker pull iotex/iotex-core:v1.14.1
- Set the environment with the following commands:
mkdir -p ~/iotex-var
cd ~/iotex-var
export IOTEX_HOME=$PWD
mkdir -p $IOTEX_HOME/data
mkdir -p $IOTEX_HOME/log
mkdir -p $IOTEX_HOME/etc
curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.14.1/config_mainnet.yaml > $IOTEX_HOME/etc/config.yaml
curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.14.1/genesis_mainnet.yaml > $IOTEX_HOME/etc/genesis.yaml
curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.14.1/trie.db.patch > $IOTEX_HOME/data/trie.db.patch
-
Edit
$IOTEX_HOME/etc/config.yaml, look forexternalHostandproducerPrivKey, uncomment the lines and fill in your external IP and private key. If you leaveproducerPrivKeyempty, your node will be assgined with a random key. -
Start from a snapshot (rather than sync from the genesis block), run the following commands:
curl -L https://t.iotex.me/mainnet-data-latest > $IOTEX_HOME/data.tar.gz
tar -xzf data.tar.gz
or download from Google Cloud:
curl -L https://storage.googleapis.com/blockchain-archive/mainnet-data-latest.tar.gz > $IOTEX_HOME/data.tar.gz
tar -xzf data.tar.gz
We will update the snapshot once a day. For advanced users, there are three options to consider:
-
Option 1: If you plan to run your node as a gateway, please use the snapshot with index data: https://t.iotex.me/mainnet-data-with-idx-latest.
-
Optional 2: If you only want to sync chain data from 0 height without relaying on legacy delegate election data from Ethereum, you can setup legacy delegate election data with following command:
curl -L https://storage.googleapis.com/blockchain-golden/poll.mainnet.tar.gz > $IOTEX_HOME/poll.tar.gz; tar -xzf $IOTEX_HOME/poll.tar.gz --directory $IOTEX_HOME/data- Optional 3: If you want to sync the chain from 0 height and also fetching legacy delegate election data from Ethereum, please change the
gravityChainAPIsin config.yaml to use your infura key with Ethereum archive mode supported or change the API endpoint to an Ethereum archive node which you can access.
- Run the following command to start a node:
docker run -d --restart on-failure --name iotex \
-p 4689:4689 \
-p 8080:8080 \
-v=$IOTEX_HOME/data:/var/data:rw \
-v=$IOTEX_HOME/log:/var/log:rw \
-v=$IOTEX_HOME/etc/config.yaml:/etc/iotex/config_override.yaml:ro \
-v=$IOTEX_HOME/etc/genesis.yaml:/etc/iotex/genesis.yaml:ro \
iotex/iotex-core:v1.14.1 \
iotex-server \
-config-path=/etc/iotex/config_override.yaml \
-genesis-path=/etc/iotex/genesis.yaml
Now your node should be started successfully.
If you want to also make your node be a gateway, which could process API requests from users, use the following command instead:
docker run -d --restart on-failure --name iotex \
-p 4689:4689 \
-p 14014:14014 \
-p 15014:15014 \
-p 8080:8080 \
-v=$IOTEX_HOME/data:/var/data:rw \
-v=$IOTEX_HOME/log:/var/log:rw \
-v=$IOTEX_HOME/etc/config.yaml:/etc/iotex/config_override.yaml:ro \
-v=$IOTEX_HOME/etc/genesis.yaml:/etc/iotex/genesis.yaml:ro \
iotex/iotex-core:v1.14.1 \
iotex-server \
-config-path=/etc/iotex/config_override.yaml \
-genesis-path=/etc/iotex/genesis.yaml \
-plugin=gateway
- Make sure TCP ports 4689, 8080 (also 14014 if used) are open on your firewall and load balancer (if any).
This is not the preferred way to start an IoTeX node
- Set the environment with the following commands:
Same as Join MainNet step 2
- Build server binary:
git clone https://github.com/iotexproject/iotex-core.git
cd iotex-core
git checkout v1.14.1
// optional
export GOPROXY=https://goproxy.io
go mod download
make clean build-all
cp ./bin/server $IOTEX_HOME/iotex-server
- Edit configs
Same as Join MainNet step 3. Also make sure you update all db paths in config.yaml to correct location if you don't put them under /var/data/
- Start from a snapshot
Same as Join MainNet step 4
- Run the following command to start a node:
nohup $IOTEX_HOME/iotex-server \
-config-path=$IOTEX_HOME/etc/config.yaml \
-genesis-path=$IOTEX_HOME/etc/genesis.yaml &
Now your node should be started successfully.
If you want to also make your node be a gateway, which could process API requests from users, use the following command instead:
nohup $IOTEX_HOME/iotex-server \
-config-path=$IOTEX_HOME/etc/config.yaml \
-genesis-path=$IOTEX_HOME/etc/genesis.yaml \
-plugin=gateway &
- Make sure TCP ports 4689, 8080 (also 14014 if used) are open on your firewall and load balancer (if any).
You can install ioctl (a command-line interface for interacting with IoTeX blockchain)
curl https://raw.githubusercontent.com/iotexproject/iotex-core/master/install-cli.sh | sh
You can point ioctl to your node (if you enable the gateway plugin):
ioctl config set endpoint localhost:14014 --insecure
Or you can point it to our API nodes:
- MainNet secure:
api.iotex.one:443 - MainNet insecure:
api.iotex.one:80
If you want to set an insecure endpoint, you need to add --insecure option.
Generate key:
ioctl account create
Get consensus delegates of current epoch:
ioctl node delegate
Refer to CLI document for more details.
Claim reward:
ioctl action claim ${amountInIOTX} -l 10000 -p 1 -s ${ioAddress|alias}
Exchange IoTeX native token to ERC20 token on Ethereum via Tube service:
ioctl action invoke io1p99pprm79rftj4r6kenfjcp8jkp6zc6mytuah5 ${amountInIOTX} -s ${ioAddress|alias} -l 400000 -p 1 -b d0e30db0
Click IoTeX Tube docs for detailed documentation of the tube service.
Our node supports most of methods of Ethereum's JSON-RPC protocol. The local endpoint of babal service is localhost:15014 on the gateway node.
Additional method support could be requested here.
logrotate is pre-installed when building the image. But crond (daemon to execute scheduled commands) doesn't automatically start when the docker contaiter starts in alpine linux.
To enable log logrotation, docker exec -it <container> crond -b is expected to be run after the container starts
Container logs can be accessed with the following command.
docker logs iotex
Content can be filtered with:
docker logs -f --tail 100 iotex |grep --color -E "epoch|height|error|rolldposctx"
When starting the container with --name=iotex, you must remove the old container before a new build.
docker stop iotex
docker rm iotex
Container can be "stopped" and "restarted" with:
docker stop iotex
docker start iotex
Make sure you have $IOTEX_HOME already set up, and all the files(configs, dbs etc) are placed in the right locations (Please refer to the Join MainNet section).
To upgrade mainnet node, use following command. By default, it will upgrade to latest mainnet version.
sudo bash # If your docker requires root privilege
bash <(curl -s https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/master/scripts/setup_fullnode.sh)To enable gateway on mainnet
sudo bash # If your docker requires root privilege
bash <(curl -s https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/master/scripts/setup_fullnode.sh) plugin=gatewayTo stop auto upgdrade cron job and iotex server program, you can run
sudo bash # If your docker requires root privilege
bash <(curl -s https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/master/scripts/stop_fullnode.sh)Node with gateway plugin enabled will perform extra indexing to serve API requests of more detail chain information, such as number of actions in a block or query actions by hash.
Please refer here for Q&A.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent