Skip to content

Introduce new SignatureScheme enum variant for Robust ECDSA and use it in the contract. #1638

Closed

Description

@netrome

Background

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.

Resources & Additional Notes

#1473 (comment)

Activity

  1. added this to the Robust ECDSA milestone on Dec 10, 2025
  2. 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
  3. netrome commented on Dec 10, 2025

    @netrome
    CollaboratorAuthor

    Base the work on introduce_signature_scheme_v2_secp256_k1 to avoid conflicts with #1640

  4. kevindeforth commented on Dec 10, 2025

    @kevindeforth
    Contributor

    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

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions