Quote from: Astrocoin on January 28, 2014, 10:09:23 PM

Quote from: r3wt on January 28, 2014, 10:01:22 PM

Quote from: Astrocoin on January 28, 2014, 09:55:25 PM

Quote from: r3wt on January 28, 2014, 09:41:50 PM

Quote from: jdh015232 on January 28, 2014, 08:28:56 PM

Quote from: r3wt on January 28, 2014, 08:24:36 PM

Really, thats your retort? more baseless accusations? FYI, i updated to the latest source as soon as i knew about it. now i'm asking the question that needs to be asked. you instead of answering attempt to shift the focus onto me, which is the retort of children and immature adults.

and fyi, the genesis hash being wrong in the checkpoint file is a major problem, for obvious reasons. this is why your coin is forked, but by all means continue to tell me why i'm wrong and you're right.

just take astrocoin off your exchange and leave the astrocoin community if you think its a scam,nobody asked you to stay here
hes probably trying to get the price low so he can buy more since he couldnt steal enough coins...idk

Actually its because the coins were stolen, and i need to find out why, but nice attempt to switch the focus off the obvious scam dev team, which has been called out repeatedly.

once again, i'll post these transactions which should not be accepted by the client but are. why they are valid is anyones guess at this point.

http://pastebin.com/rtTTZ33p

using these transactions, the attacker was able to drain the ASR wallet on our site. its unclear how they were able to make these transactions appear valid. possibly a spam attack on our node with the illicit transactions? Again, i'm here asking for help, no reason to be butthurt.

If you're looking for help, making false claims that we changed the genesis hash and other BS that we're a "scam" dev team (In what way have we scammed? NO WAY AT ALL) when all we did was fix the bug in the code is NOT the way to get help.

I made no claims until you and your sock puppets started attacking my exchange, for simply asking these questions. lie about me i'll lie about you. again, the client is accepting these transactions, and should not be. that is what i am trying to find out here, is why. there was an attack on bitcoin in 2010=2011 that was similar to this. i'm trying to figure out if this is a limited incident, ie our node being spammed with the fake transactions, or if its a global incident in the network.

maybe you could check the transactions in your client and see if they are valid. if they are not, then it is obviously a problem with our node being spammed, and i would need to add a connect directive to conf file to only accept connections/blocks from trusted nodes.

Our wallets are fine, this must be an issue just with your exchange. I don't see those txids in the blockchain, http://cryptexplorer.com
or http://altexplorer.net... , not sure exactly why.

My apologies again. i know what happened now. could you pm me with some trusted nodes that i can use with the connect directive. i need some official, trustworthy nodes to prevent this again. I will accept responsiblity for this one.