<p>This is largely what the sCrypt() based forks are intended for - both utilizing un-tapped CPU power on dedicated rigs or allowing casual miners to use their CPUs. At present, the difficulty on the Bitcoin network is so high that it's not even a question of profitability but capability - even with pooled mining, CPU mining is so slow that you may not actually submit even a single share for each round. That said, let's do the math. I'll use Tenebrix (TBX) as an example since I have numbers handy for it.</p>

<p>Keep in mind that the numbers presented are based on difficulties and exchange rates <strong>right now</strong> and as such will change. I will provide sources for all values and calculations so that you can re-calculate at any time.</p>

<p>A decent dual-core CPU will net you about 3 kH/s on Tenebrix (0.003 MH/s) and our friend the <a href="http://www.alloscomp.com/bitcoin/calculator.php" rel="nofollow">Bitcoin Mining Calculator</a> says that at the current <a href="http://blockexplorer.sytes.net/chain/Tenebrix" rel="nofollow">difficulty</a> of 0.288 you should mine 10.48 TBX per day. <a href="https://btc-e.com/exchange/tbx_btc" rel="nofollow">BTC-E</a> has the current TBX/BTC exchange rate at 0.000195, so that's worth 0.0020436 BTC per day. The same math could be done for FairBrix, LTC or any other sCrypt() derived forks.</p>

<p>Now for the BTC side of the fence: At the current difficulty of 1379647.43921 (auto-populated in the calculator, but available from the <a href="http://blockexplorer.sytes.net/chain/Bitcoin" rel="nofollow">same blockexplorer clone</a> I linked earlier) the same CPU will run about 3 MH/s on the Bitcoin network worth approximately 0.00219 BTC, roughly the same result.</p>

<p>So there's your (hopefully future-proof) answer: let the math guide you. As of this exact moment, mining TBX about the same efficiency though you'll probably see smoother returns with an sCrypt() fork (i.e. more shares per hour)</p>

CC BY-SA 3.0
2012-02-07T06:31:43.823Z
I think you make a fundamental mistake in your calculations.  My CPU will hash faster on the Bitcoin network than on the Tenebrix network, since Bitcoin uses a simpler hash.  My dual-core CPU gets around 4000 kH/s on Bitcoin, not 3 kHs, approximately 1000 times faster, and so multiply the 0.00000219 by 1000, get 0.00219, and find that the expected rewards seem to be pretty much the same as for Tenebrix.  I've been mining on P2Pool for 16 days at 4000 kH/s and have <a href="http://blockexplorer.com/address/1Ej1pLHTB7Gf3Q3VASaqo3TxEAJ3U7ejcn">received 0.0856 BTC</a>.  That's 0.005 BTC per day.
Chris Moore
CC BY-SA 3.0
2012-02-07T06:40:11.060Z
You're correct, my apologies. So yes, roughly the same result. My answer has been edited to reflect the correct math. :)
David Perry
CC BY-SA 3.0
2012-02-07T05:20:39.490Z
2012-02-07T06:43:21.273Z
2012-02-07T06:43:21.273Z
David Perry
<p>I have a useless Nvidia, until now, unconfigurable to mine (7300)</p>

<p>So, if I mine just with CPU, can I get more coins mining others coins like NMC,LQC,LTC,SC, or whatever, and trading after for BTCs?</p>

<trading><alternatives><mining-profitability><cpu-mining>
Can I CPU mine other coins to win Bitcoins?
H_7
# Can I CPU mine other coins to win Bitcoins?

(Asked by: username_0 on 2012-02-07)

I have a useless Nvidia, until now, unconfigurable to mine (7300)

So, if I mine just with CPU, can I get more coins mining others coins like NMC,LQC,LTC,SC, or whatever, and trading after for BTCs?

**Tags:** trading, alternatives, mining-profitability, cpu-mining


---

## 1 answers

### Answer by username_1 on 2012-02-07. Score: 4

This is largely what the sCrypt() based forks are intended for - both utilizing un-tapped CPU power on dedicated rigs or allowing casual miners to use their CPUs. At present, the difficulty on the Bitcoin network is so high that it's not even a question of profitability but capability - even with pooled mining, CPU mining is so slow that you may not actually submit even a single share for each round. That said, let's do the math. I'll use Tenebrix (TBX) as an example since I have numbers handy for it.

Keep in mind that the numbers presented are based on difficulties and exchange rates **right now** and as such will change. I will provide sources for all values and calculations so that you can re-calculate at any time.

A decent dual-core CPU will net you about 3 kH/s on Tenebrix (0.003 MH/s) and our friend the [Bitcoin Mining Calculator](http://www.alloscomp.com/bitcoin/calculator.php) says that at the current [difficulty](http://blockexplorer.sytes.net/chain/Tenebrix) of 0.288 you should mine 10.48 TBX per day. [BTC-E](https://btc-e.com/exchange/tbx_btc) has the current TBX/BTC exchange rate at 0.000195, so that's worth 0.0020436 BTC per day. The same math could be done for FairBrix, LTC or any other sCrypt() derived forks.

Now for the BTC side of the fence: At the current difficulty of 1379647.43921 (auto-populated in the calculator, but available from the [same blockexplorer clone](http://blockexplorer.sytes.net/chain/Bitcoin) I linked earlier) the same CPU will run about 3 MH/s on the Bitcoin network worth approximately 0.00219 BTC, roughly the same result.

So there's your (hopefully future-proof) answer: let the math guide you. As of this exact moment, mining TBX about the same efficiency though you'll probably see smoother returns with an sCrypt() fork (i.e. more shares per hour)

> **Comments:**
> **username_2**: I think you make a fundamental mistake in your calculations.  My CPU will hash faster on the Bitcoin network than on the Tenebrix network, since Bitcoin uses a simpler hash.  My dual-core CPU gets around 4000 kH/s on Bitcoin, not 3 kHs, approximately 1000 times faster, and so multiply the 0.00000219 by 1000, get 0.00219, and find that the expected rewards seem to be pretty much the same as for Tenebrix.  I've been mining on P2Pool for 16 days at 4000 kH/s and have <a href="http://blockexplorer.com/address/1Ej1pLHTB7Gf3Q3VASaqo3TxEAJ3U7ejcn">received 0.0856 BTC</a>.  That's 0.005 BTC per day.  
> **username_1**: You're correct, my apologies. So yes, roughly the same result. My answer has been edited to reflect the correct math. :)  

---

