![]() The Foundation has received no further reports of this happening. Please note that transactions don’t have a defined timeout period, but are typically discarded due to memory limits.Ideally use replace-by-fee if available, but otherwise crafting and sending a transaction spending the previously chosen inputs, will invalidate the previous transaction.Correct handling to cancel a transaction is to spend the to-be-cancelled transaction’s inputs to a different transaction, which invalidates the first.This is correct behaviour as a result of reducing fees. Dogecoin core 1.14.3 upgrade#Note, Binance updated directly from v1.14.3 to 1.14.5, in the past few days.īased on the information available it appears that the previously stuck transactions have been retried automatically, as would happen on each node restart after upgrade - and went through, since now the minimum required relay fee is lower. The sole example provided is a transaction with fees which are valid as of v1.14.5, but were invalid (too low) in 1.14.3 and before. Dogecoin core 1.14.3 update#Yesterday November 10th Binance notified the maintainers that previously stuck transactions had suddenly relayed successfully, post 1.14.5 update likely because minfees have been lowered in 1.14.5, making the previously valid but unrelayable transactions relayable. This is notable as it is anticipated this would have also prevented the issue seen. The maintainers were unable to reproduce those issues with the data we were given by Binance, but at the time suggested using the -zapwallettxes command line option to mitigate the issue. Some time later Binance notified the maintainers that they had account reconciliation issues. As the transaction had RBF disabled, it was recommended that Binance create a new transaction manually, which would consume the same inputs to forcibly invalidate the previous transaction. Notably this was suggested because replace by fee invalidates the previous transaction (hence “replace”). The maintainers suggested Binance use RBF (replace by fee) on these transactions, which would replace the original transactions with a new transaction with a higher fee paid. Several months ago (noting while an earlier post stated a year, first confirmed mention is April) Binance notified a group of Dogecoin Core maintainers that Binance had cases where transactions were stuck, meaning the transactions were not being mined successfully. It has been edited toīinance has today paused Dogecoin withdrawals and stated they have found a “minor issue” in Dogecoin. Note: A previous version of this advisory used “we” to refer to a group separate to the Foundation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |