Workflows

Phase 1

Steps:

• Orchestrator defines a Session
• Session stores information regarding what would be run at the parties involved in the MPC
• The session is sent to the parties

Phase 2

Steps:

• Orchestrator can
  • 1. share a value with other parties involved in the computation
  • 2. share a remote value (a pointer) hold by one of the parties - it uses [PRZS] (TBD) for doing this
• The shares are:
  • 1. created at the orchestrator and distributed to the parties
  • 2. created directly on the parties using the already shared seeds

Phase 3

• Orchestrator can use different operations on the shares
• The operations are implemented at the MPCTensor level