Skip to content
This repository was archived by the owner on Apr 6, 2026. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
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: 2 additions & 0 deletions pages/stack/interop.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ Documentation covering Cross Chain Message, Explainer, Message Passing, Op Super

<Card title="Interop message passing overview" href="/stack/interop/message-passing" icon={<img src="/img/icons/shapes.svg" />} />

<Card title="Make your token Superchain interop compatible" href="/stack/interop/token-compatible" icon={<img src="/img/icons/shapes.svg" />} />

<Card title="OP Supervisor" href="/stack/interop/op-supervisor" icon={<img src="/img/icons/shapes.svg" />} />

<Card title="Supersim multichain development environment" href="/stack/interop/tools/supersim" icon={<img src="/img/icons/shapes.svg" />} />
Expand Down
1 change: 1 addition & 0 deletions pages/stack/interop/_meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
"explainer": "Superchain interop explainer",
"predeploy": "Superchain interop predeploys",
"message-passing": "Superchain interop message passing",
"token-compatible": "Superchain interop compatible token",
"op-supervisor": "OP Supervisor",
"superchain-weth": "Interoperable ETH",
"superchain-erc20": "SuperchainERC20",
Expand Down
79 changes: 79 additions & 0 deletions pages/stack/interop/token-compatible.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
---
title: Superchain interop compatible tokens
lang: en-US
description: Learn how to enable seamless, low-latency cross-chain composability for your token within the Superchain.
Comment thread
zainbacchus marked this conversation as resolved.
Outdated
---
Comment thread
krofax marked this conversation as resolved.
Comment thread
krofax marked this conversation as resolved.
Comment thread
krofax marked this conversation as resolved.
Comment thread
krofax marked this conversation as resolved.

import { Callout } from 'nextra/components'
import { InteropCallout } from '@/components/WipCallout'

<InteropCallout />

# Superchain interop compatible tokens

Superchain interop enables **secure, gas-only, 1-block latency cross-chain composability** on the [Superchain interop cluster](/stack/interop/explainer#superchain-interop-cluster).
Comment thread
zainbacchus marked this conversation as resolved.
Outdated
The **recommended** approach for enabling interop capabilities for tokens is using [SuperchainERC20](/stack/interop/superchain-erc20), but there are other options depending on your needs.

## How tokens go cross-chain

Compared to a traditional ERC-20 deployment on a single chain, tokens can move across chains by granting authority to a messaging service (bridge) to **cross-chain mint/burn** them.
Comment thread
zainbacchus marked this conversation as resolved.
Outdated
When enabling cross-chain functionality, it is essential to evaluate **security, cost, and latency** of the respective messaging service.
Comment thread
zainbacchus marked this conversation as resolved.
Outdated

## Why Superchain interop messaging?
Comment thread
zainbacchus marked this conversation as resolved.
Outdated

* **Low latency:** 1-block latency ensures fast cross-chain token transfers.
* **No fees:** Transfers happen at a 1:1 rate with no liquidity pools—just gas.
* **Security:** Protected by the OP Stack's permissionless fault proofs.
Comment thread
zainbacchus marked this conversation as resolved.
Outdated
* **[Reorg awareness](./reorg):** Enables 1-block latency cross-chain composability that mitigates the double-spend problem.

## SuperchainERC20 – The Recommended Option

* **Most secure** – Fully protected by OP Stack permissionless fault proofs. No third-party dependencies.
* **1-block latency** within the Superchain.
* **Best for:** **Superchain-native tokens**, that need **the highest security, lowest latency, and seamless integration within the Superchain**


### Weakest link risk

If you allowlist both **Superchain interop and a third-party messaging service**, your token's security is **only as strong as the weakest service**.
A compromised third-party service could allow **malicious minting or double spending**.

### SuperchainTokenBridge vs. Superchain interop messaging

The [`SuperchainTokenBridge`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/SuperchainTokenBridge.sol) is an abstraction built on top of the **Cross-Domain Messenger (CDM)**.
Anyone can build a **custom bridge** on the **L2-to-L2 CDM**, but it may not follow the invariant of maintaining the **same token address across chains**.


## Alternative implementation options (ERC-7281 Standard)

If your token requires interoperability **beyond the Superchain**, you can consider one of the following **ERC-7281-compliant** options. These introduce **external dependencies** that must be allowlisted.

### xERC20 (ERC-7281)

* **Security:** Secure within the Superchain. Security outside the Superchain depends on **allowlisted third-party bridges**.
* **Latency:** 1-block latency in the Superchain. Outside latency varies based on the **messaging service used**.
* **Best for:** Projects needing **flexible bridge integrations** while retaining control over allowlisted bridges.

### OFT

* **Security:** Secure within the Superchain. Outside security depends on **allowlisted Decentralized Verification Networks (DVNs)**.
Comment thread
zainbacchus marked this conversation as resolved.
Outdated
* **Latency:** 1-block latency within the Superchain. External latency depends on **DVN finality time**.
* **Best for:** Tokens requiring **cross-chain transfer** beyond the Superchain (e.g., Solana, Arbitrum).

### NTT

* **Security:** Secure within the Superchain. External security depends on **allowlisted transceivers**.
* **Latency:** 1-block latency within the Superchain. External latency varies based on **transceiver finality**.
* **Best for:** Projects that want **Wormhole's network** for cross-chain transfer. *(Superchain integration is still in progress.)*

### Key takeaways

* **SuperchainERC20** is the most secure and recommended option for native Superchain tokens.
* **All other options (xERC20, OFT, NTT) follow the ERC-7281 standard** and require allowlisting external verification mechanisms.
* **Interoperability outside the Superchain** introduces external dependencies and potential security risks.

## Next steps

* [Deploy a SuperchainERC20 token](/stack/interop/superchain-erc20)
* [Learn more about interoperability](/stack/interop/explainer)
* [Build a cross-chain app on the Superchain](/app-developers/get-started)
7 changes: 1 addition & 6 deletions words.txt
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@ ADDIU
ADDU
airgap
Allnodes
Allocs
allocs
Alphanet
alphanet
Expand All @@ -20,6 +19,7 @@ Ankr
Apeworx
Arweave
authrpc
Autorelay
autorelay
autorelayer
basefee
Expand Down Expand Up @@ -168,14 +168,12 @@ IERC
IGNOREPRICE
ignoreprice
Immunefi
implicitly
Inator
inator
INFLUXDBV
influxdbv
initcode
interopble
invokable
IPCDISABLE
ipcdisable
ipcfile
Expand Down Expand Up @@ -360,7 +358,6 @@ seqnr
SEQUENCERHTTP
sequencerhttp
serv
settions
signup
SLLV
SLTI
Expand Down Expand Up @@ -401,7 +398,6 @@ synctarget
syscalls
thirdweb
threadcreate
tility
timeseries
triggerable
trustlessly
Expand Down Expand Up @@ -436,7 +432,6 @@ VMODULE
vmodule
xlarge
XORI
xtensibility
ZKPs
ZKVM
Zora
Expand Down