docs: aggregation mode #1964
Open
docs: aggregation mode #1964
Conversation
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
JuArce
reviewed
Jun 6, 2025
| The final aggregated proof and its blob are sent to the `AlignedProofAggregationService` contract for verification. | ||
|
|
||
| > [Note] | ||
| > Currently if you want your proof to be verified in the `AggregationMode` you need to submit it via the `VerificationLayer` (a.k.a `FastMode`). As explained above, in the next run the `AggregationMode` will fetch your proof from the `VerificationLayer` batches in spite of its verification status. |
There was a problem hiding this comment.
Suggested change
| > Currently if you want your proof to be verified in the `AggregationMode` you need to submit it via the `VerificationLayer` (a.k.a `FastMode`). As explained above, in the next run the `AggregationMode` will fetch your proof from the `VerificationLayer` batches in spite of its verification status. | |
| > Currently if you want your proof to be verified in the `AggregationMode` you need to submit it via the `VerificationLayer`. As explained above, in the next run the `AggregationMode` will fetch your proof from the `VerificationLayer` batches in spite of its verification status. |
| @@ -0,0 +1,208 @@ | |||
| ## Aggregation Mode L2 integration example | |||
|
|
|||
| This guide demonstrates how to build a toy L2 application that integrates with Aligned Aggregation Mode. The L2 does not post state diffs or any data to Ethereum, only commitments. The prover has to prove that: | |||
There was a problem hiding this comment.
Suggested change
| This guide demonstrates how to build a toy L2 application that integrates with Aligned Aggregation Mode. The L2 does not post state diffs or any data to Ethereum, only commitments. The prover has to prove that: | |
| This guide demonstrates how to build a dummy L2 application that integrates with Aligned Aggregation Mode. The L2 does not post state diffs or any data to Ethereum, only commitments. The prover has to prove that: |
JuArce
approved these changes
Jun 6, 2025
Co-authored-by: Julian Arce <52429267+JuArce@users.noreply.github.com>
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.
Description
Adds a new document to explain the internals of the
AggregationMode+ the inclusion of thel2example in the main docs.Type of change
Please delete options that are not relevant.
Checklist
testnet, everything else tostaging