Concordium node version 7.0.4 contains support for protocol version 7. This protocol version introduces changes to stake cooldown behaviour, disables shielded transfers, reduces smart contract execution costs, adds new smart contract functionality, and redefines the block hashing scheme.
Changes
Protocol version 7 introduces the following changes:
-
The cool-down behavior when the stake of a validator or delegator is reduced or removed is changed:
-
When stake is reduced, the reduction is immediately effective for future stake calculations, and the amount of the reduction is locked for a cool-down period. (Previously, the reduction was only effective after the cool-down period.)
-
Validators and delegators can make further changes to their stake while they already have stake in cooldown. This includes registering as a validator when the account was previously a delegator, or vice versa. (Previously, the account had to wait for the cool-down period to end before making further changes.)
-
-
Shielded transfers are no longer supported in the protocol. It is still possible to unshield a previously shielded balance.
-
Smart contract execution costs are reduced. This reflects a more efficient implementation of the smart contract execution engine introduced in this release.
-
Smart contracts can now query the module reference and contract name of a smart contract instance.
-
The block hashing scheme is redefined to better support light clients.
Additionaly, the node release includes a number of fixes and improvements:
-
Logging around protocol updates is improved.
-
Failed gRPC requests are now logged at DEBUG level.
-
Fixed a bug where GetBakersRewardPeriod returns incorrect data.
-
Fixed a bug where GetPoolInfo returns incorrect data.
-
Fixed a bug where a configure-validator transaction that is rejected for having a duplicate aggregation key reports the old key of the validator, rather than the new (duplicative) key.
-
Improved the behavior of the node in the event of an unrecoverable error in consensus.