CROSS-CHAIN LIQUIDITY PROTOCOL BUILT ON SUBSTRATE
Please follow the contributions guidelines as outlined in docs/CONTRIBUTING.md
.
We are welcoming and friendly community please follow our Code of Conduct.
Follow these steps to prepare a local Substrate development environment 🛠️
Install all the required dependencies with a single command (be patient, this can take up to 30 minutes).
curl https://getsubstrate.io -sSf | bash -s -- --fast
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
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
Go to the polkadot apps at https://polkadot.js.org/apps
Connect to
- Mainnet:
wss://rpc.hydradx.cloud
- local node:
ws://localhost:8000
(if you are using chopsticks)
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://rpc.hydradx.cloud:443
or against HydraDX testnet on Rococo using --uri wss://rococo-hydradx-rpc.hydration.dev:443
Useful resources:
- https://github.com/galacticcouncil/HydraDX-security
- https://apidocs.bsx.fi/HydraDX
- https://docs.hydradx.io/
- https://docs.hydradx.io/omnipool_design
- https://docs.hydradx.io/fees
Bug bounty: https://immunefi.com/bounty/hydradx/
Reponsible disclosure: [email protected]