Quote from: LiQuidx on May 04, 2015, 08:32:08 AM

Quote from: shulio on May 04, 2015, 08:20:30 AM

Quote from: LiQuidx on May 04, 2015, 08:17:17 AM

Quote from: S4VV4S on May 04, 2015, 08:15:43 AM

Quote from: shulio on May 04, 2015, 05:50:31 AM

Quote from: Stunna on May 04, 2015, 01:43:14 AM

My apology for the delay & lack of professionalism. You didn't provide enough information to verify ownership of this account as you were unable to sign addresses. However, given the information you provided I can send the equivalent balance to a new account for you. Please email us back with your new username. We get at least a dozen emails a day from users claiming to be other users and we often lose sight of emails such as yours where the account-holder is not able to provide very strong proof.

I strongly recommend setting a password, email and backup bitcoin address under profile of your new account so we can quickly & securely help you recover your account in the future.

Stunna, doesnt that every account in PD got its own unique deposit address ? and of course only those who could login into the account will know what the address is, so if someone know what the deposit address of that account it, I think that is a solid proof that he own that account

Yeah, that is actually a good - valid point.
He should be the only one that knows that deposit address and txid.

Deposit Address changes from time to time so that wouldn't be a solution i guess..

Not really, although the deposit address has changed not too long ago but my point is that if you could know the deposit address than that means that you are able to logging into the account and owned the account isnt it?

At times people are posting their txids in they chat when the depo.. That could be exploited if that was the case.

Yes it could be , but what if he kept if for himself and Stunna/Edward only receive 1 support email regarding the deposit to that address? that will means that he is the actual owner of the account. If there is multiple people who claim to have the same address than this method could not be apply