Jack Wampler

I have added the [RFC9380](https://datatracker.ietf.org/doc/rfc9380/) test vectors for the elligator2 implementation, and an interface that should work if someone wanted to use this to implement the `h2c` interface for `curve25519`...

I am working on adding some final tests to ensure that the bits of the ellgator2 representatives appear as uniform random. TLDR: The `sqrt_ratio_i` function seems to be canonical so...

The latest commit fixes several issues. 1. The Edwards RFC9380 testcases were not actually testing the things they were meant to be testing. This forced some changes in the way...

I have added another refactor to the elligator2 implementation motivated by feedback based on issues encountered with encoded key distinguishability in obfs4. The changes required to fix the distinguisher resulted...

> 1. It seems like I can't get the Elligator2 tests to fail, even when they definitely should. Is a KAT missing? > 2. I was wondering about the correctness...

Great to hear! I rebased onto the latest changes in `main`. I am happy to help with any clarifications and work in any interface changes. Okay, I am working on...

It might be more palatable if this PR made `no-std` a feature such that enabling it bumps the MSRV to 1.81 instead of forcing an MSRV bump for the library....

I recognize that typically you want an additive `std` or `alloc` feature to enable broader functionality than the scope of the original package, but I feel like this is a...

Hmmm. Some of the DNS related tests seem either flakey or like they are interleaving in a way that is doing bad things to the shared resolver.

After changing the default to use IPv4 Only nameservers the errors in the tests run as part of the github actions have gone away. However, I do not fully understand...