Skip to content

Releases: iotexproject/iotex-core

v1.7.0

16 Mar 00:25
Compare
Choose a tag to compare

Note that v1.7.0 has a hardfork, which will be activated at block height 16,509,241 (ETA is 03/24/2022 around 11pm UTC) on IoTeX mainnet.

  1. Corrected the GetHashFunc implementation in EVM (#2998)
  2. The transaction receipt and EVM log now bear correct index values (#2923)
  3. When transaction is reverted, the corresponding logs are also removed (#3014)

v1.6.4

22 Feb 17:39
Compare
Choose a tag to compare
  1. Fixed certain hardcode values in original babel service (#3038)
  2. Correctly handle array in web3 request (#3050)
  3. Added more tracing for slow API (#3057)
  4. Fixed log query (with large block range) causing high memory usage (#3062)
  5. Added gasFee info into GetActions() API (#3063)

v1.6.3

07 Feb 07:28
Compare
Choose a tag to compare
  1. Implemented HTTP server to support web3.js API in iotex-core (this removes the need of intermediate Babel bridge/service)
  2. Added eth_getStorageAt method
  3. Instrumented tracing to measure timing on critical code path
  4. Enabled EVM tracing to collect calling stacks inside EVM
  5. Performance improvement of ActPool
  6. Enabled log rotate
  7. Corrected nested context usage in transaction processing loop

v1.6.2

07 Feb 07:11
Compare
Choose a tag to compare
  1. fixed EVM calldata dump issue

v1.6.1

15 Nov 21:30
Compare
Choose a tag to compare
  1. Separated the p2p network for Mainnet and Testnet, this reduces the network traffic interference and noise between 2 networks
  2. Rectified transaction error message to be compatible with chainlink
  3. API service added ReadContractStorage() interface

v1.6.0

26 Oct 00:34
Compare
Choose a tag to compare

Note that v1.6.0 has a hardfork, which will be activated at block height 13,979,161 (ETA is 10/28/2021 around 11pm UTC) on IoTeX mainnet.

  1. Added API tracing functionality, which enables measuring and visualizing the break-down of API call timing. We'll work on API performance improvement based on the observability this tool provides in future releases
  2. Exposed gRPC health check point in the API server
  3. Fixed contract read issue for certain smart contracts we've seen earlier
  4. ioctl tool can export private key from HDWallet now

v1.5.0

18 Oct 03:43
Compare
Choose a tag to compare

Please note that v1.5.0 has a hardfork, which will be activated at block height 13,816,441 (ETA is 10/19/2021 around 1pm UTC) on IoTeX mainnet.

  1. Approved the long-awaited community proposal to extend foundation bonus for another year starting from v1.5 activation
  2. Improved the action indexer performance, smart contract query has become faster as a result

v1.4.0

28 Sep 00:01
Compare
Choose a tag to compare

Note that v1.4.0 has a hardfork, which will be activated at block height 13,685,401 (ETA is 10/11/2021 around 10pm UTC) on IoTeX mainnet.

  1. Incorporated the fix for the consensus bug that caused the minority chain split on Ethereum at Aug 17, 2021
  2. More detailed error reporting for contract execution failure
  3. Improved block sync speed by setting the proper target range
  4. Fixed API gas estimation inconsistency by honoring the input's gas limit
    and price

v1.3.0

08 Jul 00:03
Compare
Choose a tag to compare

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 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

better block sync strategy & fix read contract bug

08 Jun 03:59
068777a
Compare
Choose a tag to compare
  1. Try out new block sync strategy
  2. Fix a read contract bug, with this fix, user is able to specify the account reading the contract