I used to think most ZK projects treated proofs as an add-on—something layered on top to strengthen the privacy narrative rather than define the system itself.
But after reading through Midnight more carefully, that perspective shifted.
What stands out is that ZK isn’t positioned at the edge of the architecture—it sits at the core of how authentication works. Proof isn’t an optional feature you toggle on later; it’s a prerequisite for any state transition to be accepted.
That’s where NIGHT feels fundamentally d
ifferent. Instead of relying primarily on traditional signatures, transactions depend on cryptographic proofs to validate correctness. No valid proof, no state update. The verifier key is also embedded on-chain as part of the contract logic itself, rather than being treated as a supporting component.
With both Kachina and the proof server centered around generating and verifying proofs, ZK stops being a secondary tool. It becomes the foundation—the mechanism through which everything is authenticated