I'm failing to see you're point on multiple pools. Even if there was 4 equal size pools it would take almost nothing to ddos 3 of the pools off the network causing everyone to surge to 1 pool. I'm sure these pool owners aren't operating a google size network where DDOS attack won't phase them. Even VISA and multiple other enterprise corporations fell victim to DDOS attacks all at the same time during the wikileaks fiasco.
I still say if the system has this big of a flaw it never should have been adopted in the first place. The bitcoin system reminds me of the Death Star from Star Wars... Just gotta fire a single shot into the exhaust and it blows up.
Which is EXACTLY why I asked Tycho to voluntarily take measures to keep his pool from ever going above 50%. When I asked this, simply closing registration probably would have been adequate, but that is no longer the case. What's to stop someone from starting their own pool then writing a trojan or using a botnet to mine for their pool for the soul purpose of attacking the bitcoin system. I work in the IT dept of a very large (lets call it a corporation) we have over 10,000 HP EliteBook 8540w laptops at our discretion. I'm mining from mine and getting 65Mhash/s without any visible difference to the video performance. Let's say I create a service to mine bitcoins and push the service out to all 10,000 laptops that would give me 650Ghash/s by myself assuming a perfect setup where all laptops are deployed, in use, and online. I would now control ~25% of the total hashing power. This is just small scale example; if you applied the same theory to a worldwide computing trojan which could get up to 1.4Thash/s... bye bye bitcoin
|
|
|
Stop mining when you want to watch movies or use a different computer/dvd player to watch movies, ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif)
|
|
|
I'm failing to see you're point on multiple pools. Even if there was 4 equal size pools it would take almost nothing to ddos 3 of the pools off the network causing everyone to surge to 1 pool. I'm sure these pool owners aren't operating a google size network where DDOS attack won't phase them. Even VISA and multiple other enterprise corporations fell victim to DDOS attacks all at the same time during the wikileaks fiasco.
I still say if the system has this big of a flaw it never should have been adopted in the first place. The bitcoin system reminds me of the Death Star from Star Wars... Just gotta fire a single shot into the exhaust and it blows up.
|
|
|
I just picked up a Radeon 5850 for $149 at TigerDirect on Tuesday and out of the box with no overclocking I'm getting 270Mhash/s with "-v -w -128 -f 60" The computer is still perfectly useable and there's only slight screen slowness. I'd say the 5850 is the best hash/$ if you're on a budget.
|
|
|
It sounds like you want to obliterate pool mining all together. Everyone go back to solo mining, problem solved, :p
Even if you keep all the pools under 50% two pools combined would be well over 50% which can do far more damage and faster than 1 pool over 50%.
|
|
|
Tycho, could u add some kind if information to account page, which would show time of last submitted share? My rig are on other floor and since Im changing sometimes clocks I'd like to know if rig is down faster than 30 minutes(the noise is terrible there, so I cant stand being ther more than 2 minutes...).
It sounds like you're referring to the Failure Detection Threshold. If you setup a separate worker for each rig and set the Failure Detection Threshold as low as 1 minute you will know if a rig is down because the worker will turn red if it hasn't submitted a share in the last minute. This doesn't necessarily mean it's down though... I have mine set to 10 minutes and sometimes it will turn red as if its down, but it's not, just took longer to submit a share.
|
|
|
I use what I have available to me, and that's what I have, ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) Each laptop does 65Mhash/s so I wouldn't call it stupidly inefficient. Free Mhash is free Mhash
|
|
|
I'm mining from 11 laptops all off of a wireless 1.5mbit dsl line. No problems here boss.
|
|
|
All aboard the 1Thash/s train! toot toot!
I say if a system can be brought down by something as simple as going over 50% then it was a poorly designed system and never should have been invented in the first place. Might as well test the theories on the 50% rumors now rather than later.
|
|
|
any chances on extending the 7 minute average to show a more stable number for us light miners?
You already can... It's under "My Account" then "Advanced" button, 3rd input field down. I set mine to 30 minutes and it's even less accurate it seems like, my GPU does 40Mhash/s stable but 30 min average shows usualy between 20 and 30 Mhash/s
|
|
|
Bah, this is bizarre.
I managed to get it working on one laptop with the FirePro M5800. After uninstalling and reinstalling drivers and SDKs over and over somehow it started working. However I have a second laptop the exact same model/hardware when I installed the drivers and SDK it says OpenCL is not supported with the current drivers though they are the exact drivers from the first laptop. After messing with it for 2 hours like I did on the first, still not working, :|
I managed to get 60Mhash/s on the first Laptop with the FirePro M5800
|
|
|
Hello, I don't see any topics on the FirePro laptop graphics cards. I have an HP Elitebook with the Firepro M5800 and I saw on this page " https://en.bitcoin.it/wiki/Mining_hardware_comparison" That it can do 60Mhash/s on ubuntu. I have installed the latest graphics drivers and the SDK 2.4 but in windows 7 it does not detect it as an OpenCL device it only detects the CPU as OpenCL. Does this mean the FirePro cannot be used in Windows 7 to mine? Or is there something else I need to install to get it to work?
|
|
|
My hashrate is 'round 24.4 MH/s (seems the average somtimes reaches up to 'round 30 somtimes, but most of the times i look at the miner proggie it says it's going at 24.4 MH/s), which mode do you suggest for me? There is a description of both reward modes on the registration page and on each worker's page. Can you please tell me what was unclear for you in those descriptions so I can improve that text ? Since I'm in a similar boat with about 30MH/s I would say it's confusing because I assume at this slow of a hashrate I wouldn't be submitting any shared blocks fast enough to get any BTC from proportional. I read in the forum that PPS is better for slow hashrates and proportional is better for higher hashrates but no one gives examples of what is slow and what is fast. If above is true maybe add a recommendation to the description? PPS: recommended for 100MH/s and slower and PROP: recommended for 100MH/s and faster. OR w/e the true/accurate hashrates would be recommended for each.
|
|
|
I seem to be having an issue with multiple works on deepbit.
I have my main worker which is working fine, then I created a second one with *****@gmail.com_0
on GUIMINER I have a GPU worker and a CPU worker. GPU is using OpenCL and is working fine.
I created a new OTHER miner and selected the CPU Miner "\guiminer\miners\puddinpop\rpcminer-cpu.exe" put in my second worker ID with the _0. Im getting 5Mhash/s from the CPU however it doesn't appear to be connecting to deepbit account, the accepted rate is not going up and the worker is still showing red on deepbits.net
did I set it up wrong?
|
|
|
I see, yeah, I switched to deepbit and I'm having no issues now. Thanks.
|
|
|
Hi I am trying to do the mining pool but I keep getting the error "Problems communicating with bitcoin RPC" when I specify a host/port in poclbm.exe
If I don't specify a host/port it works fine but then I am not apart of the pool I guess.
I have forwarded port 8332 from router to my PC. I am using windows 7 64bit and I have enabled port 8332 for both inbound and outbound traffic in the win7 firewall. but I am still getting the RPC errors. Is there something I am missing? maybe a special way to enable it in the win7 firewall?
Im using both cmd line proclbm with following command: start /DC:\Users\Mike\Documents\bitcoin\poclbm_py2exe poclbm.exe --host=mining.bitcoin.cz --port=8332 --user=login --pass=password --device=0 -w 128 -f 60
I tried the GUIMINER but i get same error although every 15 mins or so on guiminer it looks like it does connect cause my Accepted thing went up even though console is spammed with the RPC error.
|
|
|
|