Quote from: truecry on August 23, 2018, 03:11:41 AM

Thanks for the explanation, that makes sense. The error message made me suspect some issue with Segwit implementation but I did not know or understand the details. You've made it clear.

The latest interpreter-fix branch synced up immediately without crashing and has been running for a while now. So it seems to be fixed at least as far as I can tell. If it crashes again I will post but it has not behaved this well (staying connected, receiving new blocks over time) in all my tests so far. Good work figuring that one out.

Glad to hear that!
Good to know that our Linux users can also participate in the network without crashes. The more different systems we support, the better for us all.
Of course, if you find any other problem, please report. Also via GitHub if you like.

Btw. we have a Bounty Fund which we use to reward people who help the project and I would like to send you some bounties.

If you like to get some ACM, please, send me your address via DM. You can also do this via Discord/Telegram if you are member there.

Best regards, and thanks again!