Skip to content

Conversation

@ec2
Copy link
Member

@ec2 ec2 commented Dec 19, 2025

No description provided.

@neutronmoderator
Copy link
Collaborator

@ec2 is this up to date? Otherwise happy to merge this, just need to fetch latest master changes to fix CI test failing

{/* </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.

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

{/* </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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"require is" => "are"

- 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
Copy link

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?

@ec2
Copy link
Member Author

ec2 commented Jan 9, 2026

Hey! Just got back from vacay, sorry for late reply. Looks like the PR feedback was addresed! It should be good to merge

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.

5 participants