Bitcoin Core v0.21.1 issue with incoming transaction

[nc50lc]

Maybe it has really to do with the size of transactions, because those from Nicehash are much larger than other, 7MB compared to usually a few hundred kb.

Most tx from Nicehash are just 7kB, about 6.8kvB in virtual size, 7MB wont even fit in a block.
But still, it's really weird that the problem only occurs when you receive transaction from them.

[1715434216]

1715434216

[1715434216]

1715434216

[1715434216]

1715434216

[1715434216]

1715434216

[1715434216]

1715434216

[wasisdn]

Maybe it has really to do with the size of transactions, because those from Nicehash are much larger than other, 7MB compared to usually a few hundred kb.

Most tx from Nicehash are just 7kB, about 6.8kvB in virtual size, 7MB wont even fit in a block.
But still, it's really weird that the problem only occurs when you receive transaction from them.

oh sorry yeah of course you are right 7kb vs few hundred byte.

Nicehash:
https://abload.de/img/snap2nljmn.jpg

other:
https://abload.de/img/snap319jxf.jpg

Could it related to my wallet address, because I use an older format address for Nicehash like 156... not bc1...?

[HCP]

Could it related to my wallet address, because I use an older format address for Nicehash like 156... not bc1...?

That shouldn't make any difference at all...


I am wondering, however, if this is related to this issue that @LoyceV found: https://bitcointalk.org/index.php?topic=5336919.0

Where Bitcoin Core is attempting to show all output addresses on the recent transactions list... and with your nicehash transaction having 200 odd outputs, it might be causing some sort of buffer overflow or "out of bounds" or similar error which is causing Bitcoin Core to shutdown?

It was noted in that LoyceV's thread, that because the list of addresses is truncated in the older versions of Bitcoin Core, that they work fine... which might also explain why you have noted that the old version is syncing/displaying those transactions without issue.

[nc50lc]

-snip-
I am wondering, however, if this is related to this issue that @LoyceV found: https://bitcointalk.org/index.php?topic=5336919.0

I think it's unrelated, that issue started in v0.21.1 while OP's started in v0.21.0.

On top of that, incoming transactions with multiple outputs that belong to your wallet will be displayed in separate entry per output and will only display that one address on 'recent transactions'.
Only those "send&receive" transactions (with in/out arrow icon, 'send to yourself') are one of the examples that still lists multiple addresses.

[wasisdn]

just to confirm after I ran BitcoinCore 0.21.1 without any problems for the entire last week until the next transaction from Nicehash arrived yesterday.
After the crash and several attempts with the same error at the same position (program closes when synchronizing the Nicehash transaction without a message) I pushed v0.20.1 into the program directory, started it and synchronized everything without problems.
Then switched back to the current v0.21.1 and its up and running again.

If you are interested, you can have a look at the last two days below, don't think I need to comment again

Transaction from NH is:

af4b27fd3e6917ddf39a16e159d2c20a4703ebaeffc554d3e29a780855a29525

Debug log:

https://pastebin.com/sWZwFZV0

I am currently running v0.21.1 and am waiting for a transaction from somewhere else.
Let's see if it goes smoothly...

[HCP]

Have you logged a description of this issue over on the Bitcoin Core github issue register? https://github.com/bitcoin/bitcoin/issues

It seems to me that you might get a better response from the developers by posting there.

There is nothing "obvious" in the debug as to why the app keeps shutting down when you receive a transaction from nicehash. Have you checked the Windows Event Viewer to see if there are any errors logged there for Bitcoin-Qt.exe?

Also, have you successfully received transactions from other sources? ie. Does Bitcoin Core shutdown when receiving any transaction... or does it only do it when you are receiving a transaction specifically from a nicehash payout?

[wasisdn]

Have you logged a description of this issue over on the Bitcoin Core github issue register? https://github.com/bitcoin/bitcoin/issues

It seems to me that you might get a better response from the developers by posting there.

There is nothing "obvious" in the debug as to why the app keeps shutting down when you receive a transaction from nicehash. Have you checked the Windows Event Viewer to see if there are any errors logged there for Bitcoin-Qt.exe?

Also, have you successfully received transactions from other sources? ie. Does Bitcoin Core shutdown when receiving any transaction... or does it only do it when you are receiving a transaction specifically from a nicehash payout?

Thanks for pointing me to the right place, just opened a new issue.
Nothing I can find in windows event related to BitcoinQT.
Still hesitating with TX from an exchange because I'm undecided about stocking up any more

[wasisdn]

