What's Changed

This release includes support for Protocol 24

horizonclient

• Fix memory leak in clients/horizonclient/client (#5789)

txnbuild

None.

Full Changelog: horizonclient-v23.0.0...horizonclient-v24.0.0

Added

• support for Protocol 24
• moved ingest/verify to be internally located at services/horizon/internal/ingest package (5670).
• Added the horizon ingest load-test command to load test Horizon's ingestion capabilities. Also added the horizon ingest load-test-restore command to restore the Horizon DB if a previous load test did not terminate gracefully (5794).
• Keep the admin server running while executing Horizon ingestion commands so that Horizon can export prometheus metrics during long running ingestion operations (5816).

This release adds support for Protocol 24

What's Changed

This release includes support for Protocol 23

horizonclient

Breaking Changes

• The errorResultXdr field from the response of the async transaction submission endpoint has been removed (5737).
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been removed (5611).

Additive Changes

• Added 1 new optional string field destination_muxed_id in the asset_balance_changes section of the /operations endpoint which represents the muxed id in the case where an asset is transferred to a muxed account destination (5715, 5739).

txnbuild

Additive Changes

• Add helper for sending a payments to smart contract destinations 5642.

Full Changelog: horizonclient-v15.0.0...horizonclient-v23.0.0

This release adds support for Protocol 23

Upgrading to this version will trigger a state rebuild. During this process, Horizon will not ingest new ledgers.

This release of Horizon requires stellar-core version v23.0.0 or higher. Older versions of stellar-core are incompatible with this build of Horizon.

This release of Horizon adds a lengthy database migration (5745) to improve the ingestion performance of trade aggregations. Horizon will not be able to ingest new ledgers while the migration is running.

Breaking Changes

In Protocol 23, Stellar Core removes in-memory mode and requires on-disk mode (using BucketListDB) for captive core (5627). As a result, the following configurations are no longer supported and have been removed:

• CAPTIVE_CORE_USE_DB
• DEPRECATED_SQL_LEDGER_STATE

Added

• Update default pubnet captive core configuration to replace Whalestack with Creit Technologies in the quorum set (5564).
• Added 1 new optional string field destination_muxed_id in the asset_balance_changes section of the /operations endpoint which represents the muxed id in the case where an asset is transferred to a muxed account destination (5715, 5739). Note that the destination_muxed_id_type field was introduced in the 23.0.0-rc1 release, however, the field turned out to be unnecessary and was removed.
• Added support for a new config parameter - EMIT_VERBOSE_META (5766). Defaults to FALSE. When set to TRUE, the transaction-meta will contain diagnostic events (in smart contract transactions). Additionally, unified events will appear in the tx-meta, as per CAP-67.

Removed

• The errorResultXdr field from the response of the async transaction submission endpoint has been removed (5737).
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been removed (5611).

New Features

• Galexie can be configured to use S3 (or services which have an S3 compatible API) instead of GCS for storage (#5748)
• Add EMIT_CLASSIC_EVENTS and BACKFILL_STELLAR_ASSET_EVENTS flags (53d703e)
• Support for Protocol 23.

Breaking Changes

⚠ This is a breaking change that requires a one-time update to your bucket. For detailed instructions, please see UPGRADE.md.

• Galexie now complies with SEP-0054 (#5773)
  • Ledger file extension changed from .zstd to .zst (standard Zstandard compression extension).
  • Galexie will create a new .config.json manifest file in the data lake on its first run if one doesn't already exist.

What's Changed

This release includes support for Protocol 23

horizonclient

Breaking Changes

• The errorResultXdr field from the response of the async transaction submission endpoint has been removed (5737).
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been removed (5611).

Additive Changes

• Added 1 new optional string field destination_muxed_id in the asset_balance_changes section of the /operations endpoint which represents the muxed id in the case where an asset is transferred to a muxed account destination (5715, 5739).

txnbuild

Additive Changes

• Add helper for sending a payments to smart contract destinations 5642.

Full Changelog: horizonclient-v15.0.0...horizonclient-v23.0.0-rc

This release adds support for Protocol 23

Upgrading to this version will trigger a state rebuild. During this process, Horizon will not ingest new ledgers.

This release of Horizon requires stellar-core version 23.0.0rc.1 or higher. Older versions of stellar-core are incompatible with this build of Horizon.

This release of Horizon adds a lengthy database migration (5745) to improve the ingestion performance of trade aggregations. Horizon will not be able to ingest new ledgers while the migration is running.

Breaking Changes

In Protocol 23, Stellar Core removes in-memory mode and requires on-disk mode (using BucketListDB) for captive core (5627). As a result, the following configurations are no longer supported and have been removed:

• CAPTIVE_CORE_USE_DB
• DEPRECATED_SQL_LEDGER_STATE

Added

• Update default pubnet captive core configuration to replace Whalestack with Creit Technologies in the quorum set (5564).
• Added 1 new optional string field destination_muxed_id in the asset_balance_changes section of the /operations endpoint which represents the muxed id in the case where an asset is transferred to a muxed account destination (5715, 5739). Note that the destination_muxed_id_type field was introduced in the 23.0.0-rc1 release, however, the field turned out to be unnecessary and was removed.

Removed

• The errorResultXdr field from the response of the async transaction submission endpoint has been removed (5737).
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been removed (5611).

What's Changed

• Skip publishing docker image with latest tag for RC builds by @urvisavla in #5704
• Add EMIT_CLASSIC_EVENTS and BACKFILL_STELLAR_ASSET_EVENTS flags (53d703e)
• Release candidate with support for Protocol 23.

This release adds support for Protocol 23

Upgrading to this version will trigger a state rebuild. During this process, Horizon will not ingest new ledgers.

This release of Horizon requires stellar-core version 23.0.0rc.1 or higher. Older versions of stellar-core are incompatible with this build of Horizon.

Breaking Changes

In Protocol 23, Stellar Core removes in-memory mode and requires on-disk mode (using BucketListDB) for captive core (5627). As a result, the following configurations are no longer supported and have been removed:

• CAPTIVE_CORE_USE_DB
• DEPRECATED_SQL_LEDGER_STATE

Added

• Update default pubnet captive core configuration to replace Whalestack with Creit Technologies in the quorum set (5564).
• Added 2 new optional string fields - destination_muxed_id_type and destination_muxed_id, in the asset_balance_changes section of the /operations endpoint. If operation is InvokeHostFunction and if the destination is a muxed address, then the destination_muxed_id_type represents the type of the muxed id - uint64,string or bytes, and destination_muxed_id contains the value (hex encoded string, if the type is bytes ) (5715).

Removed

• The errorResultXdr field from the response of the async transaction submission endpoint has been removed (5737).
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been removed (5611).