Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High-level design for efficient exact-weight TSS #17183

Open
tinker-michaelj opened this issue Dec 31, 2024 · 0 comments · May be fixed by #17199
Open

High-level design for efficient exact-weight TSS #17183

tinker-michaelj opened this issue Dec 31, 2024 · 0 comments · May be fixed by #17199
Assignees

Comments

@tinker-michaelj
Copy link
Collaborator

Problem

A threshold signature scheme (TSS) uses an access structure to control what combinations of partial signatures count as a full signature.

The natural access structure for a proof-of-stake aBFT blockchain is:

  • Partial signatures from any subset of nodes holding at least 1/3 of the stake count as a full signature.

Despite how obvious this condition is, it is extremely non-obvious how to construct a TSS with exact (e.g., 64-bit) party weights that efficiently implements this access structure.

This is because efficiency requires,

  • A stable ledger identity that provers can trust no matter how the network's membership and partial keys have evolved during any period since adoption of the TSS in which aBFT security holds.
  • Concise signatures whose size is independent of the size of the network.
  • Fixed-cost and non-interactive verification of these signatures.

But given centuries of mathematical innovation, decades of cryptography research, and finally years of accumulated ingenuity by the Hashgraph cryptography team, such a TSS now exists.

We want a design document that captures how we will implement this efficient exact-weight TSS.

Solution

Create this design document.

Alternatives

No response

@tinker-michaelj tinker-michaelj self-assigned this Dec 31, 2024
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Services Team Dec 31, 2024
@tinker-michaelj tinker-michaelj moved this from 📋 Backlog to 👷🏼‍♀️ In Progress in Services Team Dec 31, 2024
@tinker-michaelj tinker-michaelj moved this from 👷🏼‍♀️ In Progress to 👀 In Review in Services Team Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👀 In Review
Development

Successfully merging a pull request may close this issue.

1 participant