Skip to content

Java kernel v1.6.1 release note

Compare
Choose a tag to compare
@AionJayT AionJayT released this 16 Nov 16:23
· 5 commits to master since this release

This release is a mandatory update.

This kernel v1.6.1 release includes the consensus protocol upgrade. This consensus protocol upgrading changed the staker's signature scheme, changed the mining block rewards adjustment, ad rollback the transactions have been sent to the invalid destination (Not an Aion addresses). The upgrade will be implemented on mainnet at block number 7441441 and amity at block number 3658559

The Java kernel 1.6 (rev 0a5929a) migration guide

If your kernel already upgraded to v1.6 (rev 0a5929a), you can upgrade the node again or do manually configuration update. The codebase is the same as the v1.6.1 except the protocol upgrade settings.

If you run v1.6 kernel on the mainnet network, please edit the fork.properties file in the folder networks/mainnet, and update the number '7441440' under the tag 'v1.6' to '7441441'
If you run v1.6 kernel on the amity network, please edit the fork.properties file in the folder networks/amity, and update the number '3658558' under the tag 'v1.6' to '3658559'

Block signer upgrade

If you are a staking pool operator or a solo staker, this release will requires the block signer v1.2 and not compatible with v1.1, you can download it from the release page of the block signer repo or you can find it in the tooling folder inside the release package.

Mining pool software upgrade

The protocol upgrade also requires the mining pool software upgrade for the changing of the mining block rewards adjustment. For more details please see https://github.com/aionnetwork/aion_pool3/releases/tag/0.1.2

Feature:

  • Verifiable Random Functions(VRFs) support with integrated sodium library #1137 #1150
  • Mining block rewards adjustment
  • Rollback transactions due to the invalid transaction destination

Bug fixes:

  • Clean-up the blockchain kernel implementation #1138
  • FastVM callback delegate call issue #1144
  • The API calls: estimateTxNrg and callConstant doesn't check the protocol status #1145
  • Kernel new block submit issues #1148

Enhancement:

  • Blockchain implement refactor #1138 #1151 #1152
  • Kernel sync manager refactor #1141 #1143
  • Crypto native library upgrade #1137 #1150
  • Database batch operation #1139 #1142 #1147
  • P2P threads management #1149
  • Constrain the client API block submit #1155
  • Decrease Rlp decode resource requirement
  • Trie enhancement
  • P2p message system enhancement #1141
  • Remove mcf module