Also, have you successfully received transactions from other sources? ie. Does Bitcoin Core shutdown when receiving any transaction... or does it only do it when you are receiving a transaction specifically from a nicehash payout?

Just transferred from an exchange and successfully synchronized with v0.21.1 ... so the problem is always and only with Nicehash transactions in connection with v0.21.x
 
txid

e2df3a45b07736c35eb391f883d47a7ec8e1c0cec2353b251984ecc90f99c024

row 109

http://https://pastebin.com/ysuUCwYp

[HCP]

Sorry, just to clarify... you're saying that line 109 in that debug output is the transaction arriving from an exchange... correct? And that your Bitcoin Core kept running just fine after receiving that transaction?

What's interesting is that going back and looking at your previous debug... the AddToWallet output is actually quite a long way from the debug that indicates that Bitcoin Core is shutting down, it seems to be syncing a lot of blocks after it sees that transaction.

Indeed the 2nd lot of debug here: https://pastebin.com/sWZwFZV0 near the very end, it doesn't even seem to be receiving any new wallet transaction at all, it is just syncing blocks and then shuts down (line 920 onwards)

[wasisdn]

Sorry, just to clarify... you're saying that line 109 in that debug output is the transaction arriving from an exchange... correct? And that your Bitcoin Core kept running just fine after receiving that transaction?

Yes exactly, v0.21.0 and tx from a source other than NH goes through without problems.

What's interesting is that going back and looking at your previous debug... the AddToWallet output is actually quite a long way from the debug that indicates that Bitcoin Core is shutting down, it seems to be syncing a lot of blocks after it sees that transaction.

That's because I didn't have BitcoinCore running for the week when I wasn't home, and when I knew that the tx from NH had been received, I started BitcoinCore with first attempt v0.21.1 and after crash with v0.20.1. Then of course the previous days will be processed first.

Indeed the 2nd lot of debug here: https://pastebin.com/sWZwFZV0 near the very end, it doesn't even seem to be receiving any new wallet transaction at all, it is just syncing blocks and then shuts down (line 920 onwards)

Correct, just to show that v0.21.0 runs without problems after I had previously syncronized the NH tx with v.0.20.1

line:
514 - start v0.21.1 attempt to sync NH tx
623 - crash just before NH tx 
2021-05-21T02:38:23Z UpdateTip: new best=000000000000000000076abd974283d6f1ac6ee46e6275289b919a0b72578fb9 height=684340 version=0x3fffe004 log2_work=92.890824 tx=643673329 date='2021-05-20T18:13:01Z' progress=0.999835 cache=22.4MiB(168883txo)

629 - restart with v0.20.1   
733 - same entry as above but no crash
2021-05-21T02:42:49Z UpdateTip: new best=000000000000000000076abd974283d6f1ac6ee46e6275289b919a0b72578fb9 height=684340 version=0x3fffe004 log2_work=92.890824 tx=643673329 date='2021-05-20T18:13:01Z' progress=0.999843 cache=22.4MiB(168885txo) warning='89 der letzten 100 Blöcke haben eine unerwartete Version'

734-735 - incoming tx from NH
806 - shut down

812-839 start - run - shutdown v0.21.1 without tx

The lines in second attempt are longer because a warning is appended to each line (unfortunately in German): warning = '89 of the last 100 blocks have an unexpected version'

[HCP]

That is indeed a puzzle... I am honestly all out of ideas for why this seems to be happening to you. I don't imagine you're the only Bitcoin Core user receiving payouts from Nicehash, so I'm surprised there are not more reports of this issue.

Hopefully the Bitcoin Core devs are able to investigate, identify the issue and fix it in a future version. For now, unless you absolutely require features in v0.21.1, I can only suggest running v0.20.1 until a new version is released and see if that fixes it.

[wasisdn]

That is exactly what surprises me too.
Anyway, I reported the issue on Github and someone already investigate. It seems that this is a new problem and nobody is using Bitcoincore for Win64 as an external wallet with Nicehash ... except me

Thank you very much for your support, I'll keep you informed!

[wasisdn]

Just to let you know, the latest version 22.0 has fixed the wallet problem, no more crashes on incoming transactions from anywhere.
Thanks again to everyone here in the forum and of course to the github guys!

[achow101]

Just to let you know, the latest version 22.0 has fixed the wallet problem, no more crashes on incoming transactions from anywhere.
Thanks again to everyone here in the forum and of course to the github guys!

That's kind of odd since the root cause was never pinned down and so no targeted attempt to fix the problem. But if it works, great!