What does it mean for the verifier implementation to be "correct"?
I meant that there could be implementation bugs as in any cryptographic software. And it will take a lot of work to harden it.
I trade off the ability to verify a completely valid blockchain for the assumption that your organization built a proper prover and verifier.
We have not really build a new verifier, but only apply existing open source tools. We use the Giza verifier, which is mostly the Winterfell STARK library. What we have added is a translation of that verifier to Cairo.
The best of it all is that you don't have to use it. It is fully optional. It can get rolled out for low value use cases first and grow over time into a hardened library that makes sense for high-value use cases.