 Show Posts
|
|
Pages: [1] 2 3 »
|
|
Ok, just caught up. The analysis makes sense and we are comfortable enough to bring XMR back online. Crisis averted, happy trading!
R.
|
|
|
|
If you want IPs, get a legal request for information, such as a court order. It's best to have a "chain of custody" so to speak when it comes to things like this. If we handed out IPs to any random who asked, and violence of some sort ended up happening, then we would be on the hook if we couldn't show a paper trail of who requested the information. If you are on the up and up and don't plan on doing anything illegal, then there shouldn't be any problems with this. Court orders (which, again, are just a legal request for information) are standard when requesting information from third parties.
Thanks for the response BadBear, would you be able to tell us if the accounts in question have overlapping log ins from the same IP? That would answer the question without disclosing any information that could cause you legal or ethical problems. There is a considerable amount of BTC riding on this decision, any help you can render would be greatly appreciated. R. |
|
|
|
Not entirely Bittrex's fault, but they DO bear some responsibility for ICOs they host.
The need to step up to the plate and put an end to this crap.
We did not host this ICO. Although you did not host it, if you agreed to destroy coins, you shouldn't have listed it until the coins were actually destroyed. Common sense should have told you that there was a danger to having such a large premine sitting out there... and was there any real harm waiting 24-48 hours before listing the coin? Not like c-cex would eat up all of the trading profits going on. They aren't exactly an exchange juggernaut with tons of volume. Except your time line is all wrong. We were asked to destroy the pre-mine AFTER the coin was already listed. No good deed goes unpunished. In the future we will likely not offer our services in destroying coins so as not to get dragged into these scandals. |
|
|
|
i'm speaking for NEW accounts.. and if one dude makes 20 accs to scam from .. another fraud detection system should raise red flags .. one IP in multiple accounts... even paypal does that  I understood you meant new accounts, I was just wondering how that would necessarily matter, if a dev could just make multiple accounts, or even just one account a month or more earlier. I do agree there should be an ip block on multiple accounts, or let's say no more than 2-3. There could be valid reasons for needing more than one account, such as a person's email going down, or some weirdness like that. Again, not sure how that would necessarily stop a dev from scamming if all he needed is one account a month or so old. Can't, a good number of our best traders use TOR for various reasons of their own. If we banned TOR we would have a significant an influential portion of our user base out for blood. |
|
|
|
Not entirely Bittrex's fault, but they DO bear some responsibility for ICOs they host.
The need to step up to the plate and put an end to this crap.
We did not host this ICO. |
|
|
|
A very basic security feature, as every scam dev makes new <bittrex> accounts:
Limit the maximum withdrawal issue for those new accounts to 1 BTC per hour..
This way no scammer can scam for more than 1 btc .. which would make them walk away from bittrex at least.
The Dev here scammed for 20 BTC in a matter of minutes.. Its totally freakin' unbelievable that you (bittrex) allow someone to withdraw more than 20k USD (in btc) in a matter of minutes..
In EVERY security/fraud detection system of the world this transactions would raise like ALL the freakin' red flags of the world...
Trivial to circumvent, and in this particular case completely ineffective. The account was created 2014-06-04. |
|
|
|
|
Trading is now open, pardon the slight delay.
R.
|
|
|
|
|
{
"hash" : "265b783dace907be43d64b47d85dc7e6d2f01cf14771bb1ac579582b24de0a57",
"confirmations" : 1121,
"size" : 264,
"height" : 1101,
"version" : 4,
"merkleroot" : "8f4ac5efb44cfc9325f222f15bfb50b3dda4f49500d1f510f9928c10b236c301",
"mint" : 8888.00000000,
"time" : 1408057851,
"nonce" : 2674529111,
"bits" : "1b6bfffe",
"difficulty" : 606.80572702,
"previousblockhash" : "0000000000676a85677427e80f023738d11b6493262706c8bfb1f9200cdf7ed9",
"nextblockhash" : "7d58f75fb575e73fbea06b7d1390ee72301582c8aa221962b0f70203c11643c8",
"flags" : "proof-of-work",
"proofhash" : "265b783dace907be43d64b47d85dc7e6d2f01cf14771bb1ac579582b24de0a57",
"entropybit" : 1,
"modifier" : "4e804e9b388e8d6c",
"modifierchecksum" : "ab502563",
"tx" : [
"8f4ac5efb44cfc9325f222f15bfb50b3dda4f49500d1f510f9928c10b236c301"
],
"signature" : "304502201720c3b9dd90b1a0d27576eff054e7513d1e1dea039b39a217966ef204685a6e022100d 9f3e2db2c1a20d6befadcbc6a696cbfc7b96d7df7f06b92d3f88107025294c1"
}
|
|
|
|
|
Fraud check sentinels reported a false positive and woke me out a nice deep sleep. I was dreaming of explosions and other pleasant things... secondary audit turned up nothing and we verified externally that everything checks out. Market and Wallets restored, sorry for the downtime. Now if you'll excuse me, I'm going to pass out at my keyboard... g'night.
R.
|
|
|
|
|
Sorry for the lack of updates. I don't think we will be turning this back on. The block-chain is completely compromised, any rogue wallet can mint any amount of coins at will.
|
|
|
|
+1 .. that's my current theory also. R. |
|
|
|
Update: I've cancelled all existing orders on the BTC-USB market. Reading through the code again, not seeing an obvious pre/post mine.
what is the total money supply you have? When I got woken up it was "moneysupply" : 25556953.26293174, but just a few minutes ago it jumped to "moneysupply" : 45554954.73594906. |
|
|
|
|
Update: I've cancelled all existing orders on the BTC-USB market. Reading through the code again, not seeing an obvious pre/post mine.
|
|
|
|
|
Got woken up by Ryan when he caught wind of whats going on here. I disabled the wallet and market about 45 minutes ago, investigating further.
R.
|
|
|
|
|
Working to unfreeze the markets. venividiteam has been very helpful and has offered to cover any orphaned deposits, just through you should know.
R.
|
|
|
|
|
We've had multiple 15+ confirmation transactions orphan, will follow up with the developer. Market trading has resumed, but the wallets will remain offline. Sorry everyone.
R.
|
|
|
|
|
Does this look correct to everyone? BCE is obviously stuck.
Block: 4532
Hash: 91c324ac7427385270c3b6d0cb374dfcaa7a6b36fc5258a564a3484f24eab0ed
R.
|
|
|
|
|
Just got paged, investigating.
R.
|
|
|
|
Finally back on Slowtrex
I probably shouldn't reply to this... but please have a little patience. We do extensive auditing in these scenarios to keep coins safe, these audits take time. I know its frustrating, but in this business we prefer to error on the side of caution. R. |
|
|
|
|
