Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a prover process #6

Closed
cmwaters opened this issue Nov 26, 2024 · 4 comments
Closed

Create a prover process #6

cmwaters opened this issue Nov 26, 2024 · 4 comments
Assignees

Comments

@cmwaters
Copy link
Collaborator

cmwaters commented Nov 26, 2024

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.

@cmwaters
Copy link
Collaborator Author

@rootulp
Copy link
Collaborator

rootulp commented Jan 2, 2025

@S1nus is this issue close-able given https://github.com/S1nus/blevm exists?

There is a separate issue to wrap blevm in a GRPC service: #41.

@S1nus
Copy link
Collaborator

S1nus commented Jan 2, 2025

@S1nus is this issue close-able given https://github.com/S1nus/blevm exists?

There is a separate issue to wrap blevm in a GRPC service: #41.

Yes the blevm repo can house the wrapping service + proof programs

@rootulp
Copy link
Collaborator

rootulp commented Jan 2, 2025

#56 exists and targets this repo so I think the intention was for the wrapping service to live in this repo in the provers directory. IMO it's not a big deal if it lives in a separate repo either but worth clarifying with @tuxcanfly. I'll close this issue as resolved for now then.

@rootulp rootulp closed this as completed Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants