-
Notifications
You must be signed in to change notification settings - Fork 34
Normalize protocol parameter terminology across layers #1838
Copy link
Copy link
Open
Labels
cryptographyConcerned with cryptographyConcerned with cryptographyrefactoringimproving a software's internal structure without changing its external behavior or functionalityimproving a software's internal structure without changing its external behavior or functionalitytechnical debtUnaddressed shortcuts thay will become expensive problems later.Unaddressed shortcuts thay will become expensive problems later.
Description
Activity
Metadata
Metadata
Assignees
Labels
cryptographyConcerned with cryptographyConcerned with cryptographyrefactoringimproving a software's internal structure without changing its external behavior or functionalityimproving a software's internal structure without changing its external behavior or functionalitytechnical debtUnaddressed shortcuts thay will become expensive problems later.Unaddressed shortcuts thay will become expensive problems later.
Parameter names and values have different meanings across Rust, Noir, TypeScript, and Solidity. In particular,
N,T,H,NUM_PARTIES, searchN, and threshold viability values are easy to confuse.Define a shared terminology table and apply it to public types, configuration fields, generated output, and documentation. Make the distinction between committee size, honest-party count, reconstruction threshold, search parameters, and BFV parameter dimensions explicit. Add checks or typed wrappers where names alone are not enough.