Understanding DKG

February 23, 2013 | Posted in Asynchronous Key Generation for IBE

The DKG source is programmed in C++. It requires the PBC library, which in turn depends on the GMP library.

The main code of the DKG lies in node.cc. This file starts a thread and runs a DKG node at a specified port.

The node:run() runs a code that executes functions based on the network messages and user messages.

Based on various messages received (network), the run() calls the following functions:

  1. hybridVSSInit
  2. startAgreement
  3. completeDKG
  4. sendLeaderChangeMessage
  5. changePhase

The code for these functions must be studied to understand how messages are declared and sent. For adding the required functions and features, I would have to declare network messages (in networkmessage.h and networkmessage.cc), add functions in class Node() and add event code to respond to the new messages and call the corresponding new functions from Node().

Related Posts

16 Mar 2013 » Decryption for distributed Boneh-Franklin IBC

16 Mar 2013 » Encryption for distributed Boneh-Franklin IBC

15 Mar 2013 » Hash functions for distributed Boneh Franklin IBC

05 Mar 2013 » Importing and exporting an element in PBC

02 Mar 2013 » Using python to complete IBC

27 Feb 2013 » Modifying a DKG header

23 Feb 2013 » Analyzing messages in DKG

20 Feb 2013 » Pseudo code for the mathematical functions

19 Feb 2013 » Modifying the DKG protocol

19 Feb 2013 » The DKG protocol, in short

19 Feb 2013 » The DKG Protocol

19 Feb 2013 » Asynchronous Distributed Key Generation for Identity-Based Cryptography

19 Feb 2013 » Distributed Key Generation

19 Feb 2013 » Boneh Franklin IBC using the PBC library