Concordium Mainnet Node

Concordium node version 8.0.3 contains support for protocol version 8. The new consensus protocol will take effect on the mainnet on March 17, 2025. Node runners should upgrade to version 8.0.3 before the protocol update to ensure that their nodes do not shut down. Validators in particular are encouraged to update their nodes, as the new protocol introduces suspension of inactive validators, meaning that failing to update may result in your validator being suspended.

Protocol version 8 introduces the following changes:

Validators are automatically suspended if they do not produce blocks for a certain number of rounds.

The configure-validator transaction can suspend or resume a validator, including adding a validator in a suspended state.

Suspended validators are paused from participating in the consensus algorithm.

Additionally, the node release includes a number of fixes and improvements:

Add suspension info to BakerPoolStatus / CurrentPaydayBakerPoolStatus query results.

Add GetConsensusDetailedStatus gRPC endpoint for getting detailed information on the status of the consensus, at consensus version 1.

Update Rust version to 1.82.

Update GHC version to 9.6.6 (LTS-22.39).

Add GetScheduledReleaseAccounts endpoint for querying the list of accounts that have scheduled releases.

Add GetCooldownAccounts, GetPreCooldownAccounts and GetPrePreCooldownAccounts endpoints for querying the lists of accounts that have pending cooldowns in protocol version 7 onwards.

gRPC endpoints DryRun, GetBlockItemStatus and GetBlockTransactionEvents now report the parameter used to initialize a smart contract instance as part of a ContractInitializedEvent.

Fix a bug where, after a protocol update in consensus version 1 (P6 onwards), a node may miscalculate the absolute height of blocks when it is restarted.

Fix a bug where GetBlockInfo reports the parent block of a genesis block to be the last finalized block of the previous genesis index, instead of the terminal block. 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.