Open Task RFP for Replicating circom-MP-SPDZ to support MOTION

[mhchia]

trafficstars

Open Task RFP for Replicating circom-MP-SPDZ to support MOTION

Executive Summary

• Project Overview: Replicating circom-MP-SPDZ to support MOTION.

Project Details

• Motivation:
  • This project will allow people to write Circom code and run MPC with the MOTION framework, enabling more options for benchmarks and different use cases.
  • How to do it?
    • We can reuse the code in the circom-MP-SPDZ repo. Since the input files are generic and not limited to MP-SPDZ, we should be able to adapt the functions to generate circuits and inputs for MOTION, allowing parties to easily run the MOTION framework with the generated files.
• Scope of Work:
  • Task 0: Understand circom-MP-SPDZ
    • Read the circom-MP-SPDZ write-up and understand how it works.
    • Understand the circom-MP-SPDZ repo.
  • Task 1: Understand MOTION and produce documentation for:
    • Supported features:
      • Types of gates (e.g., +, -, *, /, etc.)
      • Types of input (e.g., secret/constant integer, secret/constant fixed-point, etc.)
      • Security parameters
      • Number of parties supported
      • Best practices
      • etc.
    • How to use it with an example.
  • Task 2: Replicate circom-MP-SPDZ to circom-MOTION
    • Fork the circom-MP-SPDZ repo and replace the dependency on MP-SPDZ with MOTION.
    • Modify the code to generate circuits and inputs for MOTION.
    • Modify the code to run the generated circuits and inputs with MOTION.
    • Write unit tests for circuit generation, input generation, and circuit execution.
    • Write integration tests for the entire workflow for the example circuits: two_outputs and nn_circuit_small.
    • Write documentation for the entire workflow.
• Expected Outcomes:
  • A library for people to run MPC with MOTION, supporting the same functionality as circom-MP-SPDZ:
    • All operators defined here are supported.
      • If any operation is not supported, discuss with the grant liaison.
    • Documentation on how to use the library.
    • Tests that run example circuits correctly.
    • Support for secret integers and fixed-points, unless limited by the framework.

Qualifications

• Skills Required:
  • Circom, python
  • Knowledge in MPC/FHE, e.g. attended a course or similar experience
• Preferred Qualifications:
  • Experience in using MOTION or other MPC frameworks

Administrative Details

• Grant Liaison(s):
  • Nam
    • GitHub
  • Kevin
    • GitHub
• Estimated Project Duration:
  • Estimation: 150 hours in total
    • Task 0 (30 hours): Understand circom-MP-SPDZ and how to adapt it to work with MOTION.
    • Task 1 (30 hours): Understand MOTION and produce documentation for what is supported and how to use it (with an example).
    • Task 2 (90 hours): Replicate circom-MP-SPDZ to circom-MOTION.
• Project Complexity: Hard The grantee will need to
  • Understand the entire flow of circom-MP-SPDZ.
  • Know how MOTION works from a high-level perspective and learn how to write circuits properly.

Additional Information

• Reference Material:
  • circom-MP-SPDZ write-up
  • circom-MP-SPDZ repo
  • MOTION

Submission Details

• Proposal Deadline: The deadline for submitting proposals is the end of this round of the Acceleration Program. Refer to current round
• Submission Instructions: Please submit your proposal as an issue and link back to this issue in your proposal. Refer to proposal template for more details.

[mhchia]

Added milestones.

Milestones

Milestone 1: Understanding MOTION and Documentation

• Estimated Duration: 45 hours
• FTE: 1
• Estimated Delivery Date: [Insert Date]

Deliverables and Specifications

1a. Documentation

• A comprehensive tutorial explaining MOTION's domains, supported operations and data types (and how they are compatible with circom's operations, paying special attention to binary, arithmetic in prime field and ring $2^k$), security parameters, and number of parties supported.
• Best practices and caveats.
• Step-by-step guide on executing example scenarios (covering as much of the discovered knowledge above as possible for demonstration purposes) with MOTION.

Milestone 2: Adaptation of circom-MP-SPDZ to circom-MOTION

• Estimated Duration: 105 hours
• FTE: 1
• Estimated Delivery Date: [Insert Date]

Deliverables and Specifications

2a. Functionality: Generate Circuits for MOTION from Bristol Circuit

Modify circom-MP-SPDZ code to generate MOTION circuit output from circom-2-arithc.

2b. Functionality: Generate Inputs for MOTION from circom-MP-SPDZ Inputs

Modify circom-MP-SPDZ code to generate inputs for MOTION from the inputs defined in circom-MP-SPDZ.

2c. Functionality: Run the Generated MOTION Circuits and Inputs

Modify circom-MP-SPDZ code to run MOTION and get parsed outputs.

Application

Component 2c runs MOTION with the circuits generated by component 2a with the inputs generated from component 2b.

2d. Testing Guide

• Proper unit test coverage (e.g., above 90%) for circuit generation, input generation, and circuit execution.
• Integration tests for example circuits like op_tests, naive_search, two_outputs, and nn_circuit_small (notice that you should expect some tricky issues here due to incompatibility between circom front end and MOTION backend, and also some configurations are needed, see the original circom-MP-SPDZ for reference).

2e. Documentation

• Inline documentation of the code.
• Comprehensive documentation covering the entire workflow, from code modification to testing and execution.