Babylon (v1.0.0)

This build is the mainnet-ready node build for the Babylon mainnet launch.

For those setting up a mainnet node, this v1.0.0 version is a required update from rcnet-v3.1-r5 for a successful Babylon switchover.

License

The Babylon node code is released under the Radix License. Executable components are licensed under the Radix Node EULA.

Mainnet set-up documentation

Please see the babylon migration documentation for instructions on setting up the Olympia and Babylon nodes in preparation for Babylon mainnet.

If you've already set up rcnet-v3.1-r5 node, then you will need to:

• Stop your node running, swap the binaries, restart your node
• Run the version verification check below, and then check the logs are still correctly reporting "Successfully connected to the Olympia node..."

To swap the binaries, depending on your setup:

• EITHER update with the cli
• OR update your docker container version to v1.0.0
• OR update both jar and native library with the artifacts attached below)

Then restart your node, and verify that your node is running v1.0.0 by using the System API. Go inside your host / docker container, and run the following command (replacing 3334 with the System API port you have assigned to your babylon node, if you have provided an override from the default value). You should check this returns { "version": "v1.0.0" }:

curl http://localhost:3334/system/version

Finally, check that you are still getting logs saying: "Successfully connected to the Olympia node..." and your Babylon side is ready.

On the Olympia side:

• If you're a validator, please don't forget to signal readiness if you haven't already
• Double-check you are on version 1.5.0 of your Olympia node. If you are still on an older version or downgraded, now is the time to get back on 1.5.0

Stokenet set-up documentation

As of Friday 22nd September, our main public test network, Stokenet, has had its ledger wiped, and has been restarted on a fresh slate for Babylon, running the v1.0.0 node. Stokenet now replaces Zabanet as our recommend public testnet to run nodes on and use as builders/developers.

Wiping the ledger has has allowed us to add a Babylon faucet, remove useless ledger bloat, and start the validator set from scratch, allowing for healthier consensus without lots of stake assigned to offline nodes. Stokenet is now running the same version of the network which will go live later this week for the mainnet switchover.

If you wish to set up a testnet node on our Stokenet environment, then please see the documentation site for details on setting up a node.

Your stokenet node should not be set up in migration node. If you have previously run a stokenet node, you will need to:

• Wipe your ledger
• Remove your migration-specific configuration
• Update your binaries
• Update your seednodes as follows

The configuration to use is as follows. Note that stokenet genesis is hardcoded into the node, so doesn't need to be provided:

network.id=2
network.p2p.seed_nodes=radix://node_tdx_2_1qv89yg0la2jt429vqp8sxtpg95hj637gards67gpgqy2vuvwe4s5ss0va2y@13.126.248.88,radix://node_tdx_2_1qvtd9ffdhxyg7meqggr2ezsdfgjre5aqs6jwk5amdhjg86xhurgn5c79t9t@13.210.209.103,radix://node_tdx_2_1qwfh2nn0zx8cut5fqfz6n7pau2f7vdyl89mypldnn4fwlhaeg2tvunp8s8h@54.229.126.97,radix://node_tdx_2_1qwz237kqdpct5l3yjhmna66uxja2ymrf3x6hh528ng3gtvnwndtn5rsrad4@3.210.187.161

If setting up a validator, the docs are here, and you can then request a large stake on Discord.

RCnet v3.1 - Revision 5

Set-up instructions

Please see:

• The babylon migration documentation for instructions on running this node in preparation for Babylon mainnet. Note that a replacement final node version will be available next Friday, 22nd September. This will be a required update for a successful Babylon switchover.
• The RCnet v3.1 r4 release notes for instructions on running this node as a zabanet node.

For those running on Zabanet

