NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1228 by repository stars
Latest stable
v1.14.2
Last release 2 years ago
no release in 18 months
Ships on a steady schedule
a new release about every 2 weeks
Most releases are documented
notes for 48 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
759 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Version 1.11.0 includes a hardfork that will be activated on the IoTeX mainnet at block height 24,838,201 (ETA approximately 07/20/2023 11pm UTC). It
Version 1.11.0 includes a hardfork that will be activated on the IoTeX mainnet at block height 24,838,201 (ETA approximately 07/20/2023 11pm UTC). It is imperative that all nodes upgrade to this release. Failure to do so will result in the inability to sync with the IoTeX blockchain after the activation block.
Note:
Prior to restarting the node, you must upgrade to the latest config.yaml file. It contain new configurations required for v1.11.0 to function properly.
Instructions for configuring a node can be found here: https://github.com/iotexproject/iotex-bootstrap#join-mainnet
v1.11.0 enables 3 important features:
IIP-13 supports native representation of staking buckets as Non-fungible Tokens on the IoTeX blockchain, which opens opportunities for applications such as Liquid Staking Derivatives (LSD), where these buckets can be traded or used as collateral in other DeFi protocols. This in turn increases the overall staking ratio and therefore enhances the degrees of security and decentralization of the IoTeX blockchain.
IIP-14 Account abstraction is a ground-breaking proposal that aims to enhance the IoTeX platform by abstracting various account operations and properties, such as authentication, authorization, replay protection, gas payment, batching, and atomicity. IIP-14, based on EIP-4337, makes IoTeX a more user-friendly and secure platform, surpassing the limitations of externally owned accounts (EOAs). For more information on the implementation details, please refer to our github repo here
In v1.8 release, we added ChainID into transaction to distinguish transactions on different networks. In this v1.11 release, the additional constraint is enforced that each transaction must bear with it the correct ChainID (1 for mainnet, and 2 for testnet), and the default ChainID value 0 will be rejected. This would further enhance the security of the IoTeX blockchain.
v1.11 release also comes with a couple of small improvements:
ioctl bc delegate command to retrieve the detailed info of a delegateioctl did service commandv1.11.0 comes with a hardfork, so all nodes must upgrade in order to keep syncing with the IoTeX blockchain
| Node type | Action |
|---|---|
| Delegate | Must upgrade |
| Fullnode | Must upgrade |
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
v1.10.1 is a maintenance release, with couple of improvements:
v1.10.1 is a maintenance release, with couple of improvements:
debug_traceCall and debug_traceTransaction which
further increased our chain's compatibility with the Ethereum ecosystem.Upgrade is not necessary, nodes can continue to run normally.
| Node type | Action |
|---|---|
| Delegate | Not required |
| Fullnode | Not required |
Nothing published for this version
[block] deprecate ConvertToBlockHeaderPb() #3774
v1.10.0 has a hardfork, which will be activated at block height 22,991,401 (ETA is around 04/04/2023 11pm UTC) on IoTeX mainnet.
All nodes must upgrade to this release, or otherwise the node won't be able to sync with the IoTeX blockchain after the activation block.
Also we'll use this release opportunity to disable the auto-upgrader, since the auto-upgrader is a fixed script that cannot adapt perfectly well to each release scenario, and has caused a couple of failed upgrades in the past.
In the past, if you use the one-line upgrader tool to run your IoTeX node, please continue to use it to do the v1.10.0 upgrade. This time the script will turn off the auto-upgrader (if it was turned on before). Run the script below just as before.
sudo bash # If your docker requires root privilege
bash <(curl -s https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/master/scripts/setup_fullnode.sh)
If you use the very long docker run command (like below) to run your IoTeX node, don't worry about the auto-upgrader since it is not turned on. Continue to upgrade your node using the v1.10.0 image:
docker stop iotex
docker rm iotex
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.10.0 \
iotex-server \
-config-path=/etc/iotex/config_override.yaml \
-genesis-path=/etc/iotex/genesis.yaml
v1.10.0 enables 2 important features:
Similar to how we enabled sending transfer and staking actions via web3.js protocol, in v1.10.0 claim reward is enabled as well. Delegates can now send claim reward action using Metamask.
Currently, the IoTeX node is relying on a pre-defined HTTP port to collect the real-time running status, such as the software version and blockchain height. This means that delegate nodes need to open up that HTTP port which might be a security risk, especially for nodes running on clour service provider. It also requires delegate nodes to expose their public IP address, which is not preferred due to both security and privacy concerns, and creates additional maintenance burden to manually update the IP address in case it changes.
In v1.10.0, a new node status monitoring solution is implemented based on the existing p2p network. By exchanging messages about their running status using the p2p network, delegate nodes no longer have to publicize their IP address nor open that specific HTTP port. In addition, the external IP address of a node can now freely change (like being assigned a new IP address after reboot) without worrying about status reporting/collection.
Also in upcoming new releases, we'll introduce more advanced node status monitor functionalities. For instance, an automatic alert service where delegates can register a webhook and receive notification when the node is becoming offline or entering probation.
v1.10.0 comes with a hardfork, so all nodes must upgrade in order to keep syncing with the IoTeX blockchain
| Node type | Action |
|---|---|
| Delegate | Must upgrade |
| Fullnode | Must upgrade |
Nothing published for this version
Nothing published for this version
v1.9.2 is a maintenance release, with the following fix:
v1.9.2 is a maintenance release, with the following fix:
If your node is running as gateway, it is recommended to upgrade to v1.9.2 to better protect it from potential out-of-memory attack.
| Node type | Action |
|---|---|
| Delegate | Not required |
| Gateway | Recommended |
| Fullnode | Not required |
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
v1.9.1 is a maintenance release, with 2 fixes:
v1.9.1 is a maintenance release, with 2 fixes:
ioctl node delegate command can correctly show all probated delegates now.All delegate nodes must upgrade in order to correctly report the binary version they are running.
| Node type | Action |
|---|---|
| Delegate | Must upgrade |
| Fullnode | Not required |
Nothing published for this version
After the v1.9.0 upgrade, the manual patch will no longer be needed, and we'll deprecate the patch in upcoming releases.
v1.9.0 has a hardfork, which will be activated at block height 21,542,761 (ETA is around 01/11/2023 12am UTC) on IoTeX mainnet.
All nodes must upgrade to this release, or otherwise the node won't be able to sync with the IoTeX blockchain after the activation block.
v1.9.0 enables couple of important features:
With this new feature, a newly created account will have 0 as its initial nonce. For historic reason, our mainnet is launched with that initial nonce value equal to 1, which is different from Ethereum's convention that the initial nonce starts from 0. Starting from v1.9.0, this behavior will converge to Ethereum's convention, further enhancing our chain's compatibility with Ethereum eco-system. In particular, the Gnosis Safe protocol (which hinges on this zero-nonce property) will be able to successfully integrate with the IoTeX blockchain after the v1.9.0 launch.
With v1.9.0, the EVM has been upgraded to London (and including Berlin), which enables many important EIPs. For example, EIP-2565 lowers ModExp gas cost and EIP-2930 provides an optional access list (a list of addresses and storage keys) to reduce the gas cost when accessing these addresses and keys during contract execution. Here's a complete list of EIPs enabled in London:
and EIPs enabled in Berlin:
v1.9.0 has provided a complete fix to the issue patched by v1.8.4. After the v1.9.0 upgrade, the manual patch will no longer be needed, and we'll deprecate the patch in upcoming releases.
Couple of small improvements are added into v1.9.0, including:
v1.9.0 comes with a hardfork, so all nodes must upgrade in order to keep syncing with the IoTeX blockchain
| Node type | Action |
|---|---|
| Delegate | Must upgrade |
| Fullnode | Must upgrade |
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.