Reaction from Dogecoin Developers to Binance’s DOGE Decision!

Cryptocoin. com

As reported on November 11, the cryptocurrency exchange Binance briefly suspended the withdrawals of Dogecoin due to a malfunction. According to the statements made on the official website of the exchange, a minor issue with withdrawals from the DOGE network was discovered in Binance in a version update. Now, this decision is getting reaction from Dogecoin developers. Here are the details…

Dogecoin Developer: Binance has previously reported to us that transactions were blocked

“Dogecoin Developer”, a 10-item statement was made in the past hours from the Twitter account named Dogecoin developers. Dogecoin developers briefly mention:

1. Binance has informed us that transactions have been blocked before. But the transactions were not shown to us, it was claimed that they were ‘stuck’ due to insufficient fees…
2. Binance has chosen to repost/repost these transactions. We instructed Binance to use the inputs of trades stuck. No response was made.
3. Binance later informed us of account reconciliation issues. We weren’t able to reproduce these issues with the data given to us by Binance, but suggested (months ago, now) issuing -zapwallettxes to mitigate the issue…
4. Yesterday we were informed that previously stuck transactions were suddenly successfully transferred after the 1.14.5 update.
5. The only example we have from Binance is v1. It is a (very low) fee transaction valid on 14.5 but not valid on 1. 14.3 and earlier. Note, Binance has been directly v1 over the past few days. Updated from 14. 3 to 1. 14.5…
6. What we believe is happening at the moment is that previously stuck processes are automatically retried after the upgrade, as is the case with every node restart.
7. Implications: Invalid transactions do not have a defined timeout limit, but are often discarded due to memory limits. However, if the mempool is not maintained, they can get stuck…
8. The correct action to cancel a transaction is to spend the inputs of the transaction to be canceled on a different transaction, which overrides the first…
9. For all providers concerned about static invalid transactions, we recommend stopping the nodes in the mempool just in case. dat file and then start the node with -zapwallettxes….
10. Also, this should probably be done as a routine maintenance practice; especially if you know that a number of invalid transactions have been refactored.