It wasnt an attack. No one attacks a site by generating a single wallet address. They also don't then send you a pissed off support ticket that they cannot make a deposit address.
And caching, which I already said we do not use, would not randomly give me back a very specific RPC call response from a week ago, while both before, and after that, ignoring the cache.
It's obvious you are absolutely convinced that there is no possible way in hell that it could be your wallet, so, nevermind.
And caching, which I already said we do not use, would not randomly give me back a very specific RPC call response from a week ago, while both before, and after that, ignoring the cache.
It's obvious you are absolutely convinced that there is no possible way in hell that it could be your wallet, so, nevermind.
allcrypt, I understand the stress you're in right now with the responsibilities for people's money.
We're trying to help you out.
My personal method is to rule out all the possibilities to find the problem. I can only look in to the SocialCoin code, not yours so I have to ask you all these questions in order to move forward.
I am not suggesting there's anything wrong with your code, I am simply trying to find and fix the problem as fast as possible.
Caching seemed like a possible culprit if expiry is left to 0.
If things work normally, then don't and then work normal again, it's safe to assume there was some form of attack. Maybe against the wallet, maybe sql injection to hijack other users accounts/wallets.
I would like to see this problem getting fixed. Crypto doesn't need another exchange getting in trouble and if it's caused by the wallet, the problem may be spread across every bitcoin/litecoin derivative.
If you want we can get in touch on irc and work on the problem more directly. PM me if you want.