Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add necessary features for ZSA integration #33

Conversation

ConstanceBeguier
Copy link

TODO

YaoGalteland and others added 30 commits June 3, 2024 14:32
…rcuit

Previously, the functions test_against_stored_vk and test_against_stored_proof
each generated a verification key (vk). This operation can be quite slow.
We are combining these two tests to generate the vk only once.
LookupRangeCheck45BConfig       <- LookupRangeCheckConfigOptimized
PallasLookupRangeCheck          <- PallasLookupRC
PallasLookupRangeCheckConfig    <- PallasLookupRCConfig
PallasLookupRangeCheck45BConfig <- PallasLookupConfigOptimized
Sinsemilla45BChip         <- SinsemillaChipOptimized
Sinsemilla45BInstructions <- SinsemillaInstructionsOptimized
Merkle45BChip             <- MerkleChipOptimized
Previously, the SinsemillaChip always loaded the lookup range check
without tag column and Sinsemilla45BChip always loaded the lookup
range check with tag column.
Now, we load lookup range check with or without tag according to the
lookup type (LookupRangeCheckConfig or LookupRangeCheck45BConfig).
It is now possible to use Sinsemilla/Merkle45BChip with non optimized lookup.
SinsemillaWithPrivateInitChip <- Sinsemilla45BChip
SinsemillaWithPrivateInitInstructions <- Sinsemilla45BInstructions
MerkleWithPrivateInitChip <- Merkle45BChip
…oint variable

We add enable_hash_from_private_point into SinsemillaChip in order to
put together SinsemillaChip and SinsemillaWithPrivateInitChip.
If enable_hash_from_private_point is set, it is possible to hash from
a private point. Otherwise, it is not allowed.
That allows also to put together MerkleChip and
MerkleWithPrivateInitChip.
@ConstanceBeguier ConstanceBeguier force-pushed the backward-compatibility-based-on-previous-pr branch 2 times, most recently from 6bcce18 to ab9e619 Compare July 5, 2024 11:53
@ConstanceBeguier ConstanceBeguier force-pushed the backward-compatibility-based-on-previous-pr branch from ab9e619 to 9af61eb Compare July 5, 2024 11:54
@ConstanceBeguier ConstanceBeguier changed the base branch from improve-backward-compatability-without-zsa to zsa1 July 5, 2024 13:24
@ConstanceBeguier ConstanceBeguier changed the base branch from zsa1 to improve-backward-compatability-without-zsa July 5, 2024 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant