Skip to content

Normalize protocol parameter terminology across layers #1838

Description

@0xjei

Parameter names and values have different meanings across Rust, Noir, TypeScript, and Solidity. In particular, N, T, H, NUM_PARTIES, search N, 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cryptographyConcerned with cryptographyrefactoringimproving a software's internal structure without changing its external behavior or functionalitytechnical debtUnaddressed shortcuts thay will become expensive problems later.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions