Hopefully this explains a bit to answer the above:

- Next payout I will be subtracting ฿.1 ($50)/miner in fees to address the overpay in fees from this week. This means your next dividend payout will have the BTC that was missed on the first round.

- I was mistaken about .31 KwH, it's actually .30 KwH. http://imgur.com/dcGywPf

- I was also mistaken about 2900W, it's closer to ~2800W w fluctuation spikes up to 2900W. http://imgur.com/H0B6sld and http://youtu.be/uvVCISb9N14
*Note I'm only measuring half the power consumption with the meter.

- .30c @ 24/7 still, has about $300 in fees per bi-weekly payout per miner. That is literally what it costs to run the machine.. not including cooling and maintenance.


I know that is not ideal, obviously. We're hashing at 25% less than what we should be and using a crazy amount of power. All we can do at this point is wait for firmwares from Cointerra.

Cheers
WH

I think the best way to support the developers is if he can post referral links to VPS that's recommended to solo mining with this HP. I would certainly sign up with more than 10 instances on the ones that are good to mine on a couple of different hosts.

BTW, I got this error msg when compiling the latest checked-out git on RH 6.5:

g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/root/primecoin/src -I/root/primecoin/src/obj -I/usr/local/include -DUSE_UPNP=0 -DUSE_IPV6=1 -I/root/primecoin/src/leveldb/include -I/root/primecoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/main.d -o obj/main.o main.cpp
In file included from main.cpp:16:
prime.h:13:33: warning: boost/timer/timer.hpp: No such file or directory
In file included from main.cpp:16:
prime.h:51: error: ‘boost::timer’ has not been declared
prime.h:51: error: expected initializer before ‘minerTimer’
main.cpp: In function ‘void BitcoinMiner(CWallet*)’:
main.cpp:4635: error: ‘minerTimer’ was not declared in this scope
main.cpp:4645: error: ‘boost::chrono’ has not been declared
main.cpp:4645: error: expected ‘;’ before ‘time_now’
main.cpp:4646: error: ‘boost::chrono’ has not been declared
main.cpp:4646: error: expected ‘;’ before ‘ns_now’
main.cpp:4647: error: ‘ns_now’ was not declared in this scope
make: *** [obj/main.o] Error 1

Not sure what's wrong if I'm missing something?

I think Waldo's right about stating he can not do anything about it right now. Not a 1% chance they would give refunds in 2013. What I do not understand, and think Waldo's wrong is not clarifying about the return amount in BTC in 2014 if they do not deliver.

I don't know where Waldo get's his confidence they'll return full BTC amount, when it is well known they've officially changed TOS. I'm convinced this is a mistake and may cost us greatly if we make an ill-informed decision to ask for refund in a month based on this wrong presumption.

What I do think is a need for group organizer to clarify this issue personally with someone of authority at HF. Waldo needs to get just one piece of information: Tell HF we've bought 7 batch#1 BabyJets + 7 upgrade kits for XYZ BTC. Ask how many BTC will we get back in total in case we ask for a refund, is it XYZ BTC or few percents of that sum?

If we are offered just percentage BTC back in refund, than it's foolish to ask for a refund without forming the lawyer fund and suing HF, and I'm against of optimistically asking for a refund and getting slammed by a hammer when we see the amount HF sent back.

considering all the work being done on this coin and it's algo, it's a shame it has been raped.

Selling SKN, I have 5000 for .1 BTC.

1.3 and we're even