Releases: stellar/go
horizonclient v5.0.1 & txnbuild v5.0.1
Horizon v2.0.0 Release Candidate
This is a release candidate: while SDF is confident that there are no critical bugs and release candidate is safe to use in production we encourage organizations to deploy it to production only after org-specific testing.
Before you upgrade
Please read the Captive Core doc which contains new requirements and migration guide.
Captive Stellar-Core
Introducing the release candidate with Captive Stellar-Core mode enabled by default. Captive mode relaxes Horizon's operational requirements. It allows running Horizon without a fully fledged Core instance and, most importantly, without a Core database. More information about this new mode can be found in Captive Core doc.
If you run into issues please check Known Issues or report an issue. Please ask questions in Keybase or Stack Exchange.
Breaking changes
- The
expingest
command has been renamed toingest
since the ingestion system is not experimental anymore. - Removed
--rate-limit-redis-key
and--redis-url
configuration flags.
stellar-ingest v1.0.0
The ingest
package provides primitives for reading ledger data from Stellar Core and the history archives. Horizon uses the package to ingest every new ledger emitted by the Stellar network into the Horizon database.
For more details on how to use the ingest
package, check out this tutorial.
Horizon v1.14.0
- Fix bug
/fee_stats
endpoint. The endpoint was not including the additional base fee charge for fee bump transactions (#3354) - Expose the timestamp of the most recently ingested ledger in the root resource response and in the
/metrics
response (#3281) - Add
--checkpoint-frequency
flag to configure how many ledgers span a history archive checkpoint (#3273). This is useful in the context of creating standalone Stellar networks in integration tests.
Horizon v1.13.1
Upgrading to this version from version before v1.10.0 will trigger state rebuild. During this process (which can take several minutes) it will not ingest new ledgers.
- Fixed a bug in
/fee_stats
endpoint that could calculate invalid stats if fee bump transactions were included in the ledger (#3326).
Horizon v2.0.0 Beta
THIS IS A BETA RELEASE! DO NOT USE IN PRODUCTION. The release may contain critical bugs. It's not suitable for production use.
Before you upgrade
Please read the Captive Core doc which contains new requirements and migration guide.
Captive Stellar-Core
Introducing the beta release with Captive Stellar-Core mode enabled by default. Captive mode relaxes Horizon's operational requirements. It allows running Horizon without a fully fledged Core instance and, most importantly, without a Core database. More information about this new mode can be found in Captive Core doc.
This version may contain bugs. If you run into issues please check Known Issues or report an issue. Please ask questions in Keybase or Stack Exchange.
Horizon v1.13.0
Upgrading to this version from version before v1.10.0 will trigger state rebuild. During this process (which can take several minutes) Horizon will not ingest new ledgers.
Horizon v1.12.0
horizonclient v5.0.0 & txnbuild v5.0.0
Breaking changes
- Updates the SEP-10 helper function parameters and return values to support SEP-10 v3.0
- The following functions replaced the
homeDomain
parameter withhomeDomains
(note: plural):ReadChallengeTx()
VerifyChallengeTxThreshold()
VerifyChallengeTxSigners()
ReadChallengeTx()
now returns a third non-error value:matchedHomeDomain
- The following functions replaced the
horizonclient v4.2.0 & txnbuild v4.2.0
- Add
HashHex()
,SignWithKeyString()
,SignHashX()
, andAddSignatureBase64()
functions back toFeeBumpTransaction
(#3199).