horizonclient-v13.0.0 & txnbuild

This is the stable release of Horizon Client with protocol 20 (Soroban support).

Key changes to support protocol 20 (Soroban)

New XDR Schema:

• Support for new XDR schemas.

• Three new operations related to Soroban and state expiration (see Interacting with Soroban via Stellar and State Expiration):

  • invokeHostFunctionOp: Invoke contract actions.
  • bumpExpirationFootprintOp: Bump expiration ledger of specified keys.
  • restoreFootprintOp: Restore expiration of specified ledger keys.

Horizon API Changes:

• /effects can produce two new effects:
  • contract_credited occurs when a Stellar asset moves into its corresponding Stellar Asset Contract instance
  • contract_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 asset
  • contracts_amount - the total units of that asset held by contracts
• /operations has three new response schemas corresponding to the Soroban operations (described above)

Horizon v2.27.0

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.

This stable release adds support for Protocol 20.

Changelog

Breaking Changes

• The command line flag --remote-captive-core-url has been removed, as remote captive core functionality is now deprecated (4940).
• XDR has been updated to the latest stable version for Protocol 20 (stellar-xdr @ bb54e50, 5079).

Added

• Added new command-line flag --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).
• Added contract_credited and contract_debited effects which are emitted whenever a Soroban contracts sends or receives a Stellar asset (4832).
• Added 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).
• Added responses for new operations introduced in Protocol 20: invoke_host_function, extend_footprint_ttl, and restore_footprint (4905).
• Added a ScVal.String() method to the xdr package (5112).

Fixed

• The same slippage calculation from the v2.26.1 hotfix now properly excludes spikes for smoother trade aggregation plots (4999).
• The ledger changes collected by ingest.GetChangesFromLedgerEntryChanges are now sorted in a deterministic order (5070).
• Eviction of Soroban ledger entries is accommodated by the asset stats endpoint (5033).
• Database migration performance has improved (5056).

Horizon v2.27.0 RC2

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.

Fixed

• treat null is_payment values as equivalent to false values, avoid sql nil conversion errors(5060).

Horizon v2.27.0 Release Candidate

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.

This release adds support for Protocol 20

Breaking Changes

• The command line flag --remote-captive-core-url has been removed, as remote captive core functionality is now deprecated (4940).

Added

• Added new command-line flag --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).
• Added contract_credited and contract_debited effects which are emitted whenever a Soroban contracts sends or receives a Stellar asset (4832).

• Added 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).
• Added responses for new operations introduced in protocol 20: invoke_host_function, bump_footprint_expiration, and restore_footprint (4905).

Fixed

• The same slippage calculation from the v2.26.1 hotfix now properly excludes spikes for smoother trade aggregation plots (4999).

horizonclient-v12.0.0 & txnbuild

First version of Horizon Client with protocol 20:Soroban support.

What's Changed

New XDR Schema:

• Support for new XDR schemas.

• Three new operations related to Soroban and state expiration (see Interacting with Soroban via Stellar and State Expiration):

  • invokeHostFunctionOp: Invoke contract actions.
  • bumpExpirationFootprintOp: Bump expiration ledger of specified keys.
  • restoreFootprintOp: Restore expiration of specified ledger keys.

Horizon API Changes:

• /effects can produce two new effects:
  • contract_credited occurs when a Stellar asset moves into its corresponding Stellar Asset Contract instance
  • contract_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 asset
  • contracts_amount - the total units of that asset held by contracts
• /operations has three new response schemas corresponding to the Soroban operations (described above)

horizon-v2.26.2-pre-soroban

The latest horizon master branch before soroban features were merged in

Horizon v2.26.1

Fixes

• This hotfix allows ledger ingestion to continue in case of a liquidity pool slippage miscalculation. Its only side effect is that /trades and /trade_aggregations may contain incorrect slippage (9a7522e).

Horizon v2.26.0

Changes

• Improve error handling for when stellar-core crashes (4893)
• Suppress Core timeout error in log output such as error ticking app: context deadline exceeded when ingestion state machine is in build state. (4860)

Breaking Changes

• Modify the default value of --captive-core-use-db to true (4856)
  • This updates the default behavior of captive core to start in on-disk mode.
  • To continue using the previous in-memory mode, explicitly set the --captive-core-use-db flag to false

Horizon v2.25.0

2.25.0

Changes

• Running Horizon with remote captive core is now deprecated (4826).
• Add two new configuration variables to control the behavior of state verification (4821):
  • --ingest-state-verification-frequency which specifies the frequency in checkpoints for how often state verification is run
  • --ingest-state-verification-timeout which specifies a timeout on how long state verification can run

Fixes

• Fix crash in horizon ingestion when running horizon with a remote captive core (4824).

horizonclient & txnbuild v11.0.0

v11.0.0 - 2023-03-29

Breaking Changes

• Minimum Golang version changed to 1.18
• Type of AccountSequence field in protocols/horizon.Account was changed to int64.
• Muxed accounts and ID memos can be used in the BuildChallengeTx() and ReadChallengeTx() SEP-10 utilitiy functions to identify users of shared Stellar accounts. (#4746)
  • BuildChallengeTx():
    • Muxed account addresses can be passed as the clientAccountID.
    • Adds an additional parameter of type *txnbuild.MemoID. Memos cannot be specified if the clientAccoutID id a muxed account address.
  • ReadChallengeTx():
    • Muxed account addresses may be returned as the clientAccountID.
    • Adds an additional return value of type *txnbuild.MemoID.

What's Changed in horizonclient

• fix misspelled comments
  @tsachiherman

• clients/horizonclient: fix theoretical bug in currentServerTime
  @tsachiherman

• protocols/horizon: Change Transaction.AccountSequence to int64
  @bartekn

• services/horizon, clients/horizonclient: Allow filtering ingested transactions by account or asset
  @sreuland
  @2opremio
  @bartekn
  @Shaptic

• doc: rename license file
  @leighmcculloch

What's Changed in txnbuild

• add tests for uncovered conditions
  @JakeUrban

• adjust test
  @JakeUrban

• update CHANGELOG.md
  @JakeUrban

• use *MemoID instead of Memo for param and return type
  @JakeUrban

• Update txnbuild/transaction.go
  @JakeUrban
  @leighmcculloch

• add to txnbuild CHANGELOG.md
  @JakeUrban

• add to function documentation
  @JakeUrban

• add more tests
  @JakeUrban

• added first test
  @JakeUrban

• minor adjustments for go check
  @JakeUrban

• fix tests, update webauth server
  @JakeUrban

• require memos of type ID in BuildChallengeTx
  @JakeUrban

• add memo to BuildChallengeTx params and ReadChallengeTx return value
  @JakeUrban

• Fix several typos. (#4592)
  @tsachiherman

• all: Add a set of generics and incorporate them into the codebase
  @Shaptic

• all: Bumps minimum Golang version to 1.18 (#4499)
  @Shaptic

• protocols/horizon: Change Account.Sequence to int64 (#4438)
  @bartekn

• doc: rename license file (#4350)
  @leighmcculloch

Full Changelog: horizonclient-v10.0.0...horizonclient-v11.0.0