-
Notifications
You must be signed in to change notification settings - Fork 43
release v2.1.0 #294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
release v2.1.0 #294
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# v2.1.0 Release Note | ||
|
||
## Summary | ||
**v2.1.0 has a hardfork, which will be activated at block height 33,730,921 | ||
(ETA is around 12/17/2024 02:20:40 AM +UTC) on IoTeX L1 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.1.0 image. | ||
|
||
This release introduces support for the Cancun EVM upgrade, bringing compatibility | ||
with the latest opcodes and Solidity compiler, and enabling more advanced smart | ||
contract functionality. A key highlight is the integration of EIP-4844, which | ||
supports BlobTx transactions. This allows users to send transactions with blob | ||
data that is stored on-chain for at least 20 days, optimizing data availability | ||
and on-chain storage. Additional improvements includes staking enhancements, | ||
network stability, and overall transaction processing efficiency. | ||
|
||
## Key Features and Enhancements | ||
|
||
1. Cancun EVM Compatibility: Implements the latest EVM opcodes, allowing developers | ||
to compile contracts with the most recent Solidity compiler and take advantage of | ||
the newest protocol capabilities. | ||
2. Support for EIP-4844 Blob Transactions: Enables users to send transactions | ||
containing blob data, which is verified and stored on-chain for a minimum of 20 | ||
days, optimizing data availability and chain storage efficiency. | ||
3. Support for EIP-1559 Dynamic Fee Transactions: Allows users to send transactions | ||
with dynamic fees, where the priority fee is rewarded directly to the block miner, | ||
ensuring fair and efficient fee allocation. | ||
4. Support for EIP-2930 Access List Transactions: Reduces gas consumption by allowing | ||
users to specify an access list in transactions, making execution more cost-effective. | ||
|
||
## Bug Fix and Performance Improvements: | ||
1. Staking Bucket Reset: Resolved an issue where staking bucket amounts were not | ||
properly cleared after an unstake, ensuring accurate tracking. | ||
2. Fix for Unlimited Native Staking Duration: Corrected the staking duration limit | ||
for native assets to prevent indefinite staking periods. | ||
3. LibP2P Upgrade: Enhanced the P2P network by upgrading LibP2P, leading to improved | ||
connectivity and network stability. | ||
4. Consistency Between Minting and Validation: Standardized behavior between minting | ||
and validation processes to prevent potential discrepancies and ensure stable operation. | ||
|
||
## Upgrade Priority | ||
v2.1.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 | | ||
|
||
## Commits | ||
https://github.com/iotexproject/iotex-core/compare/v2.0.8...v2.1.0 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since the patch hasn't been updated in the past few releases, we may not need to copy it every release.