Jeff Burdges

I think `#[final]` is easier to explain too. As usages of the `impl` and `use` keywords multiply, we quickly lose our ability to explain them.

The QR code sounds irrelevant here, unless you want extra shards (papers) that recombine to give a different secret, but that's likely to cause insanity. If you have a root...

There is absolutely no reason to make the QR codes contain more since the password itself contains different entropy already. This is already baked into every crypto currency accounts system...

An easy approximation: Ed25519/Ristretto results are already single threaded, which makes them incomparable here usually. If anything else, then use the smallest machine and multiply the results by 8. This...

We must ensure that whatever lands in the code cannot eventually drop validator rewards so low that our security collapses. Amusingly, the halvings plus selfish mining shall eventually kill bitcoin...

Just fyi, his 20 min talk [_"Improved CRL compression with structured linear functions"_](https://www.youtube.com/watch?v=Htms5rNy7B8#t=39m10s) at [RWC 2022](https://rwc.iacr.org/2022/program.php) discusses this some

It's odd this data is compressible, well maybe our underlying formats needs some redesign there. We've a few places where it'd be nice if we used libtorrent or some rust...

Anonymized signatures would liekly be out of scope here, but.. I've done some mid-level traits for EC VRFs in https://github.com/w3f/ring-vrf/blob/master/dleq_vrf/src/traits.rs which work around input-output pairs. I designed those traits for...

It's possible a trait would usually makes more sense here: ``` pub trait Point : Into + Into { fn into_affine(self) -> AffinePoint { self.into() } fn into_projective(self) -> ProjectivePoint...

`Vec::len` should not do this even if this feature exists, because `Vec::set_len` is better pedagogically. `static mut`s require unsafe blocks for both writing and reading. An unsafe field would likely...