From e6a9dc81809237164d24a6b833f38ea37d0a43fc Mon Sep 17 00:00:00 2001 From: Dean Eigenmann <7621705+decanus@users.noreply.github.com> Date: Wed, 11 Mar 2020 14:38:48 +0100 Subject: [PATCH] Update 2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md --- .../2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md b/_posts/2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md index a00d63a..0f54ed9 100644 --- a/_posts/2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md +++ b/_posts/2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md @@ -89,7 +89,7 @@ The above repo was used to exercise the basic paths and to gain intution of feas #### Proof time -Prove time for Semaphore (https://github.com/kobigurk/semaphore) zKSNARKs using circom, groth and snarkjs is currently way too long. It takes on the order of ~10m to generate a proof. With Websnark, it is likely to take 30s, which might still be too long. We should experiment with native code on mobile here. +Prove time for Semaphore () zKSNARKs using circom, groth and snarkjs is currently way too long. It takes on the order of ~10m to generate a proof. With Websnark, it is likely to take 30s, which might still be too long. We should experiment with native code on mobile here. See [details](https://github.com/vacp2p/research/issues/7).