No.

Gaming and using the card for mining/hashing/etc is completely different.

Perfect way to put it.  Thank you.

One change -
s/DeepBit/any pool or all the pools or any single weak point you synthetically create/$

I have the newest version.

Can someone quickly test against mining.eligius.st port 8337 or 80 ?

The beginning output says Long Polling was detected, but I get the warning about long polling failing every 20 seconds.

I'll one up your user directory of businesses with my browser integration....

How's bitcoin://1234567890addyHere:1.0amount:Comment to have the official client fire bitcoins off on mouseclicks?

I'm not sure you understand.  Knocking something offline doesn't actually accomplish anything.  Well, it shouldn't...

Security, including double spending, is enforced by the network itself.  Pools perform work ("hashing") to upkeep the network including verifying coins, coin transfers and generation.

If someone decided to take down the 4 largest pools (guaranteed to be over 50% of the network) then they could attempt to poison the chains for double spending and other fun stuff provided they could convince the leftover nodes their transactions were legitimate for some length of time.

If a majority of the network that is left over includes more private nodes than poison nodes.... the integrity can be maintained.

The security, both against double spending and other shennanigans as well as DDoS silliness, is built into the bitcoin network.  For the umpteeth time - pools create synthetic weakness.

What would be even more interesting......  Let's say an attacker could either spoof or otherwise redirect requests from a pool operators client.  Or perhaps manage to get that client to trust it as a node rather than the existing bitcoin network through the IRC mechanism.  Or the attacker was able to modify a bitcoin.conf to point to their poison nodes.  Not only could they contribute poison blocks but they could even just continuously send out unproductive (stale/corrupt) work.  The pools would appear up and working at 100%, but they wouldn't be performing the current work for network enforcement (or generation, of course).  Toss in a few poison nodes and double-spending would probably be achievable.  Even better - miners will think the pools simply aren't productive thanks to their misunderstanding of complexity and abandon the whole thing.

Even more interesting would be if the attack could intercept work from the clients and claim it.  Now there's no need to control the network for double spending - you've just made an attacker quite the rich individual and none of the pool's participants are the wiser until it's far too late.

Another factor is possibly crooked pool operators.  On the other hand, there is no contractual agreement - so really, there's no way to be crooked, now is there?  There are certainly no consequences.  There's a peer-trust faith that drives these pools with no governing body.  A pool operator could easily shut the whole payout operation down and walk away without any ramifications whatsoever.  The outcome becomes everyone hates bitcoins because the overclocker crowd is so vocal about "hackers" stealing their money.

So yes, for the umpteenth+1 time, pools create synthetic weakness.

tl;dr Hack hack hack, give me an easy target, pools create several synthetic weaknesses.

Ah, quite right.

I didn't mean to imply those were all rabid-overclocker-gpu-miners - only that there were more active clients.  Those clients probably aren't even doing any mining at all - just downloading the block chain while the user "figures this newfangled bitcoin thing" out.

In before -
OMG blah blah killowatt per hour blah blah take the case off blah blah Captain Planet will rape your children blah blah 5850 blah blah

You're doing it wrong.

They aren't installers - they are programs.

Try opening a command prompt, then navigating to where you saved them and run them that way.

You can try running them with "-help" or "--help", etc and they'll tell you what you need to supply.

After checking some of my nodes...

I have an average of 200 peer connections between all 3.

Today, I have over 700 connections.

So either all of the other bitcoin nodes have fallen down or there is a significant increase in the number of users with bitcoin clients looking for peers......

jgarzik's is nice, too.

I might not be understanding you or something....

Cards that do not support OpenCL (ATI) or CUDA (NVIDIA) cannot be used to mine.  CPUs (like the one in any computer) can be used to mine.  In fact, that's where the majority of bitcoins were mined before the GPU-only stuff came around.

The official Bitcoin client even has a built-in CPU-only miner.

CPU mining is arguably inefficient - a fast CPU gets 8MHs while a videocard that's much cheaper can get hundreds of MHs.

Nearly any miner can do CPU-only mining.  ufasoft is a popular one and is configurable to use a pool.

All of them?

Even poclbm will mine with a normal CPU on a pool.

ufasofts is another popular one that will mine against a pool CPU-only.

What brand do you have?

If you have a Sapphire, you should get the estimated numbers you're seeing other members report.

If you have a Diamond (or some other non-reference board) you will NOT be getting the numbers you see other members report and you will NOT be able to change voltages or reach higher clocks.

Random question -

The last time I tried this, it kept complaining about long polling failure while using eligius.st

Update -
I just tried it again and it constantly complains of long polling on eligius.

I'm also getting nearly 20% stale/invalid...

Ah, thanks, I couldn't quite find the words to put it as eloquently as you did.  All I could think of was "scheduling."

Something else that came up in another thread - on exit (signal, ctrl-C, etc) could you implement a "soft shutdown" that guarantees any pending blocks are reported ASAP?  I'm not sure how feasible that is for portability or if it would even be helpful, but.... it's worth a mention.

I hope you know that the *real* way to secure the network is to set up permanent nodes...

... NOT switch pools, right?

I mentioned in the other thread you were in that these "weaknesses" are synthetic weaknesses created by end users.  You're perpetuating that weakness with a fancy graph.  Even if all of the pools were only 25% and each pool had only a handful of work nodes....

.... it's just as easy to DDoS 12 machines as it is to DDoS 1.....

Not to be dismissive of the clever work you guys are admiring, but....

You all do realize that's just an Apache/PHP implementation?  It probably uses a few exec(), regex and maybe even RPC calls with the technology you already have.  It's more than likely extremely implementation specific and won't work unless you use exactly what he's using to mine.

I stopped reading when I saw all of those random drives.

Floppy?  DVD?  WD HDDs?  Media card reader?

Use your own common sense to realize all of those are about as useful as Christmas ornaments.

... and at 20% depreciation, you can still sell the miner's components for $800.

um0rion wins the thread.

Does us.mining.eligius.st work as a "normal" bitcoin node?  Is there any reason I shouldn't specify it via bitcoin.conf as a node I want to connect to every start up?

Also - how long do the payouts take?  It's been roughly 40 minutes since a block was discovered and my balance reached over the threshold of 1.0BTC... but no transfers.

Nevermind, I figured it out....