After it stabilizes, we should attempt to conform to the proofs and serializations generated by zkp (medium) whenever its proof serializations require the same space. It should be straightforward to do this using merlin's debug-transcript option.
We can minimize wire format breakage by playing around with variable names, ordering, etc, but some wire format breakage might be unavoidable.
We should probably avoid actually using zkp to generate our proofs or do verification though, because our actual protocol, any security considerations, and all optimizations should be visible here.
After it stabilizes, we should attempt to conform to the proofs and serializations generated by zkp (medium) whenever its proof serializations require the same space. It should be straightforward to do this using merlin's
debug-transcript
option.We can minimize wire format breakage by playing around with variable names, ordering, etc, but some wire format breakage might be unavoidable.
We should probably avoid actually using zkp to generate our proofs or do verification though, because our actual protocol, any security considerations, and all optimizations should be visible here.