radixdlt/babylon-gateway v1.1.0

1.1.0

on GitHub

Not recommended for public running

This release has an issue where resource summaries are not returned for uninstantiated pre-allocated accounts, so we do not recommend running this version. We will be releasing a new version next week with the v1.1.0 features and a few other fixes.

Overview

This is the v1.1.0 release for the Gateway. API docs are on Redocly here: https://radix-babylon-gateway-api.redoc.ly/

License

The Babylon Gateway code is released under the Radix License. Binaries/Executable components are licensed under the Radix Software EULA.

Note to Integrators

Please note that the Babylon Core API on the Node is more powerful than on Olympia.

Integrators looking to prepare for the Radix Babylon launch should start by considering if running their own node and using the Core API would work instead of running a Gateway and using the Gateway API.

Please see the guide for integrators here.

Running just a node is simpler than running a node and Gateway, and the Core API has a "long term support" section of the API, designed for tracking fungible balances and accounts, which is guaranteed to be compatible with mainnet launch - enabling integrators to prepare for mainnet launch immediately.

Docker Images

This release is available as tag v1.1.0 on dockerhub, for the following images:

• radixdlt/babylon-ng-database-migrations
• radixdlt/babylon-ng-aggregator
• radixdlt/babylon-ng-gateway-api

v1.0.0 to v1.1.0 Migration Guide

What’s new?

• Fixed invalid HTTP status code on input validation failure.
• Changed default configuration value of MaxPageSize for endpoints to 100. Validate if max page size is higher than DefaultPageSize.
• Added new opt-in balance_changes to /transaction/committed-details returning resource balance changes for a given transaction.
• Added new opt-in receipt_output to /stream/transactions, and /transaction/committed-details endpoints. Temporarily set by default to true, to allow client's migration.
• Added vault-related details to lookups in /state/entity/details endpoint.
• Optimized TransactionQuerier.GetTransactions not to fetch unnecessary data from underlying database.
• Added strongly-typed OAS definition for programmatic_json.
• Tuned documentation and constraints of various OAS type definitions.