Add locad devnet guide#3350
Open
nuke-web3 wants to merge 2 commits into
Open
Conversation
Contributor
📝 WalkthroughWalkthroughThis PR adds a comprehensive local deployment guide documenting how to run a complete Evolve EVM chain on a developer machine using ev-toolbox with the local-da mock data availability layer, plus updates the deployment guides index to reference it. ChangesLocal Deployment Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Author
|
Context: working on Eden docs and want to experiment with evolve and, ideally, get something like |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/guides/deploy/local.md`:
- Around line 65-69: The fenced code block in docs/guides/deploy/local.md
showing the example daemon logs lacks a language identifier; update the opening
fence for that block to include a language tag (e.g., use ```text) so the log
output renders correctly and is accessible—locate the fenced block with the
three "INF ..." log lines and change its opening backticks to ```text.
- Around line 101-110: Add a language identifier "text" to the fenced code block
that contains the sequencer startup logs (the block starting with
"single-sequencer | 🚀 INIT: Starting EVM Sequencer initialization" and the
following lines) so the snippet renders correctly; update the opening fence from
``` to ```text and leave the block content unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7560ebdd-67b0-46e8-bedf-bccc3155291d
📒 Files selected for processing (2)
docs/guides/deploy/local.mddocs/guides/deploy/overview.md
Comment on lines
+65
to
+69
| ``` | ||
| INF NewLocalDA: initialized LocalDA component=da | ||
| INF Listening on component=da host=0.0.0.0 maxBlobSize=1970176 port=7980 | ||
| INF server started component=da listening_on=0.0.0.0:7980 | ||
| ``` |
Contributor
There was a problem hiding this comment.
Add language identifier to code block.
The fenced code block showing expected output should specify a language identifier for proper rendering and accessibility.
📝 Proposed fix
-```
+```text
INF NewLocalDA: initialized LocalDA component=da
INF Listening on component=da host=0.0.0.0 maxBlobSize=1970176 port=7980
INF server started component=da listening_on=0.0.0.0:7980</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 65-65: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/guides/deploy/local.md` around lines 65 - 69, The fenced code block in
docs/guides/deploy/local.md showing the example daemon logs lacks a language
identifier; update the opening fence for that block to include a language tag
(e.g., use ```text) so the log output renders correctly and is accessible—locate
the fenced block with the three "INF ..." log lines and change its opening
backticks to ```text.
Source: Linters/SAST tools
Comment on lines
+101
to
+110
| ``` | ||
| single-sequencer | 🚀 INIT: Starting EVM Sequencer initialization | ||
| single-sequencer | ✅ SUCCESS: Sequencer initialization completed | ||
| single-sequencer | ✅ SUCCESS: Exported genesis.json to /volumes/sequencer_export/genesis.json | ||
| single-sequencer | ✅ SUCCESS: Successfully retrieved genesis hash: 0x6aec2... | ||
| single-sequencer | 🚀 INIT: Starting EVM sequencer with command: evm start ... | ||
| single-sequencer | INF Starting aggregator node component=main | ||
| single-sequencer | INF produced block component=executor height=1 | ||
| single-sequencer | INF produced block component=executor height=2 | ||
| ``` |
Contributor
There was a problem hiding this comment.
Add language identifier to code block.
The fenced code block showing healthy startup output should specify a language identifier.
📝 Proposed fix
-```
+```text
single-sequencer | 🚀 INIT: Starting EVM Sequencer initialization
single-sequencer | ✅ SUCCESS: Sequencer initialization completed
single-sequencer | ✅ SUCCESS: Exported genesis.json to /volumes/sequencer_export/genesis.json
single-sequencer | ✅ SUCCESS: Successfully retrieved genesis hash: 0x6aec2...
single-sequencer | 🚀 INIT: Starting EVM sequencer with command: evm start ...
single-sequencer | INF Starting aggregator node component=main
single-sequencer | INF produced block component=executor height=1
single-sequencer | INF produced block component=executor height=2</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 101-101: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/guides/deploy/local.md` around lines 101 - 110, Add a language
identifier "text" to the fenced code block that contains the sequencer startup
logs (the block starting with "single-sequencer | 🚀 INIT: Starting EVM
Sequencer initialization" and the following lines) so the snippet renders
correctly; update the opening fence from ``` to ```text and leave the block
content unchanged.
Source: Linters/SAST tools
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
First pass at a working local devnet using https://github.com/evstack/ev-toolbox/tree/main/ev-stacks .
In experimenting, I think we should first modify the tooling used just a bit to be a more functional and "one click" docker compose flow /
justrecipe to streamline things a bit more. Before I do that, would love a first pass review 🙏Summary by CodeRabbit