stellar/go horizon-v23.0.0

Horizon v23.0.0

on GitHub

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).