Overview
This is the v1.4.4 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
This release MUST NOT be upgraded onto your existing Network Gateway installation as it has an incompatible database schema. There’s no database migration available. What it means is that this release MUST be deployed with an empty (wiped out) database. This will result in a lengthy (approx. 4 - 16 hours depending on your infrastructure) process of resynchronization. During the resynchronization majority of the GW API endpoints will not be available.
Tip
In the upcoming weeks we’ll release the next release which will also require full ledger resynchronization.
What’s new?
API Changes
- Improved performance of
/stream/transactionsendpoint when using themanifest_class_filterfilter.
Database changes
- Replaced
IX_ledger_transaction_markers_manifest_class_is_most_specific_~index with two separate indexesIX_ledger_transaction_markers_manifest_class_is_most_specific(indexesis_most_specific= true only) andIX_ledger_transaction_markers_manifest_class(indexes all manifest classes).
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.4.4 on dockerhub, for the following images: