Open Levike34 opened 2 months ago
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?
Would be very useful if jolt could be compiled to a WASM executable