You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Get an overview of features associated with an OP Stack chain
5
+
---
6
+
7
+
# Overview
8
+
9
+
Get an overview of the capabilities associated with an OP Stack chain.
10
+
11
+
While the OP Stack allows for full customization, chains in the Superchain adhere to a [standard set of technical and governance parameters](/superchain/blockspace-charter), facilitating Superchain interoperability, network security, and ease of upgrading your chain.
|**Upgrades**| Facilitated via OP Governance | Self-managed |
24
+
|**EVM compatibility**| Equivalent | Variable |
25
+
26
+
<sup>1</sup>Data for Superchain from [Base](https://etherscan.io/address/0x73a79Fab69143498Ed3712e519A88a918e1f4072#readProxyContract#F14). Data for OP Stack from [opBNB](https://docs.bnbchain.org/bnb-opbnb/core-concepts/opbnb-metrics/).
27
+
28
+
<sup>2</sup>The standard blockspace charter has a max gas limit of [200m](https://specs.optimism.io/protocol/configurability.html#gas-limit). Both gas limit and gas target can be configured through the system config.
29
+
30
+
<sup>3</sup>While protocol blocktimes can be lowered to 1 second, subsecond blocktimes can be achieved using [Rollup Boost and Flashblocks](https://writings.flashbots.net/introducing-rollup-boost).
31
+
32
+
<sup>4</sup>Although ETH is the gas token, chain operators can achieve the same UX of a custom gas token by using an ERC-20 paymaster.
Copy file name to clipboardExpand all lines: pages/stack/interop/explainer.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -216,7 +216,7 @@ Each blockchain in the Superchain interop cluster shares the same security model
216
216
Superchain interop includes both the protocol layer message passing and the Superchain ERC20 token specification.
217
217
218
218
* **Message passing protocol:** the initial + finalizing/executing [message](cross-chain-message) that fire events to be consumed by the chains in the [dependency set](https://specs.optimism.io/interop/dependency-set.html)
219
-
* ****: the [SuperchainERC20](superchain-erc20) turns message passing into asset transfer between chains in the interop set. Learn more about how the SuperchainERC20 token standard enables asset interoperability in the Superchain [here](/stack/interop/assets/superchain-erc20)
219
+
* ****: the [SuperchainERC20](superchain-erc20) turns message passing into asset transfer between chains in the interop set. Learn more about how the SuperchainERC20 token standard enables asset interoperability in the Superchain [here](/stack/interop/superchain-erc20)
220
220
221
221
This means ETH and ERC-20s can seamlessly and securely move across L2s, and intent-based protocols (i.e., bridges) can build better experiences on top of the message passing protocol.
Copy file name to clipboardExpand all lines: pages/stack/interop/op-supervisor.mdx
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,15 @@ import { InteropCallout } from '@/components/WipCallout'
11
11
12
12
# OP-Supervisor
13
13
14
-
OP-Supervisor is a service that verifies cross-chain messages and manages interoperability between chains in the OP Stack.
14
+
OP-Supervisor is a service that verifies cross-chain messages and manages interoperability between chains in the OP Stack.
15
15
The main information it contains about other blockchains is:
16
-
- Log entries, which could be [initiating messages](./explainer#how-messages-get-from-one-chain-to-the-other) for cross-domain messages.
17
-
- Blockchain heads, which are the latest blocks at various levels of confidence and safety:
18
-
- Unsafe (the latest block available through the gossip protocol)
19
-
- Local-safe (the latest block written to L1)
20
-
- Cross-safe (the latest block written to L1, and for which all the dependencies are written to L1)
21
-
- Finalized (the latest block written to L1, and that L1 block is safe from reorgs)
16
+
17
+
* Log entries, which could be [initiating messages](./explainer#how-messages-get-from-one-chain-to-the-other) for cross-domain messages.
18
+
* Blockchain heads, which are the latest blocks at various levels of confidence and safety:
19
+
* Unsafe (the latest block available through the gossip protocol)
20
+
* Local-safe (the latest block written to L1)
21
+
* Cross-safe (the latest block written to L1, and for which all the dependencies are written to L1)
22
+
* Finalized (the latest block written to L1, and that L1 block is safe from reorgs)
22
23
23
24
```mermaid
24
25
@@ -51,14 +52,14 @@ To do this, OP-Supervisor has to have RPC access to all the chains in the depend
51
52
52
53
## How other components use OP-Supervisor
53
54
54
-
-The execution client (typically `op-geth`) queries `op-supervisor` during block-building to verify if a message is sufficiently safe to include.
55
-
To do this, the execution client looks at every executing message and queries `op-supervisor` to see if there is a corresponding initiating message.
55
+
*The execution client (typically `op-geth`) queries `op-supervisor` during block-building to verify if a message is sufficiently safe to include.
56
+
To do this, the execution client looks at every executing message and queries `op-supervisor` to see if there is a corresponding initiating message.
56
57
57
-
-`op-node` queries cross-chain safety information and coordinates safety updates between OP stack nodes and `op-supervisor`. It uses the API provided by `op-supervisor` to:
58
-
- Retrieve the unsafe, local-safe, cross-safe, and finalized heads for other chains.
59
-
- Update the unsafe, local-safe, and finalized heads for its own chain.
60
-
- Attempt to promote blocks in its own chain to cross-safe status.
61
-
- Attempt to finalize L2 blocks based on L1 finality.
58
+
*`op-node` queries cross-chain safety information and coordinates safety updates between OP stack nodes and `op-supervisor`. It uses the API provided by `op-supervisor` to:
59
+
* Retrieve the unsafe, local-safe, cross-safe, and finalized heads for other chains.
60
+
* Update the unsafe, local-safe, and finalized heads for its own chain.
61
+
* Attempt to promote blocks in its own chain to cross-safe status.
62
+
* Attempt to finalize L2 blocks based on L1 finality.
Copy file name to clipboardExpand all lines: pages/stack/interop/superchain-erc20.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ Application developers must do two things to make their tokens `SuperchainERC20`
86
86
87
87
For now, application developers should view `SuperchainERC20`as ERC20 tokens with additional built-in functions that allow cross-chain asset movement that will be enabled once Interop goes live.
88
88
89
-
For step-by-step information on implementing SuperchainERC20, see [Deploy assets using SuperchainERC20](/stack/interop/assets/deploy-superchain-erc20)
89
+
For step-by-step information on implementing SuperchainERC20, see [Deploy assets using SuperchainERC20](/stack/interop/tutorials/deploy-superchain-erc20)
90
90
91
91
<Callouttype="warning">
92
92
To enable asset interoperability, `SuperchainERC20` must give access to the address where the future `SuperchainERC20Bridge` will live.
@@ -96,4 +96,4 @@ For step-by-step information on implementing SuperchainERC20, see [Deploy assets
96
96
* Watch the [ERC20 to SuperchainERC20 video walkthrough](https://www.youtube.com/watch?v=Gb8glkyBdBA) to learn how to modify an existing ERC20 contract to make it interoperable within the Superchain.
97
97
* Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html) for in-depth implementation details.
98
98
* Check out the [SuperchainERC20 starter kit](https://github.com/ethereum-optimism/superchainerc20-starter) to get started with implementation.
99
-
* Review the [Deploy SuperchainERC20 tutorial](./tutorials/deploy-superchain-erc20) to learn how to deploy a SuperchainERC20.
99
+
* Review the [Deploy SuperchainERC20 tutorial](/stack/interop/tutorials/deploy-superchain-erc20) to learn how to deploy a SuperchainERC20.
Copy file name to clipboardExpand all lines: pages/stack/interop/tutorials/deploy-superchain-erc20.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ import { Steps } from 'nextra/components'
13
13
Interop is currently in active development and not yet ready for production use. The information provided here may change. Check back regularly for the most up-to-date information.
14
14
</Callout>
15
15
16
-
This guide explains how to issue new assets with the `SuperchainERC20` and bridge them effectively using the `SuperchainERC20Bridge`. If you want more information about the `SuperchainERC20 standard`, see our [`SuperchainERC20` standard explainer](/stack/interop/assets/superchain-erc20)
16
+
This guide explains how to issue new assets with the `SuperchainERC20` and bridge them effectively using the `SuperchainERC20Bridge`. If you want more information about the `SuperchainERC20 standard`, see our [`SuperchainERC20` standard explainer](/stack/interop/superchain-erc20)
17
17
18
18
Note that bridging assets through the Superchain using `SuperchainERC20` never affects the total supply of your asset. The supply remains fixed, and bridging only changes the chain on which your asset is located. This keeps the token's total amount the same across all networks, ensuring its value stays stable during the move and that the `SuperchainERC20` retains a unified, global supply count.
0 commit comments