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

Add wasm target #314

Closed
Levike34 opened this issue Apr 22, 2024 · 2 comments
Closed

Add wasm target #314

Levike34 opened this issue Apr 22, 2024 · 2 comments

Comments

@Levike34
Copy link

Would be very useful if jolt could be compiled to a WASM executable

@sebasti810
Copy link
Contributor

I’ve started to look into this, but want to get some clarification before I spend too much time on the wrong path - should we also have first class support for the prover, or is the verifier sufficient (as done here)? I’m assuming the big selling point here would be embedding verifiers into webapps, but does it make sense to make the prover wasm compatible as well?

One way we could do this is by introducing a new jolt command, e.g. jolt create-wasm …, which could take over the process of creating the required components and then generating the WASM-compatible binaries… should I continue down this road?

@larron
Copy link

larron commented May 25, 2024

@sebasti810 Support for in browser verifiable compute would be awesome, IE: Noir

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

4 participants