Infrastructure and APIs

Babylon Nodes

A Babylon Radix Network is formed of Babylon Nodes, connected into a Network.

Nodes run as a Java service, wrapping a natively-compiled core, written in Rust. This core includes the Babylon Radix Engine, which runs transactions, and state ledger storage, in Rocks DB.

The node’s APIs are:

• Core API - exposes transaction and state information from the node.
• System API - exposes information about system health and connections.
• Prometheus API - exposes metrics from the node in prometheus format.

Latest documentation on the Babylon APIs is accessed from our docs site here.

For most exchanges, the LTS sub-section Core API of a node should be sufficient, and offers:

• Transaction Submission
• Transaction Status
• Streaming of committed transaction outcomes, including fungible balance changes
• Streaming of committed transaction outcomes, filtered to an individual account
• Reading of current account balance for 1 or all resources.

Exchanges will need to run their own Babylon full node/s. Documentation on running a Babylon node may be found here.

Network Gateway

Wallets and Dashboards will use the Gateway API, which offers more complex APIs, which allow for more indexing and lookup of historic ledger state.

Running a Gateway is more expensive, and likely not required for most exchanges at Babylon.

If you wish to run a Gateway API, the stack will be similar to Olympia (a PostgreSQL database with docker images for a Data Aggregator and Gateway API).