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.

Sign up for GitHub

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

correction mdx files #1391

Merged
merged 5 commits into from
Feb 20, 2025
Merged

correction mdx files #1391

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
25ddba1
Update holocene-changes.mdx
eeemmmmmm Feb 19, 2025
47bdf33
Update pectra-changes.mdx
eeemmmmmm Feb 19, 2025
3fc11e7
Update batcher.mdx
eeemmmmmm Feb 19, 2025
25916cb
Update genesis.mdx
eeemmmmmm Feb 19, 2025
e9123c3
Update op-txproxy.mdx
eeemmmmmm Feb 19, 2025
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: 0 additions & 2 deletions pages/notices/holocene-changes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,6 @@ If you experience difficulty at any stage of this process, please reach out to [

The Holocene upgrade for the Soneium Minato (Sepolia) will be activated at **Fri Dec 20 at 09:00:00 UTC** (`1734685200`).

The Holocene upgrade for the Soneium Minato (Sepolia) will be activated at **Fri Dec 20 at 09:00:00 UTC** (`1734685200`).

The Holocene upgrade for the Mainnet Superchain is scheduled for **Thu 9 Jan 2025 18:00:01 UTC**, [governance approval](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515).

The Holocene upgrade for the Soneium Mainnet will be activated at **Mon Feb 03 at 09:00:00 UTC** (`1738573200`).
Expand Down
2 changes: 1 addition & 1 deletion pages/notices/pectra-changes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ The following sections are how chain operators can prepare the first part of the
## For fault proof enabled chains

<Callout type="info">
The following instructions assume your chain is on the latest contract release `op-contracts/v1.8.0` and have Holocene activated.
The following instructions assume your chain is on the latest contract release `op-contracts/v1.8.0` and has Holocene activated.
</Callout>

The following steps are to update your absolute prestate with new dispute game contracts. **This is absolutely necessary for chains running permissionless fault proofs.** For chains running the Fault Proof System with permissioned games you can skip this section because games will not be played out and the absolute prestate is not used.
Expand Down
2 changes: 1 addition & 1 deletion pages/operators/chain-operators/configuration/batcher.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ You can use [this calculator](https://docs.google.com/spreadsheets/d/12VIiXHaVEC

### Set your `--batch-type=1` to use span batches

Span batches reduce the overhead of OP Stack chains, introduced in Delta network upgrade. This is beneficial for sparse and low-throughput OP Stack chains.
Span batches reduce the overhead of OP Stack chains, introduced in the Delta network upgrade. This is beneficial for sparse and low-throughput OP Stack chains.

The overhead is reduced by representing a span of consecutive L2 blocks in a more efficient manner, while preserving the same consistency checks as regular batch data.

Expand Down
2 changes: 1 addition & 1 deletion pages/operators/chain-operators/deploy/genesis.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ This command:

### Step 2: Generate your L2 genesis file and rollup file

After your L1 contracts have been deployed, generate the L2 genesis and rollup configuration files by inspecting the deployer's `state.json.`
After your L1 contracts have been deployed, generate the L2 genesis and rollup configuration files by inspecting the deployer's `state.json`

```bash
./bin/op-deployer inspect genesis --workdir .deployer <L2_CHAIN_ID> > .deployer/genesis.json
Expand Down
2 changes: 1 addition & 1 deletion pages/operators/chain-operators/tools/op-txproxy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Even though the op-geth implementation of this endpoint includes rate limits, it

* Conditional cost is below the max
* Conditional values are valid (i.e min \< max)
* Transaction target are only 4337 Entrypoint contracts
* Transaction targets are only 4337 Entrypoint contracts

<Callout type="info">
The motivating factor for this endpoint is to enable permissionless 4337 mempools, hence the restricted usage of this methods to just [Entrypoint](https://github.com/eth-infinitism/account-abstraction/blob/develop/contracts/core/EntryPoint.sol) transactions.
Expand Down