For our protocol circuits, we want to use the VK hash to make sure the circuit has previously been deployed or that its part of a particular set of circuits. To avoid double hashing, we can use the challenge generated from Fiat-Shamiring the VK as the VK hash. This must be linked with the VK hash that's passed in through Noir's verify_proof_with_type call. Currently, that hash is set to 0 in many cases and ignored in the backend.
For our protocol circuits, we want to use the VK hash to make sure the circuit has previously been deployed or that its part of a particular set of circuits. To avoid double hashing, we can use the challenge generated from Fiat-Shamiring the VK as the VK hash. This must be linked with the VK hash that's passed in through Noir's verify_proof_with_type call. Currently, that hash is set to 0 in many cases and ignored in the backend.