[Payout Updates] Bitcoinica site is taken offline for security investigation

[realnowhereman]

I have sent additional information; but GPG encrypted (you should have explicitly supplied a key for that purpose) to genjix's public key, 634FEC67.

Could genjix confirm that that is a reasonable key to encrypt to?  If not, please supply another.

Given how insecure email is, I really don't want to be broadcasting unencrypted personal information all around the Internet.

[1714839827]

1714839827

[1714839827]

1714839827

[1714839827]

1714839827

[1714839827]

1714839827

[1714839827]

1714839827

[Mushoz]

I have sent additional information; but GPG encrypted (you should have explicitly supplied a key for that purpose) to genjix's public key, 634FEC67.

Could genjix confirm that that is a reasonable key to encrypt to?  If not, please supply another.

Given how insecure email is, I really don't want to be broadcasting unencrypted personal information all around the Internet.

Great idea, and I agree! We need a public statement on how to send verification details. Genjix, could you please comment on this?

[Mushoz]

Genjix, is it okay if I use your public PGP key to encrypt the data before sending it to verify@bitcoinica.com?
And if so, what public key would you like me to use? Thanks.

[genjix]

Genjix, is it okay if I use your public PGP key to encrypt the data before sending it to verify@bitcoinica.com?
And if so, what public key would you like me to use? Thanks.

Hey, this is my valid key: CCF588E3. The other one is old and I need to revoke it. Make sure you mention it's encrypted for me.

Also avoid sending things to my personal email if you want to keep it secure. That email is used on public terminals and is not secure - it's a personal email. Otherwise if you don't mind then you can CC me, but make sure it does actually get sent to verify@bitcoinica.com

[Mushoz]

Genjix, is it okay if I use your public PGP key to encrypt the data before sending it to verify@bitcoinica.com?
And if so, what public key would you like me to use? Thanks.

Hey, this is my valid key: CCF588E3. The other one is old and I need to revoke it. Make sure you mention it's encrypted for me.

Also avoid sending things to my personal email if you want to keep it secure. That email is used on public terminals and is not secure - it's a personal email. Otherwise if you don't mind then you can CC me, but make sure it does actually get sent to verify@bitcoinica.com

Hmmm, how do I encrypt my file using that key? I'm using the following PGP GUI:
http://gpg4win.org

Never worked with PGP before, so this is all new to me. It's asking me to use a certificate, but I want to use your key instead. How can I make the program accept a key rather than a certificate?

[rjk]

http://pool.sks-keyservers.net:11371/pks/lookup?op=get&search=0xCCF588E3

[Mushoz]

http://pool.sks-keyservers.net:11371/pks/lookup?op=get&search=0xCCF588E3

How did you get that? Thanks!

Edit: Sign & Encrypt, or just Encrypt? Just encrypting should be good, right?

[Mushoz]

Thanks for all the help guys! Mail has been sent. Hopefully this will speedup the process of returning my funds.

[btcgoldsilver]

I understood that the claims process would be a case of matching people to accounts?

But now wondering if Intersango/Bitcoinicca don't have any account info at all ! Is the claims process actually trying to recreate lost account info first based on the claims people file?

which case is it?

[flower1024]

30 May 01:52: Consensus seems to have been reached. Waiting for final confirmation to move ahead so we can work out the actual payout implementation specifics.

any progress?

[MelMan2002]

30 May 23:30: We're going to proceed with payouts of the few people we have verified hopefully tomorrow for 80% of their claims (the remaining 20% will be refunded later). A more lengthy process will be applied to everyone else.

Indeed - any payouts yet then?

[Maged]

Is the claims process actually trying to recreate lost account info first based on the claims people file?

Yup, that's why this sucks. They have the money, but they don't know who it belongs to.

[rjk]

Is the claims process actually trying to recreate lost account info first based on the claims people file?

Yup, that's why this sucks. They have the money, but they don't know who it belongs to.

According to this they might have something: https://bitcointalk.org/index.php?topic=81045.msg922321#msg922321

You can assume that we have the database now. The reconstruction work is much simpler than what I thought.

[Transisto]

According to this they might have something: https://bitcointalk.org/index.php?topic=81045.msg922321#msg922321

You can assume that we have the database now. The reconstruction work is much simpler than what I thought.

Yeah saw that on "May 25,"  

We can assume you have it, but you don't.  That's recomforting.

[ninjarobot]

Oh boy, how I enjoy waiting! It is just so much fun to visit this thread every single day for little scraps of info to feed my slowly dwindling hope of ever seeing my deposits back. I just love wasting my money *and* my time. Thanks Bitcoinica! You sure know how to treat your customers right.

Translation: I am not amused. It has been 22 days since the hack. Nobody has seen a (bit)cent back AFAIK. You are sitting on ~$1 million of user deposits. An update would be in order.

Oh, and please don't use weasel words like 'soon'. Give us a date. When do the refunds start? When do the refunds end? Clear & Simple. Let's get this over with already.

[genjix]

02 June 2012 21:26: The process is at an impasse because of some legal wrangling.

[Raoul Duke]

02 June 2012 21:26: The process is at an impasse because of some legal wrangling.

hmmm... I remember someone mentioning your lawyers in the other thread.
Wonder if it has something to do with this and the guy had a prophecy...

[bitlane]

......the guy had a prophecy...

Epiphany ?

[Vladimir]

......the guy had a prophecy...

Epiphany ?

common sense?

[bitlane]

common sense?

The greatest example (at times) of an oxymoron and paradox all rolled into 1...LOL
Common....yet not so.