doc: mention ctx requirement for `_ellswift_create` (not secp256k1_context_static)
What the developer wrote
Authored by Sebastian Falbesoner
doc: mention ctx requirement for `_ellswift_create` (not secp256k1_context_static)
What changed, and why it matters
This is a one-line documentation update. It clarifies that a specific function should not be called with a special read-only context object named secp256k1_context_static. There is no code change and no security fix.
No action needed; treat as a routine documentation clarification.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit changes only a header comment for secp256k1_ellswift_create, adding the parenthetical note ‘(not secp256k1_context_static)’ to the ctx parameter description. The implementation is untouched. It is a documentation-only clarification about API usage requirements.
Changed components
include/secp256k1_ellswift.hInspect captured patch +1 / −1
diff --git a/include/secp256k1_ellswift.h b/include/secp256k1_ellswift.h
index 0d1293e..4cda5d5 100644
--- a/include/secp256k1_ellswift.h
+++ b/include/secp256k1_ellswift.h
@@ -130,7 +130,7 @@ SECP256K1_API int secp256k1_ellswift_decode(
*
* Returns: 1: secret was valid, public key was stored.
* 0: secret was invalid, try again.
- * Args: ctx: pointer to a context object
+ * Args: ctx: pointer to a context object (not secp256k1_context_static)
* Out: ell64: pointer to a 64-byte array to receive the ElligatorSwift
* public key
* In: seckey32: pointer to a 32-byte secret key
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.