Not just that. Since they don;t hash themselves(they control a hashing machine) they don't need much computing power. You save on power costs for extra support equipment.

Regarding the auto-payout, it's not just that. It would be a website, buying and selling automatically, etc, etc. PM me if you'd like to discuss it, and I'd be glad to explain what I can do and how much I'd need.

You're handling wallets and payouts manually? I could probably code up a pretty comprehensive web frontend for managing this, but due to the likely downsides or setbacks of this idea, I'd have to discuss that over PM.

That said, some sort of automation and database would make your life easier, and you shouldn't have to care about what type of wallet the end-user uses. Offer them a paper wallet but let them keep money in your own cloud (on accounts that they have with you) and let them cash out to whatever wallet at whatever time, be it paper, web, or desktop client.

Don't think it'll be remotely profitable for you or your customers without ASICs.

You stated so indirectly. In order to steal coins from most transactions, ECDSA must be broken.

Doesn't look like OP's been around for a while now. Even so, the prices would need to be updated to match current exchange rates.

How big is this room? I doubt 10,000, though it's quite possible as we still barely know what we're dealing with.

Due to the onion nature of this i'd suspect illegal/questionable content, so I'll have to decline my previous half-offer.

Are you going to need random URLs never linked to inside the site? And would Java be acceptable?

So people would then begin to proxy onto little-used subnets.

Anyway, if foocoin were to make it out into space via satellite or radio transmitting the blockchain the IP address would lose any and all significance.

Same here. That being said, that's not that much.

A server's a server. It can do most hash calculations, though at varying speeds. Try mining both (not at the same time )and see how your luck holds out.

I'd be more specific but the details you give are too vague.

E10446:

Mine, and hope to pull a profit. Install a miner like CGminer or for Windows GUI people, *shudder*, GUIMiner, and set it up to use a pool like bitcoin.cz.

Anyway, are you sure the server is really 240GH? It's more likely 240GB which has nothing to do with mining power.

What if the incentive to mine in pools in the first place was lost? What if people could generate coins in small amounts using low-difficulty hashes, and then redeem those coins through a special txn inserted into a block (created by someone that met the high hash difficulty)? It wouldn't create too much more txn spam as mining pools already send coins out to small miners in small denominations.

Naw, PHP is better for handling individual requests, and is somewhat hard to daemonize. I would recommend Java as you can thus have a coin-game backend and a possible web service meshed together natively. With that said, this isn't something you'd do on your average web host.

You'd write a script or server program to handle it automatically, from something as simple as a loop that waits for txns to come in, to a large operation teeming with cronjobs and database storage for auditing.

Huh,. I'm not sending a Host header properly, most likely, but I'm trusting the cert nonetheless.

Is this the kind of thing we'll be remembering as the inputs.io of the meme world?

OK, as it looks, neither side is cloudflared.  Still kind of suspicious. I'm still seeing 5b 3e 9a 8f 37 c8 a9 4c 94 97 8d f5 11 16 7d 44 a2 bc 22 16

That's good news. At least the forum hasn't been cloudflared, though it doesn't rule out a bad cert.