Mine BigCoin & run a node
Quick facts
| Algorithm | to height 19,499: SHA-256d, identical to Bitcoin — from height 19,500: yespower 1.0 (N=2048, r=8, personalisation BigCoin/yespower1.0, over the 80-byte header). 2 MiB of memory per hash, so CPUs mine it and SHA-256 ASICs cannot mine it at all |
|---|---|
| Block reward | 50 BIG, halving every 210,000 blocks |
| Block interval | 10-minute target; difficulty adjusts every block (ASERT, 2-day half-life). From height 18,000 the target also eases while the chain waits, once a gap passes six hours, so a difficulty left behind by a miner who stopped clears itself |
| Reward maturity | a mined reward becomes spendable after 100 confirmations (roughly one day) |
| Network | seed node 133.242.139.204:8338 — the scripts below connect automatically |
Easy start — Windows, 2 steps
- Download BigCoin-win64-v1.9.zip from the downloads page and extract it anywhere, e.g. C:\BigCoin.
- Double-click mine-bigcoin.cmd — it is inside the zip. It starts a node, syncs the chain (a few minutes), creates a wallet with its own mining address, and starts mining. Leave the window open.
| File | mine-bigcoin-v1.8.cmd — easy solo-miner script (21.6 KB), the same file the zip bundles as mine-bigcoin.cmd. The script itself has not changed since v1.7, so v1.9 publishes no new name for it: this file is a byte-for-byte copy of mine-bigcoin-v1.7.cmd, which stays published and has this same digest. |
|---|---|
| SHA-256 | b4973f0c5c6a6f59c276f899a21a7453a60e35e3b916d222e55fa27647c4bf26 |
Already have an older script? Replace it. Scripts before v1.7 wait 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 is the one moment the old script refuses to mine.
The v1.7 script also asks the node which algorithm the next block needs instead of assuming, and sizes each
mining call by timing the previous one, which it has to: a yespower hash costs roughly 20,000 times a
double-SHA256 hash, so no fixed setting suits both sides of 19,500.
More speed: one window per CPU core is a sensible maximum; the script already starts one worker per
core and you can pass a number to override it.
Stop mining: close the mining window(s). Stop the node: run
bigcoin-cli.exe -datadir=data stop in the same folder.
Your coins: the wallet is stored in the data subfolder — back that folder up.
You can watch your mining address right here on the explorer.
Note: Windows SmartScreen may warn because the binaries are unsigned. The source code is public and every
binary can be rebuilt from it — verify the SHA-256 above after downloading.
Easy start — Linux, 3 lines
For a server, a VPS or any Linux desktop. The binaries are statically linked against Boost, libevent and SQLite, so there is nothing to compile and nothing to apt install. Requires glibc 2.35 or newer (Ubuntu 22.04+, Debian 12+, Fedora 36+); check with ldd --version.
curl -LO http://133.242.139.204/files/bigcoin-linux-x64-v1.9.tar.gz tar xzf bigcoin-linux-x64-v1.9.tar.gz && cd bigcoin ./mine-bigcoin.sh
| File | bigcoin-linux-x64-v1.9.tar.gz — Linux x86-64 release (9.6 MB) |
|---|---|
| SHA-256 | cf85ed4f4b158e3c8c292052025252182c8f80d037a8419f5ef6bea5540b5ba8 |
Workers: the script uses CPU cores − 1 by default; pass a number to override
(./mine-bigcoin.sh 4). Each worker mines to its own address inside the same
miner wallet — without that, two workers starting in the same second would
grind the identical block header in the identical nonce order and one of them would be wasted. Balances add
up in the one wallet. A count of mining addresses is not a count of miners; one person can hold any
number of them.
Stop mining: Ctrl-C — the node keeps running. Stop the node:
./bigcoin-cli -datadir=$PWD/data stop.
Headless server? Run it detached with
nohup ./mine-bigcoin.sh 4 > mine.log 2>&1 &, watch it with
tail -f mine.log, and stop it with pkill -f mine-bigcoin.sh
— there is no terminal to press Ctrl-C in, and the script treats SIGTERM exactly like Ctrl-C.
Your coins: the wallet lives in ./data. Back it up with
./bigcoin-cli -datadir=$PWD/data -rpcwallet=miner backupwallet /path/backup.dat.
Renting a server? Check your provider's terms first — many shared VPS hosts prohibit mining,
while plans with dedicated resources often allow it. Running a node alone is almost always fine.
Do not expose RPC port 8337 to the internet; only forward P2P 8338.
Run a node (no mining)
To let other nodes reach yours — over Tor, IPv6 or a forwarded port — see Run a reachable node. That page also explains what each option publishes about you, which is the part worth reading before you open anything.
A node independently verifies the whole chain and makes the network more robust. It needs no coins, earns nothing, and uses little CPU or bandwidth — an always-on PC or a Raspberry Pi-class Linux machine is plenty.
Windows: extract the release zip and run bitcoind.exe
(from v1.9 the seed node is compiled in - no config file needed)
Linux: unpack bigcoin-linux-x64-v1.9.tar.gz and run the binary
- nothing to build, nothing to install, nothing to configure:
tar xzf bigcoin-linux-x64-v1.9.tar.gz && cd bigcoin
./bitcoind -datadir=$PWD/data
(copying bitcoin.conf into the data directory is optional,
and still the place to put your own settings)
Advanced: external miners, and what happens to ASICs
bigcoind serves the standard getblocktemplate RPC, so any miner that solo-mines over getblocktemplate works — for the algorithm it was built for. Below 19,500 that is any SHA-256d miner. From 19,500 it has to be a yespower miner configured for N=2048, r=8, personalisation BigCoin/yespower1.0; a miner set up for some other yespower variant will produce nothing valid. If you would rather not verify those parameters by hand, use the bundled script or the node's own generatetoaddress — both take them from consensus. There is no official pool and none is planned; anyone is free to run their own.
SHA-256 ASICs can mine this chain only below height 19,500. From 19,500 they cannot mine it at all: yespower needs 2 MiB of memory per hash and a SHA-256 ASIC has none to give, so a block it produces is rejected as invalid rather than merely arriving too late. The same goes for a solo stratum speaking SHA-256d.
This is deliberate. 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 one 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; removing the hardware's ability to participate does. It is not a claim that BigCoin is ASIC-proof for ever: someone could build hardware for yespower, but it would need the memory, which is most of what makes a general-purpose CPU expensive, so the gap would be a small multiple rather than the four-to-six orders of magnitude SHA-256 hardware enjoyed here.