been looking into how Cosmos IBC verifies consensus on Ethereum using SP1 proofs. something I'm more interested in than the ZK proofs themselves is who controls the verifier. because you can have mathematically valid proofs, but if someone has permission to upgrade the light client or change which verification keys are trusted, that's a completely different security question. the Ethereum deployment uses a 4-of-7 multisig with timelocked administrative controls. now I want to trace exactly what those admins can change, whether a malicious verifier could be introduced through an upgrade, and what users can actually do during the timelock. ZK proves that a particular computation was executed correctly. it doesn't prove that the people controlling which computation gets verified can't change it. that's the part I want to dig into.