Skip to content
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

"Magi would operate" → "Magi will operate" ensures tense consistency. #253

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/devnet.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Devnet Environment

The devnet environment is built on the foundation of the locally available Optimism Bedrock devnet. Essentially, this environment runs `op-geth` and `geth` node in development mode, excluding the PoS client, and without finality. This is why the `--devnet` flag for Magi is necessary. This flag allows for the acceptance of any block as finalized. Otherwise, the Magi would operate exclusively with finalized blocks.
The devnet environment is built on the foundation of the locally available Optimism Bedrock devnet. Essentially, this environment runs `op-geth` and `geth` node in development mode, excluding the PoS client, and without finality. This is why the `--devnet` flag for Magi is necessary. This flag allows for the acceptance of any block as finalized. Otherwise, the Magi will operate exclusively with finalized blocks.

The devnet environment for Magi connects to the initiated OP L1 devnet node and launches its own corresponding `op-geth` node from the Magi docker. Magi employs this as its L2 node and execution engine.

Expand Down