Connect to drynet2

drynet2 is a dry-run drivechain network forked from Bitcoin mainnet at block 957,600. It runs real BIP300/301 rules. PoW difficulty is set very low, so it is possible to mine this chain at home.

Network endpoints

drynet2.drivechain.dev:8335

A full drynet2 node: the peer you sync from.

explorer.drynet2.drivechain.dev

Block explorer (mempool.space)

esplora.drynet2.drivechain.dev

Esplora REST API, for querying drynet2 programmatically — e.g. /blocks/tip/height or /address/<addr>/utxo.

explorer.drynet2.drivechain.dev:50011 explorer.drynet2.drivechain.dev:50012

Electrum server — plaintext on 50011, TLS on 50012. Point an Electrum wallet at it to hold drynet2 coins without running a node.

https://data.drivechain.dev/drynet2/

UTXO snapshots, to skip the historical download entirely — see below.

Run a node

Build the drivechain client from ecash-com/bitcoin (drynet2 branch) . Then connect to the network:

bitcoind -datadir=./drynet2 -addnode=drynet2.drivechain.dev:8335

⚠️ Always pass -datadir: because the fork identifies as main, running without it would write into a real ~/.bitcoin directory.

A full sync downloads and validates all of mainnet history up to the fork (~850 GB, several hours). For a much faster start, use the UTXO snapshot below.

Fast bootstrap (UTXO snapshot)

The client ships an assumeutxo commitment for the fork block, so you can load a ~9 GB snapshot and be validating drynet2 blocks at the tip within minutes. Historical blocks backfill in the background.

curl -O https://data.drivechain.dev/drynet2/utxo-957600.dat
curl -O https://data.drivechain.dev/drynet2/SHA256SUMS
sha256sum -c SHA256SUMS

bitcoind -daemon -datadir=./drynet2 -addnode=drynet2.drivechain.dev:8335
bitcoin-cli -datadir=./drynet2 -rpcclienttimeout=0 \
  loadtxoutset utxo-957600.dat

The snapshot is verified against a hash committed in the client’s chainparams. Expect the background history sync to eventually use the full ~850 GB of disk.

Mining

drynet2 restarted difficulty at 1 from the fork block, so blocks are CPU-mineable: point any getblocktemplate miner at your own node with a payout address of yours.