Adding multiple ASICs and pools seems to imply it's a topography. Either
split up the software, or reduce it to a single ASIC/pool graph.

Greg


On Thu, Apr 17, 2014 at 1:19 PM, David A. Harding
<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)
>
> @saivann <https://github.com/saivann> from my understanding (which could
> be flawed), many miners connect to multiple pools so that, if one pool goes
> down, they can instantly switch to another.
>
> My main intent with the illustration was to show the workflow, not
> illustrate the network topography. Do you think it would be less confusing
> if I relabeled the image "Pool-Based Bitcoin Mining Workflow"?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/saivann/bitcoin.org/pull/66/files#r11743002>
> .
>