Downloads
📦 Official distribution mirror for BigCoin releases.
Binaries are unsigned; every release can be rebuilt from the source archive below (MIT license).
⛏️ New to BigCoin? The Windows zip bundles a one-click solo miner
(
mine-bigcoin.cmd) and the Linux tarball bundles
mine-bigcoin.sh — see the
mining guide.
Latest release — v1.9 (2026-11-15)
A real rebuild. Every program here is newly compiled and reports version v31.1.9, so the package number and the number the software reports agree again — v1.8 was a documentation release that shipped v1.7's binaries and reported v31.1.7. The program version skips 31.1.8 on purpose, to put the two numbers back in step.
No consensus rule, no activation height and no default changed. A v1.9 node and a v1.7 node accept exactly the same blocks. If you are already running v1.7 or v1.8 there is nothing urgent here.
What changed: an unconfigured node now finds the network. No seed node used to be compiled into the binaries, so a node that never read bitcoin.conf never found a peer at all — and copying that file is the step a newcomer most easily misses. This release compiles this project's seed node in, and drops the 60-second pause upstream puts in front of its compiled-in seeds to give DNS seeds time to answer: BigCoin has no DNS seeds, so the minute bought nothing. Measured on an empty data directory with no config file and no -addnode:
seeds loaded +61 s → +0 s · first peer connected +61 s → +1 s
In that run the node went from the genesis block to the then-current tip at height 19,694 in 84 seconds from launch. Copying bitcoin.conf is now optional — still worth doing, because it is where your own settings go, but no longer the difference between a working node and a silent one.
The bundled readmes gained a section and a warning, both measured on this build: how to encrypt the wallet — including why the backup you keep has to be the one taken after encrypting, and the fact that a locked wallet can still mine, because getnewaddress derives from a key that is not encrypted — and what a normal shutdown or reboot does to a running node (Windows waits for it; Task Manager's End task and a power cut do not).
One source comment was corrected. The note explaining the yespower difficulty anchor quoted 4,910 H/s for the reference machine; measured again on 2026-11-15 it is 8,250 H/s idle. The anchor value itself is untouched — changing it would be a consensus change — only the comment that explains where it came from.
Proof of work is yespower 1.0, and has been since block 19,500, which this chain passed on 14 November 2026. Software v1.5 or older can no longer follow the chain at all: the hashes it computes are not the ones consensus asks for. v1.7 and v1.8 are unaffected.
The solo-miner scripts are unchanged, and this release publishes no new names for them. The current copies are mine-bigcoin-v1.8.cmd and mine-bigcoin-v1.8.sh, listed under v1.8 below — byte-for-byte the v1.7 files, and byte-for-byte the ones inside this release's archives.
| File | BigCoin-win64-v1.9.zip — Windows 64-bit binaries (mine-bigcoin.cmd included) — rebuilt, reports v31.1.9, seed node compiled in (26.1 MB) |
| SHA-256 | f3999cc9d6da8a032a4ba8d2023a098e18dfeabe90e0369693b451415c5fd5cb |
| File | bigcoin-linux-x64-v1.9.tar.gz — Linux x86-64 binaries + mine-bigcoin.sh (glibc 2.35+; Boost/libevent/SQLite statically linked, nothing to install) (9.6 MB) |
| SHA-256 | cf85ed4f4b158e3c8c292052025252182c8f80d037a8419f5ef6bea5540b5ba8 |
| File | bigcoin-source-v1.9.zip — full source code (tag v1.9) (15.4 MB) |
| SHA-256 | d287776d917d0d22c063ffbc6c6ed91bba3fe96b8c9f385a594a2de1caf790bb |
| File | bigcoin-source-v1.9-unix.tar.gz — same source as the zip above, repacked with LF line endings and executable bits so it builds on Linux as-is (the one Windows batch file keeps its CRLF endings) (13.9 MB) |
| SHA-256 | d44066c8bf5d70404b66d21d6689af4d99a13695b1bbf047816c47cc6b99c693 |
Previous release — v1.8 (2026-11-12)
A documentation release: every program in it is byte-for-byte the one in v1.7 and still reports version v31.1.7. No consensus rule, no network rule and no default has changed, and nothing was rebuilt. If you are already running v1.7 there is nothing here you need to install. Do not take that on trust — unpack both archives side by side and the digests match:
certutil -hashfile bitcoind.exe SHA256 (Linux: sha256sum bigcoin/bitcoind)
You still need v1.7 or later before block height 19,500, where the proof-of-work algorithm changes from SHA-256d to yespower 1.0 (N=2048, r=8, personalisation BigCoin/yespower1.0; every hash needs 2 MiB of memory, which no SHA-256 ASIC has). Because it is the algorithm that changes, software on v1.5 or older does not merely fall behind: the hashes it computes are no longer the ones consensus asks for, so it can neither follow the chain nor mine one valid block past that height. Watch the height, not the date: getblockcount.
What actually changed. The Windows archive now carries README.txt and bitcoin.conf in English, with README.ja.txt and bitcoin.conf.ja beside them — which is what the Linux archive has done since v1.5. Those two are exactly the files a newcomer cannot skip: no seed nodes are compiled into the binaries, so a wallet that never reads bitcoin.conf never finds the network at all. Until this release they were the only Japanese-only files in the Windows package. The source tree gains doc/BigCoin.ja.md, so the English and Japanese specifications now sit side by side instead of one of them being the only copy.
One number was wrong, and is now right. The explanation of the yespower switch in the bundled READMEs said this chain's difficulty was around 2.3, roughly 40 MH/s. Measured on 2026-11-12 it was 12.3, roughly 88 MH/s. The argument is unchanged — a single second-hand ASIC still does tens of TH/s, more than a hundred thousand times the whole chain — but the figure now matches what the node reports. The correction is written into both changelogs rather than applied quietly.
The solo-miner scripts are unchanged. They are listed below under v1.8 names so that a quick start does not mix version numbers, but they are byte-for-byte copies of the v1.7 files — same bytes, same SHA-256 — and they are the same scripts bundled inside this release's archives. The v1.7 names stay published and keep working.
| File | BigCoin-win64-v1.8.zip — Windows 64-bit binaries (mine-bigcoin.cmd included) — the v1.7 programs, English README and bitcoin.conf (26.1 MB) |
| SHA-256 | dcfebf2f476331f0d83de481379b45f4a523de7f545a456a107b01434642b972 |
| File | bigcoin-linux-x64-v1.8.tar.gz — Linux x86-64 binaries + mine-bigcoin.sh (glibc 2.35+; Boost/libevent/SQLite statically linked, nothing to install) (9.6 MB) |
| SHA-256 | 66f8b838370410119ed396d6f6cd44da9425bba7b85cedb0232fa4557743a882 |
| File | bigcoin-source-v1.8.zip — full source code (tag v1.8) (15.5 MB) |
| SHA-256 | 67b32b9f494595400654b11f42eae79a222f35d8b1ebac145d5e817ffbceb472 |
| File | bigcoin-source-v1.8-unix.tar.gz — same source as the zip above, repacked with LF line endings and executable bits so it builds on Linux as-is (the one Windows batch file keeps its CRLF endings) (14.0 MB) |
| SHA-256 | 422375eafe2e11a7daf29292b1681449599b93d874f4fbe9dc4ac90f692ed6d2 |
| File | mine-bigcoin-v1.8.cmd — easy solo-miner script for Windows, double-click to mine — unchanged since v1.7, and the same file the Windows zip bundles (21.6 KB) |
| SHA-256 | b4973f0c5c6a6f59c276f899a21a7453a60e35e3b916d222e55fa27647c4bf26 |
| File | mine-bigcoin-v1.8.sh — easy solo-miner script for Linux — unchanged since v1.7, and the same file the Linux tarball bundles (17.4 KB) |
| SHA-256 | 67d55214e84a5571358c09d2c875f0b49d94a08307ac32e93e79cc56fec574dd |
Previous release — v1.7 (2026-11-09, same programs as v1.8)
This release changes the proof-of-work algorithm. A hard fork activates at block height 19,500: below it BigCoin uses SHA-256d, from it BigCoin uses yespower 1.0 (N=2048, r=8, personalisation BigCoin/yespower1.0, computed over the 80-byte block header). Every hash needs 2 MiB of memory, which no SHA-256 ASIC has.
Nodes running v1.5 or older stop at height 19,500. Because it is the algorithm that changes and not a difficulty rule, older software does not merely fall behind — the hashes it computes are no longer the ones consensus asks for, so it can neither follow the chain nor mine one valid block past that height. Watch the height, not the date: run getblockcount and upgrade before you reach 19,500.
Why: through the SHA-256 era this chain's difficulty sat around 3 — roughly 44 MH/s — while a hobby single-chip miner at about 1.2 TH/s is some 27,000 times that, and a second-hand datacentre unit at 13 to 100+ TH/s is one to two further orders of magnitude on top. Either is enough for a single owner to take every block or rewrite recent history for the price of the electricity. No difficulty rule fixes that on a chain this small. This is not a claim of being ASIC-proof for ever; hardware for yespower is possible, but it would have to carry the memory, so the gap would be a small multiple rather than the four-to-six orders of magnitude SHA-256 hardware enjoyed here.
Also in v1.7: from height 18,000 ASERT measures elapsed time as max(parent timestamp, candidate timestamp − 6 hours). For any gap shorter than six hours that is byte-identical to the old rule, so it changes nothing about the chain as it stands; past six hours of silence the target eases on its own, so a difficulty left stranded by a miner who stopped clears itself instead of freezing the chain — which is what froze this chain for five days at height 17,324. A miner who dates a block into the future still gains at most a 2.9% discount, bounded by the existing two-hour limit on future timestamps and available to everyone equally. The ASERT fork at height 17,325 is unaffected.
Both mining scripts are new and worth taking. Every earlier version waits for the node to report that its initial block download has finished, which never happens on a node started while the chain itself is stalled — so the one moment the chain most needs another miner was the one moment the old script refused to mine. The v1.7 scripts also ask the node which algorithm the next block needs instead of assuming, and size each mining call by timing the previous one, which they have to: a yespower hash costs roughly 20,000 times a double-SHA256 hash, so no fixed setting suits both sides of 19,500.
| File | BigCoin-win64-v1.7.zip — Windows 64-bit binaries (mine-bigcoin.cmd included) (26.1 MB) |
| SHA-256 | 501613b628252dfcac7315dd2256332b0388f19ef44970f0e3794d088c9444d8 |
| File | bigcoin-linux-x64-v1.7.tar.gz — Linux x86-64 binaries + mine-bigcoin.sh (glibc 2.35+; Boost/libevent/SQLite statically linked, nothing to install) (9.6 MB) |
| SHA-256 | 753399bf4d183ecc94e17404c475b25c5201bb2b7762fb98600332720691e0cb |
| File | bigcoin-source-v1.7.zip — full source code (tag v1.7) (15.4 MB) |
| SHA-256 | 954390fb3dd8a3dc6e1feaf0469294ae5ff4957ae8de5117edf01923ba936125 |
| File | bigcoin-source-v1.7-unix.tar.gz — same source as the zip above, repacked with LF line endings and executable bits so it builds on Linux as-is (14.0 MB) |
| SHA-256 | cbae78fca9c0953f3381e6e6d27d7c8dce73fdbb38c1d8e60e780b7d7aa98926 |
| File | mine-bigcoin-v1.7.cmd — easy solo-miner script for Windows, double-click to mine — the same file the v1.7 zip bundles as mine-bigcoin.cmd (21.6 KB) |
| SHA-256 | b4973f0c5c6a6f59c276f899a21a7453a60e35e3b916d222e55fa27647c4bf26 |
| File | mine-bigcoin-v1.7.sh — easy solo-miner script for Linux — the same file the v1.7 tarball bundles as mine-bigcoin.sh (17.4 KB) |
| SHA-256 | 67d55214e84a5571358c09d2c875f0b49d94a08307ac32e93e79cc56fec574dd |
Previous release — v1.5 (2026-11-07, Linux build added 2026-11-08)
Superseded by v1.7: this build stops at block height 19,500, where the proof-of-work algorithm changes to yespower 1.0. It can neither follow nor mine the chain past that height. Maintenance release, fully compatible with v1.4 — no consensus changes. The easy solo-miner script is bundled inside the Windows zip, and the shipped binaries no longer carry the build machine's local directory paths. This was the first release with a Linux x86-64 build.
| File | BigCoin-win64-v1.5.zip — Windows 64-bit binaries (mine-bigcoin.cmd included) (26.1 MB) |
| SHA-256 | 2077bf3e39117992443c3bc70700a8327b0280f790f3682b74fa08e62938d1cf |
| File | bigcoin-source-v1.5.zip — full source code (tag v1.5) (15.4 MB) |
| SHA-256 | 5cd3148e75433cdad49ed7a669383511a2635f29287356e0d6c091d0b9303ae6 |
| File | mine-bigcoin.cmd — easy solo-miner script, double-click to mine (see the mining guide) — also bundled in the v1.5 zip (3.8 KB) |
| SHA-256 | 1fd7452f3098fce07d9a644823a618a2a0bb28153d4e12fc4b8bde7c8a41dcc6 |
| File | bigcoin-linux-x64-v1.5.tar.gz — Linux x86-64 binaries + mine-bigcoin.sh (glibc 2.35+; Boost/libevent/SQLite statically linked, nothing to install) (9.6 MB) |
| SHA-256 | 23a6f365e06f7396dfea7e53bf8d34cc7801c39bd0b929d8432f3cdf16e75cb7 |
| File | bigcoin-source-v1.5-unix.tar.gz — same source as the zip above, repacked with LF line endings and executable bits so it builds on Linux as-is (14.0 MB) |
| SHA-256 | ceda888548cb1ae9a378dc958cd0ed90743c8b6047e079e8d7eb06e5e9a94014 |
| File | mine-bigcoin.sh — easy solo-miner script for Linux — also bundled in the Linux tarball (9.7 KB) |
| SHA-256 | 566a3025395c753b0d522b8c0bfcc6e4420d2b59d9443684d3d5f226e33b5bc5 |
Previous release — v1.4 (2026-11-07)
Consensus-identical to v1.5: v1.4 activates the ASERT difficulty-adjustment hard fork at block height 17,325 (moved forward from 18,000). Like v1.5 it stops at height 19,500, where the proof-of-work algorithm changes — upgrade to v1.7.
| File | BigCoin-win64-v1.4.zip — Windows 64-bit binaries (26.1 MB) |
| SHA-256 | ed3efd7168c25e5e5b1f29a481f8eb39326bc6a29708c924f6e62199c688d306 |
| File | bigcoin-source-v1.4.zip — full source code (tag v1.4) (15.5 MB) |
| SHA-256 | c7680392269ea09060caa01aa871535c7d8c2559c3d0c60a873573ef5da08d44 |
Previous release — v1.3 (2026-11-02)
Superseded by v1.4: this build expects the ASERT fork at height 18,000 and stops following the chain at 17,325. Kept for reference only.
| File | BigCoin-win64-v1.3.zip — Windows 64-bit binaries (26.1 MB) |
| SHA-256 | b007171b076c57a1c2ac257cdd34906e826099becf2ee0358e65a16847cc2ed9 |
| File | bigcoin-source-v1.3.zip — full source code (tag v1.3) (15.5 MB) |
| SHA-256 | e0db8b661abd1fcd06a4d13f88b60bfcf363b0adb0f3f5020faa7c0585489a23 |
Previous release — v1.2 (2026-11-01)
| File | BigCoin-win64.zip — Windows 64-bit binaries (26.1 MB) |
| SHA-256 | c1d57735ce5e13866543a88c06a2fd898794cfd5a02c0fd108a0f9cb31754dc0 |
Git repository
The full history is served over plain HTTP as well, so you can clone it and compare
this fork against upstream Bitcoin Core yourself:
git clone http://133.242.139.204/git/bigcoin.git
Tags v1.0–v1.5,
v1.7, v1.8 and v1.9 hold the source archives listed above,
file for file. The archives are packed on Windows, so one of them —
contrib/bigcoin/mine-bigcoin.cmd — has CRLF line endings in the archive and
LF in the repository; VERIFYING.md gives the one extra flag that accounts for it.
Add upstream as a second remote and the whole of what BigCoin changes in Bitcoin Core v31.1 comes
to 55 files:
git remote add upstream https://github.com/bitcoin/bitcoin.git
git fetch --depth=1 upstream tag v31.1
git diff --ignore-cr-at-eol --stat v31.1 v1.9
A clone proves nothing by itself: the repository is unsigned and this host serves it
over HTTP. The digests in the announcement thread
are the anchor, and VERIFYING.md in the repository walks through checking an archive
against both them and a tag.
Verify your download
After downloading, compute the file's SHA-256 and make sure it matches the value above.
Windows: certutil -hashfile BigCoin-win64-v1.9.zip SHA256
Linux: sha256sum BigCoin-win64-v1.9.zip
Want to mine or run a node? Follow the step-by-step mining guide.
New to BigCoin? See the introduction (日本語).
The complete source is above, both as an archive and as a git repository (MIT).