Ok, found it! .. today i used core 28.1 which gives xor'ed dat files (default in 'local' directory on windows) ... also 28.0 will give you xor'ed dat files...
and i think last week i used 27.2 (defaults to 'roaming' directory on windows)..
As we speak i re-installed core 27.2 and the blk*.dat files are not xor'ed on disk but directly useable..
Thks ! reg koen
hi ok, but the files (the whole blockchain) downloaded last week (all blk*.dat) with same core sw are all prefectly 'readable' without undoing the xor ... In the sense that they start with the magic bytes / version etc Why would that be the case .. ?
It could happen due to one of these reasons,
1. Using Bitcoin Core with version below v28.0.
2. Start download blockchain with Bitcoin Core with version below v28.0.
3. Use Bitcoin Core v28.0 or newer, but manually add
blocksxor=0 on your Bitcoin Core configuration before starting download blockchain.
More information,
https://learnmeabitcoin.com/technical/block/blkdat/, XOR section.
thx, just found out the same ! reg k (gues used 27.2 last week .. cant really remember ..