Releases: stellar/go
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
andcontract_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) andcontracts_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
, andrestore_footprint
(4905).
Fixed
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 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)
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 inprotocols/horizon.Account
was changed toint64
. - Muxed accounts and ID memos can be used in the
BuildChallengeTx()
andReadChallengeTx()
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 theclientAccoutID
id a muxed account address.
- Muxed account addresses can be passed as the
ReadChallengeTx()
:- Muxed account addresses may be returned as the
clientAccountID
. - Adds an additional return value of type
*txnbuild.MemoID
.
- Muxed account addresses may be returned as the
What's Changed in horizonclient
-
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
What's Changed in txnbuild
-
use *MemoID instead of Memo for param and return type
@JakeUrban -
add memo to BuildChallengeTx params and ReadChallengeTx return value
@JakeUrban -
all: Add a set of generics and incorporate them into the codebase
@Shaptic -
protocols/horizon: Change Account.Sequence to int64 (#4438)
@bartekn
Full Changelog: horizonclient-v10.0.0...horizonclient-v11.0.0
Horizon v2.24.1
2.24.1
Changes
- Bump Go to the latest version (1.20.1), including crypto/tls, mime/multipart, net/http, and path/filepath security fixes.
Horizon v2.24.0
2.24.0
Changes
-
Add support for the experimental BucketListDB to Horizon, the parameters have been added to the Captive Core configuration / TOML files (4733):
- BucketListDB is enabled by default when
--captive-core-use-db
is set and yourstellar-core
version >= 19.6 - If
--captive-core-use-db
set but yourstellar-core
version < 19.6, an on-disk SQLite database is used (as before). - This update will not automatically trigger a state rebuild unless
EXPERIMENTAL_BUCKETLIST_DB
is set to false in the Captive Core TOML file.
- BucketListDB is enabled by default when
Fixes
- Improve error when setting
BUCKET_DIR_PATH
and using Captive Core (4736).
Horizon v2.23.1
Changes
- Bump Go to the latest version, including net/http security fixes.