Threshold ECDSA

Validators utilize the shared secrets created during the DKG process to sign various data, including transactions. When a significant portion of the network, such as N/X (e.g., 3/4), signs the same data using their DKG artifacts, the resulting signature is recognized as being signed by the collective address generated during DKG.

In addition to transaction signing, the consensus mechanism mandates the signing of any data originating from the network. This ensures that all decisions made by the network can be verified and validated.

For instance, when an HTTP request is sent, it must be signed by the network, with the signature placed in a special header. The recipient of the request can retrieve the signature and verify its authenticity by cross-referencing it with the collective address obtained from the SignerStorage. This verification process confirms that the request was indeed signed by the network, and the signature aligns with the payload.

Learn more about Threshold ECDSA here.