<p>The hashes generated by your miner is only usable for a unique set of transactions that your pool decided to include.  In addition each pool orders transactions differently and that too will affect the resulting hash.</p>

<p>Unless the pools cooperate and synchronize all the details of a given block (nonce, merkle tree, etc)  then any hash that is generated is useless to any other pool.</p>

CC BY-SA 3.0
2018-01-22T16:32:24.347Z
@nonce is what the miners use for mining, it's not part of pool details. I think, that the only thing that matters is the transactions, the Merkle tree hash.
Ilya Gazman
CC BY-SA 3.0
2013-02-28T00:05:12.160Z
2013-02-28T00:05:12.160Z
makerofthings7
<p>Is it possible to mine on different mining pool using one client?</p>

<p>Ok, I know that this sounds ridiculous, but my thoughts are as follows: if I already calculated a lot of hashes for a work for one mining pool may be I will be able to use them for another mining pool. Has anyone thought of it?</p>

<mining-pools><mining-pool-shares><mining-technical-details>
mining with one client on multiple mining pool
Salvador Dali
# mining with one client on multiple mining pool

(Asked by: username_0 on 2013-02-27)

Is it possible to mine on different mining pool using one client?

Ok, I know that this sounds ridiculous, but my thoughts are as follows: if I already calculated a lot of hashes for a work for one mining pool may be I will be able to use them for another mining pool. Has anyone thought of it?

**Tags:** mining-pools, mining-pool-shares, mining-technical-details


---

## 1 answers

### Answer by username_1 on 2013-02-28. Score: 6 | Accepted answer

The hashes generated by your miner is only usable for a unique set of transactions that your pool decided to include. In addition each pool orders transactions differently and that too will affect the resulting hash.

Unless the pools cooperate and synchronize all the details of a given block (nonce, merkle tree, etc) then any hash that is generated is useless to any other pool.

> **Comments:**
> **username_2**: @nonce is what the miners use for mining, it's not part of pool details. I think, that the only thing that matters is the transactions, the Merkle tree hash.  

---

