We need to have two machines (hence 2PC) for the process: a garbler (in Tandem's language, Contributor) and a node (that will evolve towards being the VM - in Tandem's language, Evaluator).
The Contributor is the client/who garbles. In our current architecture, it would be the Secure Binder.
Right now, our implementation on cryptomata simulates the execution by creating a local Evaluator and Contributor, which has effectively zero latency and ideal network conditions. We now need to separate both entities so that each lives in a different machine.
Associated with this: on the process of building a circuit, we need to generate it separately, instead of building AND executing. They need to be separate things.
NMCarv
commented
2 weeks ago
Idea
We need to have two machines (hence 2PC) for the process: a garbler (in Tandem's language,
Contributor) and a node (that will evolve towards being the VM - in Tandem's language,Evaluator).The Contributor is the client/who garbles. In our current architecture, it would be the Secure Binder.
Right now, our implementation on
cryptomatasimulates the execution by creating a local Evaluator and Contributor, which has effectively zero latency and ideal network conditions. We now need to separate both entities so that each lives in a different machine.Associated with this: on the process of building a circuit, we need to generate it separately, instead of building AND executing. They need to be separate things.
Resources
tandem_http_serverandtandem_http_client.