⭐ Merited by achow101 (1)
I'm sorry, I mistook your post as a "stopped synchronizing" post.
I did a quick research and I think it has something to do with SegWit (August 24, 2017).
Also, I have checked the blocks included in blk00971.dat & I've noticed that the timestamps range from last week of August to Mid September 2017.
And blk00975.dat's blocks are from September 2017, one month after SegWit (BIP144) activation.
SegWit input/output scripts structure is a lot different than the regular transaction's.
That "parser" doesn't support and cannot read SegWit Txs.
Disclaimer: I could be wrong.
I did a quick research and I think it has something to do with SegWit (August 24, 2017).
Also, I have checked the blocks included in blk00971.dat & I've noticed that the timestamps range from last week of August to Mid September 2017.
And blk00975.dat's blocks are from September 2017, one month after SegWit (BIP144) activation.
SegWit input/output scripts structure is a lot different than the regular transaction's.
That "parser" doesn't support and cannot read SegWit Txs.
Disclaimer: I could be wrong.
Nope, you're alright. Most opensource parsers doesn't handle segwit and are not able to parse blocks included in recent blk files. I had to build my own parser to be able to parse files after these ones too.
