radixdlt/babylon-gateway rcnet-v1-a8da752

RCnet-V1.0

on GitHub

Overview

This release brings the Gateway compatible with the first release candidate of the Radix Babylon Network.

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.

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.

Key changes

Overview of Gateway changes since Betanet-V2:

• /entity/overview and /entity/details endpoints replaced with single /state/entity/details.
• Fungible and non-fungible resources are now ordered by the most recently updated.
• /transaction/recent endpoint replaced with /stream/transactions returning user and non-user transactions.
• limit request parameter has been renamed to limit_per_page.
• All enum values use PascalCase naming.
• /gateway/information replaced with two separate endpoints /status/gateway-status and /status/network-configuration
• Added new configuration section CoreApiIntegration where you can configure integration with core API. For now only SubmitTransactionTimeout setting is supported.
• /stake/validator/list rework, added current stake value.
• /entity/resources merged into /state/entity/details endpoint
• new paginable endpoints /state/entity/page/{x} for metadata, fungibles, fungible-vaults, non-fungibles, non-fungible-vaults and non-fungible-vault/ids. Cursors returned from state/entity/details can be later used to query for next pages in specific endpoints.
• /transaction/committed-details endpoint operates on intent_hash_hex only now