Skip to content

Releases: OnlyPW/Bit-core

Release list

Bit Core v4.0.1.0 (wallet import in the GUI)

Bit Core v4.0.1.0 (wallet import in the GUI) Latest
Latest

Choose a tag to compare

View all tags
@OnlyPW OnlyPW released this 19 Aug 06:08
v4.0.1.0
34a4a40

Bit Core v4.0.1.0 — wallet import in the GUI

New feature release of the independent OnlyPW series, on top of v4.0.0.1
(restore peer discovery). No consensus-relevant changes.

New: File → Import Wallet...

Core-style wallets keep everything in a single Berkeley DB wallet.dat which
is locked while the node runs — restoring it always required closing the app
and copying files by hand. The GUI now does this for you:

  1. File → Import Wallet… and pick a wallet .dat backup
  2. Confirm the dialog — your current wallet is backed up automatically as
    wallet.dat.bak-<timestamp> (nothing can be lost)
  3. The application shuts down cleanly, swaps in the imported wallet and
    restarts automatically with a rescan of the blockchain

Tested end-to-end on Windows (v4.0.1.0 build):

before: wallet.dat (old) + wallet-import.dat + .wallet-import-pending
clean shutdown via RPC
after:  wallet.dat (imported) + wallet.dat.bak-20260819060438
        bit-qt.exe relaunches itself with -rescan
second shutdown: no further restart (import marker consumed)

Peer discovery (unchanged from v4.0.0.1)

  • DNS seeds: seed1/seed2.followthebit.org
  • Fixed seeds: 167.86.89.107 / 45.146.252.138 / 92.42.45.220 (port 33317)

Downloads

File Platform SHA256
Bit-v4.0.1.0.tar.gz Linux x86_64 b738b83af395eb5e6c283caaba67d11756f28afff291debe2bb61451dd4a10fd
Bit-v4.0.1.0-win64.zip Windows x64 0ef93b70c86732989886eec6c73c067b86356c6250e71f685203083dd7390850

Linux: Debian bookworm system toolchain (same linkage as v4.0.0.x).
Windows: depends cross-toolchain, mingw-w64 GCC 10 (posix), Qt 5.9.8 with
print support, statically linked, no DLLs required.

Assets 4
Loading

Bit Core v4.0.0.1 (restore peer discovery)

Bit Core v4.0.0.1 (restore peer discovery)

Choose a tag to compare

View all tags
@OnlyPW OnlyPW released this 18 Aug 21:56
v4.0.0.1
6f873e9

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

Build

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 build compiles 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.

Loading