BitFinite Node 3.1.2 is out, and two community channels are open.--- 3.1.2 ---
https://github.com/bitfinitechain/bitfinite-core/releases/tag/v3.1.2Drop-in upgrade from 3.1.x or 3.0.x. No reindex, no wallet migration, no consensus change - 3.1.1 and 3.1.2 nodes stay on the same chain. All three seeds are running it.
What is in it:
- A checkpoint at the genesis block was missing on five of our six networks. Upstream ships one everywhere; ours were emptied during the fork and only mainnet was ever restored. It bans forks that rewrite the genesis block.
- Log lines were being lost on a crash after log rotation. setbuf was applied to the file handle being closed instead of the newly opened one, so the reopened debug log stayed fully buffered. This is a Bitcoin Cash Node bug from 2018 that BCHN fixed in v29 before we found it independently - the fix is theirs, we backported it.
- An overflow assertion in the difficulty code had been commented out during our genesis work and did not need to be. Put back.
None of these are vulnerabilities and we are not calling them that.
--- how we found them ---
The unit tests had not been run in months. Nothing in our release pipeline built them, so a backport that landed tests for a half-implemented API stopped the suite compiling for two days without anyone noticing - the node itself was fine, which is why it went unseen.
That is fixed. CI now builds and runs the tests on every branch, and 117 of 120 suites pass. The three exclusions are listed with a reason each in scripts/run-tests-docker.sh.
Six suites needed repair. Five had been broken by our own rebranding - a find-replace that landed inside values carrying a checksum or an encoding (address prefixes, a base58 xpub, a client name that never existed). None of them was a defect in the node. Worth stating plainly, because "the rebrand broke the tests" is a different claim from "the code was wrong".
--- verify it yourself ---
The Linux binaries are reproducible. Building locally in Docker produces bytes identical to what the GitHub runner published - we checked again for this release. Windows are not reproducible; PE headers carry a build timestamp.
git clone https://github.com/bitfinitechain/bitfinite-core
cd bitfinite-core && git checkout v3.1.2
NO_QT=1 scripts/build-core-docker.sh linux
sha256sum build-linux/src/bitfinited
Compare against scripts/release-checksums.txt, which pins the binary hashes in git rather than trusting the SHA256SUMS inside the archive - that file travels with the artifact and can only attest to itself.
--- community ---
Telegram:
https://t.me/bitfinitechainDiscord:
https://discord.gg/8yjGUwQQcFOrganized by topic - network status, blocks found, releases, mining help, and a Chinese-language section on Telegram. The status card and block alerts come from a bot reading the node and the pools directly, so they stay current
without anyone being online.
New members are approved manually on Telegram, and Discord needs a verified phone plus accepting the rules, so expect a short wait after joining.
The only links we use are on bitfinitechain.org, on github.com/bitfinitechain, or posted inside those two servers.
Nobody from the project will message you first, and nobody will ever ask for a seed phrase or a payment.
BitFinite
