Releases: stellar/go
horizonclient & txnbuild v8.0.0-beta.0
This pre-release adds support for Protocol 18.
horizonclient
- The restriction that
Fund
can only be called on the DefaultTestNetClient has been removed. Anyhorizonclient.Client
may now call Fund. Horizon instances not supporting funding will error with a resource not found error. - Change
AccountRequest
to acceptSponsor
andLiquidityPool
filters - Change
EffectRequest
,TransactionRequest
, andOperationRequest
to accept aForLiquidityPool
filter - Change
TradeRequest
to accept both aForLiquidityPool
filter or aTradeType
filter - Add
LiquidityPoolsRequest
for getting details about liquidity pools, with an optionalReserves
field to filter by pools' reserve asset(s). - Add
LiquidityPoolRequest
for getting details about a specific liquidity pool via theLiquidityPoolID
filter.
txnbuild
New features
GenericTransaction
,Transaction
, andFeeBumpTransaction
now implement
encoding.TextMarshaler
andencoding.TextUnmarshaler
.- New asset structures that conform to the new ChangeTrust and New assets:
- Support for the core liquidity pool XDR types:
LiquidityPoolId
,LiquidityPoolParameters
,LiquidityPoolDeposit
, andLiquidityPoolWithdraw
. - Support for the new asset structures:
ChangeTrustAsset
andTrustLineAsset
.
Changes
- There's now a 5-minute grace period to
transaction.ReadChallengeTx
's minimum time bound constraint (#3824). - Assets can now be liquidity pool shares (
AssetTypePoolShare
). - All asset objects can now be converted to the new
ChangeTrustAsset
andTrustLineAsset
objects. - Assets can now be compared in accordance with the protocol, see their respective
LessThan()
implementations.
Breaking changes
ChangeTrust
requires aChangeTrustAsset
.RevokeSponsorship
requires aTrustLineAsset
when revoking trustlines.RemoveTrustlineOp
helper now requires aChangeTrustAsset
validate*Asset
helpers now require more-specific asset types.
Horizon v2.8.3
Upgrading to this version from <= v2.8.0 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
DB State Migration
- This release comes with a small DB migration. It should not take more than a couple minutes.
Scheduled Changes
In the 2.9.0 Horizon release, the --ingest
flag will be set to true
by default.
Changes
Horizon v2.8.2
Upgrading to this version from <= v2.8.0 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
In the 2.9.0 Horizon release, the --ingest
flag will be set to true
by default.
- Improve performance of
OffersProcessor
. This should speed up ingestion of latest Stellar Public Network activity by up to 30%. Please note that this change does not improve reingestion speed because ledger entries are not processed during reingestion. (3917)
Horizon v2.8.1
Upgrading to this version from <= v2.8.0 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
In the 2.9.0 Horizon release, the --ingest
flag will be set to true
by default.
- Fix bug in asset balance classification where clawback is enabled. (3847)
Horizon v2.8.0
Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
In the 2.9.0 Horizon release, the --ingest
flag will be set to true
by default.
Horizon v2.7.0
Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
In the upcoming 2.9.0 Horizon release, the --ingest
flag will be set to true
by default. Please update your deployment scripts before this.
- If
--captive-core-config-path
is not set, the config file is generated based on network passhprase. (3783) - Fix bug in horizon reap system (used by
horizon db reap
command and when horizon is configured with--history-retention-count
) which could lead to partial deletions. (3754) - Log debug messages from captive core at the appropriate log level. (3746)
- Add a feature flag
--captive-core-reuse-storage-path
/CAPTIVE_CORE_REUSE_STORAGE_PATH
that will reuse Captive Core's storage path for bucket files when applicable for better performance. (3750)
Horizon v2.6.1
Horizon v2.6.0
Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which will take at least 10 minutes), Horizon will not ingest new ledgers.
- Precompute trade aggregations during ingestion to improve performance. Will rebuild the aggregations as part of the database migrations. (3641 & 3760).
- Require
COUNT
param when runninghorizon db migrate down COUNT
to prevent accidentally running all downwards migrations. Addhorizon db migrate status
command. (#3737) - Fix a bug in
fee_account_muxed
andfee_account_muxed_id
fields (the fields were incorrectly populated with the source account details). (3735) - Validate ledger range when calling
horizon db reingest range
so that we respond with an error when attempting to ingest ledgers which are not available in the history archives. (3738) - Improve performance of transaction submission. (3563)
horizonclient v7.1.1 & txnbuild v7.1.1
horizonclient
- Added transaction and operation result codes to the horizonclient.Error string for easy glancing at string only errors for underlying cause.
- Fix bug in the transaction submission where requests with large transaction payloads fail with an HTTP 414 URI Too Long error (#3643).
- Fix a data race in
Client.fixHorizonURL
(#3690). - Fix bug which occurs when parsing operations involving muxed accounts (#3722).
txnbuild
Bug Fixes
Horizon v2.5.2
Upgrading to this version from <= v2.1.1 will trigger a state rebuild. During this process (which can take up to 20 minutes), Horizon will not ingest new ledgers.
- Fix a bug in the method unmarshaling payment operation details. (#3722)