Releases: stellar/go
horizonclient & txnbuild v23.0.0-rc
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
andarchived_contracts_amount
fields from the/assets
response have been removed (5611).
Additive Changes
- Added 1 new optional string field
destination_muxed_id
in theasset_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
Horizon v23.0.0-rc2
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 theasset_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 thedestination_muxed_id_type
field was introduced in the23.0.0-rc1
release, however, the field turned out to be unnecessary and was removed.
Removed
Galexie v23.0.0-rc2
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.
Horizon v23.0.0-rc1
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
anddestination_muxed_id
, in theasset_balance_changes
section of the/operations
endpoint. If operation isInvokeHostFunction
and if the destination is a muxed address, then thedestination_muxed_id_type
represents the type of the muxed id -uint64
,string
orbytes
, anddestination_muxed_id
contains the value (hex encoded string, if the type is bytes ) (5715).
Removed
Galexie v23.0.0-rc1.1
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)
Galexie v23.0.0-rc1
Release candidate with support for Protocol 23.
Horizon v22.0.3
What's Changed
Fixed
- Fix the account operations endpoint to include InvokeHostFunction operations. The fix ensures that all account operations will be listed going forward. However, it will not retroactively include these operations for previously ingested ledgers; reingesting the historical data is required to address that. (5574) by @urvisavla in (#5649)
Full Changelog: horizon-v22.0.2...horizon-v22.0.3
Horizon v22.0.2
Fixed
- Fix liquidity pool bug which resulted in invalid paths being included in the
/paths/strict-receive
response (5541).
Horizon v22.0.1
Fixed
- Fix the issue where the skip-txmeta flag is not being applied in
/transactions/{tx-id}
endpoint (5523). - Fix
horizon_ingest_reap_lookup_tables_duration_seconds
metric which reports the total number of lookup table rows which were reaped (5528).
Removed
- Removed defunct
init-genesis-state
command (5504).
Galexie v22.0.0
-
Add support for Protocol 22
-
Improve performance of XDR encoding / decoding (#5494)