Why does Kaspa use a dedicated hash domain for covenant IDs?

Kaspa keeps its covenant identifier hash — called CovenantIDHash — completely isolated from every other hash used in the protocol, a practice called domain separation. Without this isolation, a hash value computed legitimately for one purpose inside the protocol could theoretically be reused or confused with a hash for another purpose, opening a path for cross-context attacks. By giving CovenantIDHash its own dedicated domain, Kaspa ensures that values produced in one part of the system cannot bleed into or be mistaken for covenant identities in another part. For beginners, think of it as giving each cryptographic operation its own locked room so nothing from one room can sneak into another.