Agreed.

Greg


On Thu, Apr 17, 2014 at 1:12 PM, saivann <notifications@github.com> wrote:

> In en/developer-guide.md:
>
> > +
> > +On the other hand, if a hash is found below the target threshold, the
> > +mining hardware returns the block header with the successful nonce to
> > +the mining software. The mining software combines the header with the
> > +block and sends the completed block to the network for addition to the
> > +block chain.
> > +
> > +Pool miners follow a similar workflow, illustrated below, which allows
> > +mining pool operators to pay miners based on their share of the work
> > +done.  The mining pool gets new transactions from the network using
> > +`bitcoind`.  The miner's mining software then periodically polls the
> > +pool for new transactions using the `getblocktemplate` RPC, the same
> > +RPC solo miners use, and constructs a block and block header the same as
> > +before.
> > +
> > +![Pooled Bitcoin Mining](/img/dev/en-pooled-mining-overview.svg)
>
> @harding <https://github.com/harding> I only think it might be confusing,
> since it shows a single miner connecting to different pools, which doesn't
> happen usually. If there was only one ASIC per Mining software, you could
> perhaps show three miners and my impression is that it would be a better
> representation, and it wouldn't look cluttered.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/saivann/bitcoin.org/pull/66/files#r11742772>
> .
>