add preliminary apk-proofs spec #625
Draft
+112
−0
Conversation
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
swasilyev
reviewed
Feb 22, 2023
|
|
||
| [#sect-grandpa-apk-proof] | ||
| === Ultralight Finality Proof | ||
| A plokadot APK prover node is responsible to generate succinct proof for aggregated validator public keys who has signed a particular BEEFY message in form of a SNARK. |
0xCaso
reviewed
Mar 2, 2023
|
|
||
| [#sect-grandpa-apk-proof] | ||
| === Ultralight Finality Proof | ||
| A plokadot APK prover node is responsible to generate succinct proof for aggregated validator public keys who has signed a particular BEEFY message in form of a SNARK. |
There was a problem hiding this comment.
Suggested change
| A plokadot APK prover node is responsible to generate succinct proof for aggregated validator public keys who has signed a particular BEEFY message in form of a SNARK. | |
| A Polkadot APK prover node is responsible to generate succinct proof for aggregated validator public keys who has signed a particular BEEFY message in form of a SNARK. |
|
|
||
| In light client protocols, such commitment is used to commit to the | ||
| upcoming validator set, signed by the current validator set. Honest | ||
| validator should check the proofs of possession of each public key |
There was a problem hiding this comment.
Suggested change
| validator should check the proofs of possession of each public key | |
| validators should check the proofs of possession of each public key |
| ===== Prover | ||
|
|
||
| Prover is responsible to generate APK proofs. The `Prover` struct | ||
| encapsultes this task. It contains the following fields: |
There was a problem hiding this comment.
Suggested change
| encapsultes this task. It contains the following fields: | |
| encapsulates this task. It contains the following fields: |
| encapsultes this task. It contains the following fields: | ||
|
|
||
| * `Domains`: ??? | ||
| * `Keyset`: set of all committe public keys (?) |
There was a problem hiding this comment.
Suggested change
| * `Keyset`: set of all committe public keys (?) | |
| * `Keyset`: set of all committee public keys (?) |
0xCaso
reviewed
Mar 2, 2023
| APK proofs are SNARK based proof protocols to enable verification of | ||
| aggregated BLS signatures without the knowledge of individual public | ||
| keys of all the signers. APK proofs uses its own custom SNARK. The | ||
| protocol is implemented in two flavours: link:#BW6[BW6] and |
There was a problem hiding this comment.
just for the checks, technically both terms are correct ;)
Suggested change
| protocol is implemented in two flavours: link:#BW6[BW6] and | |
| protocol is implemented in two flavors: link:#BW6[BW6] and |
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.
This is a mainly a draft but I needed some proper way of compling the latex stuff to make sure they are correct, so I added it to the spec so I can compile the math.