Releases: stellar/stellar-core
v10.0.0rc1
This release includes changes to the protocol as well as some stability improvements.
As it changes the meta data format, a newer version (0.14.0 or greater) of Horizon is required.
Stability improvements
- Avoid 100% CPU usage when running certain commands (
--newhistfor example). - Handshake code in overlay had issue that would lead to peers not able to an error “unexpected MAC”.
- Align publish with network consensus, this avoids potentially publishing bad ledgers in case of corruption.
- Align catchup with network consensus, this avoids having to rely on timing (which may cause significant delays in catchup).
- Properly fail work when spawning a process throws an exception.
- Transactions are better flooded on the network.
- SCP: synchronize nodes over time to reduce chance of timeout
- SCP: nomination was sometimes computing “round leader” improperly, leading to timeouts
- SCP: ensure latest quorum information is used when whitelisting validators
- Move to a more recent version of asio.
- Reduced number of warnings.
- Properly kill subprocesses.
- Moved to
Catch2(testing). - Moved to c++ 14 for the toolchain.
Protocol Changes (v10)
- BumpSeqOp w/ seqnum processing changes
- Stellar Lightning - CAP0001
- Liabilities enforced across the board
- Made offer rounding behavior more intuitive
- Moved signature verification to transaction apply step
- Fast fail not allowing to change trust on native assets
New features
- Improved private network load testing
- updated
loadgeneratorto allow for more scalable and parallel submission of synthetic traffic. - Documented how to do performance testing
- updated
- New metrics:
- archive health
- performance characteristics of validators and network
- Validators can now be configured to upgrade to protocol versions other than the latest supported.
- Support for running tests in parallel
v9.2.0
Release notes
This release is a stability release, it makes some critical improvements that should help with network and node reliability.
Note:
On first run stellar-core may appear to be stuck for a while (order of a minute) while it garbage collects the bucket files - subsequent starts will not be slow. Last line before that pause will be “Loading last known ledger”.
You may want to disable garbage collection of historical meta data if you need to reingest it in Horizon for example.
Stability improvements
- Fixed an issue where the local state would get corrupted on shutdown (this would require resetting the node).
- SCP improvements (sometimes rounds were too short, sometimes too long due to timeouts).
- Send list of alternate nodes when shutting down connections due to load (improves discovery of alternate nodes even when connecting to ones that are full).
- Properly garbage collect buckets left in buckets folder.
- Fast fail when encountering unknown protocol versions.
- Reworked the admin guide to follow a “step-by-step” approach to running a node as well as integrating updated information from various sources.
- Connect to peers marked as
PREFERRED_PEERSon a regular basis, even after reaching the connection target - Avoid running out of file descriptors when connecting to more peers (when limits are not compatible with configuration file)
- Fixed an issue where nodes would experience intermittent high CPU usage when connected to many other peers
New features
- Automatic periodic maintenance now deletes unused historical data from SQL - it is enabled by default (controlled by AUTOMATIC_MAINTENANCE_PERIOD and AUTOMATIC_MAINTENANCE_COUNT ; disable it with
AUTOMATIC_MAINTENANCE_PERIOD=0). - Make sure to read the admin guide ( https://github.com/stellar/stellar-core/blob/master/docs/software/admin.md#cursors-and-automatic-maintenance ).
v9.2.0rc6 - PRE RELEASE
draft release notes https://gist.github.com/MonsieurNicolas/f561948ef5a73145a9bcd63766846df5
v9.2.0rc5 - PRE RELEASE
draft release notes https://gist.github.com/MonsieurNicolas/f561948ef5a73145a9bcd63766846df5
v9.2.0rc4 - PRE RELEASE
draft release notes https://gist.github.com/MonsieurNicolas/f561948ef5a73145a9bcd63766846df5
v9.2.0rc3 PRE-RELEASE
Merge pull request #1585 from MonsieurNicolas/prefPeersAlways Always connect to preferred peers Reviewed-by: MonsieurNicolas
v9.2.0rc2
Merge pull request #1576 from MonsieurNicolas/maintenancePerfFix improve query used to delete old entries during maintenance Reviewed-by: jonjove
v9.2.0rc1
Merge pull request #1537 from vogel/cleanup-stale-buckets Cleanup stale buckets Reviewed-by: MonsieurNicolas
v9.1.0
Release notes:
This release is highly recommended as it fixes critical stability bugs.
Stability improvements:
Consensus:
Fixed a bug in caching of quorum sets that could result in crashes or impact liveness of the network
Fixed an edge case where validators could fall back into “joining SCP” when externalizing a ledger is slow, causing nodes to stall
History subsystem:
Fixed issue when publishing to multiple archives at once
Fixed issues with level 10 merge (bucket list), resulting in some corrupted checkpoints
Networking:
Fix issue where new peers could not be discovered
Added a new setting to better control the number of inbound connections allowed (to avoid locking peers out of the network)
General:
Updated to latest versions of xdrpp, cereal
New features:
none
v9.0.1
This dot release addresses a problem with the upgrade process that would cause misconfigured nodes (validators and non validators) to get out of sync.
This problem has been present since day one but has the potential to be more of a problem as validators vote on changing more network wide settings.
Breaking changes
The following settings have been removed from the configuration file: PREFERRED_UPGRADE_DATETIME, DESIRED_BASE_FEE, DESIRED_BASE_RESERVE and DESIRED_MAX_TX_PER_LEDGER.
Read the admin guide for more details on how to configure a validator to vote for network settings changes.
Example "recipe" for a network upgrade can be found at https://github.com/stellar/stellar-core/blob/448efc241cc373c9ca0dc06c72e24bd5ad26238f/docs/software/admin.md#upgrading-network-settings