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
This is a question and maybe also a code issue, not sure. You guys have making some changes to the parameters in recent PRs so maybe this is a good time to ask.
I haven't seen any examples in the code of caching the supernova params in memory to avoid the expensive call to supernova_public_params(&instance_primary).unwrap(); each time one needs to verify a proof.
This worked well (whether or not it was the correct way 🤷) but it stopped working with the recent commits over the last day or so.
It seems to be related to the requirement that the lifetime of the store match the lifetime of the params.
let (proof, _z0, zi, _num_steps) = supernova_prover.prove_from_frames(&pp, &frames, &store...
| -------------------------------------------------^^^^^^-
| | |
| | borrowed value does not live long enough
| argument requires that `store` is borrowed for `'static`
...
346 | }
| - `store` dropped here while still borrowed
So my question is if there is a proper way to cache the params in memory that I'm not doing? Or if this is generally how it's supposed to be done then maybe there's issues with the lifetime requirements on the supernova_prover.
The text was updated successfully, but these errors were encountered:
This is a question and maybe also a code issue, not sure. You guys have making some changes to the parameters in recent PRs so maybe this is a good time to ask.
I haven't seen any examples in the code of caching the supernova params in memory to avoid the expensive call to
supernova_public_params(&instance_primary).unwrap();
each time one needs to verify a proof.I was doing it like this in my code:
This worked well (whether or not it was the correct way 🤷) but it stopped working with the recent commits over the last day or so.
It seems to be related to the requirement that the lifetime of the store match the lifetime of the params.
So my question is if there is a proper way to cache the params in memory that I'm not doing? Or if this is generally how it's supposed to be done then maybe there's issues with the lifetime requirements on the
supernova_prover
.The text was updated successfully, but these errors were encountered: