Bifrost v0.0.2

New features:

• Configuring account has been moved to backend by adding a temporary signer on user's account. This makes the whole process much faster, easier to maintain and less error prone.
• Time-locking account during a token sale.
• Allows using Distribution account (ex. when Issuing account has been locked).
• Automatically imports database schema when server is started (or asks to recreate DB if schema is out of date).

stellar-hd-wallet-v0.0.2

• Fix trimming of newlines on windows

Horizon v0.12.3

Bug fixes

• Fix a service stutter caused by excessive info commands being issued from the root endpoint.

Horizon v0.12.2

This release is a bug fix release for v0.12.1 and v0.12.0. Please see the upgrade notes below if you did not already migrate your db for v0.12.0

Changes

• Remove strict validation on the resolution parameter for trade aggregations endpoint. We will add this feature back in to the next major release.

v0.12.1 - 2017-03-13

This release is a bug fix release for v0.12.0.

Bug fixes

• Fixed an issue caused by un-migrated trade rows. (#357)
• Command line flags are now useable for subcommands of horizon.

v0.12.0 - 2017-03-08

Big release this time for horizon: We've made a number of breaking changes since v0.11.0 and have revised both our database schema as well as our data ingestion system. We recommend that you take a backup of your horizon database prior to upgrading, just in case.

Upgrade Notes

Since this release changes both the schema and the data ingestion system, we recommend the following upgrade path to minimize downtime:

1. Upgrade horizon binaries, but do not restart the service
2. Run horizon db migrate up to migrate the db schema
3. Run horizon db reingest in a background session to begin the data reingestion process
4. Restart horizon

Added

• Operation and payment resources were changed to add transaction_hash and created_at properties.
• The ledger resource was changed to add a header_xdr property. Existing horizon installations should re-ingest all ledgers to populate the history database tables with the data. In future versions of horizon we will disallow null values in this column. Going forward, this change reduces the coupling of horizon to stellar-core, ensuring that horizon can re-import history even when the data is no longer stored within stellar-core's database.
• All Assets endpoint (/assets) that returns a list of all the assets in the system along with some stats per asset. The filters allow you to narrow down to any specific asset of interest.
• Trade Aggregations endpoint (/trade_aggregations) allow for efficient gathering of historical trade data. This is done by dividing a given time range into segments and aggregate statistics, for a given asset pair (base, counter) over each of these segments.

Bug fixes

• Ingestion performance and stability has been improved.
• Changes to an account's inflation destination no longer produce erroneous "signer_updated" effects. (stellar-deprecated/horizon#390)

Changed

• BREAKING CHANGE: The base_fee property of the ledger resource has been renamed to base_fee_in_stroops
• BREAKING CHANGE: The base_reserve property of the ledger resource has been renamed to base_reserve_in_stroops and is now expressed in stroops (rather than lumens) and as a JSON number.
• BREAKING CHANGE: The "Orderbook Trades" (/orderbook/trades) endpoint has been removed and replaced by the "All Trades" (/trades) endpoint.
• BREAKING CHANGE: The Trade resource has been modified to generalize assets as (base, counter) pairs, rather than the previous (sold,bought) pairs.
• Full reingestion (i.e. running horizon db reingest) now runs in reverse chronological order.

Removed

• BREAKING CHANGE: Friendbot has been extracted to an external microservice.

Horizon v0.12.1

This release is a bug fix release for v0.12.0. Please see the upgrade notes below if you did not already migrate your db for v0.12.0

Bug fixes

• Fixed an issue caused by un-migrated trade rows. (#357)
• Command line flags are now useable for subcommands of horizon.

NOTE: We've include the v0.12.0 release notes below for easy reference

---

v0.12.0 Release notes

Big release this time for horizon: We've made a number of breaking changes since v0.11.0 and have revised both our database schema as well as our data ingestion system. We recommend that you take a backup of your horizon database prior to upgrading, just in case.

Upgrade Notes

Since this release changes both the schema and the data ingestion system, we recommend the following upgrade path to minimize downtime:

1. Upgrade horizon binaries, but do not restart the service
2. Run horizon db migrate up to migrate the db schema
3. Run horizon db reingest in a background session to begin the data reingestion process
4. Restart horizon

Added

• Operation and payment resources were changed to add transaction_hash and created_at properties.
• The ledger resource was changed to add a header_xdr property. Existing horizon installations should re-ingest all ledgers to populate the history database tables with the data. In future versions of horizon we will disallow null values in this column. Going forward, this change reduces the coupling of horizon to stellar-core, ensuring that horizon can re-import history even when the data is no longer stored within stellar-core's database.
• All Assets endpoint (/assets) that returns a list of all the assets in the system along with some stats per asset. The filters allow you to narrow down to any specific asset of interest.
• Trade Aggregations endpoint (/trade_aggregations) allow for efficient gathering of historical trade data. This is done by dividing a given time range into segments and aggregate statistics, for a given asset pair (base, counter) over each of these segments.

Bug fixes

• Ingestion performance and stability has been improved.
• Changes to an account's inflation destination no longer produce erroneous "signer_updated" effects. (stellar-deprecated/horizon#390)

Changed

• BREAKING CHANGE: The base_fee property of the ledger resource has been renamed to base_fee_in_stroops
• BREAKING CHANGE: The base_reserve property of the ledger resource has been renamed to base_reserve_in_stroops and is now expressed in stroops (rather than lumens) and as a JSON number.
• BREAKING CHANGE: The "Orderbook Trades" (/orderbook/trades) endpoint has been removed and replaced by the "All Trades" (/trades) endpoint.
• BREAKING CHANGE: The Trade resource has been modified to generalize assets as (base, counter) pairs, rather than the previous (sold,bought) pairs.
• Full reingestion (i.e. running horizon db reingest) now runs in reverse chronological order.

Removed

• BREAKING CHANGE: Friendbot has been extracted to an external microservice.

Horizon v0.12.0

Big release this time for horizon: We've made a number of breaking changes since v0.11.0 and have revised both our database schema as well as our data ingestion system. We recommend that you take a backup of your horizon database prior to upgrading, just in case.

Upgrade Notes

Since this release changes both the schema and the data ingestion system, we recommend the following upgrade path to minimize downtime:

1. Upgrade horizon binaries, but do not restart the service
2. Run horizon db migrate up to migrate the db schema
3. Run horizon db reingest in a background session to begin the data reingestion process
4. Restart horizon

Added

• Operation and payment resources were changed to add transaction_hash and created_at properties.
• The ledger resource was changed to add a header_xdr property. Existing horizon installations should re-ingest all ledgers to populate the history database tables with the data. In future versions of horizon we will disallow null values in this column. Going forward, this change reduces the coupling of horizon to stellar-core, ensuring that horizon can re-import history even when the data is no longer stored within stellar-core's database.
• All Assets endpoint (/assets) that returns a list of all the assets in the system along with some stats per asset. The filters allow you to narrow down to any specific asset of interest.
• Trade Aggregations endpoint (/trade_aggregations) allow for efficient gathering of historical trade data. This is done by dividing a given time range into segments and aggregate statistics, for a given asset pair (base, counter) over each of these segments.

Bug fixes

• Ingestion performance and stability has been improved.
• Changes to an account's inflation destination no longer produce erroneous "signer_updated" effects. (stellar-deprecated/horizon#390)

Changed

• BREAKING CHANGE: The base_fee property of the ledger resource has been renamed to base_fee_in_stroops
• BREAKING CHANGE: The base_reserve property of the ledger resource has been renamed to base_reserve_in_stroops and is now expressed in stroops (rather than lumens) and as a JSON number.
• BREAKING CHANGE: The "Orderbook Trades" (/orderbook/trades) endpoint has been removed and replaced by the "All Trades" (/trades) endpoint.
• BREAKING CHANGE: The Trade resource has been modified to generalize assets as (base, counter) pairs, rather than the previous (sold,bought) pairs.
• Full reingestion (i.e. running horizon db reingest) now runs in reverse chronological order.

Removed

• BREAKING CHANGE: Friendbot has been extracted to an external microservice.

Horizon v0.12.0 Testing

Merge pull request #315 from stellar/fix-effects-query

Fix slow effects page query

stellar-hd-wallet v0.0.1

Initial release of stellar-hd-wallet.

Bifrost v0.0.1

Initial Bifrost release.

Federation v0.2.1

• Config fields:
  • database.url changed to database.dns,
  • queries.reverse-federation is now optional,
  • fixed validating tls section in config file.
• Added HTTP requests/response logging.