So, if my holdings is 80k and the price of doge is 70k then I will be able to withdraw 10k.
Any reason why they're counting their
scam in dollars and not in Doge?
They say
Binance is actively working with the DOGE project team to resolve the issue. This sounds like they're once again trying to reverse transactions.
Nice to see they (ab)use their fuckup to pretend their made-up centralized tokens are real Doge:
users are still able to withdraw DOGE on other networks during this time.
I can't find any of this on Binance's own site, only external sites mention that Binance is blaming their users for their own problems.
Providing some clarification the Binance situation: 1) 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...
2) Binance opted to resend/reissue these transactions. We instructed Binance to use the inputs to the stuck transactions to force them to be invalidated by the replacement transactions. We were not notified as to whether or not they followed these instructions...
3) Binance later notified us that they had account reconciliation issues. We were unable to reproduce those issues with the data we were given by Binance, but we suggested (months ago, now) issuing -zapwallettxes to mitigate the issue...
4) Yesterday we were notified that previously stuck transactions (insufficient fee) had suddenly relayed successfully, post 1.14.5 update - likely because minfees have been lowered in 1.14.5...
5) The sole example we have, from Binance, is a transaction with fees which are valid as of v1.14.5, but were invalid (too low) in 1.14.3 and before. Note, Binance updated directly from v1.14.3 to 1.14.5, in the past few days...
6) Currently what we believe has happened is the previously stuck transactions have been retried automatically, as would happen on each node restart after upgrade - and went through, since now the minfee is lower....
7) Takeaways: Invalid transactions don't have a defined timeout limit, but are typically disposed of due to memory limits. However they can hang around if mempool isn't maintained...
8) Correct handling to cancel a transaction is to spend the to-be-cancelled transaction's inputs to a different transaction, which invalidates the first...
9) For any providers with concerns about stagnant invalid transactions, we recommend stopping the nodes, removing the mempool.dat file just in case, and then starting the node with -zapwallettxes....
10) Moreover, this should likely be done as a routine maintenance practice; especially if you know that a number of invalid transactions have been reissued.
TL;DR: Binance messed up and blames someone else.
Imagine you go to an ATM and take out $500. A year later, the same ATM spits out $100,000 when you're not around and the bank wants you to pay it back! That's basically what Binance is doing now.
Suggestion: fix "Binance" in the title.