Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

6.1.7 Testnet release #902

Merged
merged 3 commits into from
Oct 16, 2023
Merged

6.1.7 Testnet release #902

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fbf9018
6.1.7 Testnet release
dg-concordium Oct 13, 2023
fe46187
Apply suggestions from code review
abizjak Oct 16, 2023
f00a0aa
Merge branch 'main' into 617-testnet-node-release
abizjak Oct 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions source/mainnet/net/installation/downloads.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -240,9 +240,9 @@ For the system requirements to run a node, see :ref:`System requirements to run

.. dropdown:: Ubuntu |testnet-node-version|

To run a node on a server with Ubuntu, `download a Testnet Debian package <https://distribution.testnet.concordium.com/deb/concordium-testnet-node_6.1.6-0_amd64.deb>`_.
To run a node on a server with Ubuntu, `download a Testnet Debian package <https://distribution.testnet.concordium.com/deb/concordium-testnet-node_6.1.7-0_amd64.deb>`_.

- SHA256 checksum of the download: ``b668ea82418fc713665c15361e8ab4fc09002ffdee6e7eabe19cce05b14be0e7``
- SHA256 checksum of the download: ``b1b1e1c5e2e9e8100094a2e1d9fced47dc98e9dfcf0897e89755011adc44781a``

To learn how to run a node with Ubuntu, see :ref:`Run a node on a server with Ubuntu <run-node-ubuntu>`.

Expand All @@ -256,13 +256,13 @@ For the system requirements to run a node, see :ref:`System requirements to run

.. dropdown:: Windows |testnet-node-version|

To run a node on Windows, `download a Testnet Windows Installer package <https://distribution.concordium.software/windows/Signed/Node-6.1.6-0.msi>`_. **Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**
To run a node on Windows, `download a Testnet Windows Installer package <https://distribution.concordium.software/windows/Signed/Node-6.1.7-0.msi>`_. **Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**

To learn how to run a node on Windows, see :ref:`Run and manage a node on Windows <run-node-windows>`.

.. dropdown:: Mac |testnet-node-version|

To run a node on macOS, `download a Testnet macOS installer package <https://distribution.concordium.software/macos/signed/concordium-node-6.1.6-0.pkg>`_.
To run a node on macOS, `download a Testnet macOS installer package <https://distribution.concordium.software/macos/signed/concordium-node-6.1.7-1.pkg>`_.

To learn how to run a node on Mac, see :ref:`Run and manage a node on macOS <run-node-macos>`.

Expand Down
56 changes: 30 additions & 26 deletions source/mainnet/net/release-notes/release-notes-lp.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -903,57 +903,61 @@ Mainnet
Testnet
-------

October 10, 2023
October 16, 2023

Concordium Node 6.1.6 contains bug fixes and improvements. **This is the last release of the node that has support for V1 gRPC API.**
Version 6.1.7 adds load shedding for gRPC v2. This helps with protecting the node in case of high number of concurrent requests since they are now dropped immediately as opposed to queued.

**Improvements**
.. dropdown:: Previous releases

- Out-of-band catchup is now enabled by default on all platforms.
.. dropdown:: 6.1.6 - October 10, 2023

- The node remembers peers across restarts. When starting up it will try to connect to stored peers in addition to any supplied bootstrap and given nodes. Use the new flag ``--clear-persisted-peers`` (environment variable ``CONCORDIUM_NODE_CLEAR_PERSISTED_PEERS``) to clear stored peers on startup.
Concordium Node 6.1.6 contains bug fixes and improvements. **This is the last release of the node that has support for V1 gRPC API.**

- If the node is `configured with TLS <https://github.com/Concordium/concordium-node/blob/main/docs/grpc2.md#grpc-api-v2>`_, then `CONCORDIUM_NODE_COLLECTOR_GRPC_HOST` must be configured such that it uses the domain of the certificate, for example, ``CONCORDIUM_NODE_COLLECTOR_GRPC_HOST=https://example.concordium-node.io:20000``.
**Improvements**

- Exposed the health check service via grpc-web when grpc-web is enabled.
- Out-of-band catchup is now enabled by default on all platforms.

- Banned peers are no longer reset on startup by default. The flag ``--no-clear-bans`` has been renamed to ``--clear-bans``; when set it will clear the banned peers on startup.
- The node remembers peers across restarts. When starting up it will try to connect to stored peers in addition to any supplied bootstrap and given nodes. Use the new flag ``--clear-persisted-peers`` (environment variable ``CONCORDIUM_NODE_CLEAR_PERSISTED_PEERS``) to clear stored peers on startup.

- Add debug-level logging when a round is advanced, either due to a quorum certificate or a timeout certificate.
- If the node is `configured with TLS <https://github.com/Concordium/concordium-node/blob/main/docs/grpc2.md#grpc-api-v2>`_, then `CONCORDIUM_NODE_COLLECTOR_GRPC_HOST` must be configured such that it uses the domain of the certificate, for example, ``CONCORDIUM_NODE_COLLECTOR_GRPC_HOST=https://example.concordium-node.io:20000``.

