Overview
This is the v1.8.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
You must deploy on an empty database. There are no database migrations available to update the schema and data. It is not possible to migrate data, as the bug we are fixing in this release is related to missing entries in the database.
Bug fixes
- Fix processing multiple changes to single non fungible id data (
NonFungibleResourceManagerDataEntrySubstate) in one batch. It might result in- Wrong data stored and returned from the
/state/non-fungible/dataendpoint. - Not tracking properly that non fungible id got deleted, which might lead to returning an invalid location of non fungible id. Affected endpoints are
/state/non-fungible/location- And all endpoints that return non fungible vault content
/state/entity/details/state/entity/page/non-fungibles//state/entity/page/non-fungible-vaults//state/entity/page/non-fungible-vault/ids
- Wrong data stored and returned from the
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.8.2 on dockerhub, for the following images: