Has anyone elese noticed the estimated reward for the current round is dropping like your mining has stopped? Estimated reward is now down to 0.00004556 BTC
Normally I get 0.00030000 BTC or somewhere in that region. the last 2 or 3 rounds show a slightly lower reward than normal but I neglected that as natural fluctuation but only just noticed my estimated reward for this round is dropping by the minute the same as it does when I stop mining, yet all my workers still show last hsare as 0 minutes ago and I can't find any problems with their speed etc
Edit - It seems to be going back up now, anyone know why this might have happened?
There was an increase in pool hash rate to the vicinity of 680 TH, which would reduce the individual miners' share, then there was a drop which increased the individual shares. Now the overall pool hash rate is slowly rising again.... on average our total reward should roughly the same (greater total hash rate = more frequent blocks with smaller individual rewards). |
|
|
|
Hello,
I have installed this software on a linux server. I have pointed some of my miners to this server. But, on the pool that I use (middlecoin), the hashrate does not shows up.
This software should be able to run for stratum pools, right? Also for script?
when you say "this software", to which software are you referring? Sorry :-) - I mean this software: https://github.com/slush0/stratum-mining-proxy/Most of the popular miners (bfgminer, cgminer) will work fine directly with common stratum running pools. Are you sure that you need this proxy for your specific devices? I understand, they do. But I have about 70 miners running right now. I want to use a proxy, so that I easily can move all the miners with 1 or 2 proxy's  Yes, that make sense. Using about 45 minters here, arranged into 4 instances of bfgminer/cgminer, without the need for a proxy. I read that some miners such as Blades which have only a LAN interface are best used with a proxy, but have no direct experience with Slush's proxy s/w. Good luck. |
|
|
|
Hello,
I have installed this software on a linux server. I have pointed some of my miners to this server. But, on the pool that I use (middlecoin), the hashrate does not shows up.
This software should be able to run for stratum pools, right? Also for script?
when you say "this software", to which software are you referring? Sorry :-) - I mean this software: https://github.com/slush0/stratum-mining-proxy/Most of the popular miners (bfgminer, cgminer) will work fine directly with common stratum running pools. Are you sure that you need this proxy for your specific devices? |
|
|
|
Thanks,
Looks like it is on the move, however still in China.
Cheers
I think that is because of the weekend. If it doesn't move tomorrow i will get in contact with Bitmain. It's just that another difficulty rise is upon us.... so time is of the essence.... Cheers |
|
|
|
|
Thanks,
Looks like it is on the move, however still in China.
Cheers
|
|
|
|
or if it is even possible to have two terminals of cgminer open -
one for the gpu, and one for the red fury.... this would be ideal - but i dont know if it is possible?
thanks in advance
You can run 2 (or more) instances of your favorite miner on Windows. For example, if you want 2 instances of bfgminer, create 2 sub-directories such as c:\temp\bfgminer_gpu c:\temp\bfgminer_BF download and copy the latest install of bfgminer into each one of these sub-directories. Create a batch file (or short-cut) for each one of the instances. For the Bf devices run it with something like bfgminer.exe -G -S bigpic:all -o your_pool -p your_password Note that for bfgminer you'll need to install the Com drivers as per the instructions in the OP ( https://bitcointalk.org/index.php?topic=319419.0. If you want to run cgminer, you may follow a similar path, but make sure that you either install the USB drivers (using zadig utility) for cgminer OR the Com drivers that are required for bfgminer. If you already installed the wrong one, you will need to go to Device Manager and modify the driver to the one suitable for your miner application. You can run a combination of cgminer for some devices and bfgminer for others, as long as you assign each instance to the desired mining devices and have the appropriate drivers installed. I am running now 4 instances, 2 of bfgminer, 2 of cgminer for 5 different USB controlled miners. Good luck |
|
|
|
I just came here from the pool page. I had unconfirmed shares earlier, but that's now 0 on the "My account" page, with the confirmed being the same amount it was last night. I've got 500 GH/s going in, and nothing shows? There was 0.03+, or more, unconfirmed; now 0.0000000 ? I hope this gets fixed, and I get back what was already there pending confirmation a few hours ago....
:-/ Concerned....
Just got fixed for me, hopefully for other pool members... |
|
|
|
21434 2014-01-12 01:26:08 3:20:30 1903298449 none none  (I know, it will get fixed.... ) Edit: Fixed, thank you Slush & support team! |
|
|
|
FYI.
I too have had some delays in processing all around but everything I believe I earned, I got. Yes, "none" hiccups happen, and a host of other issues as well, however I imagine it's not exactly easy to run a BC server or you and I would be doing it. But my experience has been pretty positive. I started from scratch and learned that there is much to learn about all this. Sometimes the problems may be within your reach? I don't work for, or know Slush. Just saying. If it's technical, or analytical
and adding to the situation, GREAT. If you are here just to piss and moan, what's the point. Buy stocks! Until proven a cheat in anyway, my hash'n will happen here.
I must add that the communication from the pool owner a.k.a. Slush is BAD! But you choose who to dance with!
Oh and I have not experienced any "outage" of either the BC Server or the website in the past few week?
6 hour block just ended and my miners must have got booted towards the end when the pool crashed, reward is tiny and my shares were almost entirely wiped out. This is a forum, if people using the pool want to bitch about it they can, bitching and moaning about poor luck or administration hiccups are "on topic" for this thread. I imagine it's not easy to be president but he's got plenty of critics too. If the pool is fucked up then people should post about it, otherwise what's the point of the forum? Some more 'bitching and moaning'..... (or proactive information about issues to enable solutions.....) Slush's Support Site http://support.bitcoin.cz/Knowledgebase/List now reports "Uncaught Exception".... Had a much lower outcome for 21404 2014-01-09 03:20:04 6:16:22 3192104213 85198 0.00066507 About 1/3 of what I would expect. This is despite solid hashing throughout this block. From past experience I know that it takes typically 10-15 minutes for this to get right, but now it has been 48 minutes and it's still incorrect. Why is it a never ending saga of 'hiccups'? |
|
|
|
|
Things are back to normal at my end (block confirmations and payouts). Hopefully this will stay like this....
|
|
|
|
Package should arrive on Monday via UPS.
Beastlymac, Thanks for the update Cheers |
|
|
|
I am finding that 52:2:950 is as far as I can push mine before it starts giving ASIC error messages.
DRB 0: E8 37 max37.4 | 23.06G/21.28Gh/s | A:3938 R:48 HW:76 WU:297.2
Is that 37C temp ok? It was down at 32C on standard clocks. I don't really know where on the board that temp is being measured.
as long as you have say two fans on the heat sink you should be ok, trying pointing a fan on the other side of the board, mine was running at 53:2:950 at 35C (in a room at35C) with 3% HW....but right power supply fan not working so no mining  I measured the temp on various components on the component side with an infrared thermometer. The hottest component was the linear regulator (52.6 C) and about 40C on the Atmel micro-controller. This is with a 12 cm fan blowing directly on the component side. I suggest cooling both the heatsink side and the component side. Maybe this is why I can consistently overclock this board. In any case, failure rates of electronic components are exponentially related to temperature, therefore leaving them to cook a 'max specified temp' is a recipe for a short life span (one probably wants to let these live while they can mine efficiently). Cheers |
|
|
|
I'm trying 53:2:950 right now Your board may need 950mV to get rid of most of those HW errors. You could also try int:53:2:850. I get lower a higher hash rate and lower HW errors (virtually none) on my boards with 54:2:850 than I do at default settings (40:1:850). And definitely get another fan cooling the line regulator heatsink as well as those teeny little heatsinks, especially if you want to use 950mV. I *am* using 950mV. I said so twice already. :-) I tried int:53:2:850 earlier, the error rate was higher. I'm using a large floor fan blowing over the whole board. Pretty sure it is cooling the whole board pretty well. Without a temperature sensor gun, is there a way to tell if components are getting hot and causing the HW errors? I'm getting a HW error rate of about 3% at int:53:2:950. The board is cooled by 3 12cm fans - 1 at the heatsink side, 1 at the component side and one from the side with the airflow along the heatsink fins. The reported temp is around 32C. The long term avg hash rate is about 22.4 GH/sec WU 314/m. It does take the board a while to achieve steady state in hashing, take into account the pool applying var diff. I'm running the drillbit CGMiner 3.8.5 on win7/64. The board f/w is at the latest 'test firmware'. Cheers |
|
|
|
Unfortunately there is a repeat of the last few day's problem. Blocks confirmed in Stats do not show as 'Confirmed reward' on the account profile page (this now applies to Slush blocks #21388 and #21389, which are confirmed on the Statistics page https://mining.bitcoin.cz/stats/. I understand that there is some delay in updating, but this is beyond the 'reasonable delay' and looks like a precursor to delayed payments (again). |
|
|
|
One block fixed, two to go... 21383 and 21384 are still broken. Hopefully somebody is still working on it. As mentioned before: it's a pitty that there is no communication from the pool owner at all. A simple "We are working on it and hope it will be fixed in a few hours" would be great. That's not to much to ask for... is it?
I did not have any noticeable issue with 21383 and 21384. You are right that providing a brief feedback to pool users would be of great help to calm the situation. BTW now the reward payout was issued but it is stuck in 'confirmation limbo' (not Slush's issue, TX fees were paid) "Estimated Confirmation Time 6 hours (queue position 782)", still has 'unconfirmed' status so it's not seen by our wallets. Edit: Just got the first confirmation. |
|
|
|
Anyone have an issue with 21384? I was hashing before, during and after the block with no downtime.
21384 2014-01-06 03:05:31 2:42:21 1435249005 none none 278862 25.18020923 88 confirmations left
EDIT: Several of you posted while I was typing the original msg. Thanks, I see it's been submitted.
I see it's fixed now. It was holidays two days ago, didn't you notice? Hallelujah!!!! (so 'it' happens only on major holidays?!) |
|
|
|
That worked last time.... wake up Slush.... |
|
|
|
hi all
it seems to be that we become the same problem as last week!!!
at least the 3 last confirmed blocks 278659, 278676 and 278690 gone confirmed in stats. but don't move from unconfirmed reward to confirmed reward
*edit*
lol same time posting i see it on the last 3 blocks dont know if it also before
Hi! Can somebody tell me why blocks #278690 #278676 #278659 #278652 is confirmed but in my account payment for this blocks is still unconfirmed? It happened last week too, something about the payout account getting to low so the whole payment systems halts until BTC is added. Don’t know if that is the case here but that is what happened last week I believe. It was sorted out after about a day. I have only been around here a couple of weeks but so far everything always gets sorted out. then we have to check every reward on this pool?! every time? well I would check any pool because honest mistakes happen. You should always be looking out for yourself and not trusting someone else will do it for you. Just my opinion. again!!! #278751 #278752 i wasn't paid! what hapend with this pool? 1 of my asic dont work all night!!! where is support!? You can add 21381 (block #278819) to that list. Confirmed in stats but not applied to 'confirmed reward' on the profile account page. |
|
|
|
21384 2014-01-06 03:05:31 2:42:21 1435249005 none none 278862 25.18020923 96 confirmations left
Whoopsy.. me too. I am assuming one of you guys put in a ticket? I don't wish to duplicate.
edit: I see the answer is YES. I wish people didn't claim "ripoff" every time there was a glitch. It always gets fixed eventually.
So as long one person files a ticket we are all good or should everyone effected should file a ticket? Ticket submitted |
|
|
|
|
Show Posts