- Removed the concept of pending blocks.
- Exposed the health check service via grpc-web when grpc-web is enabled.

- ``GetPoolInfo`` now also returns the commission rates for the current reward period.
- Banned peers are no longer reset on startup by default. The flag ``--no-clear-bans`` has been renamed to ``--clear-bans``; when set it will clear the banned peers on startup.

- Added a number of endpoints to the GRPCV2 API, including:
- Add debug-level logging when a round is advanced, either due to a quorum certificate or a timeout certificate.

- ``GetBakersRewardPeriod``: provided a block, then it returns information about bakers for the reward period of the block.
- Removed the concept of pending blocks.

- ``GetBlockCertificates``: provided a block, then it returns quorum certificate, timeout certificate, and epoch finalization entry contained in the block (where present).
- ``GetPoolInfo`` now also returns the commission rates for the current reward period.

- ``GetBakerEarliestWinTime``: provided a baker ID, it returns the earliest time at which the node projects that the baker could be required to bake a block.
- Added a number of endpoints to the GRPCV2 API, including:

- ``GetFirstBlockEpoch``: returns the block hash of the first block in a given epoch.
- ``GetBakersRewardPeriod``: provided a block, then it returns information about bakers for the reward period of the block.

- ``GetWinningBakersEpoch``: returns a list of the bakers that won rounds in a specified (finalized) epoch. This only supports consensus version 1.
- ``GetBlockCertificates``: provided a block, then it returns quorum certificate, timeout certificate, and epoch finalization entry contained in the block (where present).

**Fixes**
- ``GetBakerEarliestWinTime``: provided a baker ID, it returns the earliest time at which the node projects that the baker could be required to bake a block.

- An incorrect ``peer_bucket_size`` metric calculation exposed by the bootstrapper was fixed. What was counted was not the number of peers in the bucket, but rather, roughly, how many times peers that are in the bucket have reconnected.
- ``GetFirstBlockEpoch``: returns the block hash of the first block in a given epoch.

- Fixed a bug where the block state hash was not returned properly for the genesis block.
- ``GetWinningBakersEpoch``: returns a list of the bakers that won rounds in a specified (finalized) epoch. This only supports consensus version 1.

- Fixed a bug where credential registration IDs for genesis accounts were not correctly recorded. As a result, the index of accounts by credential IDs was incorrect if the chain was started from genesis by node versions 5.1.3 up to and including 6.0. If a chain was started by an older node version and then the node was upgraded, the index is loaded correctly. This index is used when checking for duplicate credential registration IDs, and when looking up an account via a credential registration ID.
**Fixes**

- Fixed a bug in the ``InvokeInstance`` endpoint where the amount sent was used incorrectly. The consequence was that in some cases the calls would fail with an error indicating insufficient amount on the account where the amount was sufficient for the transaction.
- An incorrect ``peer_bucket_size`` metric calculation exposed by the bootstrapper was fixed. What was counted was not the number of peers in the bucket, but rather, roughly, how many times peers that are in the bucket have reconnected.

- Applied fix for processing of chain parameter updates when they occur at the same time retroactively to all protocol versions. This may break compatibility with any local/private chains on which the bug occurs.
- Fixed a bug where the block state hash was not returned properly for the genesis block.

- Fixed a bug in how the last timeout certificate is recovered at start-up.
- Fixed a bug where credential registration IDs for genesis accounts were not correctly recorded. As a result, the index of accounts by credential IDs was incorrect if the chain was started from genesis by node versions 5.1.3 up to and including 6.0. If a chain was started by an older node version and then the node was upgraded, the index is loaded correctly. This index is used when checking for duplicate credential registration IDs, and when looking up an account via a credential registration ID.

- Fixed the behavior of the block last finalized pointer in the ``GetBlockInfo`` so that it consistently returns the last finalized block at the time the block was baked.
- Fixed a bug in the ``InvokeInstance`` endpoint where the amount sent was used incorrectly. The consequence was that in some cases the calls would fail with an error indicating insufficient amount on the account where the amount was sufficient for the transaction.

.. dropdown:: Previous releases
- Applied fix for processing of chain parameter updates when they occur at the same time retroactively to all protocol versions. This may break compatibility with any local/private chains on which the bug occurs.

- Fixed a bug in how the last timeout certificate is recovered at start-up.

- Fixed the behavior of the block last finalized pointer in the ``GetBlockInfo`` so that it consistently returns the last finalized block at the time the block was baked.

.. dropdown:: 6.0.4 - August 9, 2023

Expand Down
2 changes: 1 addition & 1 deletion source/mainnet/variables.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@

.. Node version variables
.. |mainnet-node-version| replace:: 6.0.4
.. |testnet-node-version| replace:: 6.1.6
.. |testnet-node-version| replace:: 6.1.7

.. Node debian package verification variables
.. |node-deb-package| replace:: concordium-mainnet-node_6.0.4-0_amd64.deb
Expand Down
Loading