A Bitcoin miner just picked its own transactions. Pools lost a small piece of control.
Stratum V2's Job Declaration is no longer just a spec. It has now moved Bitcoin block construction from pool-only theory into production.
CryptoVibe Desk · bitcoin · mining · stratum-v2
- →DMND and GoMining mined the first known Bitcoin block using Stratum V2 Job Declaration, according to Bitcoin Magazine.
- →The point is not one block. It proves miners can keep pooled payouts while choosing their own transactions.
- →Watch whether other large miners use Job Declaration before Q4 2026, because one demo does not change Bitcoin's pool power yet.
- Stratum V2 → Stratum V2 is a mining protocol that lets miners and pools coordinate block production with more control for miners.
- Job Declaration → Job Declaration lets a miner propose its own block template while the pool checks that the template is valid.
- Block template → A block template is the miner's draft list of transactions and block data before it gets mined.
- Hashrate → Hashrate is the amount of computing power a miner uses to compete for Bitcoin blocks.
A Bitcoin miner picked its own transactions this week. Bitcoin Magazine reported that DMND and GoMining mined block 955,318 using Stratum V2 Job Declaration. The source calls it the first known production Bitcoin block built this way.
That qualifier matters. This is not independently corroborated across the source cluster. But the mechanism is the story, and the mechanism is clean: GoMining built the block template, DMND validated it, and the miner's version got mined.
Under the normal pool model, miners provide hashrate and pools choose transactions. That setup smooths revenue, but it also gives pools quiet power over Bitcoin's transaction layer. If you're mining through a pool, your machines may find the block, but the pool usually decides what goes inside it.
Job Declaration changes that split. The miner submits its proposed block template to the pool. The pool checks that it is valid. The miner keeps pooled-mining payouts, but transaction selection moves closer to the machine doing the work.
At the protocol level, this is a separation-of-concerns fix. Pools can still handle coordination and payout smoothing. Miners can handle block construction. The tradeoff is more validation work and operational complexity for miners, in exchange for less pool control over transaction ordering and inclusion.
GoMining also tied the block to GoBTC Pay. That is its open-source, non-custodial Bitcoin instant payments protocol, announced at Consensus Miami in May 2026. Bitcoin Magazine also says GoMining has 5 million users and ranks among the top 10 Bitcoin miners by hashrate. Those numbers come from the same report, so treat them as attributed, not settled fact.
The important part is narrower and stronger. A miner used Stratum V2 Job Declaration in production to power its own product end-to-end. That means the censorship-resistance argument has moved from whitepaper shape to live mining path, for now.
One block does not decentralize Bitcoin mining. It does prove the old excuse is weaker. Pools no longer need to own transaction selection just because miners want stable payouts. The code path exists, and that's the catch for every pool that still talks like template control is unavoidable.
DMND's choice to let GoMining ship Job Declaration in production matters because it turns pool-level transaction control from a Bitcoin assumption into an implementation choice.
Before Q4 2026, watch whether at least three top-20 Bitcoin miners produce public Job Declaration blocks with self-built templates.
Primary links and supporting reads used by the desk for this story.
Forward this.
