Stellar's public monorepo of go code
Full Changelog: https://github.com/stellar/go/compare/horizonclient-v13.0.0...horizonclient-v14.0.0
Full Changelog: https://github.com/stellar/go/compare/horizon-v2.29.0...horizon-v2.30.0
db_error_total
metrics key with labels ctx_error
, db_error
, and db_error_extra
(5225).MAX_CONCURRENT_REQUESTS
, defaults to 1000, limits the number of horizon api requests in flight (5244)result_meta_xdr
is now optional and Horizon API will not emit the field when Horizon has been configured with SKIP_TXMETA=true
, effectively null, otherwise if Horizon is configured with SKIP_TXMETA=false
which is default, then the API Transaction field result_meta_xdr
will remain present and populated with base64 encoded xdr (5228).SKIP_TXMETA
(5189). Defaults to FALSE
, when TRUE
the following will occur:
xdr.TransactionMeta.V3
, Operations
, TxChangesAfter
, TxChangesBefore
will be empty arrays and SorobanMeta
will be nil.DISABLE_SOROBAN_INGEST
configuration parameter, use the new SKIP_TXMETA
parameter instead.Full Changelog: https://github.com/stellar/go/compare/horizon-v2.28.1...horizon-v2.28.2
tx_bad_seq
(5191)db reingest range
with parallel workers (5168)DISABLE_SOROBAN_INGEST
(5175). Defaults to FALSE
, when TRUE
and a soroban transaction is ingested, the following will occur:
xdr.TransactionMeta.V3
, Operations
, TxChangesAfter
, TxChangesBefore
will empty arrays and SorobanMeta
will be nil.result_meta_xdr
will have same empty serialized xdr for xdr.TransactionMeta.V3
, Operations
, TxChangesAfter
, TxChangesBefore
will empty arrays and SorobanMeta
will be nil.Operation
model for InvokeHostFunctionOp
type, will have empty asset_balance_changes
removed configuration flags --stellar-core-url-db
, --cursor-name
--skip-cursor-update
, they are no longer usable.
removed automatic updating of core cursor from ingestion background processing.
Note for upgrading on existing horizon deployments - Since horizon will no longer maintain advancement of this cursor on core, it may require manual removal of the cursor from the core process that your horizon was using for captive core, otherwise that core process may un-necessarily retain older data in buckets on disk up to the last cursor ledger sequence set by prior horizon release.
The captive core process to check and verify presence of cursor usage is determined by the horizon deployment, if NETWORK
is present, or STELLAR_CORE_URL
is present or CAPTIVE-CORE-HTTP-PORT
is present and set to non-zero value, or CAPTIVE-CORE_CONFIG_PATH
is used and the toml has HTTP_PORT
set to non-zero and PUBLIC_HTTP_PORT
is not set to false, then it is recommended to perform the following preventative measure on the machine hosting horizon after upgraded to 2.28.0 and process restarted:
$ curl http://<captive_core_process_url:captive_core_process_port>/getcursor
# If there are no cursors reported, done, no need for any action
# If any horizon cursors exist they need to be dropped by id.
# By default horizon sets cursor id to "HORIZON" but if it was customized
# using the --cursor-name flag the id might be different
$ curl http://<captive_core_process_url:captive_core_process_port>/dropcursor?id=<reported_id_from_getcursor>
Support for new XDR schemas.
Three new operations related to Soroban and state expiration (see Interacting with Soroban via Stellar and State Expiration):
/effects
can produce two new effects:
contract_credited
occurs when a Stellar asset moves into its corresponding Stellar Asset Contract instancecontract_debited
occurs when a Stellar asset moves out of its corresponding Stellar Asset Contract instance/assets/:name
contains two new fields:
num_contracts
- the integer quantity of contracts that hold this assetcontracts_amount
- the total units of that asset held by contracts/operations
has three new response schemas corresponding to the Soroban operations (described above)The following release notes are a combination of the release candidates (see RC1 and RC2 for deltas) and changes since then.
Upgrading to this version from <= 2.26.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
--remote-captive-core-url
has been removed, as remote captive core functionality is now deprecated (4940).stellar-xdr
@ bb54e50, 5079).--network
to specify the Stellar network (pubnet or testnet), aiming at simplifying the configuration process by automatically configuring the following parameters based on the chosen network: --history-archive-urls
, --network-passphrase
, and --captive-core-config-path
(4949).contract_credited
and contract_debited
effects which are emitted whenever a Soroban contracts sends or receives a Stellar asset (4832).num_contracts
(total number of Soroban contracts which hold an asset) and contracts_amount
(total amount of the asset held by all Soroban contracts) fields to asset stat summaries at /assets
(4805).invoke_host_function
, extend_footprint_ttl
, and restore_footprint
(4905).ScVal.String()
method to the xdr
package (5112).v2.26.1
hotfix now properly excludes spikes for smoother trade aggregation plots (4999).ingest.GetChangesFromLedgerEntryChanges
are now sorted in a deterministic order (5070).Refer to prior Horizon-v2.27.0-rc1 release for information on bulk of changes present in 2.27.0, this is maintenance patch applied on top of Horizon-v2.27.0-rc1
for bug fix.