porcuquine
porcuquine
From https://github.com/lurk-lab/lurk-rs/issues/841#issuecomment-1792881670: > Put differently, proof of knowledge (of commitment openings — or of Lurk data content more generally) must remain a strong guarantee of Lurk proofs that imply it....
UPDATE: The items here (and others) will be worked on *during* Lurk Beta and are not blockers for reaching Beta. This is a tracking issue for explicit languages modifying the...
This is paused without having been changed yet. There is a new candidate plan, which involves making `nil` and `t` both have type `Bool`, with values 0 and 1 —...
As noted in #310, we need to improve caching performance for public params, prover keys, and verifier keys. There are many ways we can do this, and they don't all...
`lurk --version` reports the Cargo version, but this is not useful for distinguishing the characteristics of a development binary. This can come up if Lurk has been installed locally rather...
As described in #327 and emphasized in this comment, https://github.com/lurk-lab/lurk-rs/pull/327#pullrequestreview-1366861547, we should decide on and implement a strategy for output from files loaded by the REPL.
This issue is a placeholder for a larger discussion. This comment has some partial context, linked here to preserve it: https://github.com/lurk-lang/lurk-rs/pull/87/files#r857858272
As noted in comments, #397 (which adds a Trie coprocessor) could use proptests. Once that PR merges, this could be implemented.
Currently, proofs are looked up by the CID of their claim. However, this is imperfect and needs more thought. Currently, claims don't capture any info about the proof, but if...
Someday, Nova will not require `num_steps` for verification. When that happens, we will want to move iteration-count into the frame I/O and explicitly allow for hiding or revealing the count...