The audit uncovered an Elligator2 implementation that is very likely to be compatible with Monocypher (modulo padding bits). It is to our knowledge the only working, compatible, independent implementation.
Up until now we had to make do with my Python implementation (which by definition are not independent), and a couple test vectors from the RFC draft, some of which I had to negate before I used them.
We should use that independent Elligator2 implementation to make more test vectors and gain further confidence in the correctness and potential interoperability of ours.
The audit uncovered an Elligator2 implementation that is very likely to be compatible with Monocypher (modulo padding bits). It is to our knowledge the only working, compatible, independent implementation.
Up until now we had to make do with my Python implementation (which by definition are not independent), and a couple test vectors from the RFC draft, some of which I had to negate before I used them.
We should use that independent Elligator2 implementation to make more test vectors and gain further confidence in the correctness and potential interoperability of ours.