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

dkg/modular-frost 2.0 #195

Closed
kayabaNerve opened this issue Dec 27, 2022 · 1 comment
Closed

dkg/modular-frost 2.0 #195

kayabaNerve opened this issue Dec 27, 2022 · 1 comment
Labels
cryptography An issue involving cryptography/a cryptographic library discussion This requires discussion

Comments

@kayabaNerve
Copy link
Member

While it's somewhat ridiculous to discuss a 2.0 before a 1.0, there are a series of features I'd love to support which likely won't be included in the 1.0 release, yet would be breaking changes.

  • Arbitrary mutations to keys. Right now, we only support an additive offset. Monero uses the lagrange coefficient as a multiplier before adding that offset. This could be rewritten as [Mul(lagrange), Add(offset)]. Such arbitrary handling would enable easy integration with protocols such as Sub-FROST #80, while simultaneously making the lagrange function modular. This is notable as for MuSig Support Musig2 key aggregation in dkg #186, we have to define a key of key * binding * lagrange.inverse(), so when the lagrange is applied, it restores to key. Ideally, we just write [Mul(binding)].

  • Composable chaining between MuSig and FROST. While personally, I'd argue since FROST can be used everywhere it should be, I'd highlight the potential desire to use FROST in a MuSig instance which is unaware to any such sub-protocol. Accordingly, we need to support MuSig proper. This likely would be defining a two-round signature protocol crate, which a theoretical MuSig crate and the FROST crate would inherent from.

  • Abstracted key handling. Right now, the DKG stores keys in RAM. Ideally, this could be anything from the SGX (SGX-backed key management #95) to a hardware wallet.

  • Sub-FROST (Sub-FROST #80), which would be enabled via the prior bullet point.

@kayabaNerve kayabaNerve added discussion This requires discussion cryptography An issue involving cryptography/a cryptographic library labels Dec 27, 2022
@kayabaNerve
Copy link
Member Author

While I appreciate this issue existing, providing a list of items which could fit into a 2.0, we don't have the bandwidth nor benefit to work on this at this time. Since we have no active interest, I'd rather re-open this when things change then keep it open.

@kayabaNerve kayabaNerve closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2023
@kayabaNerve kayabaNerve mentioned this issue Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cryptography An issue involving cryptography/a cryptographic library discussion This requires discussion
Projects
None yet
Development

No branches or pull requests

1 participant