2 min read
Tesla CEO Elon Musk and Binance CEO Changpeng Zhao (CZ) today got into a Twitter feud following issues surrounding Dogecoin withdrawals on the cryptocurrency exchange.
According to Binance, issues encountered over Dogecoin withdrawals are down to a “technical issue” caused because the exchange has “a different technical wallet set-up for DOGE.”
“Since the incident occurred, DOGE Network has been providing us with support, but we have to rebuild the wallet entirely, which is causing a delay that we expect may last another week or so,” Binance added on Twitter.
The honorary “Dogecoin CEO,” was less than pleased with the exchange’s update.
Musk took aim at CZ over the issue today on Twitter.
“Hey CZ, what’s going on with your Doge customers? Sounds shady,” the Tesla CEO said, adding that “Doge holders using Binance should be protected from errors that are not their fault.”
Binance’s official Twitter account was the first to respond, saying the issue was “not shady,” but “frustrating and we’re working on it.”
The Binance CEO also chimed in via his personal Twitter account.
“Elon, we are pretty certain it is an issue with the latest #doge wallet. We are in communications with the devs. Apologies for any inconvenience that may have caused you,” CZ said, before ending his tweet with a link to a Tesla software glitch that caused nearly 12,000 Tesla cars to be recalled over safety concerns.
Amid the Musk and CZ drama, Dogecoin developers—tweeting under the account @dogecoin_devs—attempted to provide some clarity.
“A bit over a year ago, Binance notified us that they had stuck transactions. We were not shown these transactions, but it was suggested that they were stuck due to insufficient fees,” the devs tweeted.
Binance—according to the developers—opted to “resend/reissue” these transactions and were instructed to invalidate the stuck transactions by the replacement ones. “We were not notified as to whether or not they followed these instructions,” they added.
Today, the developers have said they believe the previously stuck transactions “have been retired automatically.”
Decrypt-a-cookie
This website or its third-party tools use cookies. Cookie policy By clicking the accept button, you agree to the use of cookies.