Observations on 8.22.2 and stuck transactions, possible issues to explore?

[ZuneTracks]

Greetings Digibyte team! I'm making this post really to just be informational about my experience sending/receiving DGB over the last few days.

Yesterday I reverted DGB Core to v7.17.3 as I had two Tx sitting unconfirmed in mempool for several days after sending them in v8.22.2. These were being sent to my Ledger cold storage wallet. One Tx was for 245 DGB and the other for 1+ DGB, sent on 5/2/2025, and 4/30/2025 respectively. When I did some digging in chainz.cryptoid.info/dgb for the originating transactions, it said that all of the transactions (several between 20 DGB-25DGB each, for mining rewards), were "not yet redeemed" by my 8.22.2 wallet, despite the wallet showing they were received.

Transaction list in my wallet:

After I uninstalled 8.22.2, rebooted, and reinstalled 7.17.3 (all on my windows 11 pro system, latest updates all around), I then sent another transaction for 24 DGB, again to my Ledger cold storage wallet, and after doing this, the two stuck Tx were then seen and confirmed in the block chain. I had tried this exact same thing in 8.22.2, in fact that was how my 245 DGB Tx became stuck, as I tried to send it hoping it would cause the 1.+ DGB transaction to be confirmed.

As a last bit of information, my debug.log on this system was over 5 GB in size. I went to look in there to see if I could find anything useful, but notepad refused to open it. I made a copy of it to offload to another drive, and then deleted it to start over. The same thing happened on my Windows 2022 server node with 8.22.2 as well. I'm not sure if this is intended behavior or not, but thought it might be useful.

[ZuneTracks]

tagging @ycagel for FYI.

[ycagel]

Passed along to the devs.

[ZuneTracks]

Passed along to the devs.

@ycagel I would be more than happy to pass along the two 5+GB debug.log files from each of my 8.22.2 clients that I saved, if they would like to review them.