Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Attributable threshold signing #212

Open
mhluongo opened this issue Jul 21, 2019 · 2 comments
Open

Attributable threshold signing #212

mhluongo opened this issue Jul 21, 2019 · 2 comments
Assignees
Labels
🗣️ discussion Open discussion ⚙️ system-design Up-front system design tbtc
Milestone

Comments

@mhluongo
Copy link
Member

mhluongo commented Jul 21, 2019

We're working with @keep-network/cryptography-advisors on an approach to add attribution of malice to Gennaro and Goldfeder 2019- the protocol currently forces a group-wide abort in the case of detected malicious behavior, and naive attributability modifications might violate the security proof.

We can likely ship without attributability and add it as an upgrade to ECDSAKeeps for future Deposits, or hack around this using voting or combinatorial retries if it's an absolute requirement. Ideally, though, we'd get a core fix to the existing protocols with a few worst-case ZKPs, and perhaps co-author a paper while we're at it.

This work will be all over the place, but I'll be tracking high-level progress relevant to tBTC here.

@Shadowfiend
Copy link
Contributor

Removed this from the sprint board until we do a prioritization pass post-mainnet. We are shipping v1 without attributability, and with 3-of-3 signing.

@mhluongo
Copy link
Member Author

Since shipping tBTC v1, the world has kept on turning. Adding @eth-r as we explore Cannetti and Gennaro '20 for tBTC v2.

@mhluongo mhluongo modified the milestones: Post-mainnet, tBTC v2 Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🗣️ discussion Open discussion ⚙️ system-design Up-front system design tbtc
Projects
None yet
Development

No branches or pull requests

5 participants