v1.3.0 release (#184)

README.md

@@ -16,16 +16,16 @@
 
 Here are the software versions we use:
 
-- MainNet: v1.2.0
-- TestNet: v1.2.0
+- MainNet: v1.3.0
+- TestNet: v1.3.0
 
 ## <a name="mainnet"/>Join MainNet
 This is the recommended way to start an IoTeX node
 
 1. Pull the docker image:
 
 ```
-docker pull iotex/iotex-core:v1.2.0
+docker pull iotex/iotex-core:v1.3.0
 ```
 
 2. Set the environment with the following commands:
@@ -40,8 +40,8 @@ mkdir -p $IOTEX_HOME/data
 mkdir -p $IOTEX_HOME/log
 mkdir -p $IOTEX_HOME/etc
 
-curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.2.0/config_mainnet.yaml > $IOTEX_HOME/etc/config.yaml
-curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.2.0/genesis_mainnet.yaml > $IOTEX_HOME/etc/genesis.yaml
+curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.3.0/config_mainnet.yaml > $IOTEX_HOME/etc/config.yaml
+curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.3.0/genesis_mainnet.yaml > $IOTEX_HOME/etc/genesis.yaml
 ```
 
 3. Edit `$IOTEX_HOME/etc/config.yaml`, look for `externalHost` and `producerPrivKey`, uncomment the lines and fill in your external IP and private key. If you leave `producerPrivKey` empty, your node will be assgined with a random key.
@@ -74,7 +74,7 @@ docker run -d --restart on-failure --name iotex \
         -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.2.0 \
+        iotex/iotex-core:v1.3.0 \
         iotex-server \
         -config-path=/etc/iotex/config_override.yaml \
         -genesis-path=/etc/iotex/genesis.yaml
@@ -93,7 +93,7 @@ docker run -d --restart on-failure --name iotex \
         -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.2.0 \
+        iotex/iotex-core:v1.3.0 \
         iotex-server \
         -config-path=/etc/iotex/config_override.yaml \
         -genesis-path=/etc/iotex/genesis.yaml \
@@ -114,7 +114,7 @@ Same as [Join MainNet](#mainnet) step 2
 ```
 git clone https://github.com/iotexproject/iotex-core.git
 cd iotex-core
-git checkout checkout v1.2.0
+git checkout checkout v1.3.0
 
 // optional
 export GOPROXY=https://goproxy.io
@@ -157,13 +157,13 @@ nohup $IOTEX_HOME/iotex-server \
 There's almost no difference to join TestNet, but in step 2, you need to use the config and genesis files for TestNet:
 
 ```
-curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.2.0/config_testnet.yaml > $IOTEX_HOME/etc/config.yaml
-curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.2.0/genesis_testnet.yaml > $IOTEX_HOME/etc/genesis.yaml
+curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.3.0/config_testnet.yaml > $IOTEX_HOME/etc/config.yaml
+curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v1.3.0/genesis_testnet.yaml > $IOTEX_HOME/etc/genesis.yaml
 ```
 
 In step 4, you need to use the snapshot for TestNet: https://t.iotex.me/testnet-data-latest and https://t.iotex.me/testnet-data-with-idx-latest. If you need legacy delegate election data(poll.db) for TestNet, you can download it here: https://storage.googleapis.com/blockchain-golden/poll.testnet.tar.gz
 
-In step 5, you need to replace the docker image tag in the command with `v1.2.0`.
+In step 5, you need to replace the docker image tag in the command with `v1.3.0`.
 
 ## <a name="ioctl"/>Interact with Blockchain
 

changelog/v1.3-release-note.md

@@ -0,0 +1,16 @@
+# v1.3 Release Note
+
+### v1.3.0 Release Note
+**Note that v1.3.0 has a hardfork, which will be activated at block height 12,289,321 (7/22/2021 ~2pm PDT) on IoTeX mainnet.**
+1. v1.3 has upgraded to latest EVM version so user can confidently deploy their
+DApps to IoTeX blockchain. This EVM upgrade supports the ChainID opcode to
+prevent relay attacks and enable cross-chain transparency, and has optimized gas
+costs of certain opcodes, especially privacy and zk computations. Click
+[here](https://github.com/iotexproject/iotex-bootstrap/blob/master/changelog/evm-istanbul.md)
+for details
+2. Optimized block sync strategy to make it more robust
+3. Fixed a bug that API query needs to wait a little while to return the latest
+committed block
+4. Fixed a bug that node stops working after network connectivity is lost. Now
+the node can detect the network loss/reconnect event, and automatically resume
+working after network connectivity is restored