You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@
19
19
20
20
Here are the software versions we use:
21
21
22
-
- MainNet: v2.1.2
22
+
- MainNet: v2.2.0
23
23
24
24
## <aname="testnet"/>Join TestNet
25
25
To start and run a testnet node, please click [**Join Testnet**](https://github.com/iotexproject/iotex-bootstrap/blob/master/README_testnet.md)
@@ -32,7 +32,7 @@ This is the recommended way to start an IoTeX node
32
32
1. Pull the docker image:
33
33
34
34
```
35
-
docker pull iotex/iotex-core:v2.1.2
35
+
docker pull iotex/iotex-core:v2.2.0
36
36
```
37
37
38
38
2. Set the environment with the following commands:
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.
Copy file name to clipboardExpand all lines: README_testnet.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@
18
18
19
19
Here are the software versions we use:
20
20
21
-
- TestNet: v2.1.2
21
+
- TestNet: v2.2.0-rc8
22
22
23
23
**Note**
24
24
To start and run a mainnet node, please click [**Join Mainnet**](https://github.com/iotexproject/iotex-bootstrap/blob/master/README.md)
@@ -31,7 +31,7 @@ This is the recommended way to start an IoTeX node
31
31
1. Pull the docker image:
32
32
33
33
```
34
-
docker pull iotex/iotex-core:v2.1.2
34
+
docker pull iotex/iotex-core:v2.2.0-rc8
35
35
```
36
36
37
37
2. Set the environment with the following commands:
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.
**v2.2.0 has a hardfork, which will be activated at block height 36,893,881
5
+
(ETA is around 06/19/2025 01:28:35 AM +UTC) on IoTeX L1 mainnet.**
6
+
7
+
All nodes **must** upgrade to this release, otherwise the node runs the risk of
8
+
not being able to sync with the IoTeX blockchain after other nodes have upgraded.
9
+
10
+
**Note:**
11
+
There's no change to the mainnet config.yaml and genesis.yaml. You only need to
12
+
restart your node with the new v2.2.0 image.
13
+
14
+
This release enables [IIP-42](https://github.com/iotexproject/iips/blob/master/iip-42.md). It reduces the block interval from 5 seconds to 2.5 seconds, effectively doubling the block production rate. This improvement enhances overall network responsiveness, and reduces transaction confirmation times. Users and developers can expect faster feedback for submitted transactions and more frequent block updates across the network. System Staking Contract Version 3 is introduced, which is optimized for the new 2.5-second block interval. It replaces Version 2, which is now deprecated. It will remain compatible even if the block interval changes again in the future.
15
+
16
+
## Key Features and Enhancements
17
+
18
+
1. Reduce block interval from 5 seconds to 2.5 seconds.
19
+
2. Introduce system staking contract version 3 and deprecate system staking contract version 2.
20
+
21
+
## Bug Fix and Performance Improvements:
22
+
1. Enhanced the P2P network by introducing stricter rate limit.
23
+
2. Upgraded golang and some dependencies.
24
+
3. Fixed minting and validation inconsistency.
25
+
26
+
## Upgrade Priority
27
+
v2.2.0 comes with a hardfork, so all nodes **must** upgrade in order to keep
0 commit comments