⛏️Open-sourced pyblockMiner — a terminal GPU/CPU miner for Bitcoin BLAKE2b, solo-lottery style.
You mine to your own address and keep 99.1% of every block, straight to your wallet. No accounts, no custody.
Live hashrate, blocks & difficulty in a clean TUI. Multi-GPU + CPU fallback.
🦀 Rust · MIT · https://t.co/K3QMu4kpKB
⚠️ Honest note: BLAKE2b is a proposed PoW change for Bitcoin (Knots PR #359) — not merged, no activation date. The pool is a regtest demo: the coin has no value. This is so miners can test BLAKE2b and see they get paid to their own address, ready for the day (if ever) the network changes its PoW. Don't trust, verify.
#Bitcoin #BLAKE2b #MiningStocks
@_PyBlock_
We should have Datum-BLAKE2b created by @Innerhat available in a few hours.
Lotto, SV2, CHIRP, and Carousel Stratums might take a little longer to adapt, but there shouldn't be any significant delay once the 1st one is published and globally available.
@Curly60e - PyBLØCK Crew.
Stayed up super late last night getting my own DATUM fork working for BLAKE2b/-sia testing using the draft hardfork PR @LukeDashjr posted the other day, applied to my node
We are hashing, team 🔥
For anyone curious about the “useragent” field of the SC Box, “intminer” is a proprietary fork of Luke’s BFGMiner for Blake2b-Sia. This is a pretty blatant GPL violation, so hopefully we can get them to release a FOSS version.
How do BLAKE2b-Sia ASICs compare with Bitcoin SHA256d miners?
Raw TH/s is meaningless across algorithms, so I normalized each miner by its share of network hashrate and expected solo block interval, then matched similar power tiers.
The results are absurd.
Example: a 130W HS BOX at 470 GH/s represents ~0.00651% of Sia’s 7-day hashrate.
The same share of Bitcoin’s 926.98 EH/s is ~60.3 PH/s—about 10,057 Avalon Nano 3S miners drawing ~1.41 MW.
That also gives the same expected solo-block interval: ~107 days for 1 HS BOX on Sia, versus ~107 days for that ~10,057-Nano fleet on Bitcoin.
One Nano 3S by itself is roughly a 2,939-year statistical wait at this network hashrate.
This is NOT saying a BLAKE2b hash does 128,000× the cryptographic work of a SHA256d hash.
It compares each miner’s share of the network it actually competes on.
Both chains target ~10-minute blocks, so equal network share ≈ equal expected block-finding probability.
Across the hardware ladder, the pattern persists: similarly powered Sia ASICs represent vastly more of their current network than similarly powered Bitcoin ASICs represent of Bitcoin.
Full methodology, 22-model table, sources and caveats in the article: https://t.co/xSAhDsZZzO
Tentative community results show Goldshell HS BOXes with stock firmware are successfully hashing over Stratum V1 and DATUM using Bitcoin BLAKE2b software fork prototypes.
Bullish.
To anyone interested in trying to run DATUM for Bitcoin Blake2b with a regtest node, there is an implementation in the works:
https://t.co/YSDsfkS46X
I’ve submitted some PRs to address some share rejection issues as well as some general JSON string parsing/handling errors.