Um, devs... whats going on? I woke up this morning to a TON of error messages. The socialcoin wallet, when making new addresses for new users, was giving out addresses that ALREADY BELONGED TO OTHER USERS!

How is this possible? Why is the wallet giving out duplicate addresses.

And by this I mean on April 11th user 1234 generated an address and the wallet said here you go, and gave him the address S12345. This address was saved in the database and linked to user 1234.

This morning, user 4321 signed up and wanted to deposit some socialcoin, and clicked the 'get me an address' button. The socialcoin wallet said "Ok, here you go!" and TRIED to give him S12345!! Thankfully, the database saw the collision and didn't allow it. However, now internal wallet accounting is off because user 1234 no longer owns the S12345 address! What the heck? How can the wallet possibly generate the same address twice? What kind of RNG are you guys using?

And it didnt happen once. It happened SIX times this morning!

How dangerous is this wallet? How many others wallets are generating addresses that other people have?

Just confirmed with Poloniex that new addresses aren't duplicates and they have no duplicate addresses in their database at present

allcrypt can you check your database and make sure it isn't something weird at your end

allcrypt, I'm not the original developer but I did the last update and looked through the code (changes from original). So let me try to assist you until SocialCoin replies.

The wallet isn't doing anything different when it comes to generating addresses except from starting with a capital 'S'.

Can you try to generate a new address with a rpc call from the command line and see if that address is already in your database?
This way we can determine if the error is in the wallet or your code.
Which command you use to generate a new address?

I don't know the code of your site, but are you using any caching mechanisms like xcache, apc, memcache?
It sounds like your application is caching the addresses somewhere and reuses them.

I will go through the code again now and see if something weird is happening but I advise you to look in to your code as well because the error is probably caused in there.

Are you sure it happened to legit users?
Since generating new addresses gives no conflicts and it stopped happening, your site may have been under attack.
Maybe someone tried to overtake someone else's wallet or some other attack.
Poloniex was recently hacked by sending the same order multiple times at the same moment.

Did you find anything out of the ordinary in the coind or webserver log files?
You should be able to track the http request and match it to the rpc call. If the call isn't showing in the coin's debug.log you have caching enabled or there was an attack.

Allcrypt, we are just making suggestions while also looking at the wallet code, like how you can't see it would be something on your site, we can't see it would be something in our code. Just let us know if it actually happens again, we will let you know if we find anything.

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.

Hi there, AllCrypt.
I'm afraid there's a very slim chance this will happen and I really believe this is something in your code site.
I remember seeing a message you guys wrote regarding another coin with the exact same issue so my assumption is there's some kind of bug in your system.
As MinerX said - The code we use to generate addresses is identical to the code used in Litecoin (other than the version) and there's absolutely no reason for this to happen.
Also, Poloniex does not have this error and he's live for quite a while (around 2 months) and generated an address automatically for every new user in the system.

So again, I'm sorry to say this but it sounds like a problem on your end.

Thanks for your support of the coin and good luck in solving this.
We're here to help with anything you might need.

hello , i have just updated the wallet with the new one on page 1 , but it wount get sycned, no connections, please tel me what to do


best regards Paulus 51

Paulus51, I see you have save the greyhounds in your sig. Would it be possible for SOC to add this organisation to its monthly donation vote?