Skip to content

Conversation

@JereSalo
Copy link
Contributor

@JereSalo JereSalo commented Dec 4, 2025

Motivation

  • Address feedback that was given to L2 docs by external users

Description

  • Add info on gas limits
  • Move aligned docs to deployment section
  • Use cargo install instead of cargo build
  • Clarify relationship between building binary with sp1 and risc0 and then initializing contracts setting what proofs to require. That if both are set to true then both proofs will be required for settlement.

@JereSalo JereSalo marked this pull request as ready for review December 4, 2025 21:35
@JereSalo JereSalo requested a review from a team as a code owner December 4, 2025 21:35
Copilot AI review requested due to automatic review settings December 4, 2025 21:35
@JereSalo JereSalo added docs Improvements or additions to documentation L2 Rollup client labels Dec 4, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR improves the quality and usability of L2 deployment documentation based on external user feedback. The changes make the documentation more accessible by switching from cargo build to cargo install, clarify the relationship between build-time and deploy-time proving system configuration, add crucial gas limit tuning information, and reorganize the Aligned integration documentation to be more discoverable within the deployment section.

Key changes:

  • Replaced cargo build with cargo install across all deployment documentation to simplify binary installation and ensure it's in $PATH
  • Added documentation for gas limit configuration parameters (--block-producer.block-gas-limit and --committer.batch-gas-limit)
  • Clarified that enabling multiple proving systems (e.g., both SP1 and RISC0) at deploy time requires all selected proofs for settlement
  • Moved Aligned integration documentation from docs/l2/aligned_integration.md to docs/l2/deployment/aligned.md for better organization

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 11 comments.

Show a summary per file
File Description
docs/l2/deployment/vanilla.md Added clarification about multi-proof requirements and gas limit configuration documentation
docs/l2/deployment/validium.md Added clarification about multi-proof requirements and gas limit configuration documentation
docs/l2/deployment/prover/overview.md Changed from cargo build to cargo install, added installation path info, and clarified proving system requirements
docs/l2/deployment/overview.md Changed from cargo build to cargo install, added installation path info, and clarified proving system requirements
docs/l2/deployment/aligned.md New file with Aligned integration guide (moved from aligned_integration.md) with updated commands using cargo install
docs/l2/deployment/README.md Added link to new Aligned documentation location in deployment section
docs/l2/aligned_integration.md Removed file (content moved to deployment/aligned.md)
docs/SUMMARY.md Updated navigation to reflect new Aligned documentation location under deployment section

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


> [!NOTE]
> This command requires the `COMPILE_CONTRACTS` env variable to be set, as the deployer needs the SDK to embed the proxy bytecode.
> In this step we are initializing the `OnChainProposer` contract with the `ALIGNED_PROOF_AGGREGATOR_SERVICE_ADDRESS` and skipping the rest of verifiers; you can find the address for the aligned aggregator service [here](https://docs.alignedlayer.com/guides/7_contract_addresses).
Copy link

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

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

Typo: "initiallizing" should be "initializing".

Copilot uses AI. Check for mistakes.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It says initializing...

```shell
# For SP1 CPU proving (very slow, not recommended)
cargo build --release --bin ethrex --features l2,l2-sql,sp1
cargo install --path cmd/ethrex --bin ethrex --features l2,l2-sql,sp1
Copy link
Contributor

@ilitteri ilitteri Dec 5, 2025

Choose a reason for hiding this comment

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

--locked is missing for all the install commands.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are right, added --locked to every cargo install I saw 9929ce3

Copy link
Contributor

@ilitteri ilitteri left a comment

Choose a reason for hiding this comment

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

  • All the cargo install commands are missing the --locked flag.
  • Some Copilot suggestions are worth applying.

@github-project-automation github-project-automation bot moved this to Requires Changes in ethrex_l2 Dec 5, 2025
@JereSalo
Copy link
Contributor Author

JereSalo commented Dec 9, 2025

  • All the cargo install commands are missing the --locked flag.

9929ce3

  • Some Copilot suggestions are worth applying.

af3c3b7
ce572eb

@JereSalo JereSalo requested a review from ilitteri December 9, 2025 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to documentation L2 Rollup client

Projects

Status: Requires Changes

Development

Successfully merging this pull request may close these issues.

3 participants