Bot releases are visible (Hide)
Published by CoderZhi 3 months ago
v2.0.1 is the first maintenance release after the latest release v2.0.0. It comes with several API fixes to maintain backward-compatibility with existing ioPay and web staking portal.
v2.0.1 does not have a hardfork, but contains several API fixes. All API nodes are recommended to upgrade to v2.0.1 in order to provide the best up-to-date service
Node type | Action |
---|---|
Delegate | Not required |
Fullnode | Not required |
API node | Recommended |
Full Changelog: https://github.com/iotexproject/iotex-core/compare/v2.0.0...v2.0.1
Published by github-actions[bot] 3 months ago
v2.0.0 has a hardfork, which will be activated at block height 31,174,201 (ETA is around 07/22/2024 00:05:55 AM UTC) on IoTeX mainnet.
All nodes must upgrade to this release, otherwise the node runs the risk of not being able to sync with the IoTeX blockchain after other nodes have upgraded.
Note:
There's no change to the mainnet config.yaml and genesis.yaml. You only need to restart your node with the new v2.0.0 image.
We are excited to unveil IoTeX Blockchain v2.0.0, a milestone in our journey towards a more scalable, secure, and user-centric blockchain ecosystem. This release introduces impactful features designed to elevate user experience and expand the capabilities of our staking eco-system, and includes enhancements aimed at improving the security and robustness of the blockchain system.
Users and developers are encouraged to review the updated documentation and migration guides ahead of the release to fully leverage these new features. We are excited to continue empowering decentralized infra for DePIN globally with the new IoTeX Blockchain v2.0.0 release.
v2.0.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 |
API node | Must upgrade |
Published by github-actions[bot] 4 months ago
v1.14.2 comes with new feature for ioID function.
ioctl ioid
commandline tool.v1.14.2 release is primarily for the new ioctl ioid
command. Delegate nodes and API nodes are not required to upgrade to v1.14.2
Node type | Action |
---|---|
Delegate | Not required |
Fullnode | Not required |
API node | Not required |
Published by github-actions[bot] 5 months ago
v1.14.1 is the first maintenance release after the latest release v1.14.0. It comes with enhancements across various components such as blockdao, staking, API. Also, ioctl commandline tool has a fresh upgrade that supports two new powerful functions: ioID and w3bstream. The ioID function enables seamless integration and management of decentralized identities on the IoTeX blockchain. The w3bstream functions allows for efficient management of w3bstream project on the chain, from project creation, device registration, to message operation and prover management.
ioid
and ws
to ioctl commandline tool. Enables the ioID management and w3bstream project functions.v1.14.1 does not have a hardfork, but contains several bug fixes, performance improvements, and new feature enhancements. All delegate nodes and API nodes are recommended to upgrade to v1.14.1 in order to provide the best up-to-date service
Node type | Action |
---|---|
Delegate | Recommended |
Fullnode | Not required |
API node | Recommended |
Published by github-actions[bot] 7 months ago
v1.14.0 has a hardfork, which will be activated at block height 29,275,561
(ETA is around 04/03/2024 00:52:05 AM UTC) on IoTeX mainnet.
All nodes must upgrade to this release, otherwise the node runs the risk of
not being able to sync with the IoTeX blockchain after other nodes have upgraded.
Note:
There's no change to the mainnet config.yaml and genesis.yaml. You only need to
restart your node with the new v1.14.0 image.
Version 1.14.0 has enabled two significant new features: IIP-24 Raise Block Gas
Limit to 50M and IIP-25 delegate endorsement.
With IIP-24, the block gas limit has now been raised to 50M, greatly enhancing
the processing capabilities of the IoTeX blockchain while ensuring its stability.
This enhancement allows the blockchain to achieve a maximum of 1000 TPS
(transactions per second), significantly speeding up transaction processing on
the blockchain, especially during times of network congestion.
The activation of IIP-25 introduces a novel governance model: it allows big
stakeholder to create a bucket for endorsing delegate. This would make delegate
management more flexible and encourage more enthusiastic projects to become IoTeX
delegates and actively participate in the IoTeX network operation, thereby
fostering the inclusivity of the IoTeX network and enhancing the diversity of the
ecosystem.
v1.14.0 release also comes with a couple of improvements:
v1.14.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 |
Published by github-actions[bot] 7 months ago
v1.13.1 is the first maintenance release after the latest release v1.13.0. It comes with a bug fix and improvement of ioctl commandline tool.
With the launch of v1.13.0 some user reported issue with old wallet address (see issue #4156 for details). The issue is quickly identified to relate to nonce calculation for certain wallet address, and is properly fixed in this release.
In v1.13.1, the ioctl commandline tool has enabled querying delegate's reward amount by name. As of now you can only query the reward amount by the actual reward address. With the functionality of querying by name, it makes delegate more convenient to check their reward and improves user experience.
v1.13.1 does not have a hard-fork, but contains a bug fix to ensure prompt transaction processing. All delegate nodes and API nodes are recommended to upgrade to v1.13.1 in order to provide the best up-to-date service
Node type | Action |
---|---|
Delegate | Recommended |
Fullnode | Not required |
API node | Recommended |
v1.13.0 has a hardfork, which will be activated at block height 28,516,681 (ETA is around 02/19/2024 00:58am UTC) on IoTeX mainnet.
All nodes must upgrade to this release, otherwise the node runs the risk of not being able to sync with the IoTeX blockchain after other nodes have upgraded.
Note:
There's no change to the mainnet config.yaml and genesis.yaml. You only need to restart your node with the new v1.13.0 image.
v1.13.0 marks a substantial advancement by upgrading IoTeX network's EVM to the latest Shanghai version. This upgrade brings in the new opcodes and improvements in Shanghai EVM, reducing gas cost with enhanced efficiency and reliability of smart contract execution, ultimately leading to a smoother and more cost-effective experience on the IoTeX network.
We are also excited to announce that v1.13.0 has enabled deterministic deployment functionality on the IoTeX network! This feature would deploy a proxy contract at a fixed address (same for all blockchains), and then it can be used to deploy any contract to a deterministic address using CREATE2. This ensures that any contract could be deployed consistently across different blockchain platforms to the same address, eliminates possible variations, and greatly enhance the predictability and reliability of smart contract deployment processes, providing developers with greater confidence in their deployments and facilitating seamless integration with other systems and protocols.
v1.13.0 release also comes with a couple of improvements:
debug_traceCall
ioctl
commandline tool added more w3bstream project commands, and setv1.13.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 |
Published by github-actions[bot] 10 months ago
v1.12.1 is the first maintenance release after the latest release v1.12.0. It comes with several important improvements and fixes for the API functionality.
This release introduces a significant enhancement to the transaction pool functionality. First, pending transactions that can soon be included in upcoming blocks will no longer be expired. Secondly, a mechanism has been implemented to replace less favorable pending transactions with more promising ones when the transaction pool approaches its capacity limit. This helps to ensure a higher likelihood of executing more successful transactions on the blockchain. With these improvement, we anticipate a relatively more stable block size, and legitimate transactions with higher gas prices stand a better chance of being swiftly processed on the blockchain, thereby enhancing the end user's experience.
v1.12.1 does not have a hardfork, but contains important feature improvements to boost the transaction pool functionality. All delegate nodes and API nodes are strongly recommended to upgrade to v1.12.1 in order to provide the best up-to-date service
Node type | Action |
---|---|
Delegate | Recommended |
Fullnode | Not required |
API node | Recommended |
v1.12.0 has a hardfork, which will be activated at block height 26,704,441 (ETA is around 11/05/2023 23:59pm UTC) on IoTeX mainnet.
All nodes must upgrade to this release, otherwise the node runs the risk of not being able to sync with the IoTeX blockchain after other nodes have upgraded.
Note:
There's no change to the mainnet config.yaml and genesis.yaml. You only need to restart your node with the new image.
v1.12.0 marks a substantial advancement by upgrading the EVM to the Bellatrix release, surpassing the previous London release. Furthermore, our team is actively preparing for the integration with most recent Shanghai release, with more desired features planned for subsequent releases.
v1.12.0 has also enabled weighted vote counting for the Staking Bucket NFT, a feature newly launched in July with version 1.11.0. As a result, buckets created under this new feature will now enjoy an equal voting power and receive identical rewards as those of native buckets with equal balances.
v1.12.0 release also comes with a couple of improvements:
ioctl bc delegate
command, allowing users to conveniently access the detailed information of any delegate by name or operator addresseth_getTransactionByHash
via ethclientv1.12.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 |
v1.11.1 is an important maintenance release, which fixes a bug in the system
staking contract. The issue was discovered in a pro-active manner, and
precautionary actions are taken to make sure that no actual harm/damage is done
to the system staking.
All nodes must upgrade to this release, otherwise the node runs the risk of
not being able to sync with the IoTeX blockchain after other nodes have upgraded.
Note:
There's no change to the latest config.yaml and genesis.yaml. You only need to
restart the node with the new image.
v1.11.1 release also comes with a couple of improvements:
ioctl] action transfer
now supports 0x address formatioctl ins register
command for INS servicev1.11.1 contains a mandatory bug fix, so all nodes must upgrade in order to
keep syncing with the IoTeX blockchain
Node type | Action |
---|---|
Delegate | Must upgrade |
Fullnode | Must upgrade |
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 |
Published by github-actions[bot] over 1 year ago
v1.10.1 is a maintenance release, with couple of improvements:
debug_traceCall
and debug_traceTransaction
whichUpgrade is not necessary, nodes can continue to run normally.
Node type | Action |
---|---|
Delegate | Not required |
Fullnode | Not required |
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 |
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 |
Published by github-actions[bot] almost 2 years ago
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 |
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 |
v1.8.4 is a hot-fix release. Please see https://github.com/iotexproject/iotex-bootstrap/blob/master/184_patch/patch.md for details