You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/mainnet/docs/installation/downloads.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -187,7 +187,7 @@ For the system requirements to run a node, see :ref:`System requirements to run
187
187
188
188
.. dropdown:: Ubuntu |mainnet-node-version|
189
189
190
-
To run a node on a server with Ubuntu, `download a Mainnet Debian package <https://distribution.mainnet.concordium.software/deb/concordium-mainnet-node_7.0.5-0_amd64.deb>`_.
190
+
To run a node on a server with Ubuntu, `download a Mainnet Debian package <https://distribution.mainnet.concordium.software/deb/concordium-mainnet-node_8.0.3-1_amd64.deb>`_.
191
191
192
192
- SHA256 checksum of the download: |node-deb-package-checksum|
193
193
@@ -199,13 +199,13 @@ For the system requirements to run a node, see :ref:`System requirements to run
199
199
200
200
.. dropdown:: Windows |mainnet-node-version|
201
201
202
-
To run a node on Windows, `download a Mainnet Windows Installer package <https://distribution.concordium.software/windows/Signed/Node-7.0.5-0.msi>`_. **Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**
202
+
To run a node on Windows, `download a Mainnet Windows Installer package <https://distribution.concordium.software/windows/Signed/Node-8.0.3-1.msi>`_. **Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**
203
203
204
204
To learn how to run a node on Windows, see :ref:`Run and manage a node on Windows <run-node-windows>`.
205
205
206
206
.. dropdown:: Mac |mainnet-node-version|
207
207
208
-
To run a node on macOS, `download a Mainnet macOS installer package <https://distribution.concordium.software/macos/signed/concordium-node-7.0.5.pkg>`_.
208
+
To run a node on macOS, `download a Mainnet macOS installer package <https://distribution.concordium.software/macos/signed/concordium-node-8.0.3-1.pkg>`_.
209
209
210
210
To learn how to run a node on Mac, see :ref:`Run and manage a node on macOS <run-node-macos>`.
Copy file name to clipboardExpand all lines: source/mainnet/docs/release-notes/release-notes-lp.rst
+60-25Lines changed: 60 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -689,52 +689,87 @@ Nodes
689
689
Mainnet
690
690
-------
691
691
692
-
October 3, 2024
692
+
March 3, 2025
693
693
694
-
Concordium node version 7.0.5 contains support for `protocol version 7 <https://proposals.concordium.software/updates/P7.html>`_.
695
-
The new consensus protocol will take effect on the mainnet on October 30, 2024.
696
-
**Node runners should upgrade to version 7.0.5 before the protocol update to ensure that their nodes do not shut down.**
694
+
Concordium node version 8.0.3 contains support for `protocol version 8 <https://proposals.concordium.software/updates/P8.html>`_.
695
+
The new consensus protocol will take effect on the mainnet on March 17, 2025.
696
+
**Node runners should upgrade to version 8.0.3 before the protocol update to ensure that their nodes do not shut down.**
697
+
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.
697
698
698
-
Protocol version 7 introduces the following changes:
699
+
Protocol version 8 introduces the following changes:
699
700
700
-
- The cool-down behavior when the stake of a validator or delegator is reduced or removed is changed:
701
+
- Validators are automatically suspended if they do not produce blocks for a certain number of rounds.
701
702
702
-
- 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.
703
-
(Previously, the reduction was only effective after the cool-down period.)
703
+
- The configure-validator transaction can suspend or resume a validator, including adding a validator in a suspended state.
704
704
705
-
- Validators and delegators can make further changes to their stake while they already have stake in cooldown.
706
-
This includes registering as a validator when the account was previously a delegator, or vice versa.
707
-
(Previously, the account had to wait for the cool-down period to end before making further changes.)
705
+
- Suspended validators are paused from participating in the consensus algorithm.
708
706
709
-
- Shielded transfers are no longer supported in the protocol.
710
-
It is still possible to unshield a previously shielded balance.
707
+
Additionally, the node release includes a number of fixes and improvements:
711
708
712
-
- Smart contract execution costs are reduced.
713
-
This reflects a more efficient implementation of the smart contract execution engine introduced in this release.
709
+
- Add suspension info to `BakerPoolStatus` / `CurrentPaydayBakerPoolStatus` query results.
714
710
715
-
- Smart contracts can now query the module reference and contract name of a smart contract instance.
711
+
- Add `GetConsensusDetailedStatus` gRPC endpoint for getting detailed information on the status of the consensus, at consensus version 1.
716
712
717
-
- The block hashing scheme is redefined to better support light clients.
713
+
- Update Rust version to 1.82.
718
714
719
-
Additionaly, the node release includes a number of fixes and improvements:
715
+
- Update GHC version to 9.6.6 (LTS-22.39).
720
716
721
-
- Logging around protocol updates is improved.
722
-
- Failed gRPC requests are now logged at ``DEBUG`` level.
723
-
- Fixed a bug where ``GetBakersRewardPeriod`` returns incorrect data.
724
-
- Fixed a bug where ``GetPoolInfo`` returns incorrect data.
725
-
- 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.
726
-
- Improved the behavior of the node in the event of an unrecoverable error in consensus.
717
+
- Add `GetScheduledReleaseAccounts` endpoint for querying the list of accounts that have scheduled releases.
718
+
719
+
- Add `GetCooldownAccounts`, `GetPreCooldownAccounts` and `GetPrePreCooldownAccounts` endpoints for querying the lists of accounts that have pending cooldowns in protocol version 7 onwards.
720
+
721
+
- gRPC endpoints `DryRun`, `GetBlockItemStatus` and `GetBlockTransactionEvents` now report the parameter used to initialize a smart contract instance as part of a `ContractInitializedEvent`.
722
+
723
+
- 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.
724
+
725
+
- 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.
727
726
728
727
.. dropdown:: Previous releases
729
728
729
+
.. dropdown:: 7.0.5 - October 3, 2024
730
+
731
+
Concordium node version 7.0.5 contains support for `protocol version 7 <https://proposals.concordium.software/updates/P7.html>`_.
732
+
The new consensus protocol will take effect on the mainnet on October 30, 2024.
733
+
**Node runners should upgrade to version 7.0.5 before the protocol update to ensure that their nodes do not shut down.**
734
+
735
+
Protocol version 7 introduces the following changes:
736
+
737
+
- The cool-down behavior when the stake of a validator or delegator is reduced or removed is changed:
738
+
739
+
- 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.
740
+
(Previously, the reduction was only effective after the cool-down period.)
741
+
742
+
- Validators and delegators can make further changes to their stake while they already have stake in cooldown.
743
+
This includes registering as a validator when the account was previously a delegator, or vice versa.
744
+
(Previously, the account had to wait for the cool-down period to end before making further changes.)
745
+
746
+
- Shielded transfers are no longer supported in the protocol.
747
+
It is still possible to unshield a previously shielded balance.
748
+
749
+
- Smart contract execution costs are reduced.
750
+
This reflects a more efficient implementation of the smart contract execution engine introduced in this release.
751
+
752
+
- Smart contracts can now query the module reference and contract name of a smart contract instance.
753
+
754
+
- The block hashing scheme is redefined to better support light clients.
755
+
756
+
Additionaly, the node release includes a number of fixes and improvements:
757
+
758
+
- Logging around protocol updates is improved.
759
+
- Failed gRPC requests are now logged at ``DEBUG`` level.
760
+
- Fixed a bug where ``GetBakersRewardPeriod`` returns incorrect data.
761
+
- Fixed a bug where ``GetPoolInfo`` returns incorrect data.
762
+
- 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.
763
+
- Improved the behavior of the node in the event of an unrecoverable error in consensus.
764
+
730
765
.. dropdown:: 6.3.2 - September 30, 2024
731
766
732
767
Concordium node version 6.3.2 fixes a bug in the handling of smart contract names that could cause the node to crash.
733
768
**This is a critical bug fix, and node runners should update as soon as possible.**
734
769
735
770
.. dropdown:: 6.3.1 - June 24, 2024
736
771
737
-
Concordium node version 6.3.1 fixes a bug where a node may fail to produce a timeout certificate due to incorrectly computing the total weight of finalizers that have signed timeout messages.
772
+
Concordium node version 6.3.1 fixes a bug where a node may fail to produce a timeout certificate due to incorrectly computing the total weight of finalizers that have signed timeout messages.
0 commit comments