Releases: stellar/go
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
andarchived_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 thestellar-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
andamount
fields from Asset stats related endpoints, andvalid_before
andvalid_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
andamount
columns have been dropped fromexp_asset_stats
table in Postgres.
-
Renamed
errorResultXdr
field toerror_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 theextras
field in the response of the async transaction submission endpointPOST /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 🐳 !
Horizon v2.32.0
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
anddatastore-config
on thereingest
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
Horizon v2.31.0
2.31.0
What's Changed
If you are using a custom captive-core config and setting Horizon CAPTIVE_CORE_USE_DB=false
, then need to make sure to set EXPERIMENTAL_BUCKETLIST_DB=false
in the captive core config toml to be compatible with stellar-core versions 21 and earlier
Breaking Changes
- Change ingestion filtering logic to store transactions if any filter matches on it. (5303)
- The previous behaviour was to store a tx only if both asset and account filters match together. So even if a tx matched an account filter but failed to match an asset filter, it would not be stored by Horizon.
- Captive-core configuration parameters updated to align with stellar-core v21 (5333)
- BucketlistDB is now the default database for stellar-core, deprecating the usage of
EXPERIMENTAL_BUCKETLIST_DB
in captive core configuration toml. - A new mandatory parameter
DEPRECATED_SQL_LEDGER_STATE
(default: false) is required by stellar-core on its captive core configuration toml file. if the toml provided byCAPTIVE_CORE_CONFIG_PATH
does not have this new setting, Horizon will add it automatically, therefore, no action required. - If using
EXPERIMENTAL_BUCKETLIST_DB_INDEX_PAGE_SIZE_EXPONENT
orEXPERIMENTAL_BUCKETLIST_DB_INDEX_CUTOFF
in captive core configuration toml, they must be renamed toBUCKETLIST_DB_INDEX_PAGE_SIZE_EXPONENT
andBUCKETLIST_DB_INDEX_CUTOFF
respectively.
- BucketlistDB is now the default database for stellar-core, deprecating the usage of
Added
- Bump XDR definitions (5289), (5330)
- Add new async transaction submission endpoint (5188)
- Add
horizon_ingest_errors_total
metric key (5302) - Add transaction hash to txsub timeout response (5328)
- Add new captive-core flags for V1 Meta (5309)
- Add version check for protocol 21 (5346)
- Improve horizon history reaper (5331). New reaper configuration flags
REAP_FREQUENCY
- the frequency in units of ledgers for how often history is reaped.
Fixed
- Fix the following ingestion error:
error preparing range: error starting prepare range: the previous Stellar-Core instance is still running
(5307)
horizonclient & txnbuild v14.0.0
This release includes support for Protocol 21
horizonclient
- services/horizon: return null txmeta in api model when SKIP_TXMETA enabled (#5228)
- clients/horizonclient: allow sending user-defined headers on requests (#5214)
- clients/stellarcore horizon: Obtain and expose diagnostic events in transaction endpoint (#5148)
- Bump go version to 1.22 (#5232)
txnbuild
- Bump XDR for soroban-pubnet release (#5079)
Full Changelog: horizonclient-v13.0.0...horizonclient-v14.0.0
Horizon v2.30.0
What's Changed
This is the first release that supports Protocol 21.
Added
- Bump XDR for protocol 21
- Make reaping batch sizes configurable via --history-retention-reap-count (#5272)
- Log tx meta when ingestion failures occur (#5268)
- Add deprecation warning for --captive-core-use-db (#5231)
Fixed
- Optimized reingestion by addressing performance slowdown due to unnecessary operations on history_transactions_filtered_tmp. Removed obsolete EnableIngestionFiltering flag. (#5283)
- Fix deadlock in parallel ingestion (#5263)
- Add missing tables to TruncateIngestStateTables() (#5253)
- Performance improvements in ingest library
- Reduce memory consumption of CheckpointChangeReader during state verification and state rebuild (#5270)
- Remove unnecessary use of ChangeCompactor to reduce memory bloat during ingestion (#5252)
Full Changelog: horizon-v2.29.0...horizon-v2.30.0
Horizon v2.29.0
Changelog
Added
- New
db_error_total
metrics key with labelsctx_error
,db_error
, anddb_error_extra
(5225). - Bumped go version to the latest (1.22.1) (5232)
- Add metrics for ingestion loaders (5209).
- Add metrics for http api requests in flight and requests received (5240).
- Add
MAX_CONCURRENT_REQUESTS
, defaults to 1000, limits the number of horizon api requests in flight (5244)
Fixed
- History archive access is more effective when you pass list of URLs to Horizon: they will now be accessed in a round-robin fashion, use alternative archives on errors, and intelligently back off (5224)
- Remove captive core info request error logs (5145)
- Removed duplicate "Processed Ledger" log statement during resume state (5152)
- Fixed incorrect duration for ingestion processor metric (5216)
- Fixed sql performance on account transactions query (5229)
- Fix bug in claimable balance change processor (5246)
- Delay canceling queries from client side when there's a statement / transaction timeout configured in postgres (5223)
Breaking Changes
- The Horizon API Transaction resource field in json
result_meta_xdr
is now optional and Horizon API will not emit the field when Horizon has been configured withSKIP_TXMETA=true
, effectively null, otherwise if Horizon is configured withSKIP_TXMETA=false
which is default, then the API Transaction fieldresult_meta_xdr
will remain present and populated with base64 encoded xdr (5228).
Horizon v2.28.3
Changelog
Fixed
- Fix claimable_balance_claimants subquery in GetClaimableBalances() 5207
Added
- New optional config
SKIP_TXMETA
(5189). Defaults toFALSE
, whenTRUE
the following will occur:- history_transactions.tx_meta column will have serialized xdr that equates to empty for any protocol version, such as for
xdr.TransactionMeta.V3
,Operations
,TxChangesAfter
,TxChangesBefore
will be empty arrays andSorobanMeta
will be nil.
- history_transactions.tx_meta column will have serialized xdr that equates to empty for any protocol version, such as for
Breaking Changes
- Removed
DISABLE_SOROBAN_INGEST
configuration parameter, use the newSKIP_TXMETA
parameter instead.
horizon-v2.28.2
What's Changed
Fixed
- History archive caching would cause file corruption in certain environments 5197
- Server error in claimable balance API when claimant, asset and cursor query params are supplied 5200
Full Changelog: horizon-v2.28.1...horizon-v2.28.2