ingonyama-zk / blaze Goto Github PK

result param shouldn't be hardcoded to usize.

The arkworks-rs 0.4.0 may be coming in this month.

Are you interested in the discussion of integration? We can have some formal discussion in one or two weeks... but the idea is to make this a plug-in alternative as a backend for arkworks-rs.

The API would be the one that needs to most attention---since 0.5.0 may be two years later. In the worst case, a fork with patches-crates.io provides a drop-in replacement.

At first, maybe we will do it in the same machine (i.e., local), and then we can think about a distributed manner.

Description

Require to move dev specific dependencies into [dev-dependencies].

Motivation

Tests require generation of examples and the libraries that are used now are pulled in when building the project, although they can be replaced

Hi,

I've been searching for a prover as a service that let's you effortlessly deploy and scale a prover for an application that relies on proof generation. There are many applications where it's okay to generate a proof in a server for use elsewhere without exposing any useful private inputs. If anyone has a suggestion, or knows if Ingonyama is heading in this direction, please let me know.

Cheers!

Trying to use the published AFI specified here - https://github.com/ingonyama-zk/cloud-ZK/blob/main/A_Step-by-step_guide_for_building_an_AWS_AFI.MD#load-the-afi but it's not found

Within the F1 instance

sudo fpga-load-local-image -S 0 -I agfi-00b931a86bfddf91d
Error: (5) invalid-afi-id
The agfi id passed is invalid or you do not have permission to load

Using CLI

aws ec2 describe-fpga-images --fpga-image-ids afi-08036a63bbd0a73d2 --region us-east-1

An error occurred (InvalidFpgaImageID.NotFound) when calling the DescribeFpgaImages operation: Image ID 'afi-08036a63bbd0a73d2' not found.

Description

Make precompute factor not hard coded in tests

Should the package be named blaze rather then ingo-fpga?

copy them over from private repo

Hey all, I was just going through the repository and associated blog: https://www.ingonyama.com/blog/hardware-review-gpus-fpgas-and-zero-knowledge-proofs.

The blog compares your work @ 128 MHz with Sppark's MSM. I wonder if you have also closed timing with a higher frequency (350+ MHz) and have results just to see what kind of peak performance is possible and if that gets close to the state-of-the-art GPU performance.

Thanks a lot in advance!