Not a required update (unless you're running a Core API and with to update to newest Gateway when it launches).

Adds a resolution of GenericSubstitution::Remote in the stream transactions endpoint for use by the Gateway.

RCnet v3.1 - Revision 4

Overview

This is the fourth release candidate of the Radix Babylon mainnet.

The network which will run our public RCnet v3.1 network will be zabanet(it will replace RCnet v3 running on Zabanet with a ledger wipe, when we publish later this week). As such you may see zabanet in some docs - particularly where we want to differentiate between this network, and other networks running an RCnet v3.1 build (such as migrated stokenet).

IMPORTANT: If you were running a node for RCnet v2 or RCnet v3, please delete your ledger during your update to the v3.1 node.

Node Runners

• Links to all the API docs are here
• Basic docs on node running are here.

Running with the Node Runner CLI

Our recommended approach. See the docs here and the relevant release can be obtained from here: https://github.com/radixdlt/babylon-nodecli/releases/tag/2.0.rcnet-v3-rc5

Please let us know in #node-runners in Discord if you encounter problems.

Running via docker

• Image rcnet-v3.1-r4 is available from docker hub
• An example docker compose file is available here
• Supported environment variable configuration is here - as well as normal configuration, you will need to set up environment variables for RCnet v3.1 / Zabanet as follows:

RADIXDLT_NETWORK_ID: 14
RADIXDLT_NETWORK_SEEDS_REMOTE: radix://node_tdx_e_1q0gm3fwqh8ggl09g7l8ru96krzlxdyrc694mqw8cf227v62vjyrmccv8md5@13.126.65.118,radix://node_tdx_e_1q0juzf2gnhfhy2aj6x88x4f459tf2a2mdk56jm3ffhzp94fn8k0q5lkse34@52.64.209.45,radix://node_tdx_e_1qdzlwtjn9wcmcyt3mp3g4qaerr6fgrl86ze6t20427tf4rmnu670y0cgszc@54.72.0.65,radix://node_tdx_e_1qfz9r8xp95vuzjq503l856ywukrdnukcz4232tr4nsx7ff2efvfnwvaq080@35.168.132.18
RADIXDLT_GENESIS_DATA: /wYAAHNOYVBwWQDRAgBo6NIQvgoUXCEGCgEACQEABQkHKAAAIQoJZAAAAAr0DRoICrgLCRsMCuCTBAUKFTQkoOyCkOtRDo+1mgUYGQEgoAAAZKeztuANGRMJARU7FQkgoAAAEGMtXsdrFYENAeAgIgMEASAhAQKA0fJ+apHv10KbZw/zq1+awjGS4SYu/i7pxk+BCLnNoAAAAGCKph7+xG3S1QgAAAAVArABICEEBiAHIQPRuKXAudCPvKj3zj4XVhi+ZpB40WuwOPhKleZpTJEHvAEBAQFiswDwkCAhAgIMBG5hbWUiAAEME0RlZmF1bHQgdmFsaWRhdG9yIDECDAN1cmwiDQEMGGh0dHBzOi8vd3d3LnJhZGl4ZGx0LmNvbYDRk4ZR64ZKF0UXY8UqyV6ghwcOhTBATZMlYRUFrK8GIAchA+XBJUid03IrstGOc1U1oVaVdVttqaluKU3EEtUzPZ4KAQEBAaAAAGRSWQGCpgAEMgKOpgBw6qD7P5CmKE5Vw2wD57719pXjLq07Mg+HaguVWgMlTHxF9y5TK7G8EXHYYoqDuRj0lA/n0LOlqfVXlpqPc+a88vZMAQAzkqYAcKvDUcvEhfpU9zJiX0WLTYhldkUKzZWgKxkIj7BjAaaAAkRRnMEtGcFIFHx+emiO5YbZ8tgVVRUsdZwN5KVZSxM39qYAADSSpgCQ4Bhb5cGHtROfCGYqZsBNXyin+4PMPOq2HReDCj0BAiCAAdHyfmrZAgwgIQQCjr4CECAhAQIJQfUwoAAAAOg8gNCfPC47AwEREQEFRxDlwSVInWpfAppHAH4AApZHAIKhAYZHAAHuJEDq7XRG0JwsnwwR60wAAAAgDAYMdHJhbnNmZXJfeHJkCGGJkHN3YXAIbWV0YWRhdGERZnVuZ2libGVfcmVzb3VyY2UVbm9uX2Y+FgB0HWFjY291bnRfYXV0aG9yaXplZF9kZXBvc2l0b3Jz

Running natively

The main change to Olympia is that the node now has its core written in Rust, but still uses java as the system orchestrator.

To run the node, you will need both:

• The attached JAR (in babylon-node-rcnet-v3.1-r4.zip)
• The native library, compiled for your node's system architecture. This will have a name like libcorerust.so / corerust.dll / libcorerust.dylib depending on the platform.
  • We prebuild this for many platforms - see the attached zip files. EG the contents of babylon-node-rust-arch-linux-x86_64-release-rcnet-v3.1-r4.zip can be used for x86_64 linux deployments. Note they need to use a version of libc at least as recent as Ubuntu 22.04.2.0 LTS (Jammy Jellyfish).
  • If you need another architecture, you will need to compile it yourself on the desired target - see section below.

You will then need to run the JAR, but make the native library available for java to connect via JNI. This can be done in one of multiple ways:

• On Linux:
  • Put the native library in /usr/lib/jni or /usr/lib - be sure it's named libcorerust.so
  • Start the jar with an environment variable LD_PRELOAD=/path/to/native_library.so.
• General:
  • Put the library at one of the java.library.paths (on Ubuntu: e.g. /usr/lib/jni, on OSX: e.g. ~/Library/Java/Extensions/)
  • Run the jar with -Djava.library.path=<path_to_library_directory> and put the library there. EG on windows, the library will need to be called corerust.dll.

Configuration to use with your RCnet v3 / zabanet node is as follows. This can be specified in a file called "default.config" alongside the home directory of the node, or put in another file and referenced via a --config=path/to/config-file command line parameter.

network.id=14
network.p2p.seed_nodes=radix://node_tdx_e_1q0gm3fwqh8ggl09g7l8ru96krzlxdyrc694mqw8cf227v62vjyrmccv8md5@13.126.65.118,radix://node_tdx_e_1q0juzf2gnhfhy2aj6x88x4f459tf2a2mdk56jm3ffhzp94fn8k0q5lkse34@52.64.209.45,radix://node_tdx_e_1qdzlwtjn9wcmcyt3mp3g4qaerr6fgrl86ze6t20427tf4rmnu670y0cgszc@54.72.0.65,radix://node_tdx_e_1qfz9r8xp95vuzjq503l856ywukrdnukcz4232tr4nsx7ff2efvfnwvaq080@35.168.132.18
network.genesis_data=/wYAAHNOYVBwWQDRAgBo6NIQvgoUXCEGCgEACQEABQkHKAAAIQoJZAAAAAr0DRoICrgLCRsMCuCTBAUKFTQkoOyCkOtRDo+1mgUYGQEgoAAAZKeztuANGRMJARU7FQkgoAAAEGMtXsdrFYENAeAgIgMEASAhAQKA0fJ+apHv10KbZw/zq1+awjGS4SYu/i7pxk+BCLnNoAAAAGCKph7+xG3S1QgAAAAVArABICEEBiAHIQPRuKXAudCPvKj3zj4XVhi+ZpB40WuwOPhKleZpTJEHvAEBAQFiswDwkCAhAgIMBG5hbWUiAAEME0RlZmF1bHQgdmFsaWRhdG9yIDECDAN1cmwiDQEMGGh0dHBzOi8vd3d3LnJhZGl4ZGx0LmNvbYDRk4ZR64ZKF0UXY8UqyV6ghwcOhTBATZMlYRUFrK8GIAchA+XBJUid03IrstGOc1U1oVaVdVttqaluKU3EEtUzPZ4KAQEBAaAAAGRSWQGCpgAEMgKOpgBw6qD7P5CmKE5Vw2wD57719pXjLq07Mg+HaguVWgMlTHxF9y5TK7G8EXHYYoqDuRj0lA/n0LOlqfVXlpqPc+a88vZMAQAzkqYAcKvDUcvEhfpU9zJiX0WLTYhldkUKzZWgKxkIj7BjAaaAAkRRnMEtGcFIFHx+emiO5YbZ8tgVVRUsdZwN5KVZSxM39qYAADSSpgCQ4Bhb5cGHtROfCGYqZsBNXyin+4PMPOq2HReDCj0BAiCAAdHyfmrZAgwgIQQCjr4CECAhAQIJQfUwoAAAAOg8gNCfPC47AwEREQEFRxDlwSVInWpfAppHAH4AApZHAIKhAYZHAAHuJEDq7XRG0JwsnwwR60wAAAAgDAYMdHJhbnNmZXJfeHJkCGGJkHN3YXAIbWV0YWRhdGERZnVuZ2libGVfcmVzb3VyY2UVbm9uX2Y+FgB0HWFjY291bnRfYXV0aG9yaXplZF9kZXBvc2l0b3Jz

Compiling the native library for your architecture

If you need an architecture other than those offered in the attached zip files, you will need to compile it yourself on the desired target.

Pre-requisites

• clang
• git
• openjdk-17-jdk-headless
• rustup (e.g. curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh) - note: the prepackaged rust-1.62-all on Ubuntu is insufficient

Build steps

On your node:

1. Clone the repository git clone https://github.com/radixdlt/babylon-node.git, change directory to babylon-node, and checkout the branch release/rcnet-v3.1
2. Run ./gradlew installDist in babylon-node
3. Run cargo build --release in babylon-node/core-rust
4. Copy the created rust library found in babylon-node/core-rust/target/release/libcorerust.so (libcorerust.dylib on OSX, corerust.dll on Windows) to one of the java.library.paths (on Ubuntu: e.g. /usr/lib/jni, on OSX: e.g. ~/Library/Java/Extensions/)

You can then start your node as normal, eg with env RADIX_NODE_KEYSTORE_PASSWORD=[validator.ks passphrase] ./core/build/install/core/bin/core

Note: ./core/build/install/ directory can be safely moved to a directory under /opt, e.g. /opt/radixdlt.

Service files for Debian

A .deb for the node containing a useful base .service can be created as follows:

1. Clone the repository and cd babylon-node
2. Run ./gradlew deb4Docker
3. Install the package that was created with dpkg -i
4. Fine-tune the installed service file - e.g. by adding the RADIX_NODE_KEYSTORE_PASSWORD environment variable.

APIs/Monitoring:

APIs now live here:

• Core (bound to localhost:3333) - Core API docs here
• System (bound to localhost:3334) - System API docs here
• Prometheus (bound to localhost:3335) - they have been rehashed a lot to be a lot more consistent and powerful, although we don't have a great guide for these just yet.

Validator Registration:

Details are available here: https://docs-babylon.radixdlt.com/main/node-and-gateway/register-as-validator.html

RCnet v3.1 - Revision 3

NOTE: Please use https://github.com/radixdlt/babylon-node/releases/tag/rcnet-v3.1-r4

---

Another small consensus-related bug fix on top of rncet-v3.1-r2. A straightforward swap-in update for rcnet-v3.1-r2.

When this release finishes building, it is recommended to be run by validators on babylon-stokenet.

RCnet v3.1 - Revision 2

NOTE: Please use https://github.com/radixdlt/babylon-node/releases/tag/rcnet-v3.1-r4

---

A small consensus-related bug fix on top of rncet-v3.1-r1. A straightforward swap-in update for rcnet-v3.1-r1.

When this release finishes building, it is recommended to be run by validators as part of the Stokenet switchover.

RCnet v3.1 - Revision 1

NOTE: Please now use/see https://github.com/radixdlt/babylon-node/releases/tag/rcnet-v3.1-r4

RCnet v3 - Revision 4

Overview

This is the third release candidate of the Radix Babylon mainnet.

The network which runs our public RCnet v3 network has a logical name of zabanet- which you will see in some places - particularly where we want to differentiate between this network, and other networks running an RCnet v3 build (such as migrated stokenet).

IMPORTANT: If you were running a node for RCnet v2, please delete your ledger during your update to the phase 3 node.

Node Runners

• Links to all the API docs are here
• Basic docs on node running are here.

Running with the Node Runner CLI

Our recommended approach. See the docs here and the relevant release can be obtained from here: COMING SOON

Please let us know in #node-runners in Discord if you encounter problems.

Running via docker

• Image rcnet-v3-r4 is available from docker hub
• An example docker compose file is available here
• Supported environment variable configuration is here - as well as normal configuration, you will need to set up environment variables for RCnet v3 / Zabanet as follows:

RADIXDLT_NETWORK_ID: 14
RADIXDLT_NETWORK_SEEDS_REMOTE: radix://node_tdx_e_1q0gm3fwqh8ggl09g7l8ru96krzlxdyrc694mqw8cf227v62vjyrmccv8md5@13.126.65.118,radix://node_tdx_e_1q0juzf2gnhfhy2aj6x88x4f459tf2a2mdk56jm3ffhzp94fn8k0q5lkse34@52.64.209.45,radix://node_tdx_e_1qdzlwtjn9wcmcyt3mp3g4qaerr6fgrl86ze6t20427tf4rmnu670y0cgszc@54.72.0.65,radix://node_tdx_e_1qfz9r8xp95vuzjq503l856ywukrdnukcz4232tr4nsx7ff2efvfnwvaq080@35.168.132.18
RADIXDLT_GENESIS_DATA: /wYAAHNOYVBwWQDRAgBo6NIQvgoUXCEGCgEACQEABQkHKAAAIQoJZAAAAAr0DRoICrgLCRsMCuCTBAUKFTQkoOyCkOtRDo+1mgUYGQEgoAAAZKeztuANGRMJARU7FQkgoAAAEGMtXsdrFYENAeAgIgMEASAhAQKA0fJ+apHv10KbZw/zq1+awjGS4SYu/i7pxk+BCLnNoAAAAGCKph7+xG3S1QgAAAAVArABICEEBiAHIQPRuKXAudCPvKj3zj4XVhi+ZpB40WuwOPhKleZpTJEHvAEBAQFiswDwkCAhAgIMBG5hbWUiAAEME0RlZmF1bHQgdmFsaWRhdG9yIDECDAN1cmwiDQEMGGh0dHBzOi8vd3d3LnJhZGl4ZGx0LmNvbYDRk4ZR64ZKF0UXY8UqyV6ghwcOhTBATZMlYRUFrK8GIAchA+XBJUid03IrstGOc1U1oVaVdVttqaluKU3EEtUzPZ4KAQEBAaAAAGRSWQGCpgAEMgKOpgBw6qD7P5CmKE5Vw2wD57719pXjLq07Mg+HaguVWgMlTHxF9y5TK7G8EXHYYoqDuRj0lA/n0LOlqfVXlpqPc+a88vZMAQAzkqYAcKvDUcvEhfpU9zJiX0WLTYhldkUKzZWgKxkIj7BjAaaAAkRRnMEtGcFIFHx+emiO5YbZ8tgVVRUsdZwN5KVZSxM39qYAADSSpgCQ4Bhb5cGHtROfCGYqZsBNXyin+4PMPOq2HReDCj0BAiCAAdHyfmrZAgwgIQQCjr4CECAhAQIJQfUwoAAAAOg8gNCfPC47AwEREQEFRxDlwSVInWpfAppHAH4AApZHAIKhAYZHAAHuJEDq7XRG0JwsnwwR60wAAAAgDAYMdHJhbnNmZXJfeHJkCGGJkHN3YXAIbWV0YWRhdGERZnVuZ2libGVfcmVzb3VyY2UVbm9uX2Y+FgB0HWFjY291bnRfYXV0aG9yaXplZF9kZXBvc2l0b3Jz

Running natively

The main change to Olympia is that the node now has its core written in Rust, but still uses java as the system orchestrator.

To run the node, you will need both:

• The attached JAR (in babylon-node-rcnet-v3-r4.zip)
• The native library, compiled for your node's system architecture. This will have a name like libcorerust.so / corerust.dll / libcorerust.dylib depending on the platform.
  • We prebuild this for many platforms - see the attached zip files. EG the contents of babylon-node-rust-arch-linux-x86_64-release-rcnet-v3-r4.zip can be used for x86_64 linux deployments. Note they need to use a version of libc at least as recent as Ubuntu 22.04.2.0 LTS (Jammy Jellyfish).
  • If you need another architecture, you will need to compile it yourself on the desired target - see section below.

You will then need to run the JAR, but make the native library available for java to connect via JNI. This can be done in one of multiple ways:

• On Linux:
  • Put the native library in /usr/lib/jni or /usr/lib - be sure it's named libcorerust.so
  • Start the jar with an environment variable LD_PRELOAD=/path/to/native_library.so.
• General:
  • Put the library at one of the java.library.paths (on Ubuntu: e.g. /usr/lib/jni, on OSX: e.g. ~/Library/Java/Extensions/)
  • Run the jar with -Djava.library.path=<path_to_library_directory> and put the library there. EG on windows, the library will need to be called corerust.dll.

Configuration to use with your RCnet v3 / zabanet node is as follows. This can be specified in a file called "default.config" alongside the home directory of the node, or put in another file and referenced via a --config=path/to/config-file command line parameter.

network.id=14
network.p2p.seed_nodes=radix://node_tdx_e_1q0gm3fwqh8ggl09g7l8ru96krzlxdyrc694mqw8cf227v62vjyrmccv8md5@13.126.65.118,radix://node_tdx_e_1q0juzf2gnhfhy2aj6x88x4f459tf2a2mdk56jm3ffhzp94fn8k0q5lkse34@52.64.209.45,radix://node_tdx_e_1qdzlwtjn9wcmcyt3mp3g4qaerr6fgrl86ze6t20427tf4rmnu670y0cgszc@54.72.0.65,radix://node_tdx_e_1qfz9r8xp95vuzjq503l856ywukrdnukcz4232tr4nsx7ff2efvfnwvaq080@35.168.132.18
network.genesis_data=/wYAAHNOYVBwWQDRAgBo6NIQvgoUXCEGCgEACQEABQkHKAAAIQoJZAAAAAr0DRoICrgLCRsMCuCTBAUKFTQkoOyCkOtRDo+1mgUYGQEgoAAAZKeztuANGRMJARU7FQkgoAAAEGMtXsdrFYENAeAgIgMEASAhAQKA0fJ+apHv10KbZw/zq1+awjGS4SYu/i7pxk+BCLnNoAAAAGCKph7+xG3S1QgAAAAVArABICEEBiAHIQPRuKXAudCPvKj3zj4XVhi+ZpB40WuwOPhKleZpTJEHvAEBAQFiswDwkCAhAgIMBG5hbWUiAAEME0RlZmF1bHQgdmFsaWRhdG9yIDECDAN1cmwiDQEMGGh0dHBzOi8vd3d3LnJhZGl4ZGx0LmNvbYDRk4ZR64ZKF0UXY8UqyV6ghwcOhTBATZMlYRUFrK8GIAchA+XBJUid03IrstGOc1U1oVaVdVttqaluKU3EEtUzPZ4KAQEBAaAAAGRSWQGCpgAEMgKOpgBw6qD7P5CmKE5Vw2wD57719pXjLq07Mg+HaguVWgMlTHxF9y5TK7G8EXHYYoqDuRj0lA/n0LOlqfVXlpqPc+a88vZMAQAzkqYAcKvDUcvEhfpU9zJiX0WLTYhldkUKzZWgKxkIj7BjAaaAAkRRnMEtGcFIFHx+emiO5YbZ8tgVVRUsdZwN5KVZSxM39qYAADSSpgCQ4Bhb5cGHtROfCGYqZsBNXyin+4PMPOq2HReDCj0BAiCAAdHyfmrZAgwgIQQCjr4CECAhAQIJQfUwoAAAAOg8gNCfPC47AwEREQEFRxDlwSVInWpfAppHAH4AApZHAIKhAYZHAAHuJEDq7XRG0JwsnwwR60wAAAAgDAYMdHJhbnNmZXJfeHJkCGGJkHN3YXAIbWV0YWRhdGERZnVuZ2libGVfcmVzb3VyY2UVbm9uX2Y+FgB0HWFjY291bnRfYXV0aG9yaXplZF9kZXBvc2l0b3Jz

Compiling the native library for your architecture

If you need an architecture other than those offered in the attached zip files, you will need to compile it yourself on the desired target.

Pre-requisites

• clang
• git
• openjdk-17-jdk-headless
• rustup (e.g. curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh) - note: the prepackaged rust-1.62-all on Ubuntu is insufficient

Build steps

On your node:

1. Clone the repository git clone https://github.com/radixdlt/babylon-node.git, change directory to babylon-node, and checkout the branch release/rcnet-v3
2. Run ./gradlew installDist in babylon-node
3. Run cargo build --release in babylon-node/core-rust
4. Copy the created rust library found in babylon-node/core-rust/target/release/libcorerust.so (libcorerust.dylib on OSX, corerust.dll on Windows) to one of the java.library.paths (on Ubuntu: e.g. /usr/lib/jni, on OSX: e.g. ~/Library/Java/Extensions/)

You can then start your node as normal, eg with env RADIX_NODE_KEYSTORE_PASSWORD=[validator.ks passphrase] ./core/build/install/core/bin/core

Note: ./core/build/install/ directory can be safely moved to a directory under /opt, e.g. /opt/radixdlt.

Service files for Debian

A .deb for the node containing a useful base .service can be created as follows:

1. Clone the repository and cd babylon-node
2. Run ./gradlew deb4Docker
3. Install the package that was created with dpkg -i
4. Fine-tune the installed service file - e.g. by adding the RADIX_NODE_KEYSTORE_PASSWORD environment variable.

APIs/Monitoring:

APIs now live here:

• Core (bound to localhost:3333) - Core API docs here
• System (bound to localhost:3334) - System API docs here
• Prometheus (bound to localhost:3335) - they have been rehashed a lot to be a lot more consistent and powerful, although we don't have a great guide for these just yet.

Validator Registration:

Details are available here: https://docs-babylon.radixdlt.com/main/node-and-gateway/register-as-validator.html

RCnet v3 - Revision 3

Not for public running - please see Revision 4

RCnet v3 - Revision 2

Not for public running - please see Revision 4

RCnet v3 - Revision 1

Not for public running - please see Revision 4