Bitflash
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
| File | Platform | Size |
|---|---|---|
| Bitflash-1.2.15-windows.zip | Windows, x86_64 — portable zip, extract and run Bitflash.exe | 7.8 MB |
| Bitflash-1.2.15-x86_64.AppImage | Linux, x86_64 — AppImage, chmod +x and run | 4.3 MB |
| bitflash-node-1.2.15-x86_64 | Linux, x86_64 — headless node binary, for servers | 2.7 MB |
SHA256SUMSSHA256SUMS.ascSigning key
02Checksums
| Bitflash-1.2.15-windows.zip | 6a8f08acf27558db9e21e81efa12a911a0e003e789188c973df90703c4782e5f |
| Bitflash-1.2.15-x86_64.AppImage | 1f2821ad75ccd925315e2f6a80921697421ee9096ef60d6aa6a16478d224914c |
| bitflash-node-1.2.15-x86_64 | cd8f663624f160b9f674b99b4d0540b001084f9350af0d1cf5fe0125b2d7615f |
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 SHA256SUMSOn Windows, without a shell:
certutil -hashfile Bitflash-1.2.15-windows.zip SHA256Checksums prove the files match each other; a signature proves they came from Bitflash. Import the release key once, then verify the checksum file against it before trusting it:
curl -O https://releases.bitflash.network/bitflash-release-key.asc
gpg --import bitflash-release-key.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMSThe signing key fingerprint is 910A 2B4C CA87 9E81 FB4B 2AEA 1D4A 53D3 B78A A4B8. Check the gpg --verify output names exactly that key — a good signature by some other key means nothing.
The repository helper does this end to end, and refuses anything not signed by the pinned key:
scripts/verify-release.sh latestThe 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.