@stevedylandev.eth

That's kind of the beauty of ZK proofs. The proof system guarantees that the prover knows content that hashes to the specific CID committed in the public output. While the file contents are private inputs, they're cryptographically bound to the public CID output through the ZK proof. To prevent the attack you described (serving wrong content with a valid proof): 1. The proof verifies the prover knows content matching the CID 2. The verifier must also hash the received content to confirm it matches the CID The security comes from combining proof verification with a simple content hash check. The system prevents the gateway from creating valid proofs for modified content due to the collision-resistance of cryptographic hash functions.

1 reply

0 recast

0 reaction