Why does Kaspa's KIP-0016 use precompiles instead of raw ZK scripting?

KIP-0016 relies on proven, pre-built ZK implementations (called precompiles) rather than asking developers to write raw zero-knowledge proof logic directly in Kaspa scripts. Implementing ZK contracts at a scripting level is highly error-prone, and the history of ZK systems is filled with discovered vulnerabilities and exploits — so leaning on battle-tested implementations is a deliberate safety choice, not a limitation. For a beginner, the takeaway is that Kaspa's designers chose reliability over flexibility in this first step: get ZK on the network safely before adding more granular, lower-level opcodes in future proposals.