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/versionFinally, 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.