What this isBigCoin (BIG) is an independent proof-of-work chain based on Bitcoin Core v31.1, launched from its own genesis block on 21 October 2026. The proof-of-work is identical to Bitcoin's (double SHA-256), the block reward is 50 BIG halving every 210,000 blocks, and since block 17,325 the difficulty retargets every block (ASERT, two-day half-life). That last part is why it is CPU-minable: difficulty tracks whoever is actually mining, in both directions.
Ground rules, same as the ANN thread: nothing is for sale, no exchange listings are sought, no price talk. Block 1 contains a fully disclosed founder reward of 1,000,000 BIG, visible on-chain. BIG has no promised value. The only way to get it is to mine it.
ANN thread:
https://bitcointalk.org/index.php?topic=5598514Explorer (live difficulty, every block and address):
http://133.242.139.204/Downloads:
http://133.242.139.204/downloadsThere is no pool run by the project. Everything below is solo mining against your own node: when you find a block, the full 50 BIG goes to your own address. Rewards mature after 100 confirmations (roughly a day).
Windows — two steps1. Download BigCoin-win64-v1.5.zip from the downloads page and extract it anywhere.
2. Double-click mine-bigcoin.cmd (bundled in the zip). It starts a node, syncs the chain in a few minutes, creates a wallet and a mining address automatically, and mines. Leave the window open; run one window per CPU core at most. Your wallet lives in the "data" subfolder — back it up.
SmartScreen will warn because the binaries are unsigned. Verify checksums instead of trusting the download:
BigCoin-win64-v1.5.zip 2077bf3e39117992443c3bc70700a8327b0280f790f3682b74fa08e62938d1cf
mine-bigcoin.cmd 1fd7452f3098fce07d9a644823a618a2a0bb28153d4e12fc4b8bde7c8a41dcc6
curl -LO http://133.242.139.204/files/bigcoin-linux-x64-v1.5.tar.gz
tar xzf bigcoin-linux-x64-v1.5.tar.gz && cd bigcoin
./mine-bigcoin.sh
Static against Boost/libevent/SQLite — nothing to compile, nothing to apt install. Needs glibc 2.35+ (Ubuntu 22.04+, Debian 12+, Fedora 36+). The script uses CPU cores minus one by default; pass a number to override (./mine-bigcoin.sh 4). Ctrl-C stops mining, the node keeps running.
bigcoin-linux-x64-v1.5.tar.gz 23a6f365e06f7396dfea7e53bf8d34cc7801c39bd0b929d8432f3cdf16e75cb7
mine-bigcoin.sh 566a3025395c753b0d522b8c0bfcc6e4420d2b59d9443684d3d5f226e33b5bc5
The bundled scripts use the node's built-in block generator: zero setup, but single-threaded per window and unoptimized. Any miner that supports solo getblocktemplate is several times faster on the same hardware — for example cpuminer-opt (
https://github.com/JayDDee/cpuminer-opt):
1. In the data folder's bitcoin.conf add RPC credentials (RPC listens on localhost only — never forward port 8337 to the internet):
server=1
rpcuser=anyname
rpcpassword=pick-a-long-random-password
2. Restart the node, then:
cpuminer -a sha256d -o http://127.0.0.1:8337 -u anyname -p your-password --coinbase-addr=big1youraddress -t 8
If your cpuminer build rejects a bech32 (big1...) address for --coinbase-addr, create a legacy one: bigcoin-cli getnewaddress "" legacy
ASICs and stratum hardwareASICs and NerdMiner-class devices speak stratum, not getblocktemplate. Run a solo stratum server (for example ckpool in solo mode) next to your own node; it pays each found block straight to the address you log in with. Fair warning in both directions: the network is small enough today that a single ASIC would dominate it — and per-block ASERT means difficulty would chase it up within days, so the free lunch is shorter than it looks.
Upgrade notev1.4 (7 November 2026) was a hard fork at height 17,325. Nodes older than v1.4 cannot follow the chain — they stall silently at 17,324. Run v1.5.
Risk, stated plainlyBigCoin has no promised value, no exchange, and no buyer of last resort. Mine it because running a young chain interests you, not as an investment. Everything above is verifiable: the binaries rebuild from the source archive on the downloads page (MIT), and every block, address and balance is public on the explorer.
Seed node: 133.242.139.204:8338 — the scripts connect to it automatically.
