cads: if random keys were engineered so that whitespaces and symbols appeared less frequently, that would reduce security of keys of a given length, but that might not be a bad solution.

cads: If they did, vanity addresses could be a lot nicer in the front end. But then all addresses would look a lot uglier everywhere else.

cads: it's a damn shame that public keys can't include punctuation or whitespace!

cads: Anyway, that's all I have. </math> </rant>

cads: If Bob has clients that will actually trust him with their private keys, he can _also_ test each P(B) with an "interesting prefixes" algorithm, and build up a database of keys that he can sell to customers at a lower price than his fully secure keys.

cads: If Bob is given a list (U_1, V_1) .. (U_n, V_n) of pairs of public keys and target prefixes, then he can economize a great deal. For every private key B that Bob computes, he can compute P(B) once, then test whether P(B) + U_k has prefix V_k, for any k in 1 .. n.

cads: Oh, I made a small error. s/a vanity address V/a vanity address with prefix V s/such that P(B) + U = V/such that P(B) + U has V as a prefix.

cads: Two parties Alice and Bob can generate a vanity address V with no trust. Alice generates a random private key A, and sends Bob her public key U = P(A). Then Bob finds private key B such that P(B) + U = V. Bob delivers B to Alice, and Alice's brand new key is A' = A+B.

cads: Let P : Priv -> Pub be a function that takes a ECDSA private key to its public key, and let A, B : Pub be two public keys. Then P(A+B) = P(A) + P(B).

cads: I only know what I've learned in the half hour I've known about it, but it seems to be very scalable and fault tolerant - a reasonable usecase may be to use it in in on a load balancing cloud backend to aggregate all the realtime stats, and feed them to users on a well styled JS frontend.

cads: I recently ran into graphite, a tool for high performance, mission critical real time data graphing, http://graphite.wikidot.com/faq

cads: thanks for the leads, parseval

cads: what're you using as the charting backend?

cads: thanks for the input guys!

cads: a site with better marketing than vanity pool may increase the demand for vanity addresses enough to make the enterprise worthy

cads: I'm thinking it might be most economical to throw a vanity miner into the cloud, if the demand is high enough

cads: so I could use these guys as a marketplace for my own services if I wished

cads: I'm learning that!

cads: oh wow, that scheme is brilliant

cads: vanity pool seems to let people in the community do the work and submit it

cads: seeing one implemented as a TOR hidden service

cads: I'm seeing a forum post where a person offers to generate 3 or 4 sufficx vanity addresses for 0.10 BTC, lol

cads: I'm assuming that if such a service exists it would implement a novel secure handoff procedure.

cads: nevermind that only chumps would pay for someone to generate a public/private key pair and then give it to them so they can use it.

cads: hey guys, are there any services out there that take BTC and give you a vanity address of your choice?