Skip to content

Releases: stellar/go

horizonclient & txnbuild v8.0.0-beta.0

04 Oct 21:35
a1db2a6
Compare
Choose a tag to compare
Pre-release

This pre-release adds support for Protocol 18.

horizonclient

  • The restriction that Fund can only be called on the DefaultTestNetClient has been removed. Any horizonclient.Client may now call Fund. Horizon instances not supporting funding will error with a resource not found error.
  • Change AccountRequest to accept Sponsor and LiquidityPool filters
  • Change EffectRequest, TransactionRequest, and OperationRequest to accept a ForLiquidityPool filter
  • Change TradeRequest to accept both a ForLiquidityPool filter or a TradeType filter
  • Add LiquidityPoolsRequest for getting details about liquidity pools, with an optional Reserves field to filter by pools' reserve asset(s).
  • Add LiquidityPoolRequest for getting details about a specific liquidity pool via the LiquidityPoolID filter.

txnbuild

New features

  • GenericTransaction, Transaction, and FeeBumpTransaction now implement
    encoding.TextMarshaler and encoding.TextUnmarshaler.
  • New asset structures that conform to the new ChangeTrust and New assets:
  • Support for the core liquidity pool XDR types: LiquidityPoolId, LiquidityPoolParameters, LiquidityPoolDeposit, and LiquidityPoolWithdraw.
  • Support for the new asset structures: ChangeTrustAsset and TrustLineAsset.

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 and TrustLineAsset objects.
  • Assets can now be compared in accordance with the protocol, see their respective LessThan() implementations.

Breaking changes

  • ChangeTrust requires a ChangeTrustAsset.
  • RevokeSponsorship requires a TrustLineAsset when revoking trustlines.
  • RemoveTrustlineOp helper now requires a ChangeTrustAsset
  • validate*Asset helpers now require more-specific asset types.

Horizon v2.8.3

22 Sep 12:25
e6f322c
Compare
Choose a tag to compare

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

  • Fix ingestion of fee bump transactions which have muxed source accounts (3948).
  • Add an index on trade aggregations, to improve ingestion performance (3947).

Horizon v2.8.2

15 Sep 18:59
633f388
Compare
Choose a tag to compare

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

26 Aug 17:41
2a5c9ac
Compare
Choose a tag to compare

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

23 Aug 17:41
57979d4
Compare
Choose a tag to compare

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.

  • Limit reap to 100k ledgers/second, to prevent excess CPU usage (3823).
  • Improve performance of path finding endpoints (3818).

Horizon v2.7.0

02 Aug 18:05
4228fac
Compare
Choose a tag to compare

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

12 Jul 16:14
71350e6
Compare
Choose a tag to compare

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.

  • Fix bug introduced in v2.6.0 (#3737), preventing usage of horizon db migrate up/down/redo commands. (#3762)

Horizon v2.6.0

12 Jul 13:03
8107a7c
Compare
Choose a tag to compare

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 running horizon db migrate down COUNT to prevent accidentally running all downwards migrations. Add horizon db migrate status command. (#3737)
  • Fix a bug in fee_account_muxed and fee_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

25 Jun 19:58
2601c84
Compare
Choose a tag to compare

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

  • Claimable balance IDs are now precomputed correctly (Transaction.ClaimableBalanceID(int)) even when the transaction's source account is a fully-muxed account (#3678).
  • Fix muxed account address parsing for account merge operation (#3722).

Horizon v2.5.2

25 Jun 13:13
739936f
Compare
Choose a tag to compare

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)