I might please like assist understanding the brand new -blocksxor enhancement, primarily from an admin perspective. I did see the next helpful information.
Output from bitcoind –help:
-blocksxor
Whether or not an XOR-key applies to blocksdir *.dat information. The created XOR-key
can be zeros for an current blocksdir or when `-blocksxor=0` is
set, and random for a freshly initialized blocksdir. (default: 1)
From v28.0 launch notes:
Block information at the moment are XOR’d by default with a key saved within the blocksdir. Earlier releases of Bitcoin Core or earlier exterior software program will be unable to learn the blocksdir with a non-zero XOR-key. Check with the -blocksxor assist for extra particulars. (#28052)
Feedback for this transformation are at: Pull Request #28052
Studying additional, it appears like this enhancement compensates for some AV softwares wrongly flagging blockchain storage information. It appears like this was initially reported in opposition to chainstate information (Subject #4069), whereas this new “-blocksxor” remediation offers with faulty AV flags to the blocks knowledge information themselves.
For the brand new enhancement, it appears like a rolling random XOR obfuscation blocks listing which is then used to optionally obfuscate file contents.
My questions I would please like assist with are:
- I did not see the “rolling” nature of those keys described? When are the random XOR keys generated, and when do they “roll?” Are new keys created for every block? Does the brand new -blocksxor key-file comprise a number of obfuscation keys, it should?
- Additionally, how does this assist forestall AV softwares from persevering with to wrongly flag these knowledge information? Does not randomly XOR(ing) continued knowledge simply “kick the can down the highway”? Finally the identical downside might occur. Are there AV-integration assessments which show out this XOR(ing) resolution?