Practical Asynchronous Distributed Key Generation

Practical Asynchronous Distributed Key Generation
复制标题

DOI:
10.1109/sp46214.2022.9833584
复制
发表时间:
2022-05
期刊:
2022 IEEE Symposium on Security and Privacy (SP)
影响因子:
--
通讯作者:
Sourav Das;Thomas Yurek;Zhuolun Xiang;Andrew K. Miller;Lefteris Kokoris-Kogias;Ling Ren
Sourav Das;Thomas Yurek;Zhuolun Xiang;Andrew K. Miller;Lefteris Kokoris-Kogias;Ling Ren
中科院分区:
其他
文献类型:
--
作者:
Sourav Das;Thomas Yurek;Zhuolun Xiang;Andrew K. Miller;Lefteris Kokoris-Kogias;Ling Ren

文献摘要

相似文献

分布式密钥生成(DKG)是一种在没有可信第三方的情况下引导阈值密码系统的技术,并且是分散式协议(如随机性信标,阈值签名和一般多方计算)的构建块。直到最近,DKG协议都假设了同步模型,因此当它们的底层网络假设不成立时,它们是脆弱的。异步DKG协议的最新进展是不够的,因为它们要么效率低下,要么功能有限,导致缺乏具体的实现。在本文中,我们提出了一个简单而具体有效的异步DKG(ADKG)协议。在n个节点的网络中,我们的ADKG协议可以容忍$t\lt n/3$个恶意节点,并且具有$O(\kappa n^{3})$的通信开销,其中$\kappa$是安全参数。我们的ADKG协议产生一个字段元素作为秘密,因此与现成的阈值密码系统兼容。我们实现了我们的ADKG协议,并使用地理上分布的AWS实例中多达128个节点的网络对其进行评估。我们的评估表明,我们的协议需要低至3和9.5秒终止32和64个节点,分别。此外,每个节点在两个实验期间分别仅发送0.7 MB和2.9 MB的数据。
Distributed Key Generation (DKG) is a technique to bootstrap threshold cryptosystems without a trusted third party and is a building block to decentralized protocols such as randomness beacons, threshold signatures, and general multiparty computation. Until recently, DKG protocols have assumed the synchronous model and thus are vulnerable when their underlying network assumptions do not hold. The recent advancements in asynchronous DKG protocols are insufficient as they either have poor efficiency or limited functionality, resulting in a lack of concrete implementations. In this paper, we present a simple and concretely efficient asynchronous DKG (ADKG) protocol. In a network of n nodes, our ADKG protocol can tolerate up to $t\lt n/3$ malicious nodes and have an expected $O(\kappa n^{3})$ communication cost, where $\kappa$ is the security parameter. Our ADKG protocol produces a field element as the secret and is thus compatible with off-the-shelf threshold cryptosystems. We implement our ADKG protocol and evaluate it using a network of up to 128 nodes in geographically distributed AWS instances. Our evaluation shows that our protocol takes as low as 3 and 9.5 seconds to terminate for 32 and 64 nodes, respectively. Also, each node sends only 0.7 Megabytes and 2.9 Megabytes of data during the two experiments, respectively.