You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Introduce new SignatureScheme enum variant for Robust ECDSA and use it in the contract. #1638
The first step in integrating Robust ECDSA in the MPC code is to upgrade the SignatureScheme enum variant to support Robust ECDSA as a new domain and make the necessary contract changes to support creating a new domain for Robust ECDSA.
User Story
As a node operator I want to be able to support the new Robust ECDSA scheme.
Acceptance Criteria
The MPC contract supports creating a new domain for Robust ECDSA. The MPC nodes will initially ignore these domains.
changed the title [-]Introduce new `SignatureScheme` enum variant for Robust ECDSA and use it in the contract[/-][+]Introduce new `SignatureScheme` enum variant for Robust ECDSA and use it in the contract.[/+]on Dec 10, 2025
Activity
[-]Introduce new `SignatureScheme` enum variant for Robust ECDSA and use it in the contract[/-][+]Introduce new `SignatureScheme` enum variant for Robust ECDSA and use it in the contract.[/+]netrome commentedon Dec 10, 2025
Base the work on introduce_signature_scheme_v2_secp256_k1 to avoid conflicts with #1640
kevindeforth commentedon Dec 10, 2025
This might get a bit more complicated, as the robust ecdsa will require a different threshold value from what we use right now in the contract
c.f. https://nearone.slack.com/archives/C0912BTG51T/p1765383919608359?thread_ts=1765374628.931179&cid=C0912BTG51T