Andrew Miller

The following codebase by ConsenSys appears to be based on this repo, but has fixed the build script to work with the new build system in libsnark https://github.com/ConsenSys/zero-knowledge-proofs

This kind of approach is very interesting. It would definitely be great to remove the need for pairing crypto. The tradeoff is roughly the following: Right now, it's possible to...

Ok, I didn't notice the submodules. `git clone` with `--recursive` makes progress. Now I'm able to produce iso's, but their hashes don't match. I didn't save the whole log the...

OK, I think this is probably fine. Here are my diffs. http://filebin.ca/30NaVJ3xP4gU/diff-network http://filebin.ca/30NY8Z1rLub2/diff-compute I'm not 100% sure how to read all what is different. Here's an excerpt from the `mpc_compute`...

There are two kinds of costs here, one being the computation time for the SHA2 calls, the other is the cost of accessing the memory elements. The elements in memory...

Hi Mark, thanks for looking into this and posting it. The simulation that runs from the docker file right now is probably not good for large numbers of nodes, since...

@Vagabond yes your description is exactly what I mean by "coin schedule". The trailing `...`s in the options mean repetitions of the pattern `1,0,coin()`

@ChronusZ even if every node starts by inputting `1`, and therefore every honest node sees `bin_values={1}`, it is still necessary to continue participating in the protocol until another coin returns...

> @amiller It doesn't really matter if the actual process needs to continue longer after you've already produced an output right? Continuing longer only parallelizes with the rest of the...

Here's my current thinking: I can issue additional *more permissive* licenses as time progresses, but cannot effectively withdraw existing ones. I like to use CRAPL as a conservative default for...