Follow these steps to independently verify that this CyberLiquid L1 demo cluster produces deterministic, high-throughput consensus. No trust required — everything is reproducible on your own machine.
Get the source code and compile the binaries (~5 min).
git clone https://github.com/hyperliquid-dex/hl-source hl-source cd hl-source cargo build --release
This produces all binaries in target/release/.
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shVerify the ≥10,000 actions/sec throughput claim using the built-in benchmark harness.
./bench/demo_stress.sh \ --target-tps 30000 \ --duration 60 \ --api-url http://195.245.241.75/exchange \ --info-url http://195.245.241.75/info
Expected: consensusTps ≥ 10,000 in the output. Results saved to report.json.
Download blocks from the demo cluster and replay them on your local engine. This proves that a fresh engine produces the same state from the same inputs.
./bench/verify_replay.sh \ --rpc 195.245.241.75:4100 \ --url http://195.245.241.75:3001 \ --count 200
Expected: ALL BLOCKS APPLIED with zero mismatches.
Query the demo cluster for recent block hashes and verify they are consistent across all validators.
# Get recent block hashes from the demo cluster
curl -sS http://195.245.241.75/info \
-d '{"type":"recentBlockHashes"}' \
-H 'content-type:application/json' | python3 -m json.tool
# Compare heights across validators
for port in 3001 3002 3003; do
echo -n "Validator :$port → "
curl -sS http://195.245.241.75:$port/info \
-d '{"type":"explorerState"}' \
-H 'content-type:application/json' 2>/dev/null \
| python3 -c "import json,sys; d=json.load(sys.stdin); print(f'h={d.get("blockHeight",0)} actions={d.get("totalActions",0)}')"
doneExpected: All 3 validators at the same height (±5 blocks) and same action count.
Start your own non-validator sentry node that syncs from the demo cluster in real-time.
./target/release/hl-run-non-validator \ --validator-rpc 195.245.241.75:4100 \ --validator-url http://195.245.241.75:3001 \ --info-port 3099
See Sentry Quickstart for full documentation.
Deterministic build recipe to verify your locally compiled binary matches the one running on the demo cluster.