05:04:40 tritonn: If you decide to move forward with your submission, make sure to read the update: https://github.com/j-berman/fcmp-plus-plus-optimization-competition?tab=readme-ov-file#update-helioselene-submission-deadline-extended 05:05:31 Any changes to the Ed25519 type results in an invalid submission, and changes to the Ed25519 arithmetic will not be counted. 06:27:09 A contest "extension" for minor rule clarifications like requiring Crandall optimizations seems normal, but you wouldn't expect a short "extension" to fundamentally alter the nature of a contest. 06:27:11 The `Field25519` type was *very* explicitly part of the original contest scope. 06:27:13 The contest rules state: 06:27:15 > You may modify all of of `helioselene-contest-src` 06:27:17 The tests and benches explicitly include `Field25519` from `helioselene-contest-src`. Then they carefully initialize the `Field25519` values of the reference code and the contest code separately, conveying that the two types are distinct. 06:27:19 When evaluating the submissions, the judges realized that there were integration issues. Other code is using Luke Parker's `FieldElement` type, which is only trait compatible with our versions. 06:27:21 Proposed compromise: 06:27:23 I don't program in Rust full time, I have other projects, and I'm old enough that I no longer binge code all night like tritonn. That's why I started working on my entry part-time *months* ago. 06:27:25 Allow me to produce an entry that is compatible with Luke Parker's FieldElement for easy testing and integration. When implementing 06:27:27 the Selene point, I will even set the Scalar to Luke's type: 06:27:29 ``` 06:39:14 It's too late in to say that we have to use the field math from Luke Parker's Field25519 implementation which is in conflict with the original contest. 10:22:29 > Allow me to produce an entry that is compatible with Luke Parker's FieldElement 10:22:31 No, use the struct directly. 10:22:33 > If given permission to change the benchmark/test code 10:22:35 No. 10:22:37 > It's too late in to say that we have to use the field math from Luke Parker's Field25519 implementation which is in conflict with the original contest 10:22:39 You have already lost the original contest. Feel free to participate in the ongoing contest. Please stop spamming the channel. 10:22:41 > I don't program in Rust full time, I have other projects, and I'm old enough that I no longer binge code all night 10:22:43 Then stop wasting time.