public class NistCurveProcessor extends java.lang.Object implements CurveProcessor
Although the cofactor is 1 for all NIST curves, RFC 9380 still requires the "clear_cofactor" step
for consistency. In Bouncy Castle, invoking ECPoint.multiply(BigInteger.ONE) is not a
trivial no-op: it forces normalization of the internal point representation and ensures that the
returned point is in canonical affine form.
This normalization step is required for correct alignment with the specification and for matching the published test vectors. Returning the input point directly (without normalization) may leave the point in a projective or mixed representation, which causes test vector comparisons to fail even though the mathematical value of the point is the same.
| Constructor and Description |
|---|
NistCurveProcessor()
Constructs a new instance of NistCurveProcessor.
|
| Modifier and Type | Method and Description |
|---|---|
ECPoint |
add(ECPoint p,
ECPoint q)
Add two points in the curve group.
|
ECPoint |
clearCofactor(ECPoint ecPoint)
Clears the cofactor from the given elliptic curve point.
|
AffineXY |
mapToAffineXY(ECPoint p)
Converts an elliptic-curve point into the affine (x, y) coordinate representation defined by the
hash-to-curve suite.
|
public NistCurveProcessor()
public ECPoint add(ECPoint p, ECPoint q)
add in interface CurveProcessorpublic ECPoint clearCofactor(ECPoint ecPoint)
clearCofactor in interface CurveProcessorecPoint - the elliptic curve point to processpublic AffineXY mapToAffineXY(ECPoint p)
CurveProcessorThe returned coordinates are intended for serialization, testing, and interoperability with the reference outputs defined in RFC 9380. For most Weierstrass curves, this is simply the affine (x, y) coordinates of the given point. For curves that use a different coordinate model in the specification (e.g. Montgomery curves such as curve25519), this method applies the appropriate coordinate transformation.
This method does not change the underlying group element represented by the point. It only changes how that point is expressed as field elements. The input point is expected to be a valid point on the curve used by the implementation.
mapToAffineXY in interface CurveProcessorp - a valid elliptic-curve point