That script prints test vectors to the standard output, in the following
order:
- private key
- public key (X coordinate)
- public key (Y coordinate, never exposed by Monocypher)
- Boolean (0 if we can't convert, 1 if we can)
- hash of the public key (or zero if we couldn't convert)
I could use that script to generate the test vectors automatically, but
I hesitate to introduce a hard dependency on SAGE.
The alternative is to put the test vectors themselves under version
control. We could add a target to the makefile that checks whether the
test vectors and the script are in sync, but that would break if we end
up adding vectors manually (which typically happens whenever project
Whycheproof publishes new vectors).