<p>Well that is simply bad luck. It can happen if the miner uses multiple Bitcoin nodes to handle the getwork or stratum requests. In the case of GHash.io my guess is that they either have so many resources that a single nodes cannot handle all the work to keep them working, so they created multiple nodes and distributed the resources on them.</p>

<p>Another reason might be that they have multiple locations, and in order to keep latency low, they have local nodes feeding work to the resources. This scenario would fit pools like btcguild.</p>

<p>While certainly annoying, it is not really anything you can do against it, if they'd known from the other block from their own network they would simply have dropped it and we wouldn't have known about it.</p>

CC BY-SA 3.0
2013-12-13T09:24:56.957Z
That make sense. They're big, so they basically end up competing with themselves... too big IMO :/
ktorn
CC BY-SA 3.0
2013-12-13T17:48:24.210Z
Well they are not really competing with themselves. If the second node would have known the block hash from the first they'd simply not have found a block, since they'd had to restart searching for one. The only thing they might have lost is the fee differential between the two blocks. In this case though they were lucky since the block with higher fees (0.127 vs. 0.119) made it into the blockchain.
cdecker
CC BY-SA 3.0
2013-12-13T09:10:20.037Z
2013-12-13T09:10:20.037Z
cdecker
<p>Just noticed <a href="https://i.sstatic.net/ccO5F.jpg" rel="nofollow noreferrer">2 conflicting blocks by the same pool</a>.</p>

<p>One of the blocks was naturally <a href="https://blockchain.info/block-height/274626" rel="nofollow noreferrer">orphaned</a>, but why would the same pool broadcast 2 such blocks? Does it happen often?</p>

<mining-pools><stale-block>
Block orphaned by same miner?
ktorn
# Block orphaned by same miner?

(Asked by: username_0 on 2013-12-13)

Just noticed [2 conflicting blocks by the same pool](https://i.sstatic.net/ccO5F.jpg).

One of the blocks was naturally [orphaned](https://blockchain.info/block-height/274626), but why would the same pool broadcast 2 such blocks? Does it happen often?

**Tags:** mining-pools, stale-block


---

## 1 answers

### Answer by username_1 on 2013-12-13. Score: 2 | Accepted answer

Well that is simply bad luck. It can happen if the miner uses multiple Bitcoin nodes to handle the getwork or stratum requests. In the case of GHash.io my guess is that they either have so many resources that a single nodes cannot handle all the work to keep them working, so they created multiple nodes and distributed the resources on them.

Another reason might be that they have multiple locations, and in order to keep latency low, they have local nodes feeding work to the resources. This scenario would fit pools like btcguild.

While certainly annoying, it is not really anything you can do against it, if they'd known from the other block from their own network they would simply have dropped it and we wouldn't have known about it.

> **Comments:**
> **username_0**: That make sense. They're big, so they basically end up competing with themselves... too big IMO :/  
> **username_1**: Well they are not really competing with themselves. If the second node would have known the block hash from the first they'd simply not have found a block, since they'd had to restart searching for one. The only thing they might have lost is the fee differential between the two blocks. In this case though they were lucky since the block with higher fees (0.127 vs. 0.119) made it into the blockchain.  

---

