Bit Core v4.0.0.1 (restore peer discovery)
Bit Core v4.0.0.1 — restore peer discovery
First release of the independent OnlyPW release series: DNS seeds + fresh fixed seeds are now compiled in.
Pure peer-discovery change — no consensus-relevant code touched (genesis,
checkpoints, pow/auxpow, ports, prefixes, serialization all unchanged).
Changes vs. bittoshimoto v4.0.0.0 release
src/chainparams.cpp (mainnet only)
- //vSeeds.push_back(CDNSSeedData("", ""));
- //vSeeds.push_back(CDNSSeedData("", ""));
+ vSeeds.push_back(CDNSSeedData("followthebit.org", "seed1.followthebit.org"));
+ vSeeds.push_back(CDNSSeedData("followthebit.org", "seed2.followthebit.org"));src/chainparamsseeds.h (pnSeed6_main only, IPv4-in-IPv6, port 33317)
- {...0x2D,0x0E,0x32,0x1F}, 33317}, // dead
- {...0xBC,0xE3,0x3B,0x28}, 33317}, // dead
- {...0xBC,0xE3,0x3A,0x0E}, 33317} // dead
+ {{...0xA7,0x56,0x59,0x6B}, 33317}, // seed1.followthebit.org 167.86.89.107
+ {{...0x2D,0x92,0xFC,0x8A}, 33317}, // seed2.followthebit.org 45.146.252.138
+ {{...0x5C,0x2A,0x2D,0xDC}, 33317} // 92.42.45.220Build
Identical toolchain/linkage to the original release (Debian 12 bookworm,
system libraries): libboost 1.74, libdb 5.3, OpenSSL 3, libevent 2.1,
libminiupnpc 17, libzmq 5. ./autogen.sh && ./configure --with-incompatible-bdb && make. Binaries not stripped, with debug info — like the original.
Test log (2026-08-18)
$ ./bitd --version
BIT Core Daemon version v4.0.0.1
# fresh datadir, NO addnode: node bootstrapped purely via compiled-in fixed seeds
$ bit-cli getpeerinfo
{ "addr": "167.86.89.107:33317", "subver": "/bit:4.0.0/", "startingheight": 523765 }
# DNS seed hostnames embedded in binary
$ strings bitd | grep followthebit
seed1.followthebit.org
seed2.followthebit.org
# same chain as unpatched node (getblockhash identical at 0 / 1000 / 5000 / 20000)
height 0: 456ef94b5dd68b7a96438e3e2c551ddecd7b715cfe011228ac049a2482259862 (= genesis, both nodes)
height 1000: identical patched vs. unpatched
height 5000: identical patched vs. unpatched
height 20000: identical patched vs. unpatched
SHA256
c7588aad44d7842e23e6371255c6901fa1f082bae525af4c6868859a93bfcc27 Bit-v4.0.0.1.tar.gz
Docker (Bitcore-docker-B1T, same commit series)
- bit.conf template + entrypoint-generated config:
port=33317,rpcport=45873 - docker-compose:
33317:33317(P2P) +127.0.0.1:8332:45873(RPC, localhost only) - entrypoint merge: existing bit.conf keeps rpcuser/rpcpassword, only appends
addnode bootstrap lines if none present SOURCE_BUILD=1 docker compose buildcompiles from this source instead of
downloading the release tarball
Windows (win64)
Bit-v4.0.0.1-win64.zip — same layout as the previous release
(Bit-v4.0.0.1-win64/bin/{bitd.exe, bit-cli.exe, bit-tx.exe, bit-qt.exe}),
statically linked, no DLLs required. Built with the depends cross-toolchain
(mingw-w64 GCC 10, posix threads) on Debian bullseye; Qt 5.9.8 with
print support enabled, OpenSSL 1.0.2u, Boost 1.71, Berkeley DB 5.3.
2186aec31e3a5e83ed6bfc77eec9c88c331dcc95966e92e68ee37c14d7acfa5a Bit-v4.0.0.1-win64.zip
Test (native Windows 10/11, fresh datadir, no addnode):
$ ./bitd.exe --version
BIT Core Daemon version v4.0.0.1
$ bit-cli getpeerinfo # bootstrapped purely via compiled-in fixed seeds
{ "addr": "167.86.89.107:33317", "subver": "/bit:4.0.0/" }
Note: the DNS seed hostnames are embedded as immediate operands (GCC 10
optimisation), so strings bitd.exe will not show them — the live
connection test above is the authoritative check.