00:48:02 <br-m> <jeffro256> Nope 
00:48:21 <br-m> <jeffro256> It probably should at some point 
00:50:01 <br-m> <jeffro256> It creates complete results AFAICT. I test scalar-point multiplication by doing scalar-point multiplications on Ed25519, then converting them to X25519 since they are birationally equivalent 
00:50:32 <br-m> <jeffro256> So it at least gets those values right, as well as the RFC 7748 test vectors
00:51:54 <br-m> <jeffro256> And scalar-point multiplication over X25519 is basically the only operation Carrot cares about. An audit would probably have results limited to perhaps side channel attacks, or memory sanitization 
00:52:08 <br-m> <jeffro256> But iy should probably be done eventually 
00:52:43 <br-m> <jeffro256> Key generation doesn't even happen on mx25519