Bitcoin Knots
Run a BLAKE2b node if you intend to mine this chain. Bitcoin Knots is highly recommended: it combines a full node and wallet, and it gives miners fine control over how block templates are constructed. Other software that supports getblocktemplate can be used for SHA256d, including Bitcoin Core, but it gives the miner much less control. For this chain you need a Knots version that includes the BLAKE2b change. Source is at github.com/bitcoinknots/bitcoin.
After the BIP-110 softfork, Bitcoin Core and older Knots releases still use the legacy SHA256d algorithm and follow a different blockchain. You need a Knots version that includes the BLAKE2b change. See what this means for node operators.
What DATUM is
DATUM stands for Decentralized Alternative Templates for Universal Mining. Early Bitcoin treated the person running a node as the miner: that machine chose the payments and submitted the block. Pools later started building the block themselves so many miners could share luck and get steadier pay. The hardware still hashes. The pool decides what goes in the block. When a handful of pools pick every payment, they can stall or drop ones they dislike.
DATUM reverses that. The DATUM Gateway asks your local node for a block template, sends work to your hardware, and submits a found block to the network from that node. The person running the node is the miner. The gateway and the node can share one machine.
You can still smooth income through a DATUM-supporting pool. The pool coordinates how the block reward is split based on work done. It does not create the work or the block template, and the DATUM protocol has no way for the pool to hand you the information needed to build one. The pool does send the generation payout split for a template you construct locally. In the current protocol the pool also checks that a found block is valid, so miners do not accidentally publish a bad block while the software is still in testing; that check is not meant to last. The work your hardware sees comes only from your node, which is why Knots matters: you choose transactions there.
- Talks to a local node over RPC using
getblocktemplate. - Talks to hardware over Stratum v1, including version rolling (ASICBoost).
- Talks to a pool, if you use one, over the DATUM protocol, an encrypted custom link between the Gateway and the pool, not a Stratum v2 add-on.
- Supports Bitcoin only. Choose transactions on the node; the pool does not hand you a ready-made block.
While limits on arbitrary data storage are in effect, a block may also be no larger than about 300 kB (700,000 weight units). getblocktemplate reports that as weightlimit. Do not point the gateway at a 4,000,000-weight policy and expect those templates to be valid.
BLAKE2b mining
SHA256d mining against an ordinary getblocktemplate node needs no node source changes. The Gateway uses standard GBT. BLAKE2b header-v2 mining is supported from the first block, including Antminer A3 and other Sia-style BLAKE2b hashers such as the Goldshell SC5 Pro and SC Lite, and needs a Knots node built with the BLAKE2b proof-of-work change. Current Knots getblocktemplate on that branch still looks like ordinary BIP22 GBT and does not advertise blake2b, so the Gateway default (auto) stays on SHA256d. Set mining.pow_algorithm to blake2b in the gateway config:
"mining": {
"pow_algorithm": "blake2b",
"allow_hasher_time_rolling": false
}This software is still in public beta. Build and configuration details are in the DATUM Gateway repository.