Releases: Concordium/concordium-client
concordium-client 7.0.1
This release supports node version 7 and protocol version 7.
Changes
- Display the account balance "at disposal" in
account show
. - List the cooldowns on an account, and their expiration times (from protocol version 7).
- Improved checks when configuring a validator or delegator.
- Fix the display of the expected expiry of pending changes to an accounts stake (before protocol version 7) to correctly account for the change taking place at a payday.
- Fix a bug in correctly accounting for parsed events.
- Rename the
--out
flag forvalidator add
to--validator-credentials-out
to fix a conflict with the--out
flag for outputting the (partially-signed) transaction.
concordium-client 6.3.0
This release introduces a new multi-sig
feature for all transaction types and deprecates shield/transferEncrypted
functionalities.
Changes
- Change the command
transaction submit
to submit already-signed transactions to the chain (transactions must now already be signed, e.g. withtransaction add-signature
). This is a breaking change. - Add the command
transaction add-signature
to add signatures to a partially-signed transaction. - Add the optional
--out
flag to all transaction-creating commands to output a partially-signed transaction to a file. - Remove the command
account shield
to disable the transfer of CCD from the public balance to the shielded balance of an account. - Remove the command
transaction send-shielded
to disable the transfer of CCD from the shielded balance of the account to the shielded balance of another account. - Remove he command
raw SendTransaction
.
concordium-client 6.2.1
This release introduces new "validator" terminology in the cilent, deprecating the old "baker" terms in line with the tokenomics revision.
In addition to this renaming this version of the client adds understanding of verifiable builds when deploying and inspecting smart contract modules.
Changes
- Remove uses of baker terminology.
- Revise client's reconnect handling so that the client will no longer attempt to automatically reconnect on timeouts and node resource exhaustion.
- The module inspect command now attempts to print any embedded verifiable build information.
- The module deploy command now warns if a module is being deployed that does not have embedded verifiable build information.
concordium-client 6.1.0
Concordium-client 6.1.0 adds support for the new API available in node version 6.1.
It is only compatible with node version at least 6.1.
Changes
- Add
baker win-time
command for determining the earliest time a specified baker is expected to
bake. - End stream consumption early if an error is returned.
- Add support for the following node version 6.1 queries under the
raw
command:GetBakersRewardPeriod
GetBlockCertificates
GetBakerEarliestWinTime
GetWinningBakersEpoch
GetFirstBlockEpoch
- Add support for
CommissionRates
inCurrentPaydayBakerPoolStatus
(Only available for node versions > 6.0).
- Show all options for importing an account.
concordium-client 6.0.1
Version 6.0.1 of the client adds protocol 6 support for the client.
Changes and bugfixes.
- Remove a stray CTrue in output of consensus show-chain-parameters.
- The client now outputs protocol version as part of raw GetBlockInfo and block show commands.
- The client needs node version at least 5.4.
- Add raw GetNextUpdateSequenceNumbers subcommand.
- Add node version to the output of raw GetNodeInfo.
- Add current timeout duration, current round, current epoch and trigger block time to the output of raw GetConsensusInfo.
- Add current timeout duration, current round, current epoch and trigger block time to the output of consensus status when they are present.
- Add round and epoch to the output of raw GetBlockInfo.
- Add round and epoch to the output of block show when they are present.
- Print "Block time" instead of "Slot time" in the output of block show.
- In the output of consensus show-parameters, only print election difficulty when present.
concordium-client 5.2.0
This release extends the client interface and fixes UI bugs.
Changes
- Fix a bug in display of
consensus show-chain-parameters
output. This
is only relevant when the queried chain runs protocol version 6. - Add
raw GetBlockTransactionEvents
that prints the list of transaction outcomes
in a given block.
concordium-client 5.1.1
This release of concordium-client changes the communication of the client with the node. The client now requires access to the node's V2 GRPC API, compared to the previous V1 API which is being deprecated.
The majority of the user interface of the client has remained the same, however some raw
commands have been removed and replaced with other raw
commands. See below for details.
Changelog.
- The
--grpc-authentication-token
option has been removed. - The client now uses the V2 GRPC API exposed by the node. This introduces some breaking
changes:- Since the node serves the V2 GRPC API at port 20000 by default, the default value of
the--grpc-port
option has been updated to reflect this. raw
family of commands:- Commands
raw GetTransactionStatusInBlock
,raw StartBaker
,raw StopBaker
,
raw JoinNetwork
andraw LeaveNetwork
have been removed. - Command
raw GetBlockSummary
has been removed, and replaced by the commands
raw GetBlockPendingUpdates
,raw GetBlockSpecialEvents
,
raw GetBlockChainParameters
raw GetBlockFinalizationSummary
. These provide
a more granular way of accessing to the same data. raw BanNode
andraw UnbanNode
no longer support node IDs, but now rather
take just an IP address.raw DumpStart
takes a parameter specifying the path of the file to write
dumped packets to, and furthermore supports a flag to specify whether raw
packets should be written to the file.- Output of
raw GetBannedPeers
prints a JSON list of banned IP addresses,
represented as strings. - Output of
raw GetPeerUptime
now prints an integer representing the uptime
of the node in milliseconds. - Slight changes to
raw GetNodeInfo
. Notably the baker ID is now included in
the output when the node is in the baker or finalization committee. Various
consensus-related details about the node is also elaborated upon. - Slight changes to
raw GetPeerData
output. Notably the catch-up status and
consensus-related details about the peer is elaborated upon. raw SendTransaction
no longer allows for specifying a network ID.
- Commands
consensus show-parameters
now additionally prints the election difficulty.- Slight changes to error message information and their phrasing for other families
of commands.
- Since the node serves the V2 GRPC API at port 20000 by default, the default value of
concordium-client 5.0.2
5.0.2
- Receive function parameters are now displayed as JSON in
transaction status
whenever they could be succesfully parsed by a smart contract schema embedded
in the module or supplied by the user using the--schema
option.
concordium-client 5.0.1
5.0.1
- Add support of contract schema V3.
- V3 schemas offer the same options as V2, but also optionally includes a schema for contract events.
-transaction status
now displays contract events, and a schema can be provided with--schema
, which
will be used to parse the contract events. By default events are parsed with the schema embedded in the
contract, if present.
- This enables concordium-client to interact with contracts and schemas
usingconcordium-std
version 5. - Improved formatting of
transaction status
output using contract schemas if
they are available for displaying contract events. - Output function parameters as hex strings in
transaction status
. - Add support for protocol version 5.
- Add a
--secure
flag to enable connecting to gRPC using TLS. All commands that query the node support this.
concordium-client 4.2.0
4.2.0
- Fix handling of
--no-confirm
incontract init
,contract update
,module deploy
, andregister data
transactions. This flag is now respected. - Add support for importing accounts exported by the browser extension wallet.
- Make the output of CCD amounts consistent when printing transaction outcomes.
The output should now alwaysx.y CCD
for somex
andy
.