Horizon v1.11.1

• Fix bug in parsing db-url parameter in horizon db migrate and horizon db init commands (#3192).

Horizon v1.11.0

• The service field emitted in ingestion logs has been changed from expingest to ingest (#3118).
• Ledger stats are now exported in /metrics in horizon_ingest_ledger_stats_total metric (#3148).
• Stellar Core database URL is no longer required when running in captive mode (#3150).
• xdr: Add a custom marshaller for claim predicate timestamp (#3183).

Horizon 1.10.1

• Bump max supported protocol version to 15.

horizonclient v4.1.0 & txnbuild v4.1.0

• Add helper function ParseAssetString(), making it easier to build an Asset structure from a string in canonical form and check its various properties (#3105).

• Add helper function Transaction.ClaimableBalanceID(), making it easier to calculate balance IDs for claimable balances without actually submitting the transaction (#3122).

• Add support for SEP-10 v2.1.0.

  • Remove verification of home domain. (Will be reintroduced and changed in a future release.)
  • Allow additional manage data operations that have source account as the server key.

Horizon 1.10.0

After upgrading Horizon will rebuild its state. During this process (which can take several minutes) it will not ingest new ledgers.

• Fixed a bug that caused a fresh instance of Horizon to be unable to sync with testnet (Protocol 14) correctly. (#3100)
• Add Golang- and process-related metrics. (#3103)
• New network_passphrase field in History Archives (added in Stellar-Core 14.1.0) is now checked. Horizon will return error if incorrect archive is used. (#3082)
• Fixed a bug that caused some errors to be logged with info level instead of error level. (#3094)
• Fixed a bug in /claimable_balances that returned 500 error instead of 400 for some requests. (#3088)
• Print a friendly message when Horizon does not support the current Stellar protocol version. (#3093)

Horizon 1.9.1

• Fixed a bug that caused a fresh instance of Horizon to be unable to sync with testnet (Protocol 14) correctly. (#3096)
• Use underscore in JSON fields for claim predicate to make the API consistent. (#3086)

txnbuild v4.0.1

v4.0.1 - 2020-10-02

• Fixed bug in TransactionFromXDR() which occurs when parsing transaction XDR envelopes which contain Protocol 14 operations.

horizonclient v4.0.0 & txnbuild v4.0.0

Added support for the new operations in Protocol 14. Now it is possible to:

• Create and claim claimable balance operations (see CAP-23) with the {Create,Claim}ClaimableBalance structures and their associated helpers
• Begin/end sponsoring future reserves for other accounts (see CAP-33) with the {Begin,End}SponsoringFutureReserves operations
• Revoke sponsorships of various objects with the RevokeSponsorship operation (see CAP-33).

Added new client methods and effects supporting Protocol 14:

• New client methods
  • ClaimableBalances(req ClaimableBalanceRequest) - returns details about available claimable balances, possibly filtered to a specific sponsor or other parameters.
  • ClaimableBalance(balanceID string) - returns details about a specific, unique claimable balance.
• New effects:
  • ClaimableBalance{Created,Updated,Removed}
  • ClaimabeBalanceSponsorship{Created,Updated,Removed}
  • AccountSponsorship{Created,Updated,Removed}
  • TrustlineSponsorship{Created,Updated,Removed}
  • Data{Created,Updated,Removed}
  • DataSponsorship{Created,Updated,Removed}
  • SignerSponsorship{Created,Updated,Removed}

Also:

• Removed JSON variant of GET /metrics, both in the server and client code. It's using Prometheus format by default now.
• Added NextAccountsPage.
• Fixed Fund function that consistently errored.
• Added support for Go 1.15.

Breaking changes

• Dropped support for Go 1.13.
• Add support for SEP-10 v2.0.0.
  • Replace BuildChallengeTx's anchorName parameter with homeDomain.
  • Add homeDomain parameter to ReadChallengeTx, VerifyChallengeTxThreshold, and VerifyChallengeTxSigners.

Horizon 1.9.0

This is release adds support for the upcoming Protocol 14 upgrade. However, Horizon still maintains backwards compatibility with Protocol 13, which means it is still safe to run this release before Protocol 14 is deployed.

After upgrading Horizon will rebuild it's state. During this process (which can take several minutes) it will not ingest new ledgers.

The two main features of Protocol 14 are CAP 23 Claimable Balances and CAP 33 Sponsored Reserves. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them. Sponsored Reserves allows an account to pay the reserves on behalf of another account.

In this release there is a new claimable balance resource which has a unique id, an asset (describing which asset can be claimed), an amount (the amount of the asset that can be claimed), and a list of claimants (an immutable list of accounts that could potentially claim the balance).

The GET /claimable_balances/{id} endpoint was added to Horizon's API to allow looking up a claimable balance by its id. See the sample response below:

{
  "_links": {
    "self": {
      "href": "/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000"
    }
  },
  "id": "000000000102030000000000000000000000000000000000000000000000000000000000",
  "asset": "native",
  "amount": "10.0000000",
  "sponsor": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML",
  "last_modified_ledger": 123,
  "claimants": [
    {
      "destination": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML",
      "predicate": {
        "unconditional": true
      }
    }
  ],
  "paging_token": "123-000000000102030000000000000000000000000000000000000000000000000000000000"
}

There is also a GET /claimable_balances endpoint which searches for claimable balances by asset, sponsor, or claimant destination.

To support CAP 33 Sponsored Reserves we have added an optional sponsor attribute in the following Horizon resources: accounts, account signers, offers, trustlines, and claimable balances. If the sponsor field is present it means that the account with id sponsor is paying for the reserves for the sponsored account / account signer / offer / trustline / claimable balance. We have also added an optional sponsor query parameter to the following endpoints:

• GET /accounts
• GET /offers
• GET /claimable_balances

If the sponsor query param is provided, Horizon will search for objects sponsored by the given account id.

Horizon 1.9.0 Release Candidate

This is an experimental Horizon release which adds support for the upcoming Protocol 14 upgrade. The Horizon 1.9.0 release candidate will allow you to test Protocol 14 features on a standalone network before Protocol 14 is deployed to pubnet and testnet. Horizon still maintains backwards compatability with Protocol 13, which means it is still safe to run this release before Protocol 14 is deployed. However, the API changes introduced in this release are subject to change depending on the feedback we receive when Protocol 14 support is implemented in the Horizon SDKS.

The two main features of Protocol 14 are CAP 23 Claimable Balances and CAP 33 Sponsored Reserves. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them. Sponsored Reserves allows an account to pay the reserves on behalf of another account.

In this release there is a new claimable balance resource which has a unique id, an asset (describing which asset can be claimed), an amount (the amount of the asset that can be claimed), and a list of claimants (an immutable list of accounts that could potentially claim the balance).

The GET /claimable_balances/{id} endpoint was added to Horizon's API to allow looking up a claimable balance by its id. See the sample response below:

{
  "_links": {
    "self": {
      "href": "/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000"
    }
  },
  "id": "000000000102030000000000000000000000000000000000000000000000000000000000",
  "asset": "native",
  "amount": "10.0000000",
  "sponsor": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML",
  "last_modified_ledger": 123,
  "claimants": [
    {
      "destination": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML",
      "predicate": {
        "unconditional": true
      }
    }
  ],
  "paging_token": "123-000000000102030000000000000000000000000000000000000000000000000000000000"
}

There is also a GET /claimable_balances endpoint which searches for claimable balances by asset, sponsor, or claimant destination.

To support CAP 33 Sponsored Reserves we have added an optional sponsor attribute in the following Horizon resources: accounts, account signers, offers, trustlines, and claimable balances. If the sponsor field is present it means that the account with id sponsor is paying for the reserves for the sponsored account / account signer / offer / trustline / claimable balance. We have also added an optional sponsor query parameter to the following endpoints:

• GET /accounts
• GET /offers
• GET /claimable_balances

If the sponsor query param is provided, Horizon will search for objects sponsored by the given account id.