bc-java

Note that there may be incompatibilities (as noted in the article) until NIST has published the final revisions. Some specifications are on Round 3 kyber, others are on FIPS 203. This one will interoperate with Bouncy Castle (both Java and C#) as we both use FIPS 203 draft, but it won't interoperate with OQS simultaneously (three-way interop) as that is still on the Round 3 submission. See also: https://github.com/bcgit/bc-java/issues/1578 (Disclosure: BC is my employer)

The readme mentions a dependency on Bouncy Castle - note that BC already contains several Java-based PQC signature schemes, see https://doc.primekey.com/bouncycastle/interoperability#Inter... and https://github.com/bcgit/bc-java

Not sure why you have to wait. I use ChaCha in production in JDK 8: https://github.com/bcgit/bc-java/blob/master/core/src/main/j... Why would native be any better? I would think that as long as the implementation matches the reference it wouldn't matter.

Lots of nice detail as well. In the house of code one the protagonist is writing up the HeartBeatMessage class from the bouncycastle tls library: https://github.com/bcgit/bc-java/blob/master/core/src/main/j... in the Breaking Bad one has some java code that evaluates to his name on the tablet. public class JavaDoc { public String name() { return asList('I', 'x', '`', 'u', '`', 'a', 'x', 'd', 'q', 'f') .stream() .filter(c -> c != 120) .map(c -> (char) (c + 1)) .map(c -> "" + c) .reduce((a, b) -> a + b) .get(); } } https://gist.github.com/benmmurphy/386be40056bf3a2e263e