Concordium/concordium-node 6.2.3-0

6.2.3

on GitHub

Node version 6.2.3 removes V1 API, supports new "validator" terminology in place of "baker", and improves account state management to reduce memory and disk usage.

The node's public API is extended with a new DryRun endpoint that can simulate effects of sequences of transactions.

Changes

• The transaction table is only used for tracking next available account nonce
  for accounts that have non-finalized transactions. This reduces memory usage
  and startup time.

• The account map is now kept solely on disk in a separate lmdb database and it is no longer part of the internal block state database.
  This change results in less memory usage per account and a decrease in the growth of the database.

• Support validatorId in addition to bakerId in the credentials to start a validator.

• Add options CONCORDIUM_NODE_VALIDATOR_CREDENTIALS_FILE and
  CONCORDIUM_NODE_VALIDATOR_DECRYPT_CREDENTIALS that alias
  CONCORDIUM_NODE_BAKER_CREDENTIALS_FILE
CONCORDIUM_NODE_BAKER_DECRYPT_CREDENTIALS, respectively
  The latter two options are still available, but hidden in the help text.

• Remove V1 GRPC API from the node. This removes configuration options
  CONCORDIUM_NODE_RPC_SERVER_PORT, CONCORDIUM_NODE_RPC_SERVER_ADDRESS,
  CONCORDIUM_NODE_RPC_SERVER_TOKEN, CONCORDIUM_NODE_DISABLE_RPC_SERVER_NODE_ENDPOINTS
  and their command line equivalents.

• Add an additional health-check service to the V2 GRPC API.
  This service conforms to the standard GRPC health service API.

• New DryRun endpoint that allows simulating the execution of transactions.