The core component that is used to participate in a Cardano decentralised blockchain.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by LaurenceIO over 2 years ago
Node version 1.34 brings a number of important new features that will benefit stake pool operators and other users, including
It also includes a number of stability improvements, plus improvements to the performance of Plutus scripts.
To avoid increased synchronisation times, we recommended that Windows users DO NOT upgrade to node version 1.34.0. We recommend instead that they continue to run node 1.33.0. Future releases will address this issue which is specific to Windows.
Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
cardano-node
. (#3450, #3496, #3497, #3498, #3570)transaction build
and transaction build-raw
commands. (#3483)leadership-schedule
command. This can calculate a stake pool's leadership schedule for the current and following epoch. It requires access to the VRF signing key for that stake pool. (#3464, #3494)
> cardano-cli query leadership-schedule \
--testnet-magic 42 \
--genesis example/shelley/genesis.json \
--stake-pool-id pool12t0y7agkqct89pf00eeytkvfjlquv76tjy27duannan9w63ckxv \
--vrf-signing-key-file example/node-pool1/shelley/vrf.skey
--current
SlotNo UTC Time
--------------------------------------------------------
4073 2021-12-29 17:26:54.998001755 UTC
4126 2021-12-29 17:27:00.298001755 UTC
4206 2021-12-29 17:27:08.298001755 UTC
4256 2021-12-29 17:27:13.298001755 UTC
4309 2021-12-29 17:27:18.598001755 UTC
4376 2021-12-29 17:27:25.298001755 UTC
4423 2021-12-29 17:27:29.998001755 UTC
4433 2021-12-29 17:27:30.998001755 UTC
transaction build
and transaction build-raw
commands. This is specified by using the --cddl-format
flag. (#3505)kes-period-info
command in the CLI. This checks that your operational certificate is correct. It checks:
> cardano-cli query kes-period-info --testnet-magic 42 \
--op-cert-file example/node-pool1/shelley/node.cert
✓ The operational certificate counter agrees with the node protocol state counter
✓ Operational certificate's kes period is within the correct KES period interval
{
"qKesNodeStateOperationalCertificateNumber": 6,
"qKesCurrentKesPeriod": 404,
"qKesOnDiskOperationalCertificateNumber": 6,
"qKesRemainingSlotsInKesPeriod": 3760228,
"qKesMaxKESEvolutions": 62,
"qKesKesKeyExpiry": "2022-03-20T21:44:51Z",
"qKesEndKesInterval": 434,
"qKesStartKesInterval": 372,
"qKesSlotsPerKesPeriod": 129600
}
transaction sign
command now allows for incremental signing by providing an already signed transaction via --tx-file
. This allows more easily adding multiple signatures to a transaction. (#3549)transaction build
command now supports an option (--calculate-plutus-script-cost
) to compute the cost for included scripts. (#3589)
cardano-cli transaction build \
--alonzo-era \
--cardano-mode \
--testnet-magic "$TESTNET_MAGIC" \
--change-address "$utxoaddr" \
--tx-in "$plutusutxotxin" \
--tx-in-collateral "$txinCollateral" \
--tx-out "$dummyaddress+10000000" \
--tx-in-script-file "$plutusscriptinuse" \
--tx-in-datum-file "$datumfilepath" \
--protocol-params-file "$WORK/pparams.json" \
--tx-in-redeemer-file "$redeemerfilepath" \
--calculate-plutus-script-cost "$WORK/create-datum-output.scriptcost"
> cat $WORK/create-datum-output.scriptcost
[
{
"executionUnits": {
"memory": 1700,
"steps": 476468
},
"lovelaceCost": 133,
"scriptHash": "67f33146617a5e61936081db3b2117cbf59bd2123748f58ac9678656"
}
]
lovelaceToTxOutValue
. (#3381)currentEpochEligibleLeadershipSlots
and nextEpochEligibleLeadershipSlots
to get the leadership slots for the current/next epoch respectively. (#3464, #3494)capi
library to support using the cardano node as a C library in other software. (#3501)fromShelleyAddr
now takes an explicit ShelleyBasedEra
parameter to determine the era. The previous behaviour (with an implicit IsShelleyBasedEra
constraint) can be obtained with fromShelleyAddrIsSbe
. (#2253, #3606)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO almost 3 years ago
Cardano Node version 1.33.0 is a performance-focused release, bringing significant improvements in sync time, block propagation time, and reduced memory usage. Incremental stake aggregation and reward calculation allows much more uniform computation across the epoch, reducing the likelihood of spikes in CPU usage during the reward calculation period and so improving the consistency of block production.
In addition, more information is provided during node initialisation, and changes have been made to improve the handling of unexpected shutdowns when initialising the node. DNS support for IPv6 has been added. Tracing has been provided for Plutus scripts, making it easier to debug failure conditions.
With this version, the ledger state will need to be replayed from the genesis block, meaning that the initial synchronisation may be slow. Users should account for this when deploying the node.
Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
tx-generator
internal testing infrastructure. (#3425, #3426, #3427, #3436)TxIn
as a key in JSON maps. (#3438)db-analyser
tool. (#3471)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO almost 3 years ago
Cardano Node version 1.32.1 introduces a number of improvements and enhancements to improve the usability of the Cardano node. Native asset name rendering has been changed in order to eliminate problems caused by non-printing characters, CLI commands now default to the Alonzo era, and default values have been added to simplify startup where a genesis file is not supplied (eg in test or standalone settings). Additional logging is available during node startup, enabling progress to be tracked more easily, and statistics counting has been disabled in order to reduce noise. Limits have been added to mini protocols. There is better rendering of some trace messages.
Documentation has also been improved in various areas.
This version also adds experimental support for peer-to-peer network. It is unverified and unsupported, and hence not recommended to be enabled in production.
Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
{
"thread": "5",
"sev": "Notice",
"data": {
"startupTime": "1638866965"
},
"loc": null,
"env": "1.31.0:be123",
"msg": "",
"app": [],
"host": "waldorf",
"at": "2021-12-07T08:49:24.22Z",
"ns": [
"cardano.node.nodeconfig"
],
"pid": "33952"
}
RemoteConnectionId
in trace messages. (#3199)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO almost 3 years ago
Cardano node version 1.31.0 introduces a number of new features and provides performance improvements, including
reducing default logging information, and optimising memory and time behaviour. It also provides support for improved rewards logging in db-sync, includes a new CLI command to query stake pools, enhances the transaction build
CLI command, fixes an issue where connections were dropped when using query tip
, and provides various other CLI enhancements. It allows signatures to be specified when spending from pre-Plutus time-lock/multi-signature scripts, improves error logging for Plutus scripts, adds new logging modes, allows the size of the mempool to be configured, provides support for multiple versions of Plutus, and improves networking behaviour and robustness.
It is recommended that all users upgrade to this new version.
calculate-min-req-utxo
requires a transaction output (TxOut era
) instead of a Value
in order to calculate the min required UTxO in the Alonzo era. This is required in the Alonzo era, and the change is made everywhere for consistency.Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
trace-dispatcher
library. This is built to replace the existing iohk-monitoring-framework
. (#3073)maybeToStrictMaybe
during translation of ProtocolParameters
. This turns out to trigger a GHC bug, resulting in extremely high compilation time. (#3275)GetChainBlockNo
and GetChainPoint
. (#3346)cardano-protocol-tpraos
. (#2445)RetiredPools
event, which gives details about retiring pools and the refund (or not) of the pool deposit. (#2487, #2495)Value
and TxInfo
in the spec. (#2383, #2494)accept
on IPv6 sockets. (#3368
build
or build-raw
commands. Required signers must be present in the witnesses, and only required signers are visible to Plutus scripts. (#3123)query tip
command. This fixes an occasional bug where the query tip
command would fail. (#3130)tx build
command. (#3032)tx build
command now validates its inputs (ensuring they are in the UTxO and that only basic VKey-locked inputs are used as collateral.) (#3151)tx build
now uses the set of existing stake pools to determine if a pool is already registered (and hence whether it must pay a deposit). (#3152)calculate-min-req-utxo
now requires a transaction output, not just a value as before. This is required in the Alonzo era, and the change is made everywhere for consistency. (#3181)tx build
command to spend the entirety of a UTxO and create no change output. (#3188)tx view
command. (#2613)GetChainBlockNo
and GetChainPoint
queries in the query tip command. There is a fallback to the older method using the full chain sync query. (#3179)--tx-out-datum-embed-value
. This mechanism can for example be used to provide the actual script locking an output, for use when spending it. (#3171)transaction build
command. (#3317)getBlockHeader
for Alonzo. This was a stray function that got missed when implementing Alonzo in the API. (#3158)chainSyncServerHeaderTracer
. This fixes a bug which caused logs to be unnecessarily verbose. (#3252)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO over 3 years ago
Node version 1.27.0 provides important new functionality, including supporting new CLI commands that have been requested by stake pools, providing garbage collection metrics.
It includes the performance fixes for the epoch boundary calculation that were released in node version 1.26.2, plus a number of bug fixes and code improvements.
It also includes many fundamental changes that are needed to prepare for forthcoming feature releases (notably Plutus scripts in the Alonzo era).
Note that this release includes breaking changes to the API and CLI commands, and that compilation using GHC version 8.6.5 is no longer supported.
There are some breaking changes:
--certificate-file $certfile --certificate-script-file $scriptfile
--tx-out $txout --minting-script-file $scriptfile
--withdrawal $withdrawal --withdrawal-script-file $scriptfile
--tx-in $txin --txin-script-file $scriptfile
Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO over 3 years ago
This point release is a recommended upgrade for all stake pool operators. It is not required for relays or other passive nodes. It ensures that block producing nodes do not unnecessarily re-evaluate the stake distribution at the epoch boundary.
Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO over 3 years ago
This release includes significant performance improvements and numerous other minor improvements and feature additions. In particular the reward calculation pause is eliminated, and the CPU load for relays handling lots of incoming transactions should be significantly reduced.
The focus of the current development work is on completing and integrating support for the Alonzo era. This release includes many of the internal changes but does not yet include support for the new era.
cardano-cli query tip
query has changed - see release notes for the CLI below.cardano-cli query ledger-state
query now produces a binary file if --out-file
is specified. If required (e.g. for use in cncli
), JSON output can be obtained by omitting this parameter, and redirecting the standard output to a fileThis release will automatically perform a DB migration on the first startup after the update. The migration should take 10-20 minutes however it can take up to 60 minutes depending on your CPU.
To mitigate downtime:
See #311 for example scripts of how this can be done.
Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO over 3 years ago
This release is expected to be the final release for the upcoming Mary hard fork, and everyone must upgrade to this (or a later) version to cross the Mary hard fork.
The Mary hard fork introduces native token functionality to Cardano. This is directly useful and is also one of the significant building blocks for the later Goguen smart contracts.
A launchpad testnet for the native token functionality has been running since December, using the cardano-node 1.24.2 release. This 1.25.1 release contains relatively minor changes for the Mary era compared to the 1.24.2 release. It is nevertheless not compatible with the 1.24.2 version and the existing testnet. The launchpad testnet will not be restarted and will remain on 1.24.2. Public testnet and staging have been upgraded to 1.25.1. If you have already tested integration with the existing launchpad testnet then no new integration work is expected for this release other than upgrading the node version and moving to the staging or public testnet.
Exchanges and other users that integrate closely with Cardano must take action to test their integration before the transition takes place on mainnet. Exchanges can use launchpad or staging, SPOs can use staging, and everyone should use public testnet once it forks. Staging will go through the Mary hard fork on 28th January, and public testnet will go through the Mary hard fork during week commencing 1st February. The native token functionality does have an impact for all custom wallet implementations: it is not a feature that can be ignored and remain compatible. All addresses are capable of receiving native tokens.
Stake Pool Operators (SPOs) and Exchanges should take note that the metric namespace has undergone consolidation, so all metrics now reside in cardano.node.metrics
:
The node configs require no changes, but allow dropping entries that became redundant: wherever cardano.node.Forge.metrics.*
, cardano.node.ChainDB.metrics.*
or cardano.node.BlockFetchDecision.connectedPeers
were mentioned, those entries can be removed. Only cardano.node.metric
needs to remain. Please see #2281 for further details.
This release uses a new cabal snapshot so could be rather resource intensive when building for the first time.
cardano.node.metrics
. This requires a one-off change to the node configuration to route all metrics to the metrics backend and not have them in the log files. This should reduce the number of such changes in future. (#2281)Platform | Block Production | Relay | Client (Desktop) |
---|---|---|---|
Linux | ✔️ | ✔️ | ✔️ |
Windows | ❌ | ❌ | ✔️ |
MacOS | ❌ | ❌ | ✔️ |
Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO almost 4 years ago
This release provides support for the upcoming Allegra (token locking) Hard Fork and Mary Hard Fork and the new features they bring.
Everyone must upgrade to this (or a later) version to cross the Allegra Hard Fork.
Daedalus users should look for Daedalus release 3.0.0 which includes a version of the node that will cross the Token locking Cardano update, however people using the node directly must upgrade.
Stake Pool Operators (SPOs) and Exchanges should update their node config "options" section with an extra entry:
"options": {
"mapBackends": {
"cardano.node.resources": [
"EKGViewBK"
],
See link to configuration files in documentation section below.
LastKnownBlockVersion-*
entries in the node config files for the Shelley-based eras. This means the configuration does not need to be updated for the Token locking or native tokens eras. (#2193)cardano-cli shelley transaction build-raw
becomes simply cardano-cli transaction build-raw
. The existing names are also kept for compatibility. (#2076, #2145)transaction policyid
for making multi-asset policy ids (#2176)byron transaction txid
to help scripts with getting the transaction id for Byron transactions made using the cli (#2169)--tx-file
flag for the command transaction txid
to accept complete txs, not just tx bodies (#2169)--ttl
flag in the --help
output (#2189, #2190)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by LaurenceIO almost 4 years ago
This release includes a substantial amount of internal changes to support the upcoming Allegra and Mary hard forks and the new features they bring. This is not the final release before the Allegra hard fork, but it does include the bulk of the functionality for both Allegra and Mary hard forks.
Another notable change in this release is an adjustment to the pool ranking that will benefit small pools that have not yet made many blocks. We have adjusted the initial Bayesian prior so that instead of assuming new pools will perform at some less-than-perfect average level, we assume they will perform more-or-less perfectly. This prior is still updated based on the actual performance history, so pools that perform poorly will still drop in ranking. This change will especially benefit small pools that have produce few blocks so far, because they have very little performance history and so their score will be more influenced by the initial prior.
Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by tatyanavych about 4 years ago
This patch release updates Cardano Node 1.21.0 with a few minor fixes. In particular, it resolves a problem on startup when the node is configured to use systemd
socket activation.
Deployed on the testnet on 6 October 2020.
Deployed on the mainnet on 6 October 2020.
systemd
socket activation (#1927)systemd
(#1775)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by dcoutts about 4 years ago
This release includes support in the cardano-cli
for multi-signature addresses and transactions. It also resolves a problem that has been affecting pool operators at the 48-hour mark within each epoch. It has various other minor improvements and fixes detailed below.
The "Live View" mode for the Cardano node is being deprecated in favour of a new external "RT View" (RT for real-time) monitoring tool which is cross-platform and has a richer browser-based interface. The new RT View component will be released separately. The Live View mode is still available in this release of the node, but will be removed in a future release.
stack
build support (#2638)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | |
Release Manager | ✔️ |
Published by tatyanavych about 4 years ago
This release is light on user-visible changes as the development has been focusing on preparations for the multi-asset features and on paying down technical debt. It does however include a number of performance improvements in the node, a few new CLI commands, and an improvement that will enable Daedalus to report stake pool saturation.
Note that this release will automatically perform a DB migration on the first startup after the update. The migration will take 10-20 minutes depending on your CPU. If this is a problem for your use, then see below for steps to mitigate this.
Deployed on the testnet on 21 September 2020.
Deployed on the mainnet on 23 September 2020.
This update includes a change in the format of a part of the chain DB (specifically the ledger state snapshots). The migration for this is handled automatically by the node on startup. The migration will take 10-20 minutes depending on your CPU.
To mitigate downtime:
See #311 for example scripts of how this can be done.
convert-cardano-address-key
for converting more legacy signing key formats (#1756, #1822)create-genesis-key-delegation-certificate
for creating genesis key delegation certificates (#1784)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by disassembler about 4 years ago
This release delivers minor improvements to the performance of the node, fixes KES period reporting for newly generated KES keys, and disables RDRAND
for seed generation.
Deployed on the testnet on 2 September 2020.
Deployed on the mainnet on 4 September 2020.
RDRAND
disabled (#1787)--treasury
flag for MIR cert creation (#1780)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by tatyanavych about 4 years ago
This release delivers major improvements to the performance of the node, including synchronisation time, startup time and epoch boundary processing.
It also introduces a number of new and updated CLI commands and an enhancement to show KES periods in the Live View console.
Deployed on the testnet on 20 August 2020.
Deployed on the mainnet on 20 August 2020.
stake-address-info
query (#1546, #1636, #1671)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by tatyanavych about 4 years ago
This is the final planned release before the Shelley hard fork. It is necessary to use this 1.18.0 version to successfully cross the hard fork.
This release delivers the complete set of Shelley features together with the mechanism that will be used to transition from the federated Byron era to the decentralised Shelley era (the hard-fork combinator).
Important new features include:
To support the new Cardano mainnet, a new configuration mode for the node has been introduced: the "Cardano" mode uses the hard-fork combinator to provide a single mode that is the sequential composition of the two current eras (Byron;Shelley). This will also be used for future versions of the node, allowing easy transitions between future eras. If you plan to use a manually configured node on the mainnet, it is crucial to use the Protocol: Cardano
mode and the correct ShelleyGenesisHash
in the node configuration file.
New Cardano documentation site with cardano-node documentation is now available. The specific configuration to run a node on mainnet or any of the testnets is also available. Note that it is necessary to use the exact Shelley genesis file to successfully cross the hard fork, and it is highly recommended to include that hash in the node configuration file, as in the provided sample configuration.
The 1.15.0, 1.15.1, 1.16.0, 1.17.0 tagged versions were not released for general use, however, for applications that were successfully integrated against 1.16.0 or 1.17.0, this release should be a drop-in replacement: there are no client interface changes compared to the unreleased 1.16.0 or 1.17.0 tags. In particular, the node's client protocols and transaction formats are unchanged since 1.16.0.
Deployed on the testnet on 25 July 2020.
Deployed on the mainnet on 25 July 2020.
QueryHardFork
) that are specific to the hard fork support (#2365, #2370)key
command with key utilities (#1487, #1493)ed25519
keys (#1411)stake-address key-hash
and VRF key hashing node key-hash-VRF
commands (#1407)info
(#1426) and query tip
commands (#1340, #1365)byron-witness-count
in the command for fee calculation (#1516)protocolMagicId
from the Shelley genesis file (#1668)stkCreds
and stpools
maps from formal spec, in line with simplifications from the executable specification (#1692)lens
with microlens
(#1705)KeepAlive
responder-side protocol handler (#2392)calculate-min-fee
command (#1401, #1408)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by tatyanavych over 4 years ago
This patch release provides fixes for hashing of stake pool metadata, and query that dumps the ledger state.
Deployed on the Shelley testnet on 29 June 2020.
Deployed on the mainnet on 30 June 2020.
metadata-hash
(#1346)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by dcoutts over 4 years ago
This release delivers new and refined CLI commands, support for transaction metadata, the new ledger minimum pool cost feature, and enhancements to pool rankings. It also includes a new implementation of the VRF cryptography primitives, improvements in the KeepAlive
network mini-protocol, the Byron-to-Shelley hard-fork implementation, block fetch calculation, logging and reporting, and simplified Docker image usage.
There are Shelley breaking changes in this release including changes in the implementation of address hash and VRF cryptography primitives, and removal of the decaying deposit feature. The Shelley features have been pre-released for public testing and review on the re-spawn of Cardano Shelley Testnet. The Shelley changes are not available in the Byron mode.
Deployed on the Shelley testnet on 23 June 2020.
minPoolCost
(#1539, #1546)--metadata-file
for transaction construction using the build-raw
command (#1038, #1233)--withdrawal
in transaction construction (#1117, #1237)metadata-hash
(#1207, #1234, #1299)--pool-metadata-file
, used in metadata-hash
command, and --metadata-url
, --metadata-hash
, used in the pool registration certificate command registration-certificate
(#1234)--multi-host-pool-relay
, --single-host-pool-relay
, --pool-relay-port
in pool registration certificate command registration-certificate
(#1282, #1296)convert-itn-key
to convert ITN keys (#1070, #1136)txid
to get the transaction id of a transaction body (#1231)CARDANO_NODE_LOGGING_HOSTNAME
(#1278)KeepAlive
network mini-protocol (#2230) for apps with scheduled stopcardano-node
is used now as the entry-point, aligning with the existing interface of the underlying service, and removing the convention of mounting volumes into specified directories. As a result, previously pre-set arguments including, but not limited to --config
or --socket-path
, now need to be passed at runtime based on user specific configuration. See the diff and inline description for more info. The quickstart mode of passing a NETWORK
environment is not impacted by this change" (#1317). This is a breaking change. Customised (other than testnet and mainnet) Docker image build may failcardano-node --version
command (#1263)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by tatyanavych over 4 years ago
This release completes the development of many core Shelley features and provides basic Shelley functionality for stake pools and delegation. It delivers new CLI commands for obtaining Shelley stake pool information and creating MIR certificates, a new network KeepAlive
mini-protocol. It also prepares the Cardano blockchain for the Byron-to-Shelley hard fork operational change that will deactivate Byron mode and will enable the Shelley decentralised mode. This release also includes improvements in existing Shelley CLI commands, as well as in KES and VRF cryptographic key processing, Praos chain selection and hard fork implementation. In addition, logging, tracing, error messages and documentation have been improved, and a few outstanding issues have been fixed, notably, an issue that was causing high CPU usage on MacOS.
The Shelley features have been pre-released for public testing and review on the Cardano Shelley Testnet.
They are not available in the Byron mode, and are, therefore, deactivated on the Cardano mainnet.
Deployed on the Shelley testnet on 5 June 2020.
Deployed on the mainnet on 9 June 2020.
KeepAlive
network mini-protocol (#2175)epochSlots
in validate-cbor
command (#848)cardano-cli
does not have description of the new, Shelley relevant, commands (#1071)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |
Published by tatyanavych over 4 years ago
This release includes the integration of the majority of the Shelley features within the node and corresponding support in the command line tool. This includes the ability:
The Shelley features are not available in the Byron mode, and so, are deactivated on the Cardano mainnet. They are pre-released and being tested on the Cardano Shelley Testnet.
In addition, logging, tracing and error messages have been improved, and a few issues have been fixed.
Deployed on the mainnet on 28 May 2020.
cardano-cli
has been extracted into a separate cardano-node sub-component (#819). It provides a command line interface for various low-level node-related functionality. Byron and Shelley relevant commands are distinguished by its prefixed byron
and shelley
command keywords. Documentation on constructing a Shelley chain from scratch (#893, #932, #1000) has been added. The following new commands were implemented:
--version
flag, with git revision (#959)cardano-client
library in the network component to provide a simpler node client API (#2109)--shutdown-on-slot-synced
flag for the benchmarking and CI tests (#776)systemd
socket activiation support (#856, #1022, #1995)systemd
support on Linux is now optional (#911)FetchDecision
tracing output (#863)TCP_NODELAY
for faster block relaying (#2069)epochSlots
in validate-cbor
command (#848)Role | Approval |
---|---|
Technical Lead | ✔️ |
QA Engineer | ✔️ |
Ops | ✔️ |
Release Manager | ✔️ |