Generating and standardizing elliptic curves to use them in a cryptographic context is a hard task. There have been several attempts to define public elliptic curves for a general cryptographic use, such as NIST FIPS 186–2 curves , Brainpool curves , SECG curves , ANSSI FRP256v1 , Curve25519 , and OSCCA SM2 . Recent years have seen some distrust cast on previously standardized curves and the emergence of the need to standardize new curves. Different parties have spoken their point of view on the (dis)trust they have on previously standardized curves whether it is because of the properties they satisfy or don’t satisfy or the process used to generate them. Such analyses often come with a list of security and performance/implementation-related criteria a curve should satisfy, and a proposal on how to cor rectly generate such a curve in a way that can be trusted [10, 17, 18, 48, 2], together with a proposal of such a correctly generated curve [7, 17, 2].