Integrator Concepts

High Level Overview Radix Engine addresses are Bech32m encoded, where they are made up of a Human Readable Part (HRP), separator, and a base32m encoded data part which includes a 6 character checksum of the HRP and data. The human readable...

There are three main Radix environments. Each environment has a different network ID and each has a recognizable address format. Mainnet Mainnet is the official Radix Public Network. It's Production. It has real assets, and its history goes b...

Babylon Nodes The 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...

The Babylon Radix Network uses HotStuff BFT - with a decentralized validator set. This process has deterministic finality: commits are final and there are no probabilistic forks in the ledger. Unlike most blockchains, the transaction stream is no...

The Babylon Radix network supports ECDSA Secp256k1 and Ed25519 for accounts and transaction signing. The Babylon Radix network uses Blake2b-256 as its primary hashing mechanism - but integrators should not need to use Blake2b themselves for ...

Ledger data is stored in small versioned chunks called substates. Substates contain programmatic information which is encoded in a custom encoding called “ SBOR ” (Scrypto binary object representation). This can be converted to/from JSON with the ...

This section describes the state model in some detail. This detail may not be necessary for all use cases. The Babylon state model consists of a forest of state trees. At the top of each tree is a global entity - such as an account, resource...

The “Radix” token is called “XRD” and is the native token of the Radix ledger. It behaves like any other resource on the network. It is a fungible resource and there are 1018 “attos” in 1 XRD. In other words, it has the default/maximum divisibili...

Construction process For most users, the transaction construction process will be handled in their mobile Radix Wallet. Integrators wishing to construct transactions programmatically will need to integrate the Radix Engine Toolkit (RET) into the...

The faucet is available on test networks to get XRD. There are a number of ways to use the faucet: In the mobile wallet, after you’ve created an account, you can click the … menu and request test XRD. The LTS Toolkit has a function for buildin...

Details are below: Node release: https://github.com/radixdlt/babylon-node/releases/ Docs: https://docs.radixdlt.com/ Typescript Radix Engine Toolkit version: https://www.npmjs.com/package/@radixdlt/radix-engine-toolkit?activeTab=version...

There will be occasional network upgrades, called “Protocol Updates” (sometimes called “forks” on other chains) which will require upgrading your Babylon node software. If you stick to using the LTS supported endpoints for your integrations, these...

Not so relevant to exchange integrations - but for completeness, it’s useful to briefly explain how users will interact with the Radix ecosystem. Users will use a mobile wallet. The mobile wallet is designed to feel intuitive for both a mainstre...