Prover service for EVM

[cmwaters]

Similar to #33, we need a proving service the relayer can use to update the groth16 client on simapp/celestia.

This will wrap the program https://github.com/S1nus/blevm/tree/main and should comply with the current proposed interface (of course subject to change) here. We can worry about the membership proofs later, in the short term we should just worry about proving the state transition function

[rootulp]

@cmwaters has an in-flight PR that sets up some directories we can re-use in this issue: #33

• This issue is to create an evm-prover that wraps around blevm.
• Generates one proof per block.
• celestia-prover has an input for Tendermint RPC, queries latest height from chain (chainHeight), queries latest height of the client (clientHeight), generates a proof from clientHeight to chainHeight.
• Currently blevm prooves one EVM block is valid and included in Celestia data root. Aggregation hasn't been built yet.
• This service should generate one STARK proof per block. Then generate one recursive proof that includes all the blocks from clientHeight to chainHeight.
• To get the best performance, aggregate in a tree structure. Group two leaves, another two leaves, then group one level up two child nodes. We can make the outermost SNARK proof aggregate any number of heights.
• We can punt the design of aggregation of block heights (performance improvement).

When do we generate the proof?

• Option A: generate one STARK proof per block height, generate aggregated proof every block range of 16. Generate a Groth16 proof around the aggregate proof.
• Option B: generate one proof per block height, generate aggregated proof when user requests it. Generate a Groth16 proof around aggregate proof.

Partially blocked on #42

[rootulp]

Stand-up notes

• Javed was looking at Celestia prover and will open a PR soon to copy over main.rs from blevm
• SimApp needs a GRPC server for querying client state + consensus state. SimApp's IBC client 02 has a query service that you can query client state.
• IBC team has Rust code to query client state + consensus state (likely ibc-rs or a lib that Hermes uses).
• IBC team is building their own relayer.

[rootulp]

• This service needs to query the Groth16 client on SimApp for the client and consensus state.
• @rootulp extract fix for client and consensus state initialization