Kevin Lewi

Hello! Just wondering if there is a timeline or any blockers for upgrading the pre-release (v4.0.0-pre.1 currently) to v4.0.0. The opaque-ke library (https://github.com/novifinancial/opaque-ke) is also currently on a pre-release, depending...

Extending limited history to properly check for the existence of past values

1

In general, this change improves the security properties that are supposed to be attained from a limited history proof. A (full) key history proof provides a list of all past...

Eliminate stale markers

1

Stale versions of nodes do not need to be written. They can instead be substituted by checking if the next version has been written. We should (1) stop writing stale...

Features should be additive, don't use nostd feature, but use an std one instead

1

Based on https://doc.rust-lang.org/cargo/reference/features.html?highlight=additive#feature-unification We should replace our nostd feature to instead have an std feature that enables std.

We should add fixture generation for creating the lookup, history, and audit proofs so that if their format or logic changes, we can easily detect so. This also essentially allows...

If the lookup proof is for a version which is already a power of 2, then the existence proof and marker version proof will be identical. This means that we...

Lots of things that currently have `pub` visibility do not need to be publicly visible. Let's do a pass over everything that is pub and see if it can be...

Update docs on the existing lookup proof generation

1

We should indicate that the existing lookup proof generation / verification should be deprecated, and history proofs with MostRecent(1) should be used instead

Adding individual epoch auditing in kt auditor example

1

This adds the ability for the whatsapp-kt-auditor example to audit a specific epoch, rather than loading all proofs first and then picking the epoch (which can be much slower)