Connect to drynet1

drynet1 is a dry-run drivechain network forked from Bitcoin mainnet at block 955,584 (the last block shared with mainnet is 955,583). It runs real BIP300/301 rules. The chain identifies itself as main — mainnet nodes reject its blocks and vice versa, so the networks can never mix.

Network endpoints

Node (P2P)drynet1.drivechain.dev:8335Seed (history)seed.drynet1.drivechain.dev:8334Snapshot downloadshttps://data.drivechain.dev/drynet1/

Run a node

Build the drivechain client from ecash-com/bitcoin (drivechain-ecash branch) — it carries the drynet1 fork parameters. Then connect to the network:

bitcoind -datadir=./drynet1 \
  -addnode=drynet1.drivechain.dev:8335 \
  -addnode=seed.drynet1.drivechain.dev:8334

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

A full sync from the seed 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 drynet1 blocks at the tip within minutes. Historical blocks backfill in the background.

curl -O https://data.drivechain.dev/drynet1/utxo-955584.dat
curl -O https://data.drivechain.dev/drynet1/SHA256SUMS
sha256sum -c SHA256SUMS

bitcoind -daemon -datadir=./drynet1 -addnode=drynet1.drivechain.dev:8335
bitcoin-cli -datadir=./drynet1 -rpcclienttimeout=0 \
  loadtxoutset utxo-955584.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

drynet1 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.