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
There are solutions, but I was not able to implement them in #50
Another problem is that there is no info about the trace or the time exposed in Miden v0.3. So we don't know how many cycles or how long it took, see #29. The problem with the duration of the proving step could be solved by adding a timestamp to the frontend.
Proving a Miden program in the App.tsx
We add another function like for run_program. The return values so far are the stack_output and the overflow_addresses.
However, we do not get the proof or any other info yet to print, see above.
In an ideal world, we would get some info while the proving step is executed, like the info that is logged when you prove via the CLI.
Open questions to clarify in the working group
Maybe the ability to prove is enough for this iteration, but if not we need to answer
What do we want to output while proving?
What do we want to output during proving?
How do we want to show the proof?
Any opinions / ideas on the above @grjte or @Overcastan ?
The text was updated successfully, but these errors were encountered:
But importing Miden VM v0.3. and using miden::prove:: does not expose this logger. Do you know a way how to access the logger? I mean it does not even log, when we don't use the Miden CLI I assume.
At the moment, we only execute the Miden assembly program. We should add the ability to prove and also to verify a program.
Proving a Miden program in lib.rs
We can add the feature as another function,
pub fn prove_program
and also have the program, the inputs and the output_count as function inputs.The problem so far is, that we can't return a tuple or a complex struct from Rust to the frontend using
wasm-bindgen
, see https://stackoverflow.com/questions/75064800/how-to-return-a-tuple-to-frontend-from-wasmThere are solutions, but I was not able to implement them in #50
Another problem is that there is no info about the trace or the time exposed in Miden v0.3. So we don't know how many cycles or how long it took, see #29. The problem with the duration of the proving step could be solved by adding a timestamp to the frontend.
Proving a Miden program in the App.tsx
We add another function like for
run_program
. The return values so far are the stack_output and the overflow_addresses.However, we do not get the proof or any other info yet to print, see above.
In an ideal world, we would get some info while the proving step is executed, like the info that is logged when you prove via the CLI.
Open questions to clarify in the working group
Maybe the ability to prove is enough for this iteration, but if not we need to answer
Any opinions / ideas on the above @grjte or @Overcastan ?
The text was updated successfully, but these errors were encountered: