Closed fscoto closed 2 years ago
Field prime is q, matching other pages + I-D.
Ah sorry, this is my fault. I was being lazy and didn’t explain my reasoning in a separate commit.
In the general case you are correct: Elligator 2 works with GF(q), where q = pn. And we shall use "q" whenever we’re talking about the general case.
Prime fields however are most common, and we often speak in contexts where we really are working under a prime field GF(p). Saying "GF(p)" when talking in a context where the field can only be prime has the advantage of providing another hint that yes, we’re talking about a prime field. On the other hand the fact that we sometimes say "GF(q)" might look like an inconsistency and distract readers.
Personally, I prefer using "GF(p)" to talk about prime fields. You can still override me if you think I’m wrong though.
No, that makes perfect sense to me if you're talking about thecase where q = p¹. I do believe this should be noted, however. How does this next commit read?
To me this is good to ship. Unless you want to re arrange the miscellaneous commit to avoid spurious modifications, we can merge.
I'm in favor of leaving history as it is.
Field prime is q, matching other pages + I-D.
Minor capitalization and wording nits.
Random oracle is a theoretical ideal like OTP for encryption; avoid claiming we can make one. There is another instance of this, but I cannot think of a nice way to resolve it.
skin: Fix
<a>
tag.