We are currently constructing a StdlibProof from a HonkProof inside the recursive verifiers which is an insecure pattern. Moreover, not hashing the verification key leads to potential weak Fiat-Shamir issues.
GoblinProof passed to the recursive verifier should also be a stdlib proof and translation evaluations should be constrained prior entering the verify function
We are currently constructing a StdlibProof from a HonkProof inside the recursive verifiers which is an insecure pattern. Moreover, not hashing the verification key leads to potential weak Fiat-Shamir issues.