Skip to content


Repository files navigation

HydraDX node


Contributions & Code of Conduct

Please follow the contributions guidelines as outlined in docs/ We are welcoming and friendly community please follow our Code of Conduct.

Local Development

Follow these steps to prepare a local Substrate development environment 🛠️

Simple Setup

Install all the required dependencies with a single command (be patient, this can take up to 30 minutes).

curl -sSf | bash -s -- --fast

Manual Setup

Find manual setup instructions at the Substrate Developer Hub.


Once the development environment is set up, build the node. This command will build the Wasm and native code:

cargo build --release



The easiest way to run and interact with HydraDX node is to use Chopsticks

npx @acala-network/chopsticks@latest --config=launch-configs/chopsticks/hydradx.yml 

Now you have a test node running at ws://localhost:8000

Local Testnet with Zombienet

Relay chain repository (polkadot) has to be built in ../polkadot Grab zombienet utility used to start network from releases

Start local testnet with 4 relay chain validators and HydraDX as a parachain with 2 collators.

cd ./rococo-local
zombienet spawn config-zombienet.json

Interaction with the node

Go to the polkadot apps at

Connect to

  • Mainnet: wss://
  • local node: ws://localhost:8000 (if you are using chopsticks)

Testing of storage migrations and runtime upgrades

The try-runtime tool can be used to test storage migrations and runtime upgrades against state from a real chain. Run the following command to test against the state on HydraDX. Don't forget to use a runtime built with try-runtime feature.

try-runtime --runtime ./target/release/wbuild/hydradx-runtime/hydradx_runtime.wasm on-runtime-upgrade --checks all live --uri wss://

or against HydraDX testnet on Rococo using --uri wss://


Useful resources:

Bug bounty:

Reponsible disclosure: