synchronization – Why cant we set the chainstate obfuscation key?

I used to be lately studying the bitcoind logs in the course of the IBD and noticed that there was a number of obfuscation keys.

2025-08-21T10:31:45Z Utilizing obfuscation key for blocksdir *.dat information (/mnt/bitcoin/blocks): '0000000000000000'
...
2025-08-21T10:31:49Z Utilizing obfuscation key for /mnt/bitcoin/chainstate: 21971f03125cd7c5
2025-08-21T10:37:48Z Utilizing obfuscation key for /mnt/bitcoin/indexes/txindex: 0000000000000000
2025-08-21T10:37:48Z Utilizing obfuscation key for /mnt/bitcoin/indexes/coinstats/db: 0000000000000000

I’ve set blocksxor=0 and I can see It has been utilized for blocksdir .dat
It seems to be like it is usually utilized to bitcoin/indexes/*
However plainly there’s one other obfuscation key for the chainstate.
Is there a technique to set the chainstate obfuscation key?
Why is not the chainstate obfuscation key not the identical because the one used in every single place else?

Thanks all!

I used to be lately studying the bitcoind logs in the course of the IBD and noticed that there was a number of obfuscation keys.

2025-08-21T10:31:45Z Utilizing obfuscation key for blocksdir *.dat information (/mnt/bitcoin/blocks): '0000000000000000'
...
2025-08-21T10:31:49Z Utilizing obfuscation key for /mnt/bitcoin/chainstate: 21971f03125cd7c5
2025-08-21T10:37:48Z Utilizing obfuscation key for /mnt/bitcoin/indexes/txindex: 0000000000000000
2025-08-21T10:37:48Z Utilizing obfuscation key for /mnt/bitcoin/indexes/coinstats/db: 0000000000000000

I’ve set blocksxor=0 and I can see It has been utilized for blocksdir .dat
It seems to be like it is usually utilized to bitcoin/indexes/*
However plainly there’s one other obfuscation key for the chainstate.
Is there a technique to set the chainstate obfuscation key?
Why is not the chainstate obfuscation key not the identical because the one used in every single place else?

Thanks all!