Henry de Valence

I think that @isislovecruft started working on it in the summer. Right now any work on it is blocked on merging #215, which restructures all of the backend code (e.g.,...

Do you have a Cannonlake CPU? This looks like an error that might result from specifying a target feature that your CPU doesn't support. You can check via `cat /proc/cpuinfo...

HmmmMMMMmmmm, interesting. I'll try taking a look at this next week, but I might not have access to my Cannonlake CPU. There might be a problem because the implementation was...

Related: #256, #257 . On my cannonlake machine the current `develop` branch works, but trying to remove the llvm intrinsics causes an ICE on skylake.

I would prefer not to have a `verify_with_rng` and instead find a way for verification be a stand-alone operation that depends only on the proof.

Instead of moving to a new `verification` module, I think it would be better to keep all of this as part of the rangeproof. Currently, the `Verification` struct holds a...

We could just use compressed points in the struct, and call `.map(|p_bytes| p.decompress())`, with some extra iterator combinators to handle the `None` case.

Just wondering, what's the motivation for making the batch verification API mix all kinds of proofs in a single batch, instead of requiring that the batch contains only the same...

The point about varying aggregation sizes (`m`) is convincing, and that seems like something we should support in the future. But as things are now, I think it actually violates...

This is really cool! A few comments / questions based on a quick read of the source code: 1. I'm a little uncertain about the type signature of `vartime_triple_scalar_mul_basepoint`. Specifically,...