Mar 7, 2025

The witness hash is never needed again after block.check which confirms the witness commitment. But the block.hash and tx.hash are stored to the database as search keys for the header and tx tables respectively. So they are never computed again, since they can be read directly. Point hashes are tx hashes (if valid) but must be redundantly stored in order to allow for correlation to the spent tx.output given concurrent download. A sequential store (like Core) could correlate valid point hashes to txs and replace the point hash with a tx surrogate (store) key. But it Core doesn't do this, because it doesn't really have a database.