Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Horizon 1.5.0 support #287

Closed
abuiles opened this issue Jul 1, 2020 · 0 comments · Fixed by #549
Closed

Horizon 1.5.0 support #287

abuiles opened this issue Jul 1, 2020 · 0 comments · Fixed by #549

Comments

@abuiles
Copy link
Contributor

abuiles commented Jul 1, 2020

Horizon 1.5.0 added a new field to the ledgers resource called tx_set_operation_count, if your SDK has support for /ledgers or ledger resources, then it should include this new field. The value can be a number or null.

This value represents the total number of operations in the transactions set. You can use it to find out if recent ledgers have been full (and therefore subject to surge pricing) or not.

Are you curious about other changes in Horizon?

My two picks are:

  1. The removal of --ingest-failed-transactions flag, which means from now on Horizon will always ingest failed transactions. If you run your own Horizon, this might have an impact on your database.
  2. A new experimental mode of doing database reingestion which uses a Stellar Core subprocess instead of a persistent Stellar Core database. Please give this a try and let us know if you find any issue!

You can see the full changelog in the release notes https://github.com/stellar/go/releases/tag/horizon-v1.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant