user134226: The secp256k1 standard (as defined in https://www.secg.org/sec2-v2.pdf, section 2.4.1) has a set of recommended parameters.

Is there a particular reason why these parameters are just 'recommended', and not 'required'?
Are we still talking about 'secp256k1' if different parameters are used?


user208: The SEC2 document recommends the use of a number of curves. One of these curves is called secp256k1.
The recommendation doesn't refer to the parameters. What is recommended is the use of the secp256k1 curve and the parameters are integral to how the curve is defined. If you use any other parameters, you can't call it secp256k1.

134226: <p>The secp256k1 standard (as defined in <a href="https://www.secg.org/sec2-v2.pdf" rel="nofollow noreferrer">https://www.secg.org/sec2-v2.pdf</a>, section 2.4.1) has a set of recommended parameters.</p>
<ul>
<li>Is there a particular reason why these parameters are just 'recommended', and not 'required'?</li>
<li>Are we still talking about 'secp256k1' if different parameters are used?</li>
</ul>
 208: <p>The SEC2 document recommends the use of a number of curves. One of these curves is called <code>secp256k1</code>.</p>
<p>The recommendation doesn't refer to the parameters. What is recommended is the use of the <code>secp256k1</code> curve and the parameters are integral to how the curve is defined. If you use any other parameters, you can't call it <code>secp256k1</code>.</p>
