Issues with blk00000.dat and parsing

Been running a full node for a while, all good until now. It’s synced and keeping up with new blocks. I tried using blockchain_parser.blockchain to analyze local data but the CPU usage went through the roof for hours. Looks like it’s stuck on the first block. The blk00000.dat file starts with something odd... is that normal? Can I force an update on just that block?

You might have hit a snag with blockchain_parser.blockchain. It probably can't handle the new XOR’d blocks from Bitcoin version 28.0 and up. Check their repo for any issues. If it turns out that’s the case, maybe start fresh with a new data directory? Just set blocksxor=0 in your config or as a command line option.

Thanks for the advice, I added blocksxor=0. Turns out I wasn’t on the stable release of 28, so I’m upgrading to 29.0 now. Let’s see if re-syncing fixes the issue.

Wouldn't it be quicker to just un-XOR the current blockchain files instead of doing a full re-sync? I mean, if some tools aren't compatible with the XORed files, that could save time. The xor.dat in the blocks folder has the XOR value used for obfuscation. Shouldn’t be too hard to write something to un-XOR it. Haven't tried it yet myself.