Bug fix

• p2p outbound connection (PR #515)
• zmq server shutdown (PR #505)
• vm issue fix

Enhancement/Feature

• Database support state pruning to decrease database space usage. (PR #478) (PR #482) (PR #498) (PR #513)
• log system enhancement (PR #502) (PR #518)
• Java API getNrgPrice implement (PR #500)
• Java API package into the release build (PR #520)
• Keystore path enhancement (PR #516)

Migration

• new db option in the config settings, can keep using previous settings. for more detail in the database config settings, please see https://github.com/aionnetwork/aion/wiki/Database#state-database-pruning
• new log enhancement. Please check the ''log system settings'' in https://github.com/aionnetwork/aion/wiki/Installation. The p2p setting "show-status" has been removed in this version and migrated into the log system. Please set the P2P log module to DEBUG level to see the p2p peer status.

Checksum

• a checksum is a small-sized datum derived from a block of digital data for the purpose of detecting errors which may have been introduced during its transmission or storage.

How to use Checksum

• download the aion kernel release binary and the checksum file (the file name SHA1SUMS) and put the files into the same folder.
• open terminal and go to the folder.
• type in sha1sum -c SHA1SUMS
• if the binary file is complete and no error, you will see the message output like this :
  aion-v0.2.6.2f8fdfa-2018-05-10.tar.bz2: OK

Bug fix

• transaction error handling (PR#485)
• console check in CLI node (PR#494)
• aion account format check in keystore (PR#481)
• p2p handshake version length bug (PR#497)

Enhancement/Feature

• Java API support get account nonce.

Migration

• new db option in the config settings, can keep using v0.2.5 settings. If you want to skip db checking in the begin of the aion kernel launch. need to add <check_integrity>false</check_integrity> in the DB category.

Checksum

• a checksum is a small-sized datum derived from a block of digital data for the purpose of detecting errors which may have been introduced during its transmission or storage.

How to use Checksum

• download the aion kernel release binary and the checksum file (the file name SHA1SUMS) and put the files into the same folder.
• open terminal and go to the folder.
• type in sha1sum -c SHA1SUMS
• if the binary file is complete and no error, you will see the message output like this :
  aion-v0.2.6.2f8fdfa-2018-05-10.tar.bz2: OK

Bug fix

• lose peer connections in some situations (PR#454)
• java API hang due to the heavy data polling (PR#462)
• aion.sh not working with symlinks (Issue#416)
• unable to generate blocks with seed mode enabled (Issue#455)

Enhancement/Feature

• database check and corrupt data fix when the kernel launch (can be skipped by changing the check_integrity of the DB category in the config file)
• web3 API eth_accounts reenable

Migration

• new db option in the config settings, can keep using v0.2.5 settings. If you want to skip db checking in the begin of the the kernel launch. need to add <check_integrity>false</check_integrity> in the DB category.

Checksum

• a checksum is a small-sized datum derived from a block of digital data for the purpose of detecting errors which may have been introduced during its transmission or storage.

How to use Checksum

• download the aion kernel release binary and the checksum file (the file name SHA1SUMS) and put the files into the same folder.
• open terminal and go to the folder.
• type in sha1sum -c SHA1SUMS
• if the binary file is complete and no error, you will see the message output like this :
  aion-v0.2.6.2f8fdfa-2018-05-10.tar.bz2: OK

Migration

This is the first AION MainNet release, users should use a completely new configuration file and database for this network.

Changelog

• Migrates runtime from JDK 9.0.4 to JDK 10.0.1
• Database related optimizations related to TransactionStore
• P2P layer refinements related to behavioural changes and peer state management
• Bug fixes

Migration

This version includes an update to AionAPI, client side AionAPI must be updated to v0.1.5

Changelog

• P2p layer stabilisation includes io check and improved message handling
• Db module optimisation
• Tx related code base refine
• Api update

Migration

This build restructures some database layouts, nodes that update must delete their previous database folder and resync to head.

Changelog

• Improvements to P2P layer
• Restructuring of Database layouts
• Adds an additional seed node to the default config

Migration

If mining, this change must be coupled with the latest mining pool and miner changes, available here. This version resolves a compatibility issue we found in the previous release.

Joining the network requires a new config, and database. Previous keystore files can be carried over.

Changelog:

• Revised RPC Server
• Improved double-hashing mining algorithm
• Fixed compatibility with certain contracts
• Revised configurations updated to match latest changes

NOTE: This build is run on a separate TestNet (dubbed Q2/Ascent), joining this testnet requires a completely refreshed configuration file, genesis and database. Previously generated keystores will also fail to work, for the purposes of this TestNet please generate new keys for your accounts.

This update also breaks miner compatibility check here for updated pool and reference miner builds.

• Changes the Address of accounts, from publicKey to a modified hash of the publicKey.
• Changes some consensus rules regarding transaction validation.
• Includes some parameter changes.