forked from visoftsolutions/noir_rs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: Use simple "flat" CRS. (AztecProtocol#3748)
There's no need for us to have such a convoluted set of transcripts for our CRS in a complicated format. This: * Uses a single 6GB "flat" CRS with no header data in the ignition s3 bucket, in normalised big-endian form. * Allows us to use our normal deserialization functions for the fields, as opposed to specific custom SRS reading code. * Means we can now download, without complexity, any size CRS we need. * Changes names to eg `bn254_g1.dat` so doesn't conflict with old cache. * Get's rid of `size` file and just directly analyses file sizes. It doesn't address: * The new grumpkin CRS that arrived yesterday. Someone else can tackle that one. We also need to figure out how to generate a real one. Another trusted setup??....
- Loading branch information
1 parent
7c43145
commit 6bd1984
Showing
8 changed files
with
108 additions
and
112 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters