Judging from yesterday’s performance and what the profit calculator was telling me, mining feather coin at my current status (hash rate and kWh price) was unprofitable. Even if I powered my pc entirely from solar panels (price of kWh = 0), still I would have to also increase my hash rate to achieve some returns.
If I do the calculation you provide me, we have
19.400.000.000 h/s (19.4 Gh/s) / 80.000.000 (80 Kh/s) = 242.5 minutes = 4.04 hours
40 ftc is about 2$.
kWh price in prime time (noon) here is 0.21$. So 0.21 * 4 = 0.84$. So, he have a profit.
So, which of these two are correct?
EDIT: Wrong Kh/s to H/s conversion. The process is unprofitable. Unless you have free energy and a 500 kh/s mining power.
that is correct, but we decided against a faster downward adjustment, as this may create other problems.
In theory we could adjust eHRC to dampen the difficulty decrease calculation less than the increase calculation. Then the BC would need less blocks to adjust the difficulty down.
I used cpuminer-neoscrypt on Intel Core2 Duo running Debian 9.1. My power consumption was running around 130W, making it awfully inefficient, even if I could muster 1 FTC per day as @looarn mentioned.
My understanding is that by the nature of p2pool’s PPLNS payout scheme, 6 kH/s is well below the noise level at current difficulty, thus yielding zilch shares.
I’ve switched to GPU mining since then, getting ~500 kH/s with much better results - ~16 coins per day. Still, it’s not profitable at the current price level due to high electricity cost in my area.
i am very much in the same boat, except your card is doing much better than mine! dual xeons and a 780 make for a high electric bill, but guess its better than folding for free! new rig will do better i hope
I run multiple daemons on a single machine but thinking about this on a much larger scale, Bittrex has tons of coins and needs a daemon for each so they probably run multiple systems, if not separate servers for each daemon for better security. It could be something like the server crashed or had an issue, not necessarily the daemon itself.