No, they auto-tune during each startup/reboot. Been that way for many batches now. Thanks for the heads up. To bad  The 0.1 W/Gh/s is really nice but I wanted to use less power/watts, then the stock ~1300watts. Did you also put a governor on your car that only lets it top out at 12 MPH?  |
|
|
|
...
ACH issues shouldn't have anything to do with BTC transfers, given that ACH is a clearinghouse for traditional banking and not related to Bitcoin in any way. ..... While all of that may be true, it has nothing to do with transferring BTC from one BTC address to another BTC address (as in the mentioned issue ".05 BTC from BTC.com to Coinbase").  |
|
|
|
...
ACH issues shouldn't have anything to do with BTC transfers, given that ACH is a clearinghouse for traditional banking and not related to Bitcoin in any way. |
|
|
|
...side note: My S7LN died today, the temp in my garage got up to 95 degrees and my miner didn't like that at all. I was lucky that I was able to bring it back to life after a few reboots and lowering the frequency to keep the temp a bit lower. If you bought 1 and still have the original PSU running, then you're doing better than us; we had around 1 PSU out of every 12 LNs survive past the 5 month mark. That being said, get more air moving in there; even at a low freq, hot air is not your friend.  |
|
|
|
Noob question, but when i set up another miner do i use the same worker name or a different one if i want to have both of my miners mining on kano?
You can do it both ways, you can set up MyAccount.MyWorkers and monitor them separately on your end, or you can set up MyAccount.MyWorker1and MyAccount.MyWorker2 and monitor them separately at the pool site. I imagine, that's not really the answer you were looking for, but it's all a matter of preference. |
|
|
|
for the record.... src/net.cpp:1118:72: error: too many arguments to function 'UPNPDev* upnpDiscover(int, const char*, const char*, int, int, int*)'
devlist = upnpDiscover(2000, multicastif, minissdpdpath, 0, 0, 0, 0); means that, when it goes to build, it's expecting: upnpDiscover(int, const char*, const char*, int, int, int*) and line number 1118 of the file net.cpp is feeding it: upnpDiscover(int, const char*, const char*, int, int, int, int*) So it has no clue what the last 0 is or what to do with it. |
|
|
|
Why not use "USE_UPNP=-" and be done with the nonsense? If you need to have a port open for it to work, just open the port manually. Hello, with qmake "USE_UPNP=1" the same error.. "USE_UPNP=1" is not "USE_UPNP=-" "=1" tells it to build with UPNP (which is the default; so, no, there would not be any change). Just build it without UPNP (which is what the "=-" means) and open port if necessary. Be in control of your network programs. |
|
|
|
For lack of better terms, "a mining collective". When you mine in a pool you use the hashrate of everyone in the pool to find blocks (this is very advantageous for those with very small hashrates compared to the overall network size). For most people this provides a more consistent and even payout period. |
|
|
|
Why not use "USE_UPNP=-" and be done with the nonsense? If you need to have a port open for it to work, just open the port manually. |
|
|
|
...It would be nice to see this pool maintain a hash rate over 1PH like the solo pool. ...
While I can say that I love the payout concept, I'm not sure that it will catch on before a few blocks are found. When you combine that with the psychology of 12.5 + fees for solo vs less for this pool, it's sadly going to be a bit before this pool has the continual wide interest that the solo pool does. |
|
|
|
At 3.24 khash/s, there's less than an infinitesimal chance that you found 2 bitcoin blocks in under 4 minutes. |
|
|
|
Perhaps we need to rent a billboard.  |
|
|
|
Well, they finally pushed the payments, relatively "on time", but..... I've tried to make an FLDC transfer 4 different times and every time I get a pop-up message telling me I don't have enough BTC to make the transfer. This wouldn't be an issue, except for the fact that EVERY time I've deposited the amount of BTC "required", it changes to .0004 more than the last amount (i.e., 0.00113619, 0.00153619, 0.00153619,etc). Yeah, Counterparty rocks. |
|
|
|
Ya basically you can try upping the frequency a bit at a time till you find one thats the most stable without slowing you down if you go too high on the frequency it can cause your miner to become unstable and or not get any faster after a point. and one frq that might be the sweet spot on someone elses miner or power supply may not be the same exact sweet spot as all other miners of the same model or even same batch. due to minor variations in the chips and other steps in the manufacturing process. no two are exactly 100% the same all the time... So many people forget that; that's the main reason there's such a difference in the maxes of ours. Average Rate - Error Rate = Real Average Rate I've cranked some up to a "6TH", but the error rate was so high that the actual was under 4TH. |
|
|
|
Thanks. With power costs and exchange rate to CDN factored in it works out to $9.14 per day profit. So 197 days to ROI.
If you did your maths correctly, I'm guessing that most people wish they had your cheap electric rates.  |
|
|
|
Haha if you have been around for a while you would know that full blocks are due to massive microtx and dust spam instigated by some shady elements of crypto society during major uptrends. It happened November, 2015, June and August, 2016 and is apparently happening again. I'm sure mempool will be naturally cleaned till the end of the current activation period.
I've been around long enough to see devs delay payments for nearly a week (last month and the month before, if memory serves) and not even try to push until the mempool was under 10k, so 70-90k doesn't provide much hope. |
|
|
|
Was the FLDC prize already paid?
They usually go out somewhere between 6pm UTC on the 1st Saturday of the month and the end of the week after that. Devs like to blame late payments on the BTC mempool; so, with 81+ MB in unconfirmed BTC tx, we might get payments for April sometime before September. |
|
|
|
...wtf is a s7 supposed to run this high?...
We run ours between 5.1TH(768) and 5.5TH(800).  |
|
|
|
|
Show Posts
