Overview
This is the `v1.10.6`` release for the Gateway. API docs are on Redocly here: https://docs.radixdlt.com/docs/network-apis
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 a Gateway running v1.9.2 or older, you must deploy on an empty database. There are no database migrations available to migrate the database schema and data.
Warning
If you are upgrading from a Gateway running v1.10.0 or newer.
There are some cosmetic changes to manifest classifications. To ensure consistent classification across all transactions, deploy on an empty database. If minor inconsistencies are acceptable, (for details check What's new section below) you can safely deploy on top of an existing database
What’s new?
- Updated Radix Engine Toolkit to
2.3.5to resolve issue in2.3.4with static analysis of certain transactions. - As a result of Radix Engine Toolkit update, manifest classification has changed. The General class now has more relaxed rules, so more transactions will be classified as general.
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.10.6 on dockerhub, for the following images: