What mining hardware i need for 0.1 BTC a day?

[Campsis]

Can anyone help me please?

Is anyone making such amount?

Thx

[thehairymob]

You will need at least a rig that can do 5TH/s. 

[byt411]

You will need at least a rig that can do 5TH/s. 

Stop making up random numbers to mislead people.

Can anyone help me please?

Is anyone making such amount?

Thx

At current difficulty, you would need a minimum of 6TH/s.

[alh]

And in two weeks from now, you'll need about 10% more hashrate to maintain that .1 BTC per day.

[xstr8guy]

Plug in your own numbers...

https://alloscomp.com/bitcoin/calculator

And remember to factor in the difficulty adjustment ever 2016 blocks (about every 12 days) and the cost of electricity and cooling. Oh and don't forget, many ASIC manufacturers don't include PSUs with mining gear. So you may have to buy them separately.

Also be sure you have the electrical capacity to properly operate all of those THs. Spondoolies make some nice machines but they run best with higher voltages than you will have available in your typical American home.

[ChuckBuck]

You'd need this today:

http://www.spondoolies-tech.com/products/sp35-yukon-power-november-batch-1

Unfortunately, this is a pre-order, so by the time it ships in November, you won't make 0.1 BTC a day and you'll be mining in both a BTC and Fiat loss.

Well that sucks.   

[Master One]

If I've calculated this right, it's exactly 6.5903155 TH/s you need for BTC0.1 a day right now with a total network hash rate of 237,251,358 GH/s.

So just 66 TH/s and you make BTC1 a day, I'm in!  

[Master One]

At current difficulty, you would need a minimum of 6TH/s.

I may have misunderstood something, but doesn't it depend on actual network hash rate instead of current difficulty, resulting in a variable amount of BTC mined per day with a given available hash rate?

[byt411]

At current difficulty, you would need a minimum of 6TH/s.

I may have misunderstood something, but doesn't it depend on actual network hash rate instead of current difficulty, resulting in a variable amount of BTC mined per day with a given available hash rate?

When network hashrate goes up, it makes the difficulty go up, which makes the earnings go down. So basically he skipped the middle part but he's right.

[Master One]

When network hashrate goes up, it makes the difficulty go up, which makes the earnings go down. So basically he skipped the middle part but he's right.

But difficulty get changed every ~ 12 days only whereas network hash rate changes all the time, so calculation on needed hash power for a certain amount of mined BTC per day should be based on network has rate only, right?

[byt411]

When network hashrate goes up, it makes the difficulty go up, which makes the earnings go down. So basically he skipped the middle part but he's right.

But difficulty get changed every ~ 12 days only whereas network hash rate changes all the time, so calculation on needed hash power for a certain amount of mined BTC per day should be based on network has rate only, right?

You can do both. You can either calculate the amount of total expected mined coins within a given timeframe, calculate the percentage of the total network hashrate that you control, and then multiply it by the percentage. That gives an estimation of what you will get within that given timeframe too.

[Korbman]

All good advice so far.

Personally, I've always used two equations.
#1 - Calculating how many Bitcoins are generated over a period at a specific hashrate:
(BR)(HR)(T)
(Diff) x 2³²

#2 - Calculating how much hashrate is needed to generate a specific amount of Bitcoins over a period of time.
2³²x(BTC)(Diff)
     (BR)(T)

Where:
BR -- Current Block Reward
HR -- Your current hashrate in hashes per second
T   -- Time in seconds; calculating generated coins per day would mean 86,400 seconds
Diff -- Current (or predicted) difficulty
BTC -- Bitcoins generated over the period of time, (T)


In other words, to generate BTC0.1 per day (ignoring variability / pool luck / energy costs, etc):
2³²x(0.1)(29,829,733,124)
     (25)(86,400)

Comes out to: 5,931,376,306,295.74 hashes per second ...or 5.93 TH/s for easy viewing.