You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a separately running process that can take as inputs the JSON RPC of both the reth and Celestia nodes and have a simple public API that generates groth16 proofs (and the accompanying public inputs) given a specified height range. This would then be used by the relayer to update simapps ZK IBC Client that tracks the state of the reth rollup.
FYI we have a similar prover process going the other direction known as the operator which generates succinct proofs of the tendermint header to be processed by the reth node.
The text was updated successfully, but these errors were encountered:
We need a separately running process that can take as inputs the JSON RPC of both the reth and Celestia nodes and have a simple public API that generates groth16 proofs (and the accompanying public inputs) given a specified height range. This would then be used by the relayer to update simapps ZK IBC Client that tracks the state of the reth rollup.
FYI we have a similar prover process going the other direction known as the
operator
which generates succinct proofs of the tendermint header to be processed by the reth node.The text was updated successfully, but these errors were encountered: