Quote from: guruvan on April 01, 2012, 01:55:16 AM

Quote from: etotheipi on April 01, 2012, 01:20:04 AM

This sounds like the exact problem I was hoping to solve with Armory's signature blocks (and message signing just implemented in Satoshi 0.6.0). The only requirement is that the user's first ever deposit is with an address they exclusively own. All future deposits to their account can be through any means whatsoever.

Require the user to use one of their own addresses, X, for the very first deposit even if it's just 0.001 BTC. After that, any interaction they have with the casino must be through signature blocks, signed by X. ("I would like to cashout 12 BTC to the following address ... ")_signed_by_X. This is a guarantee that the same person who originally funded the account is the person who is sending you the message -- and that the message can't be altered on the way. After that first deposit, they can "refill" their account however they want (green addresses, friends, other addresses). Only the first one matters.

You can make all interaction between customer and casino as anonymous as Bitcoin itself -- they would not even need a login/password/email/anything. They only communicate through signature blocks on your webpage or email, and your software can easily check that the signature on the message matches X. Right now it would require manually creating the sig blocks, but it could eventually be a capability somehow integrated with a client or browser, just for this purpose. You could initiate SSL connections between casino and customer using public key X.

Of course, if you don't want pure anonymity, you can require more information to open an account, but there's a ton of flexibility with this method.

This has exceptional potential! (I somehow knew you'd have a significant chunk of solution for this!)

I'd still like to solve the first contact issue, and then solve the don't accept totally unsolicited funds issue, but this has a lot what I was looking for. (I hate to admit it's been a week or 10 days since I looked at Armory, and I've not had much time to dig all through it, it is the Awsum - I'll test the newest one tonight!)

Unfortunately, Armory's signatures are not compatible with Satoshi client's sign-message functionality. But, I plan to get it matching as soon as I'm done with RAM-reduction and compressed public-key support.

Also, the Satoshi client also doesn't use any kind of signature blocks: only "here's a chunk of seemingly-random data representing your signature, do whatever you want with it." It doesn't even have a GUI for verifying them. So I'm trying to convince the devs they should use some kind of signature block scheme which is user-friendly (relatively speaking) and easy to cut-and-paste into email or webpage. In return I'll switch Armory to use their signing protocol