Superchain Interop-Compatible Tokens

pages/stack/interop.mdx

@@ -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" />} />

pages/stack/interop/_meta.json

@@ -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",

pages/stack/interop/token-compatible.mdx

@@ -0,0 +1,89 @@
+---
+title: Superchain interop compatible tokens
+lang: en-US
+description: Learn how different tokens can benefit from Superchain interop and benefit from secure, low-latency, cross-chain composability.
+---
+
+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).
+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 traditional ERC-20 tokens deployments on a single blockchain, cross-chain tokens can move between different networks through giving crosschainMint and crosschainBurn permissions to a verification mechanism (such as a bridge protocol) that validates when tokens should be burned on one chain and minted on another.
+
+For example when transferring a SuperchainERC20 between chains in the Superchain interop cluster, the Superchain interop protocol ensures the tokens are burned on the source chain before authorizing the corresponding mint on the destination chain.
+
+When enabling cross-chain functionality for your token, it is essential to evaluate the security, cost, and latency of the respective verification mechanism.
+
+
+## Why give your token cross-chain functionality with Superchain interop?
+
+*   **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:** Fault Proofs secure Superchain interop end to end.
+*   **[Reorg awareness](./reorg):** Enables 1-block latency cross-chain composability that mitigates the double-spend problem.
+
+## SuperchainERC20
+
+SuperchainERC20 is the simplest and most trust-minimized way to enable token interoperability within the Superchain.
+
+*   **Security:** Fault Proofs secure Superchain interop end to end. No third-party dependencies.
+*   **Latency:** 1-block latency within the Superchain interop cluster.
+*   **Cost:** Gas on source chain and destination chain. 
+*   **Cross-chain address:** Deterministic, no token registry required. 
+*   **Supported ecosystem:** Superchain interop cluster.
+
+
+## Alternative implementation options (ERC-7281 Standard)
+
+### 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.
+
+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:** Variable due to weakest-link scenario based on allowlisted verification mechanisms.
+*   **Latency:** 1-block latency in the Superchain. Outside latency varies based on the messaging service used.
+*   **Cost:** Variable based on allowlisted verification mechanisms.
+*   **Cross-chain address:** Deterministic or requires cross-chain registry per deployment.
+*   **Best for:** Projects needing flexible bridge integrations while retaining control over allowlisted bridges.
+
+### OFT
+
+*   **Security:** Variable due to weakest-link scenario based on allowlisted verification mechanisms.
+*   **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:** Variable due to weakest-link scenario based on allowlisted verification mechanisms.
+*   **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 simplest way for token issuers to get Superchain interop cluster wide distribution.
+*   Token issuers can use other options (xERC20, OFT, NTT) and allowlist Superchain interop or the SuperchainTokenBridge to benefit from Superchain interop. 
+*   When using tokens other than SuperchainERC20, token issuers should include a ERC-7802 interface to simplify developer experience.
+*   Using 3rd party verification mechanisms 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)

words.txt

@@ -8,7 +8,6 @@ ADDIU
 ADDU
 airgap
 Allnodes
-Allocs
 allocs
 Alphanet
 alphanet
@@ -20,6 +19,7 @@ Ankr
 Apeworx
 Arweave
 authrpc
+Autorelay
 autorelay
 autorelayer
 basefee
@@ -168,14 +168,12 @@ IERC
 IGNOREPRICE
 ignoreprice
 Immunefi
-implicitly
 Inator
 inator
 INFLUXDBV
 influxdbv
 initcode
 interopble
-invokable
 IPCDISABLE
 ipcdisable
 ipcfile
@@ -360,7 +358,6 @@ seqnr
 SEQUENCERHTTP
 sequencerhttp
 serv
-settions
 signup
 SLLV
 SLTI
@@ -401,7 +398,6 @@ synctarget
 syscalls
 thirdweb
 threadcreate
-tility
 timeseries
 triggerable
 trustlessly
@@ -436,7 +432,6 @@ VMODULE
 vmodule
 xlarge
 XORI
-xtensibility
 ZKPs
 ZKVM
 Zora