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)

Horizon v22.0.0

This release adds support for Protocol 22

Breaking Changes

• --parallel-job-size configuration parameter for the stellar-horizon db reingest command has been removed.
  Job size will be automatically determined based on the number of workers (configuration parameter --parallel-workers), distributing
  the range equally among them. The minimum job size will remain 64 ledgers and the start and end ledger range will be rounded to
  the nearest checkpoint. (5484)

• Removed num_accounts and amount fields from Asset stats related endpoints, and valid_before and valid_after fields from transaction related endpoints. Issue - 5438, PR - 5478

  • These fields have already been functionally deprecated as of release v2.1.0. As a part of this release, these fields are omitted from API Response
  • Additionally, the num_accounts and amount columns have been dropped from exp_asset_stats table in Postgres.

Added

• Added response for new constructor functionality (introduced in protocol 22) in invoke host function operation (5488).

• Add metrics which give insight into how long it takes for ingestion to startup (5449).

• Added error_result_xdr field in the response of the async transaction submission endpoint, POST /transactions_async. error_result_xdr should be used instead of errorResultXdr which is now deprecated. (5445)

Fixed

• Fixed the error field nested in the extras field in the response of the async transaction submission endpoint POST /transactions_async. (5440)

• Improved performance of requests which query the lower boundary of horizon's history when running a horizon instance with the --history-retention-count flag. (5410, 5448, 5465)

• Improve performance of ingestion when running horizon with the --history-retention-count flag by executing reaping of history lookup tables concurrently with ingestion. (5405)

• Improve performance of ingestion when consuming ledgers via the BufferedStorageBackend. (5494)

Deprecations

• The errorResultXdr field from the response of the async transaction submission endpoint has been deprecated and will be removed in the v23 release. (5496)
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been deprecated and will be removed in the v23 Horizon release. (5496)

Galexie v22.0.0-rc1

• Add support for Protocol 22

• Improve performance of XDR encoding / decoding (#5494)

horizonclient & txnbuild v15.0.0

This release includes support for Protocol 22

horizonclient

• Add new new async transaction submission endpoint (#5188)
• Removed num_accounts and amount fields from Asset stats related endpoints, and valid_before and valid_after fields from transaction related endpoints (#5478)

txnbuild

• Bump XDR definitions for protocol 22 (#5443, #5457, #5474)

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

Horizon v22.0.0-rc2

This release adds support for Protocol 22

Deprecations

• The errorResultXdr field from the response of the async transaction submission endpoint has been temporarily reinstated. However it will be removed in the v23 release. (5496)
• The num_archived_contracts and archived_contracts_amount fields from the /assets response have been deprecated and will be removed in the v23 Horizon release. (5496)

Horizon v22.0.0-rc1

This is the release candidate for Protocol 22

Breaking Changes

• --parallel-job-size configuration parameter for the stellar-horizon db reingest command has been removed.
  Job size will be automatically determined based on the number of workers (configuration parameter --parallel-workers), distributing
  the range equally among them. The minimum job size will remain 64 ledgers and the start and end ledger range will be rounded to
  the nearest checkpoint. (5484)

• Removed num_accounts and amount fields from Asset stats related endpoints, and valid_before and valid_after fields from transaction related endpoints. Issue - 5438, PR - 5478

  • These fields have already been functionally deprecated as of release v2.1.0. As a part of this release, these fields are omitted from API Response
  • Additionally, the num_accounts and amount columns have been dropped from exp_asset_stats table in Postgres.

• Renamed errorResultXdr field to error_result_xdr in the response of the async transaction submission endpoint, POST /transactions_async. (5445)

Added

• Added response for new constructor functionality (introduced in protocol 22) in invoke host function operation (5488).

• Add metrics which give insight into how long it takes for ingestion to startup (5449).

Fixed

• Fixed the error field nested in the extras field in the response of the async transaction submission endpoint POST /transactions_async. (5440)

• Improved performance of requests which query the lower boundary of horizon's history when running a horizon instance with the --history-retention-count flag. (5410, 5448, 5465)

• Improve performance of ingestion when running horizon with the --history-retention-count flag by executing reaping of history lookup tables concurrently with ingestion. (5405)

• Improve performance of ingestion when consuming ledgers via the BufferedStorageBackend. (5494)

Galexie v1.0.0

🎉 The First Release of Galexie (Ledger Exporter) 🎉

Galexie is a lightweight application designed to bundle, process, and store Stellar network data in an external data store. It offers the following features:

• 🔍 Data Extraction: Extracts raw ledger data from the Stellar network.
• 📦 Compression: Compresses raw data for efficient storage.
• 💾 Storage Options: Supports various storage solutions, starting with Google Cloud Storage (GCS).
• ⚙️ Modes of Operation: Can operate in either batch mode or streaming mode.

Want to run your own Galexie instance? 🚀 Check out the Admin Guide for setup instructions 📚. Grab the Docker image here 🐳 !