feat: build scalable cryptographic verification for Federation & Cross-Provider (#32)#50
Open
kasim672 wants to merge 2 commits into
Open
Conversation
kasim672
force-pushed
the
feat/issue-32-scalable-crypto-verification-federation
branch
from
July 22, 2026 18:29
0df89b3 to
7012b75
Compare
Contributor
Author
|
@keepsloading conflict is resolved |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Abstracts cryptographic proof verification payloads across the Federation & Cross-Provider Synchronization Protocol to be proving-system agnostic.
Key Improvements:
pi_a,pi_b,pi_c) fields inschemas/zk-sync-request.schema.jsonandschemas/zk-sync-response.schema.jsonwith generalizedproving_scheme(groth16,plonk,halo2) andproof_datapayloads.specs/RFC-006-Federated-State-Sync.mdwith Section 3.4 detailing scheme-agnostic batch and recursive verification mechanics across federated providers.PROTOCOL-304tospecs/EPIC-Federation-Cross-Provider-Issues.md.Closes #32