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
Currently, the "Download" button is explained in the middle of a paragraph of the initial example, and this is the only place it is mentioned.
Being able to download, and replay, proofs is an important feature though that deserves better explanation. Probably should additionally get its own heading to help readers find it: "Storing proofs", "Storing (partial) proofs", "Storing (partial) proofs and reloading" or something like that, and then a bit more about the reloading process.
The text was updated successfully, but these errors were encountered:
Good point. Perhaps we also need a chapter with "typical workflows" for more involved protocols, which could refer to this. This could then also point out more clearly that one needs to observe partial deconstructions, which users often miss initially.
Currently, the "Download" button is explained in the middle of a paragraph of the initial example, and this is the only place it is mentioned.
Being able to download, and replay, proofs is an important feature though that deserves better explanation. Probably should additionally get its own heading to help readers find it: "Storing proofs", "Storing (partial) proofs", "Storing (partial) proofs and reloading" or something like that, and then a bit more about the reloading process.
The text was updated successfully, but these errors were encountered: