v2.4.4

Improvements

• Internal lint and refactoring

Bug Fixes

• Fix bugs on testmode

Tools

aergocli

• Added support deploy payload in hexadecimals
• Added -nonce flag to contract deploy.

brick

• Added timestamp command
• Added the ability for the check command to also check the expected result
• Fix bugs

Misc

• Fix broken CI/CD integrations - migrate to Github Actions from Travis-CI

v2.4.3

Bug Fixes

• Fix synchronization issues in V2 blocks.

v2.4.1

Bug Fixes

• Fix possible freezing under gas shortage condition

v2.4.0

Breaking Changes

• Increase call depth limit from 5 to 64, allowing more flexible DApp development (applied from the block height 111499715).

Improvements

• Prevent octal number from being used as a contract parameter.
• Store the same contract code just once.
• Now Lua VM stops ongoing TX execution upon block generation timeout.

Bug Fixes

• Fix possible indeterministic gas estimation.
• Fix possible state mismatch between nodes resulting from JSON arguments.
• Fix RPC stream freezing issue.

v2.3.0

Breaking Changes

• Update BadgerDB to v3 (previously v1.6) to resolve long boot time (over 1 hour on a typical 4 core machine).

Data Migration Instructions

The old data is not compatible with this version. For correct operation, the data of the state and chain subdirectories in the Aergo data dir must be migrated. The procedure is as it follows.

1. Shutdown Aergo.

2. Install the badger v1.6.

$ go get github.com/dgraph-io/badger/v1.6

3. Perform backup for each DB diretory.

$ badger backup --dir <state or chain> -f <backup file>

4. Install the badger v3

$ go get github.com/dgraph-io/badger/v3

5. Restore each data directory (for safety, don't forget to rename the old directories).

$ badger restore --dir <chain or state> -f <backup files>

6. Now, you can boot Aergo from the migrated data.

Please notice two different versions of badger are used for backup (v1.6) and restore (v3).

Bug Fixes

• Revert the commit 32a8a4b, which may cause blockchain fork between a block producer and all the other nodes.

v2.2.10

Bug Fixes

• Chain Service
  • Fix chain synchronization failure caused by contract timeout error in chain service.
• SQL
  • Fix DB corruption error resulting from integer overflow of DB size limit.

v2.2.8

Bug Fixes

• Fix the nil pointer dereference raised whenever GetStateQuery and GetStateAndProof (RPC commands) returns any error. In this situation, the client could not get a correct error response, since the error in the response be always the timeout error due to some internal reason.

v2.2.7

Bug Fixes

• Fix LIB upon BP membership change.
• Fix broken tests.

v2.2.6

Breaking Changes

• The max block body size (maxblocksize) is hard-limited to carry no more than 8MiB. If maxblocksize is set to a value violating this limit, the aergosvr will not start.

Bug Fixes

• Now aergocli can get a block larger than 4MiB.

v2.2.5

Breaking Changes

• Now contract.balance function can be used to get the staking amount of an address and the last staking block height by adding a string constant "stakingandwhen" as its second argument.

Bug Fixes

• The built-in function system.getTimestamp now returns the timestamp value of the current best block in a query, while it returns a OS system time in the previous releases. Warning: any full node under operation must be upgraded to this version.