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

Jump to bottom

Fixed errors in RPC and typos in docs #1014

Merged
merged 2 commits into from
Oct 22, 2024
Merged

Fixed errors in RPC and typos in docs #1014

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
306aa31
Fixed errors and typos in docs
intls Oct 22, 2024
47bce27
Merge branch 'main' into docs_errors
intls Oct 22, 2024
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
14 changes: 7 additions & 7 deletions pages/builders/chain-operators/configuration/rollup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ and is used as part of building the L2 genesis state.
* **Default value:** None
* **Recommended value:**
* **Notes:** Must not be `address(0)`
* **Standard Config Requirement:** Implementation contract must the most
* **Standard Config Requirement:** Implementation contract must be the most
up-to-date, governance-approved version of the OP Stack codebase, and, if the
chain has been upgraded in the past, that the previous versions were a standard
release of the codebase.
Expand All @@ -196,7 +196,7 @@ genesis state.
* **Default value:** None
* **Recommended value:**
* **Notes:** Must not be `address(0)`
* **Standard Config Requirement:** Implementation contract must the most
* **Standard Config Requirement:** Implementation contract must be the most
up-to-date, governance-approved version of the OP Stack codebase, and, if the
chain has been upgraded in the past, that the previous versions were a standard
release of the codebase.
Expand All @@ -212,7 +212,7 @@ used as part of building the L2 genesis state.
* **Default value:** None
* **Recommended value:**
* **Notes:** Must not be `address(0)`
* **Standard Config Requirement:** Implementation contract must the most
* **Standard Config Requirement:** Implementation contract must be the most
up-to-date, governance-approved version of the OP Stack codebase, and, if the
chain has been upgraded in the past, that the previous versions were a standard
release of the codebase.
Expand All @@ -228,7 +228,7 @@ used as part of the derivation pipeline.
* **Default value:** None
* **Recommended value:**
* **Notes:** Must not be `address(0)`
* **Standard Config Requirement:** Implementation contract must the most
* **Standard Config Requirement:** Implementation contract must be the most
up-to-date, governance-approved version of the OP Stack codebase, and, if the
chain has been upgraded in the past, that the previous versions were a standard
release of the codebase.
Expand All @@ -244,7 +244,7 @@ is used as part of the derivation pipeline.
* **Default value:** None
* **Recommended value:**
* **Notes:** Must not be `address(0)`
* **Standard Config Requirement:** Implementation contract must the most
* **Standard Config Requirement:** Implementation contract must be the most
up-to-date, governance-approved version of the OP Stack codebase, and, if the
chain has been upgraded in the past, that the previous versions were a standard
release of the codebase.
Expand Down Expand Up @@ -572,7 +572,7 @@ addition of permissionless proposals.
* **Type:** Number
* **Default value:** None
* **Recommended value:**
* **Notes:** his MUST be the timestamp corresponding to the block defined by
* **Notes:** this MUST be the timestamp corresponding to the block defined by
the l1StartingBlockTag.
* **Standard Config Requirement:**

Expand Down Expand Up @@ -1005,7 +1005,7 @@ gas on L2.
Alt-DA Mode enables seamless integration of various Data Availability (DA)
Layers, regardless of their commitment type, into the OP Stack. This allows
any chain operator to launch an OP Stack chain using their favorite DA Layer
for sustainably low costs. Lean more [here](/stack/beta-features/alt-da-mode).
for sustainably low costs. Learn more [here](/stack/protocol/features/alt-da-mode).

***

Expand Down
2 changes: 1 addition & 1 deletion pages/builders/chain-operators/deploy/genesis.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ go run cmd/main.go genesis l2 \
--l2-allocs=<Path to L2 genesis state dump> \
--outfile.l2=<Path to L2 genesis output file: i.e. ./genesis.json> \
--outfile.rollup=<Path to rollup output file: i.e. ./rollup.json> \
--l1-rpc=<RPC URL for an Ethereum L1 node. Cannot be used with --l1-starting-bloc>>
--l1-rpc=<RPC URL for an Ethereum L1 node. Cannot be used with --l1-starting-block>>
```

## Next steps
Expand Down
2 changes: 1 addition & 1 deletion pages/builders/chain-operators/features/bridged-usdc-standard.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This explainer provides a high-level overview of the Bridged USDC Standard and h

## Bridged USDC Standard

USDC is one of the most bridged assets across the crypto ecosystem, and USDC is often bridged to new chains prior to any action from Circle. This can create a challenge when bridged USDC achieves substantial marketshare, but native USDC (issued by Circle) is preferred by the ecosystem, leading to fragmentation between multiple versions of USDC. Circle introduced the [Bridged USDC Standard](https://www.circle.com/en/bridged-usdc) to ensure that chain operators can easily deploy a form of bridged USDC that is capable of being upgraded in-place by Circle to native USDC, if and when appropriate, and prevent the fragmentation problem.
USDC is one of the most bridged assets across the crypto ecosystem, and USDC is often bridged to new chains prior to any action from Circle. This can create a challenge when bridged USDC achieves substantial market share, but native USDC (issued by Circle) is preferred by the ecosystem, leading to fragmentation between multiple versions of USDC. Circle introduced the [Bridged USDC Standard](https://www.circle.com/en/bridged-usdc) to ensure that chain operators can easily deploy a form of bridged USDC that is capable of being upgraded in-place by Circle to native USDC, if and when appropriate, and prevent the fragmentation problem.

Bridged USDC Standard for the OP Stack allows for an efficient and modular solution for expanding the Bridged USDC Standard across the Superchain ecosystem.

Expand Down
Loading