WiP

Author: titouantanguy

…old-networking/protos/choreography.proto …re/experiments/protos/choreography.protocore/threshold-networking/protos/choreography.proto renamed to core/experiments/protos/choreography.proto core/threshold-networking/protos/choreography.proto renamed to core/experiments/protos/choreography.proto

@@ -4,3 +4,7 @@ pub mod choreography;
 pub mod conf;
 pub mod utils;
 pub mod zk_utils;
+
+pub mod choreography_gen {
+    tonic::include_proto!("ddec_choreography");
+}

core/experiments/src/lib.rs

@@ -15,7 +15,7 @@
 //! a part of the client code (along with other dependencies)
 //! into wasm and then using wasm-pack to generate the JS bindings.
 //! Care must be taken when new code is introduced to core/service
-//! or core/experiments since wasm does not support every feature
+//! or core/threshold-* since wasm does not support every feature
 //! that Rust supports. Specifically, for our use-case, we will not
 //! try to compile async, multi-threaded or IO code.
 //!

core/service/src/client/js_api.rs

@@ -97,7 +97,7 @@ pub async fn setup_threshold_no_client<
     // use NoiseFloodSmall unless some other DecryptionMode was set as parameter
     let decryption_mode = decryption_mode.unwrap_or_default();
 
-    // a vector of sender that will trigger shutdown of core/experiments servers
+    // a vector of sender that will trigger shutdown of the threshold core servers
     let mut mpc_shutdown_txs = Vec::new();
 
     for (i, (mpc_listener, _mpc_port), cur_vault) in

core/service/src/client/test_tools.rs

@@ -497,7 +497,7 @@ where
             ))
         })?;
         tracing::info!(
-            "core/experiments on {} shutdown completed successfully",
+            "Threshold core on {} shutdown completed successfully",
             mpc_socket_addr
         );
         Ok(())

core/service/src/engine/threshold/service/kms_impl.rs

@@ -12,7 +12,3 @@ mod ggen {
     #![allow(clippy::derive_partial_eq_without_eq)]
     tonic::include_proto!("ddec_networking");
 }
-
-pub mod choreography_gen {
-    tonic::include_proto!("ddec_choreography");
-}

core/threshold-networking/src/lib.rs

@@ -8,4 +8,4 @@ for operations like decryption, key generation and CRS generation.
 
 Using the KMS node the Core service will receive and validate a call and then call directly into the Threshold Service software component and ask it to execute the raw MPC protocols needed. This will make it run a specific MPC protocol with the other nodes' Threshold Services. The result will then be returned to the Core Service which will take care of encrypting/signing and any other kind of packaging before return the result to the external gRPC caller.
 
-For more details on the Connector, consult the KMS Core Service [README](../../core/service/README.md) and the Threshold Service [README](../../core/experiments/README.md). For information on how to interact with a running KMS Core (whether local or a remote deployment) consult the Core Client [README](../../core-client/README.md).
+For more details consult the KMS Core Service [README](../../core/service/README.md). For information on how to interact with a running KMS Core (whether local or a remote deployment) consult the Core Client [README](../../core-client/README.md).

docs/explanations/node.md

@@ -4,13 +4,13 @@
 Remove the core/experiments reference below when we copy this file to experiments
 since core/experiments will be at the root.
 -->
-The code under `core/experiments` implements threshold multi-party computation protocols
+The code under `core/threshold-*` implements threshold multi-party computation protocols
 such as threshold key generation, threshold decryption
 and so on for TFHE, BFV and BGV.
 The protocols are designed to be both secure and robust when a fraction
 of the parties are malicious.
 This page describes how to run the benchmarks in a wide range of configurations on the threshold protocols.
-For the rest of this page, we assume the user is working under the `core/experiments` directory.
+For the rest of this page, we assume the user is working under the `core/experiments` directory, which implements a testing environment for the MPC protocols.
 
 ## Directory overview