Anyone else seeing this?
# Block found at Duration Total shares Your shares Your BTC reward Block # Block value Validity
21272 2013-12-26 05:32:42 0:41:38 294919785 none none 277006 25.12342259 99 confirmations left
I think, for me, it got made up for in block #21278... 21278 2013-12-26 15:58:16 0:00:27 2849511 252 0.00222816 277073 25.02399804 29 confirmations left ^^^^^^^ where I got double what I usually get per block. But, maybe that's just me. In my case it got fixed 'post mortem', and the reward reflected this. Happy End  (but why did we need to go through 'hoops' to get there....) Cheers |
|
|
|
Anyone else seeing this?
# Block found at Duration Total shares Your shares Your BTC reward Block # Block value Validity
21272 2013-12-26 05:32:42 0:41:38 294919785 none none 277006 25.12342259 99 confirmations left
me three. +1 |
|
|
|
Happy Holidays!!!! Big thanks to the Drillbit Team for all of your hard work.... Enjoy your achievements and look forward to some more cheers |
|
|
|
|
Hi LogicalUnit,
I have been following your mining blog, and learnt some things from your lessons. Following a similar path here, although started with GPUs, then BE's, then BF's and now augmented by some Drillbit miners (An Aussie product from Sydney!).
Enjoy your journey (and ignore the nay-Sayers).
Cheers
|
|
|
|
Hi,
i have a short question:
# Block found at Duration Total shares Your shares Your BTC reward Block # Block value Validity
21229 2013-12-21 00:36:48 9:39:26 4091124633 17590 0.00000000 276127 25.12559563 34 Bestätigungen ausstehend
My miner can't finished the block couse of an hardware problem but is it true that i get no reward or will it be calculated later?
thanks
deagel
It depends when did your hardware stop working, Slush uses an exponentially decaying function, the formula is somewhere in the FAQ or on this thread. In some cases the reward is reported as zero or low, then it is updated to the correct value. This may happen even if your system was hashing the full time. If you stopped hashing a long enough time before the block was found, then your reward will reduce to almost nothing. On the other hand if you hopped to another pool or had a hardware problem, but got back to Slush enough time before the end of the block, then you'll get essentially the full reward as if you were there 100% of the time... Thats meen the best way to loos not your reward is to mine with to workers. That if one is going down the second one safe your reward? the best way is to mine with all possible miners/workers that you have, and have a good power backup, good internet connection, then use a 'backup pool' so if your main pool goes down, you don't waste your mining resources and automatically switch to an alternative pool.... It probably doesn't matter if you group your miners into a single 'worker' or not, unless the separation into separate workers involves some redundancy that improves your overall reliability (such as if 2 workers have each a separate PC, if one PC fails the other one will keep going, but you'll have higher electricity costs...) |
|
|
|
Hi,
i have a short question:
# Block found at Duration Total shares Your shares Your BTC reward Block # Block value Validity
21229 2013-12-21 00:36:48 9:39:26 4091124633 17590 0.00000000 276127 25.12559563 34 Bestätigungen ausstehend
My miner can't finished the block couse of an hardware problem but is it true that i get no reward or will it be calculated later?
thanks
deagel
It depends when did your hardware stop working, Slush uses an exponentially decaying function, the formula is somewhere in the FAQ or on this thread. In some cases the reward is reported as zero or low, then it is updated to the correct value. This may happen even if your system was hashing the full time. If you stopped hashing a long enough time before the block was found, then your reward will reduce to almost nothing. On the other hand if you hopped to another pool or had a hardware problem, but got back to Slush enough time before the end of the block, then you'll get essentially the full reward as if you were there 100% of the time... |
|
|
|
|
difficulty just rose to 1180923195 (30% increase)
|
|
|
|
Hi all, I just removed the Block Erupters from my rig, leaving me with 3 Blue Fury ASICs connected to my MinePeon. I reset the command line to "default bfgminer" and now the miner starts and connects to my pools, but it does not detect the mining hardware.
What command parameters do I need to make Blue Fury ASICs work with bfgminer 3.3.0?
Thanks
There are instructions about miner and driver installation earlier in this thread (for example https://bitcointalk.org/index.php?topic=319419.msg3698786;topicseen#msg3698786). Good luck |
|
|
|
How high did you overclock it to test. I'd think default would use regular port power. Whatever Angus and tk are doing the 3.8.5 version seems to fix where I was getting alot of errors regardless of what they were. I've got 8 eroupters and an recommended overclock setting thumb with a fan with 8 HW errors back from 300 or so with 3.8.4.. I know Kano and ckolivias will commit suicide again but if the version of libusb has so many problems why not get a newer version (yes I said that  , its probably like updating visual basic to visual studio code ) The previous libusb problem I sorted out before, a few months ago, was in pretty much every version. The libusb problems ckolivas has been spending a lot of time sorting out over the past month or so are in the windows libusb version (not a linux issue) There is no newer windows version that handles these problems - the linux kernel already handles them - that's why they aren't an issue on linux. I am getting the USB timeouts with the Drillbit 3.8.4 cgminer build on Ubuntu 13.10 which is up to date, it's actually a clean machine I built just for the Drillbit board a week ago. They are pretty intermittent, like once or twice a day. erk, There is a new 'test' release of firmware and windows miner s/w at http://drillbitsystem.com/forum/index.php?topic=235.0. While you may not be using Windoz, the test version of cgminer fork (3.8.5, but only windows version at this point) seems a lot more robust in regards to USB errors in my case. Cheers |
|
|
|
+1 blockchain.info maybe inaccurate, however you are right that it offers no clues as to why this one is invalid...  |
|
|
|
|
Stats still 'processing' after more than 1 hour? (block 275090)
|
|
|
|
Payouts 'stuck' again? Edit: just got paid, thanks Slush!!!! |
|
|
|
YAY my 2 boards arrived today, oddly about 30 mins after sending barn an email requesting an update !! now for some reading and prep work to the desk Thanks again to barn and the team for a great GB. ( issues aside they were all delt with very well indeed ) When the nightmare is over for you chaps, drop us a line and im sure we can arrange a few beers to be delivered to drillbit HQ Happy Hashing.... (let us know how it is performing) Cheers |
|
|
|
|
pool hash rate is dropping, was close to 500TH/s now 430TH/s, also experienced some connection problems. Are we under DDOS attack again or is there something to be fixed/tweaked on our servers?
|
|
|
|
Barn, Thanks for the modded board. To provide an idea what it looks like  It has been hashing for a while, tried different settings. This is after almost an hour on int:50:2:950 (but results are similar to stock)  checking temperatures ambient 27.2 C large heatsink 32.1 C Power MosFets 30.7 C new Lin Reg 31.9 C (Edit: this is on the clip on heatsink, the regulator body is at 39.2 C now) top right hand BF ASIC (near board's corner) 29.8C (I posted a similar input at http://drillbitsystem.com/forum/index.php?topic=206.105) Happy Hashing!!!  ps: just completed the night hashing, no problems. |
|
|
|
As i already expected nothing has been arrived and no answers from barntech where my order is.
There is no trackable info found anywhere with the given code.
I see other people in europe got their items a few days ago, the usa people are already hashing.... here nothing and diff going up soon again
Where are you Bronan? I think that in Australia Barntech held off board shipping until the fix is applied. Cheers |
|
|
|
vardiff not working or my miner got crasy?
I have restarted it and now it sits on diff 3 for 15+ minutes
Same here. Cgminer had some message that it lost connection to the pool, now it sits on diff 3 (which is probably not the right one for a 20GH/sec miner)  No problem with either connection od dificulty setting here. It eventually fixed itself (I might have switched or restated the errant worker) |
|
|
|
There has been no payment for the last 21 confirmed blocks, this is at least 525 BTC.....(more than 400K US$)
Just got paid a few minutes ago.... Phew..... |
|
|
|
|
There has been no payment for the last 21 confirmed blocks, this is at least 525 BTC.....(more than 400K US$)
|
|
|
|
|
Show Posts
