If you already mine a yespower coin, this post is the part you actually need: the parameters, a vector to check your build against, and the command line. The announcement thread is elsewhere and linked at the bottom; this one is for getting a miner pointed at the chain.
BigCoin (BIG) is an independent Bitcoin Core 31.1 fork, own genesis 21 October 2026, no ICO, no presale, nothing for sale and no exchange listings sought. It ran on SHA-256d until height 19,500 and has been yespower 1.0 since 14 November 2026. There is no pool and I am not running one, so everything below is solo against your own node: the full 50 BIG goes to your own address.
Parametersversion YESPOWER_1_0
N 2048
r 8
pers "BigCoin/yespower1.0" (19 bytes, no terminating NUL)
hashed the standard 80-byte block header
r=8 rather than the usual 32 is where the 2 MiB per hash comes from. This is not one of the named variants shipped as its own algo, but it does not need to be: cpuminer-opt's generic yespower is YESPOWER_1_0 and reads N, r and the personalisation string from the command line.
Known-answer vector - check this before you spend hoursHash the 80 bytes 0x00 0x01 ... 0x4f. They deserialise to a block header and re-serialise to exactly the same bytes, so you need no block from this chain to reproduce it:
input 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
202122232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f
404142434445464748494a4b4c4d4e4f
yespower 757a410daff6f040692bdb64ff06bf6f00b95de24b9616f66e70ef6c7087e1e3
raw output order, as the function writes it
e3e187706cef706ef616964be25db9006fbf06ff64db2b6940f0f6af0d417a75
the same bytes reversed, i.e. how a hash is normally printed
sha256d e40105b4d7aff1df002bf704c28f346695527bda3bf62f120705b04f04982c85
for comparison - block identity is still double-SHA-256 in both eras
Reproduce the yespower line and your build is hashing this chain. The vector is pinned as a unit test in src/test/pow_tests.cpp in the source archive, and I reproduced it independently by building the vendored reference yespower on its own, outside the node, from nothing but the three parameters above.
Command lineRPC credentials go in your data folder's bitcoin.conf. RPC is localhost-only; do not forward 8337:
server=1
rpcuser=anyname
rpcpassword=pick-a-long-random-password
Then, on one line:
cpuminer -a yespower --param-n 2048 --param-r 8 --param-key "BigCoin/yespower1.0" -o http://127.0.0.1:8337 -u anyname -p your-password --coinbase-addr=<your address> -t 8
Use a legacy address for --coinbase-addr - cpuminer does not know the big1 bech32 prefix, so bech32 is usually rejected. bigcoin-cli getnewaddress "" legacy
What I have and have not verifiedVerified: the parameter triple above reproduces the chain's hashes, and cpuminer-opt's generic yespower algorithm sets YESPOWER_1_0 and takes all three from --param-n / --param-r / --param-key, so no patched miner is required.
Not verified: I have not driven a block through cpuminer-opt's getblocktemplate path end to end and watched the node accept it. The hashing side is confirmed; the plumbing is not. If you get an accepted block that way, please post it. If it fails, post that instead, with the error - that is more useful to everyone reading than me guessing, and I will correct the guide thread either way.
What a given hashrate should expectWork per block on 17 November 2026 is about 13.7 million yespower hashes:
1,000 H/s about 3.8 hours per block
2,000 H/s about 1.9 hours
4,000 H/s about 57 minutes
6,000 H/s about 38 minutes
10,000 H/s about 23 minutes
Averages of a random process, not schedules - half of all waits are longer than the mean. Difficulty retargets every single block (ASERT, two-day half-life, in place since height 17,325), so it follows hashrate up and down within hours instead of lagging 2016 blocks behind it. Practically: if you arrive, the numbers above get worse quickly, and if you leave they recover just as quickly. Live difficulty is on the explorer; anything I write in a post goes stale.
Block reward is 50 BIG halving every 210,000 blocks, 10-minute target, and coinbase outputs mature after 100 confirmations.
Getting the nodeWindows: the release zip includes a script that starts a node, syncs, makes a wallet and mines, if you would rather not wire up cpuminer at all.
Linux: a static x64 tarball, glibc 2.35+, nothing to compile.
Either way the full source is published and the binaries rebuild from it (MIT).
The binaries are unsigned, so SmartScreen warns and some antivirus products flag an unsigned program that mines on that basis alone. Neither warning says anything about the file; the digest does, and all of them are below.
Stated plainlyBIG has no promised value, no exchange, no buyer of last resort, and I will never sell mine. Block 1 contains a fully disclosed founder reward of 1,000,000 BIG, visible on-chain, which puts the cap at about 22,000,000. Mine it because running a young chain interests you. No price talk in this thread, please - that is the rule in the ANN thread and it applies here too.
Links and digestsBlock explorer http://133.242.139.204/
Downloads http://133.242.139.204/downloads
Mining status http://133.242.139.204/mining/status
Faucet http://133.242.139.204/faucet
Reachable node http://133.242.139.204/node
Source git clone http://133.242.139.204/git/bigcoin.git
Seed node 133.242.139.204:8338
Seed node (Tor) rjxywola2kupk4rp67qzidqiuxwvr76xmri5zimt6ecrvhx4xv5t7wyd.onion:8338
ANN thread https://bitcointalk.org/index.php?topic=5598514
Mining guide https://bitcointalk.org/index.php?topic=5599204
f3999cc9d6da8a032a4ba8d2023a098e18dfeabe90e0369693b451415c5fd5cb BigCoin-win64-v1.9.zip
cf85ed4f4b158e3c8c292052025252182c8f80d037a8419f5ef6bea5540b5ba8 bigcoin-linux-x64-v1.9.tar.gz
d287776d917d0d22c063ffbc6c6ed91bba3fe96b8c9f385a594a2de1caf790bb bigcoin-source-v1.9.zip
d44066c8bf5d70404b66d21d6689af4d99a13695b1bbf047816c47cc6b99c693 bigcoin-source-v1.9-unix.tar.gz
b4973f0c5c6a6f59c276f899a21a7453a60e35e3b916d222e55fa27647c4bf26 mine-bigcoin-v1.8.cmd
67d55214e84a5571358c09d2c875f0b49d94a08307ac32e93e79cc56fec574dd mine-bigcoin-v1.8.sh
cpuminer-opt is
https://github.com/JayDDee/cpuminer-opt - I do not host it, ship it, or have any connection to it.
- Masashi Takamoto