How far can a digital asset exchange go to shut down somebody’s account? As famous trader CoinMamba discovered, a centralized exchange like Binance can close accounts for the same vague, hand-wavy reason as any other financial institution — especially when its account owner threatens to create social media drama.
This week, Binance placed an account belonging to an influential trader who goes by the name ‘CoinMamba’ in withdraw-only mode after he claimed to have been a victim of an exploit of his account’s API key.
Specifically, CoinMamba has accused Binance of refusing to help recover the funds he lost to the exploit as early as December 6.
For context, most centralized crypto exchanges allow owners to create an API key that allows them to authorize trades through third-party applications. These secret keys are basically login credentials that allow traders to access their accounts and execute trades. A typical API key for a customer of a centralized exchange can execute an order of limitless size.
The exploit in question occurred after CoinMamba shared his API key with a trading bot provider called 3Comma. CoinMamba then claims that Binance restricted his account after he tweeted about a problem with 3Comma, that prevented him from taking advantage of market conditions to minimize losses incurred by 3Comma’s trading decisions.
Binance says it placed CoinMamba’s account into withdraw-only mode after the account holder posted threats in its customer service chat — and appears to have screenshots of the conversation to prove it.
Soon afterward, Binance gave CoinMamba 72 hours to withdraw assets before the company intended to close the account. He managed to withdraw the funds, as requested. CoinMamba then said he would audition new exchanges for better service.
CoinMamba and Binance disagree over next steps
With the account closed and de-funded, Binance suggests that CoinMamba report the alleged hack and nefarious trades to law enforcement. The exchange would assist law enforcement to investigate hacks. However, CoinMamba did not seem to file an official report, opting instead to blame Binance for the incident.
CoinMamba claims that his recent tweets were a factor in the suspension. However, another influential Twitter account using the alias FatManTerra accused CoinMamba of threatening to take the case to Twitter if Binance did not provide compensation for a scam by a third party. According to FatManTerra, Binance couldn’t compensate every victim who claimed to be a victim of a hack or scam.
Binance CEO Changpeng Zhao (CZ) confirmed that Binance could investigate, but he didn’t see it as a matter of providing compensation. According to CZ, an API key provided by 3Comma and used by CoinMamba may have caused the problem. He says he can block 3Comma’s API keys if CoinMamba cannot prevent the keys from getting leaked.
Read more: FOI reveals 20% of UK crypto fraud last year relied on Binance
According to CZ, traders can lose or “steal” their API keys. He said the exchange does not, as a matter of policy, pay for losses due to a misplaced API key. Binance documentation clearly states the risks of creating any API key.
In a previous tweet, CZ noted unusual trading activity after users shared their API keys with a third party. He recommended deleting the API keys altogether.
3Comma provides trading bots that traders can use on digital asset exchanges like Binance. For its part, 3Comma CEO Yuriy Sorokin claimed that CoinMamba’s keys were not leaked due to an error by 3Comma and recommended contacting law enforcement about the problem.
He also called CoinMamba’s case a strange one. He says CoinMamba claimed that he was using the spot API, but whoever allegedly hacked his Binance account had transferred funds to a futures/margin account and was, instead, making trades on these non-spot markets.
CoinMamba expressed concern that Binance has his personal information through its KYC/AML procedures and could theoretically dox him. At least one person who claimed to be a former corporate lawyer did not buy that Binance would be so cavalier as to dox CoinMamba over the dispute.
Moreover, another Twitter user opined that publicizing CoinMamba’s private details would be illegal. However, posting a screenshot of a snippet of a chat with customer service staff without identifying information was perfectly legal.
Read more: Binance denies using customers’ UNI for its own Uniswap votes
Mamba has decided to stop the drama
Despite initially following through on his threat to make details of their dispute public, CoinMamba has apparently simmered down a little and looks to have realized that picking a fight with the world’s largest crypto exchange is probably not going to get him anywhere.
In a tweet posted early Wednesday morning, the trader revealed that, after speaking with close friends, he’s decided to “stop the drama with Binance” and move on.
“I still don’t agree with how they handled this situation but I could’ve acted in a different way as well,” he wrote.
“It was just frustrating to lose a significant amount due to an exploit and emotions took over. Another lesson for me I guess.”
He also revealed that he’s opened an account on another exchange and will continue his trading there.
For more informed news, follow us on Twitter and Google News or listen to our investigative podcast Innovated: Blockchain City.
Source: https://protos.com/explained-binances-beef-with-crypto-trader-coinmamba/