I wonder if you could compile solidity into an intermediate representation, which can be further compiled to:

1. EVM bytecode
2. Zk-friendly VM

Half baked idea that requires associating the ZK instructions with the deployed contracts.

You could run a sidecar along with main chain that’s zk-friendly. 

Idk how but maybe you could easily generate ZKPs of a tx’s state update from just:

1. State root
2. Tx hash
3. Signature

—-

The proof should be done over the zk friendly sidecar so it can be much quicker. Then maybe we can have commit/reveal block building?

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

http://opacity.network

This would require all validators to have the source or IR available, interesting to think about how that would work

Pragmatism (Security) at OP Labs.
Prev: ConsenSys & Coinbase.

Attribs: Friendly, curious, introverted, mid-witted.
Chans: /eth-security /maurelian /stoicism




Half baked disclaimer included.

Could just be an EigenLayer AVS to

Yeah, just thinking it thru. Iff the IR is available at deploy time, then validators on the AVS could verify that the IR produces the bytecode on the EVM chain. And The sequencer would be creating an invalid transition if it allows bytecode to be deployed without the IR having been registered previously.