Overview
This is the v1.6.1
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.
Notes for Gateway runners
Caution
It is MANDATORY to upgrade to v1.6.1
Gateway before bottlenose protocol version is enacted on network.
Caution
Gateway v1.6.1
is intended to work with 1.2.1
node version. Please make sure to upgrade node before upgrading gateway.
Upgrade scenarios
Tip
If you are upgrading from Gateway running v1.5.1
or later version it is safe to deploy on top of existing database. There are compatible migrations that will upgrade database schema.
Caution
If you are upgrading from Gateway running v1.4.4
or older it is required to deploy on empty database. There's no database migration available.
What’s new?
- Added support to run Gateway after enacting bottlenose protocol update.
API Changes
- Added
well_known_addresses.locker_package
address property to the/status/network-configuration
endpoint response. - Added a new endpoint
/state/account-locker/page/vaults
which allows to read all resource vaults for a given AccountLocker. - Added a new endpoint
/state/account-lockers/touched-at
which allows to read last touch state version for a given collection of AccountLockers.
Database changes
- Added a new set of AccountLocker-related tables:
account_locker_entry_definition
,account_locker_entry_resource_vault_definition
andaccount_locker_entry_touch_history
. - Added two new columns
account_locker_of_account_entity_id
andaccount_locker_of_account_locker_entity_id
to theentities
table filled for AccountLocker-related Vaults and KeyValueStores. - Changed
IX_entity_vault_history_vault_entity_id_from_state_version
index to match all existing vaults rather non-fungible ones only.
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.6.1
on dockerhub, for the following images: