Skip to content

Releases: stellar/stellar-core

v9.2.0rc5 - PRE RELEASE

10 Mar 00:15
6dfee37
Compare
Choose a tag to compare

v9.2.0rc4 - PRE RELEASE

08 Mar 21:40
bd4940e
Compare
Choose a tag to compare

v9.2.0rc3 PRE-RELEASE

08 Mar 01:08
74cae1e
Compare
Choose a tag to compare
v9.2.0rc3 PRE-RELEASE Pre-release
Pre-release
Merge pull request #1585 from MonsieurNicolas/prefPeersAlways

Always connect to preferred peers

Reviewed-by: MonsieurNicolas

v9.2.0rc2

01 Mar 22:58
139d548
Compare
Choose a tag to compare
v9.2.0rc2 Pre-release
Pre-release
Merge pull request #1576 from MonsieurNicolas/maintenancePerfFix

improve query used to delete old entries during maintenance

Reviewed-by: jonjove

v9.2.0rc1

28 Feb 23:55
8d37e95
Compare
Choose a tag to compare
v9.2.0rc1 Pre-release
Pre-release
Merge pull request #1537 from vogel/cleanup-stale-buckets

Cleanup stale buckets

Reviewed-by: MonsieurNicolas

v9.1.0

18 Jan 18:37
Compare
Choose a tag to compare

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

20 Dec 16:17
Compare
Choose a tag to compare

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.

https://github.com/stellar/stellar-core/blob/448efc241cc373c9ca0dc06c72e24bd5ad26238f/docs/software/admin.md#network-configuration

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

v9.0.0

08 Dec 19:23
Compare
Choose a tag to compare

Before upgrading please review https://github.com/stellar/stellar-core/blob/master/docs/software/admin.md#network-configuration

Focus:

Protocol updates Invariant support part1

Release notes:

To make things simpler to track and understand, we’re switching to version numbers setup as protocol_version.release_number.patch_number.

It then follows that this version is named 9.0.0 as it's the first version implementing the protocol version 9.

Stability improvements:

Improvements to the overlay code that should increase the chances to connect to preferred peers even when fully connected.

core is less pedantic when configuring nested quorum sets #1425

Protocol Changes (v9): Unify how validators can update network configurations with protocol changes - all network wide configurations are now gated by the PREFERRED_UPGRADE_DATETIME to allow for validators to agree in advance on when changes would take effect

Support for validators to vote for minimum reserve

Manage Offer Updates

always set aside the minimum balance when creating XLM offers #1430

Don't check for the fee twice #1220

New features:

Invariants are coming. In this release we’re adding the capability for validators to perform additional checks on transactions as well as integrity check of the buckets. Invariants are turned off by default.

Some work was done to enable parallel catchup (only used when performing full history validation for now)

v0.6.4

01 Nov 23:50
Compare
Choose a tag to compare

Stability improvements

  • Many history catchup fixes - should be much more accurate in catching up directly
  • Nodes should again be able to keep up with the network when restarting without having to
  • Windows Build works again
  • Improved ledger entries validations
  • Mac and Windows dev experience improvements
  • publish/fetch tools now inherit environment (allows to use GCP tool set for example)

New features

  • Added capability to catch up to a specific ledger number from the command line without joining the network (useful when preparing machines before joining the network or for reconstructing a specific ledger state)

v0.6.3

08 Aug 18:36
Compare
Choose a tag to compare

New Features

  • Added --catchup-complete It does a complete catchup without following the current network then quits. Useful to run on a new instance to get the vast majority of the history before you try to sync.

Fixes

  • Many catch-up speed improvements
  • Better diagnostics
  • Fixed crash during catchup