Quite! Some like big endian, because tradition (&#x27;network byte order&#x27;); little endian, because simplicity (current CPUs); mostly it&#x27;s actually just classic bikeshedding¹.<p>Since X25519 and Ed25519 had already been deployed by a fair few people, all of whom used little-endian, recommending the opposite without a compelling reason would have been a bit too silly. (Upstream working groups are encouraged to consider the field elements as opaque octet strings, to <i>try</i> to avoid arguing the exact same point again.)<p>[1] <a href="http:&#x2F;&#x2F;bikeshed.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;bikeshed.com&#x2F;</a>