Overview
This is the v1.7.2 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.
Upgrade scenarios
Caution
If you are upgrading from Gateway running v1.6.3 or older it is required to deploy on empty database. There are no database migration available to migrate database schema and data.
Tip
If you are upgrading from Gateway running v1.7.0 or v1.7.1 it is safe to deploy on top of existing database. There are compatible migrations that will upgrade database schema and data.
Node requirement
Warning
It is required to run v1.2.3 node or newer for the new feature to work. If you are connected to a node running v1.2.2 or older, the new radix_engine_toolkit_receipt feature will be ignored.
API Changes
- Added
opt_insproperty to/transaction/previewrequest. Currently, there is only one option to useradix_engine_toolkit_receipt, it controls whether the preview response will include a Radix Engine Toolkit serializable
receipt or not (defaults tofalse).
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.7.2 on dockerhub, for the following images: