Bitflash BTF · RandomX · MIT

Downloadscurrent v1.2.15windows + linuxsha256 with every release

Downloads

Every release ships the binaries and a SHA256SUMS file covering them. Verifying takes a second and is worth doing — it is the only thing standing between you and a file somebody else swapped out.

01Bitflash v1.2.15

FilePlatformSize
Bitflash-1.2.15-windows.zipWindows, x86_64 — portable zip, extract and run Bitflash.exe7.8 MB
Bitflash-1.2.15-x86_64.AppImageLinux, x86_64 — AppImage, chmod +x and run4.3 MB
bitflash-node-1.2.15-x86_64Linux, x86_64 — headless node binary, for servers2.7 MB

SHA256SUMS

02Checksums

Bitflash-1.2.15-windows.zip6a8f08acf27558db9e21e81efa12a911a0e003e789188c973df90703c4782e5f
Bitflash-1.2.15-x86_64.AppImage1f2821ad75ccd925315e2f6a80921697421ee9096ef60d6aa6a16478d224914c
bitflash-node-1.2.15-x86_64cd8f663624f160b9f674b99b4d0540b001084f9350af0d1cf5fe0125b2d7615f

Every hash above was recomputed from the artifact when this page was built.

Verify what you downloaded

Put the release files and SHA256SUMS in one directory:

sha256sum -c SHA256SUMS

On Windows, without a shell:

certutil -hashfile Bitflash-1.2.15-windows.zip SHA256

When a signature is published, check who signed the checksum file before trusting the checksums:

gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

The repository carries a helper that fetches a release, verifies the signature when present, and then checks the hashes:

scripts/verify-release.sh latest

The full audit procedure is in release verification.

Keep your node current

Consensus rules have changed since the first releases. 1.2.1 fixed a bug that let anyone spend anyone's coins, and 1.2.2 added a per-block signature-operation cap. A node on an older build will accept blocks that current nodes reject, which puts it on a different chain with no warning at all.

Your wallet and chain data live in %APPDATA%\Bitflash on Windows or ~/.bitflash on Linux and are shared by every version, so upgrading is just replacing the binary. Never delete that directory to "fix" something without a backup — it holds your keys.