Bridge v0.0.32

0.0.32

• Bridge server now uses the new Go SDK.
• Unit tests added.

Breaking changes

• MySQL is no longer supported. To migrate your data to postgresql use any of the tools provided here.

• Requests to /builder for AllowTrust operations must specify the source account for the operation.

Changes

• Payload MAC authentication uses X-Payload-Mac header (old X_PAYLOAD_MAC header is still provided for backward compatibility, but it is deprecated and will be removed in future versions).

Compliance v0.0.32 rc1

Release Candidate. Do not use in production.

0.0.32

• Compliance server now uses the new Go SDK.
• Unit tests added.

Breaking changes

• MySQL is no longer supported. To migrate your data to postgresql use any of the tools provided here.

Bridge v0.0.32 rc1

Release Candidate. Do not use in production.

0.0.32

• Bridge server now uses the new Go SDK.
• Unit tests added.

Breaking changes

• MySQL is no longer supported. To migrate your data to postgresql use any of the tools provided here.

• Requests to /builder for AllowTrust operations must specify the source account for the operation.

Changes

• Payload MAC authentication uses X-Payload-Mac header (old X_PAYLOAD_MAC header is still provided for backward compatibility, but it is deprecated and will be removed in future versions).

Ticker v1.0.0

This is the first release of the ticker, a new API server that provides statistics about assets and markets on the Stellar network.

For more information, check out the README and the API docs.

Horizon v0.18.0

Breaking changes

• Horizon requires Postgres 9.5+.
• Removed paging_token field from /accounts/{id} endpoint.
• Removed /operation_fee_stats endpoint. Please use /fee_stats.

Deprecations

• fee_paid field on Transaction resource has been deprecated and will be removed in 0.19.0. Two new fields have been added: max_fee that defines the maximum fee the source account is willing to pay and fee_charged that defines the fee that was actually paid for a transaction. See CAP-0005 for more information.
• The following operation type names have been deprecated: manage_offer and create_passive_offer. The names will be changed to: manage_sell_offer and create_passive_sell_offer in 0.19.0.

Changes

• The following new config parameters were added. When old max-db-connections config parameter is set, it has a priority over the the new params. Run horizon help for more information.
  • horizon-db-max-open-connections,
  • horizon-db-max-idle-connections,
  • core-db-max-open-connections,
  • core-db-max-idle-connections.
• Fixed fee_paid value in Transaction resource (#1358).
• Fix "int64: value out of range" errors in trade aggregations (#1319).
• Improved horizon db reingest range command.

Horizon v0.18.0 rc2

Release Candidate. Do not use in production.

Breaking changes

• Horizon requires Postgres 9.5+.
• Removed paging_token field from /accounts/{id} endpoint.
• Removed /operation_fee_stats endpoint. Please use /fee_stats.

Deprecations

• fee_paid field on Transaction resource has been deprecated and will be removed in 0.19.0. Two new fields have been added: max_fee that defines the maximum fee the source account is willing to pay and fee_charged that defines the fee that was actually paid for a transaction. See CAP-0005 for more information.
• The following operation type names have been deprecated: manage_offer and create_passive_offer. The names will be changed to: manage_sell_offer and create_passive_offer in 0.19.0.

Changes

• The following new config parameters were added. When old max-db-connections config parameter is set, it has a priority over the the new params. Run horizon help for more information.
  • horizon-db-max-open-connections,
  • horizon-db-max-idle-connections,
  • core-db-max-open-connections,
  • core-db-max-idle-connections.
• Fixed fee_paid value in Transaction resource (#1358).
• Fix "int64: value out of range" errors in trade aggregations (#1319).
• Improved horizon db reingest range command.

Horizon v0.18.0 rc1

Release Candidate. Do not use in production.

Breaking changes

• Horizon requires Postgres 9.5+.
• Removed paging_token field from /accounts/{id} endpoint.
• Removed /operation_fee_stats endpoint. Please use /fee_stats.

Changes

• The following new config parameters were added. When old max-db-connections config parameter is set, it has a priority over the the new params. Run horizon help for more information.
  • horizon-db-max-open-connections,
  • horizon-db-max-idle-connections,
  • core-db-max-open-connections,
  • core-db-max-idle-connections.
• Improved horizon db reingest range command.
• Fix "int64: value out of range" errors in trade aggregations (#1319).

horizonclient v1.2.0 & txnbuild v1.2.0

horizonclient

• Added support for returning the previous and next set of pages for a horizon response; issue #985.
• Fixed bug reported in #1254 that causes a panic when using horizonclient in goroutines.

txnbuild

• In addition to account responses from horizon, transactions and operations can now be built with txnbuild.SimpleAccount structs constructed locally (#1266).
• Added MaxTrustlineLimit which represents the maximum value for a trustline limit (#1265).
• ChangeTrust operation with no Limit field set now defaults to MaxTrustlineLimit (#1265).
• Add support for building ManageBuyOffer operation (#1165).
• Fix bug in ChangeTrust operation builder (1296).

Snapshots 2019-05-10-20:51:24

snapshots

Generated snapshots from TravisCI for build 4085 on 2019-05-10-20:51:18

horizonclient v1.1.0 & txnbuild v1.1.0

horizonclient

• new Client.Root() method for querying the root endpoint of a horizon server
• client now returns concrete effect types (#1217)
• set testnet default when no HTTP client is provided

txnbuild

• support for multiple signatures in transactions
• individual operations now have their own optional source account