Determine how to integrate ZK Verifier into Sovereign Light Clients

[Farhad-Shabani]

Background

Right now, there are ambiguities about the best way to fit a ZK verifier into Sovereign light clients. This issue is about figuring out how to smoothly add that verifier into the CW contract of rollup clients. The goal? To get a single, slick WASM light client that can keep tabs on both the DA layer and rollup states within a Sovereign-driven rollup.

Here is what we're pondering

• Is the proof data structure discussed in Determine aggregated proof data structure #53 good enough for verification? Or do we need to toss in something extra, like a structured Proof Specification like what we have as ProofSpecs for Tendermint light clients?

• Do we need to set up a way for the ZK proof verifier to call up some guest code or programs when it's time to check that SNARK proof?