From e92cfe75481a3b8bfcf23e83c3178d53c829a2ab Mon Sep 17 00:00:00 2001 From: Zain Bacchus Date: Thu, 27 Feb 2025 16:01:03 -0700 Subject: [PATCH 1/6] Update about cross-chain token address --- pages/stack/interop/token-compatible.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pages/stack/interop/token-compatible.mdx b/pages/stack/interop/token-compatible.mdx index e61479203..59b959507 100644 --- a/pages/stack/interop/token-compatible.mdx +++ b/pages/stack/interop/token-compatible.mdx @@ -58,6 +58,13 @@ The [`SuperchainTokenBridge`](https://github.com/ethereum-optimism/optimism/blob Alternatively, you can build a custom bridge using the `L2ToL2CrossDomainMessenger` to facilitate cross-chain mint/burns that **does not** require a deterministic address across chains but does require the token issuer to manage a token registry per chain. +#### Cross-chain token address + +When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to burn/mint is. When using SuperChainTokenBridge, there is an invariant that tokens must be deployed at a deterministic address across chains. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. + +If using another verification mechanism you likely will need to maintain a token registry per chain that indicates that valid address mapping to burn/mint. + + #### Weakest link scenario If you allowlist both Superchain interop and a third-party verification mechanism, your token's security is only as strong as the weakest verification mechanism. From 662840cfe3d1d2c16c47a27356817619ba2a1a3d Mon Sep 17 00:00:00 2001 From: Zain Bacchus Date: Thu, 27 Feb 2025 16:08:20 -0700 Subject: [PATCH 2/6] Update token-compatible.mdx --- pages/stack/interop/token-compatible.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/stack/interop/token-compatible.mdx b/pages/stack/interop/token-compatible.mdx index 59b959507..015bc44bd 100644 --- a/pages/stack/interop/token-compatible.mdx +++ b/pages/stack/interop/token-compatible.mdx @@ -60,9 +60,9 @@ Alternatively, you can build a custom bridge using the `L2ToL2CrossDomainMesseng #### Cross-chain token address -When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to burn/mint is. When using SuperChainTokenBridge, there is an invariant that tokens must be deployed at a deterministic address across chains. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. +When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to burn/mint is. When using SuperChainTokenBridge, there is an invariant that tokens must be deployed at a deterministic address across chains in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. -If using another verification mechanism you likely will need to maintain a token registry per chain that indicates that valid address mapping to burn/mint. +If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to burn/mint when moving across chains. #### Weakest link scenario From a00484b223cd2dd28f43abccd2eb1a6a12a1dcd0 Mon Sep 17 00:00:00 2001 From: Zain Bacchus Date: Thu, 27 Feb 2025 16:09:57 -0700 Subject: [PATCH 3/6] Update token-compatible.mdx --- pages/stack/interop/token-compatible.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/token-compatible.mdx b/pages/stack/interop/token-compatible.mdx index 015bc44bd..bdad8f25c 100644 --- a/pages/stack/interop/token-compatible.mdx +++ b/pages/stack/interop/token-compatible.mdx @@ -60,7 +60,7 @@ Alternatively, you can build a custom bridge using the `L2ToL2CrossDomainMesseng #### Cross-chain token address -When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to burn/mint is. When using SuperChainTokenBridge, there is an invariant that tokens must be deployed at a deterministic address across chains in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. +When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to burn/mint is. When using the `SuperChainTokenBridge`, there is an invariant that tokens must be deployed at a deterministic address across chains in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to burn/mint when moving across chains. From ece91de67e158b5498b3b6c28d22c5a805724e5e Mon Sep 17 00:00:00 2001 From: Zain Bacchus Date: Thu, 27 Feb 2025 16:11:10 -0700 Subject: [PATCH 4/6] Update token-compatible.mdx --- pages/stack/interop/token-compatible.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/stack/interop/token-compatible.mdx b/pages/stack/interop/token-compatible.mdx index bdad8f25c..07eee8159 100644 --- a/pages/stack/interop/token-compatible.mdx +++ b/pages/stack/interop/token-compatible.mdx @@ -60,9 +60,9 @@ Alternatively, you can build a custom bridge using the `L2ToL2CrossDomainMesseng #### Cross-chain token address -When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to burn/mint is. When using the `SuperChainTokenBridge`, there is an invariant that tokens must be deployed at a deterministic address across chains in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. +When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to facilitate cross-chain mint/burns is. When using the `SuperchainTokenBridge`, there is an invariant that tokens must be deployed at a deterministic address across chains in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. -If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to burn/mint when moving across chains. +If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to facilitiate cross-chain mint/burns when moving across chains. #### Weakest link scenario From b6e5390beb3bea5c2d0964ccdfbd2f6ab222895f Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 28 Feb 2025 00:16:41 +0100 Subject: [PATCH 5/6] updated link paths --- pages/stack/interop/token-compatible.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/token-compatible.mdx b/pages/stack/interop/token-compatible.mdx index 07eee8159..fc552a53e 100644 --- a/pages/stack/interop/token-compatible.mdx +++ b/pages/stack/interop/token-compatible.mdx @@ -60,7 +60,7 @@ Alternatively, you can build a custom bridge using the `L2ToL2CrossDomainMesseng #### Cross-chain token address -When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to facilitate cross-chain mint/burns is. When using the `SuperchainTokenBridge`, there is an invariant that tokens must be deployed at a deterministic address across chains in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. +When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to facilitate cross-chain mint/burns is. When using the `SuperchainTokenBridge`, there is an invariant that tokens must be deployed at a [deterministic address across chains](/stack/interop/superchain-erc20#requirements) in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to facilitiate cross-chain mint/burns when moving across chains. From 41e2606f33bfde60a981d6497c02f8bd23ca3a2d Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 28 Feb 2025 00:23:07 +0100 Subject: [PATCH 6/6] fix lint issues --- pages/stack/interop/token-compatible.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/token-compatible.mdx b/pages/stack/interop/token-compatible.mdx index fc552a53e..ee7b3422b 100644 --- a/pages/stack/interop/token-compatible.mdx +++ b/pages/stack/interop/token-compatible.mdx @@ -62,7 +62,7 @@ Alternatively, you can build a custom bridge using the `L2ToL2CrossDomainMesseng When deploying your token cross-chain it is critical to ensure the verification mechanism knows what the valid address mapping to facilitate cross-chain mint/burns is. When using the `SuperchainTokenBridge`, there is an invariant that tokens must be deployed at a [deterministic address across chains](/stack/interop/superchain-erc20#requirements) in the Superchain interop cluster. This simplifies development experience by ensuring the token issuer does not need to manage a cross-chain token registry per chain. -If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to facilitiate cross-chain mint/burns when moving across chains. +If using another verification mechanism you likely will need to maintain a token registry per chain that indicates the valid address mapping to facilitate cross-chain mint/burns when moving across chains. #### Weakest link scenario