-
Notifications
You must be signed in to change notification settings - Fork 0
Add docs on claim digest match and blake3 #8
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
base: master
Are you sure you want to change the base?
Conversation
|
@ec2 is this up to date? Otherwise happy to merge this, just need to fetch latest master changes to fix CI test failing |
developers/tutorials/proof-types.mdx
Outdated
| {/* </StripRustCodeComments> */} | ||
|
|
||
| In addition, Boundless also supports requesting a Blake3 Groth16 proof. This proof type allows for proofs to be verified in environments where SHA2 hashing is impossible or expensive (e.g. BitVM). You can specify this in your proof request by setting the `proof_type` to `ProofType::Blake3Groth16`: | ||
| Note: Blake3 Groth16 proofs require is only supported with the `ClaimDigestMatch` predicate, meaning that you should only use this if you do not require the journal to be delivered on-chain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be important to note that with this proof type the journal must be of 32 bytes
developers/tutorials/proof-types.mdx
Outdated
| {/* </StripRustCodeComments> */} | ||
|
|
||
| In addition, Boundless also supports requesting a Blake3 Groth16 proof. This proof type allows for proofs to be verified in environments where SHA2 hashing is impossible or expensive (e.g. BitVM). You can specify this in your proof request by setting the `proof_type` to `ProofType::Blake3Groth16`: | ||
| Note: Blake3 Groth16 proofs require is only supported with the `ClaimDigestMatch` predicate, meaning that you should only use this if you do not require the journal to be delivered on-chain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"require is" => "are"
developers/tutorials/proof-types.mdx
Outdated
| - If you only need on-chain verification, use the default merkle inclusion proof | ||
| - If you need cross-chain verification or raw proof data, use Groth16 | ||
| - If you need to compose the proof by verifying it within another zkVM guest program, use Groth16 | ||
| - If you don't need the journal to be authenticated, consider using the ClaimDigestMatch predicate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, is authenticated the correct term? Cause doesn't claim digest essentially authenticate the journal also?
|
Hey! Just got back from vacay, sorry for late reply. Looks like the PR feedback was addresed! It should be good to merge |
No description provided.