Skip to content

Releases: stellar/go

Horizon v22.0.2

13 Dec 16:49
425a97f
Compare
Choose a tag to compare

Fixed

  • Fix liquidity pool bug which resulted in invalid paths being included in the /paths/strict-receive response (5541).

Horizon v22.0.1

13 Nov 19:58
f09f3e4
Compare
Choose a tag to compare

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

07 Nov 13:28
d757d60
Compare
Choose a tag to compare
  • Add support for Protocol 22

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

Horizon v22.0.0

07 Nov 11:00
749abd7
Compare
Choose a tag to compare

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

31 Oct 17:53
9653cac
Compare
Choose a tag to compare
Galexie v22.0.0-rc1 Pre-release
Pre-release
  • Add support for Protocol 22

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

horizonclient & txnbuild v15.0.0

31 Oct 15:44
364ca19
Compare
Choose a tag to compare

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

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

Horizon v22.0.0-rc2

25 Oct 10:32
364ca19
Compare
Choose a tag to compare

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

15 Oct 19:33
783bb05
Compare
Choose a tag to compare

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

31 Jul 16:34
4f5ad3e
Compare
Choose a tag to compare

🎉 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 🐳 !

Horizon v2.32.0

31 Jul 17:38
8b1dba4
Compare
Choose a tag to compare

Added

  • Reingest from pre-computed tx meta on remote cloud storage. (4911), (5374)
    • Configure horizon reingestion to obtain ledger tx meta in pre-computed files from a Google Cloud Storage(GCS) location.
    • Using this option will no longer require a captive core binary be present and it no longer runs a captive core sub-process, instead obtaining the tx meta from the GCS backend.
    • Horizon supports this new feature with two new parameters ledgerbackend and datastore-config on the reingest command. Refer to Reingestion README.
  • Add metrics for reaping of history lookup tables (5385).
  • Add --reap-lookup-tables (defaults to true) which will disable reaping of history lookup tables when set to false. (5366).

Fixed

  • Fix ingestion duration metric so it includes time spent reaping history lookup tables (5361).
  • Optimize query for reaping history lookup tables (5393).