Slush 50BTC BTC Guild GHash.io All DDoS'd at the same time. Will P2Pool save us? This is *very* suspicious and calls for attention  This has happened quite a few times over the last couple of years. In the end rollover to solo mining to keep the network safe. (And this is good opportunity to install and play with pool software if you're running an ASIC, since the client, of course, won't cope). Except, for many of us solo mining = no mining. There is a reason for pools. |
|
|
|
|
Geesh, it isn't bad enough that there is going to be a ton of new hashing power coming on line over the next week, they hafta take away what little i earn now with an attack? stoko!
|
|
|
|
 ...it's looking like it might be 1.4w/Gh/s ...at the wall!!  Wadda ya mean "it don't fit?"  |
|
|
|
Has anyone found a good Anker style hub that fits the depth of the Bitfury USBs? Right now I have 4 Red Fury USBs in a 7 port aluminum Anker hub and they fit perfectly but it kills me to not be able to use the other 3 slots, lol. I'd really like something with a similar style to the aluminum, squarish Ankers... no plastic or sleek design.  can you fit extension cords in the other slots? |
|
|
|
ok, I'm sett5ing up an old style blade. I have this issue: Also, a bit of a tip for fresh asic Blade Runners (heh):
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch. If you have a crossover cable around you can plug the blade straight into your network card in your pc. You will manually have to set the pc's Ip to match the blades current configuration for the ip subnet. Then navigate to the blade settings, change them to work with your router configuration. Then disconnect the blade and plug it into the router, it should find it by then. Restore your pc original Ip setting and you should be up an running Is a crossover cable really needed? i thought that i read somewhere that network cards autosense. or was that something else? |
|
|
|
xxxxxx 5:07:34+
20204 2013-09-28 14:59:00 2:29:29 167585958 103761 0.01674833 260589 25.36520000 60 confirmations left
20203 2013-09-28 12:29:31 6:12:36 420930780 239865 0.01634494 260573 25.05004290 44 confirmations left
20202 2013-09-28 06:16:55 15:59:47 1084831858 532510 0.01066657 260522 25.00830000 confirmed
I think we need more sacrifices. Bring out the virgins!
Where the hell do ya find a virgin in this day and age? |
|
|
|
ok, I'm sett5ing up an old style blade. I have this issue: Also, a bit of a tip for fresh asic Blade Runners (heh):
The initial post doesn't tell that your home network should be in the same subnet than your Blade. Blade's subnet is originally 192.168.1.x 255.255.255.0. My home network is 192.168.0.x 255.255.255.0, so I had a little bit of trouble at connecting the Blade's config page. The only thing I could do was to change my home network to the Blade's original one (and my PCs ip address too, at least to automatic and release and renew the address), change the Blade's subnet and other settings to 192.168.0.x and revert my home networks setting to the one that all my other network devices use (easier this way than to convert all the other devices to use 192.168.1.x subnet).
I'm not real comfortable messing with my router. Is there some other way to change the Blade to 192.168.0.xxx? Since this is a common problem they should have used more than one IP and made it selectable with a DIP switch. |
|
|
|
For your next assignment, figure out why the luck on several pools has gone down the crapper. heh, actually something doesn't feel right but i can't put my finger on it. It feels like the luck calculation is flawed in some way.
Similar to what I mentioned earlier talking with organofcorti: Bad luck is defined as a long period without blocks. That means at any given time, you're probably more likely to be experiencing bad luck rather than good luck. Good luck comes in very short bursts since they're defined as many blocks in a less than normal amount of time. Those bursts make up for that extended period of bad luck. The other issue is network growth is outpacing most pools, so they're losing overall network share. BTC Guild actually lost a bit of network share recently now that MegaBigPower went solo. The smaller your share of the network, the worse bad luck feels since the time it takes to solve a block that takes 5-9x difficulty worth of shares is much longer when you're only 5-6% of the network. So then the increase in overall hashrate without a proportional growth in a pool's hashrate would manifest as Bad Luck? That i can wrap my head around. |
|
|
|
I've seen our luck as high a 170%, so i guess 26% is within the realm of possibility. It sure doesn't feel right though. If the luck goes negative, do we have to give Bitcoins back?  as it is, we're like about 6.6% of the whole pie. Must the Gods deny us even that? |
|
|
|
Is it time to change Mh/s to Gh/s on your tables?
Done. This was something I started on a while ago and never finished. All numbers on the site are now in MH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH). Take a break man. heh did you mix up the Ms and Gs in this post?  Whoops. All numbers are in GH/s :p For your next assignment, figure out why the luck on several pools has gone down the crapper. heh, actually something doesn't feel right but i can't put my finger on it. It feels like the luck calculation is flawed in some way. |
|
|
|
Is it time to change Mh/s to Gh/s on your tables?
Done. This was something I started on a while ago and never finished. All numbers on the site are now in MH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH). Take a break man. heh did you mix up the Ms and Gs in this post? |
|
|
|
that is pretty sweet. |
|
|
|
Migration complete apart from ozbot
What is ozbot? |
|
|
|
|
once the miner is up and running stable, can we close the browser window? will it keep going with out it?
|
|
|
|
|
Is it time to change Mh/s to Gh/s on your tables?
|
|
|
|
I worked for 27 years as a software engineer. During that time our company never delivered on or before deadline.
Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law. http://en.wikipedia.org/wiki/Hofstadter's_lawI saw about 10 years of software engineering myself. This certainly always held true for our teams. I was once tasked with coming up with a schedule for a task. I came up with 1500 hours using the tools we were supposed to use to do schedules. One of the hardware guys, who liked to dabble in software, looked at my schedule and claimed he could do it in half the time. I refused to shorten my schedule and was taken off the project. My replacement came up with 1200 hours. When the job was done, it took 1800 hours. |
|
|
|
I don't like the auction format. do you have any plans to go to a regular pricing model after your auctions give you a ballpark figure as to what people will pay?  |
|
|
|
I've been quiet here, just watching all the noise. I worked for 27 years as a software engineer. During that time our company never delivered on or before deadline. There was a school of thought that said no matter how long you make the schedule, the people will stretch out their work to fill it. So, it became tradition to make schedules too short, knowing that they would be missed, just to insure that things got done as fast as possible. Sad I know. So, when i see deadlines missed here, i'm not surprised. Personally, i feel that any deadline that is met +- two weeks is quite an accomplishment. It seems that there are a lot of people here who take pleasure in seeing others fail. No matter what anyone says in this thread, it is going to take as long as it takes. And for those who think they are all that because they said someone wouldn't meet a deadline and they didn't, lets see you do better. KNC appears to be doing the best they can, give them credit for that and not their lack of accurate schedule making skills. |
|
|
|
Voodoo: oddly, the pool falls below 80Th/s and a block gets found. I wonder if the pool is having trouble dealing with the current amount of traffic, a scaling issue. or perhaps it is just coincidence.  Ive tried twice almost a week apart to get my 38GH/s bitfury to work with the pool, both with 1 and 2 worker accounts, and can never get past ~6GH/s even after 12 hours. yesterdays luck just made it all the more frustrating! I couldn't get my new Bitfury to work at all with this pool, it is currently mining away on BTCguild. I have a couple of ASICminer blades that i haven't bothered to get running yet. hopefully they'll work ok here. |
|
|
|
|
Show Posts
