Skip to content

Fix #1191: Naming convention for secret function arguments#1875

Open
kallal79 wants to merge 1 commit into
bitcoin-core:masterfrom
kallal79:fix-issue-1191-secret-naming
Open

Fix #1191: Naming convention for secret function arguments#1875
kallal79 wants to merge 1 commit into
bitcoin-core:masterfrom
kallal79:fix-issue-1191-secret-naming

Conversation

@kallal79

Copy link
Copy Markdown
Contributor

This PR establishes a formal, side-channel-aware naming convention for secret function arguments. It updates CONTRIBUTING.md to require the sec prefix for any function arguments processed in constant time. Relevant secret arguments in the API (like key32, nonce32, tweak32, and aux_rand32) have been renamed to seckey32, secnonce32, sectweak32, and aux_secrand32. Arguments that are intentionally not constant-time (such as public tweaks) remain unchanged, clearly distinguishing their behavior. All underlying source files, headers, and tests have been updated and fully tested to ensure no regressions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant