From 78ea50408919cfcd7dd54e0663460930bccedb63 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Fri, 1 Nov 2024 07:17:05 -0700 Subject: [PATCH 1/9] Add new doc --- pages/stack/interop/_meta.json | 3 +- .../superchainerc20-best-practices.mdx | 47 +++++++++++++++++++ 2 files changed, 49 insertions(+), 1 deletion(-) create mode 100644 pages/stack/interop/superchainerc20-best-practices.mdx diff --git a/pages/stack/interop/_meta.json b/pages/stack/interop/_meta.json index 0c2da550c..888b70670 100644 --- a/pages/stack/interop/_meta.json +++ b/pages/stack/interop/_meta.json @@ -5,5 +5,6 @@ "superchain-erc20": "SuperchainERC20", "superchain-weth": "SuperchainWETH (Interoperable ETH)", "op-supervisor": "OP Supervisor", - "transfer-superchainERC20": "How to transfer a SuperchainERC20" + "transfer-superchainERC20": "How to transfer a SuperchainERC20", + "superchainERC20-best-practices": "SuperchainERC20 best practices" } \ No newline at end of file diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/superchainerc20-best-practices.mdx new file mode 100644 index 000000000..27d163e13 --- /dev/null +++ b/pages/stack/interop/superchainerc20-best-practices.mdx @@ -0,0 +1,47 @@ +--- +title: Best practices for deploying new assets with SuperchainERC20 +lang: en-US +description: Essential best practices for deploying and managing SuperchainERC20 assets across the Superchain +--- + +# Best practices for deploying new assets with SuperchainERC20 + +The following best practices are essential for deploying and managing `SuperchainERC20` assets across Superchain-compatible networks. These guidelines help ensure optimal cross-chain functionality, consistent metadata, and efficient resource utilization. + +## Consistent addressing across chains + +* Use predefined addresses: Assign and verify unique addresses for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. + +## Token metadata consistency + +* Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. + +* Implement metadata verification: Add checks to ensure that metadata (e.g., `decimals`) matches across chains. + +## Efficient cross-chain transfers with crosschainBurn and crosschainMint + +* Maintain supply consistency: Use `crosschainBurn` to decrement token balances on the originating chain and `crosschainMint` to increase balances on the destination chain. These functions should mirror asset movement across chains without altering the total supply. + +* Implement error handling in transfer functions: Validate addresses and amounts before initiating cross-chain transfers. Cross-chain transfers are irreversible, so checks help prevent unrecoverable asset loss. + +## Optimizing gas usage for high-volume transfers + +* Minimize storage access: Use memory variables instead of storage where possible in high-frequency functions. Reduced storage access lowers gas fees, improving efficiency for high-volume transactions. + +* Batch transfers within gas limits: For batch transfers, ensure that gas limits are optimized to accommodate transaction volumes. Where possible, split large transactions to prevent them from failing due to gas constraints. + +## Sequence for deployment and bridging + +* Deploy on the origin chain first: Start with deployment on the primary chain to serve as the authoritative ledger for total supply. Subsequent chain instances should use this origin to track and verify supply. + +* Bridge tokens sequentially: When deploying across multiple chains, bridge tokens in a consistent, sequential order from the origin chain. This helps prevent supply misalignment and ensures accurate tracking. + +## Comprehensive testing before mainnet deployment + +- **Test with production-like conditions**: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. + +## Next steps + +* Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html) for in-depth implementation details. +* Watch the [Superchain interop design video walkthrough](https://www.youtube.com/watch?v=FKc5RgjtGes) for a visual explanation of the concepts. +* Review the [Superchain Interop Explainer](explainer) for answers to common questions about interoperability. From d4cf07925eb788e0e19109b8d4a1f48525a75bd6 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Fri, 1 Nov 2024 07:23:27 -0700 Subject: [PATCH 2/9] Fix docs --- .../superchainerc20-best-practices.mdx | 38 ++++++------------- 1 file changed, 11 insertions(+), 27 deletions(-) diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/superchainerc20-best-practices.mdx index 27d163e13..1c915fef1 100644 --- a/pages/stack/interop/superchainerc20-best-practices.mdx +++ b/pages/stack/interop/superchainerc20-best-practices.mdx @@ -1,47 +1,31 @@ --- -title: Best practices for deploying new assets with SuperchainERC20 +title: Best practices for managing SuperchainERC20 tokens lang: en-US -description: Essential best practices for deploying and managing SuperchainERC20 assets across the Superchain +description: Essential best practices for deploying and managing SuperchainERC20 assets across Superchain-compatible networks. --- -# Best practices for deploying new assets with SuperchainERC20 +# Best practices for managing SuperchainERC20 tokens -The following best practices are essential for deploying and managing `SuperchainERC20` assets across Superchain-compatible networks. These guidelines help ensure optimal cross-chain functionality, consistent metadata, and efficient resource utilization. +The following best practices are essential for deploying and managing `SuperchainERC20` assets across the Superchain. These guidelines help ensure optimal cross-chain functionality. + +Note that the total supply of your tokens never fluctuates across the Superchain. Cross-chain burning and minting only affects the location of a token across the Superchain. ## Consistent addressing across chains -* Use predefined addresses: Assign and verify unique addresses for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. +* Use predefined addresses: Assign and verify the same address for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. Otherwise, the SuperchainERC20Bridge would need a way to verify if the tokens they mint on destination correspond to the tokens that were burned on source. Consider using `Create2Deployer` or one of our [predeploys](https://specs.optimism.io/interop/predeploys.html) to ensure this. ## Token metadata consistency * Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. - -* Implement metadata verification: Add checks to ensure that metadata (e.g., `decimals`) matches across chains. - -## Efficient cross-chain transfers with crosschainBurn and crosschainMint - -* Maintain supply consistency: Use `crosschainBurn` to decrement token balances on the originating chain and `crosschainMint` to increase balances on the destination chain. These functions should mirror asset movement across chains without altering the total supply. - -* Implement error handling in transfer functions: Validate addresses and amounts before initiating cross-chain transfers. Cross-chain transfers are irreversible, so checks help prevent unrecoverable asset loss. - -## Optimizing gas usage for high-volume transfers - -* Minimize storage access: Use memory variables instead of storage where possible in high-frequency functions. Reduced storage access lowers gas fees, improving efficiency for high-volume transactions. - -* Batch transfers within gas limits: For batch transfers, ensure that gas limits are optimized to accommodate transaction volumes. Where possible, split large transactions to prevent them from failing due to gas constraints. - -## Sequence for deployment and bridging - -* Deploy on the origin chain first: Start with deployment on the primary chain to serve as the authoritative ledger for total supply. Subsequent chain instances should use this origin to track and verify supply. - -* Bridge tokens sequentially: When deploying across multiple chains, bridge tokens in a consistent, sequential order from the origin chain. This helps prevent supply misalignment and ensures accurate tracking. ## Comprehensive testing before mainnet deployment -- **Test with production-like conditions**: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. +* Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. + +* Validate transfer handling: Test edge cases such as maximum balance transfers and inter-chain latency to ensure asset reliability across different scenarios. ## Next steps * Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html) for in-depth implementation details. * Watch the [Superchain interop design video walkthrough](https://www.youtube.com/watch?v=FKc5RgjtGes) for a visual explanation of the concepts. -* Review the [Superchain Interop Explainer](explainer) for answers to common questions about interoperability. +* Review the [Superchain Interop Explainer](explainer) for answers to common questions about interoperability. \ No newline at end of file From 49c69292b288b980e17fcd3e66afcfb5c46d5f35 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Fri, 1 Nov 2024 07:24:13 -0700 Subject: [PATCH 3/9] Apply linting --- .../interop/superchainerc20-best-practices.mdx | 16 ++++++++-------- words.txt | 12 +----------- 2 files changed, 9 insertions(+), 19 deletions(-) diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/superchainerc20-best-practices.mdx index 1c915fef1..4270e13a5 100644 --- a/pages/stack/interop/superchainerc20-best-practices.mdx +++ b/pages/stack/interop/superchainerc20-best-practices.mdx @@ -8,24 +8,24 @@ description: Essential best practices for deploying and managing SuperchainERC20 The following best practices are essential for deploying and managing `SuperchainERC20` assets across the Superchain. These guidelines help ensure optimal cross-chain functionality. -Note that the total supply of your tokens never fluctuates across the Superchain. Cross-chain burning and minting only affects the location of a token across the Superchain. +Note that the total supply of your tokens never fluctuates across the Superchain. Cross-chain burning and minting only affects the location of a token across the Superchain. ## Consistent addressing across chains -* Use predefined addresses: Assign and verify the same address for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. Otherwise, the SuperchainERC20Bridge would need a way to verify if the tokens they mint on destination correspond to the tokens that were burned on source. Consider using `Create2Deployer` or one of our [predeploys](https://specs.optimism.io/interop/predeploys.html) to ensure this. +* Use predefined addresses: Assign and verify the same address for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. Otherwise, the SuperchainERC20Bridge would need a way to verify if the tokens they mint on destination correspond to the tokens that were burned on source. Consider using `Create2Deployer` or one of our [predeploys](https://specs.optimism.io/interop/predeploys.html) to ensure this. ## Token metadata consistency -* Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. +* Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. ## Comprehensive testing before mainnet deployment -* Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. +* Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. -* Validate transfer handling: Test edge cases such as maximum balance transfers and inter-chain latency to ensure asset reliability across different scenarios. +* Validate transfer handling: Test edge cases such as maximum balance transfers and inter-chain latency to ensure asset reliability across different scenarios. ## Next steps -* Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html) for in-depth implementation details. -* Watch the [Superchain interop design video walkthrough](https://www.youtube.com/watch?v=FKc5RgjtGes) for a visual explanation of the concepts. -* Review the [Superchain Interop Explainer](explainer) for answers to common questions about interoperability. \ No newline at end of file +* Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html) for in-depth implementation details. +* Watch the [Superchain interop design video walkthrough](https://www.youtube.com/watch?v=FKc5RgjtGes) for a visual explanation of the concepts. +* Review the [Superchain Interop Explainer](explainer) for answers to common questions about interoperability. diff --git a/words.txt b/words.txt index 2e0d2c443..a1c2f1f8e 100644 --- a/words.txt +++ b/words.txt @@ -11,7 +11,6 @@ Allocs allocs altda ANDI -Ankr Apeworx Arweave authrpc @@ -77,7 +76,6 @@ datacap DATADIR datadir Dencun -derviation Devnet devnet Devnode @@ -150,7 +148,6 @@ Holesky holesky IGNOREPRICE ignoreprice -Immunefi implicity Inator inator @@ -199,7 +196,6 @@ minsuggestedpriorityfee Mintable Mintplex MIPSEVM -Mitigations Monitorism Moralis Mordor @@ -293,8 +289,6 @@ Protip Proxied proxyd pseudorandomly -Pyth -Pyth's QRNG Quicknode quicknode @@ -329,9 +323,6 @@ safedb Schnorr secp SELFDESTRUCT -SEPOLIA -Sepolia -sepolia seqnr SEQUENCERHTTP sequencerhttp @@ -400,7 +391,6 @@ VMDEBUG vmdebug VMODULE vmodule -voxel wagmi Warpcast xlarge @@ -409,4 +399,4 @@ xtensibility ZKPs ZKVM Zora -zora \ No newline at end of file +zora From ddf5ea9f29ad2c49c71b4a38266207c6c18e5290 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Fri, 1 Nov 2024 07:26:52 -0700 Subject: [PATCH 4/9] Wording and style fixes --- .../interop/superchainerc20-best-practices.mdx | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/superchainerc20-best-practices.mdx index 4270e13a5..2fb7f26d0 100644 --- a/pages/stack/interop/superchainerc20-best-practices.mdx +++ b/pages/stack/interop/superchainerc20-best-practices.mdx @@ -1,7 +1,7 @@ --- title: Best practices for managing SuperchainERC20 tokens lang: en-US -description: Essential best practices for deploying and managing SuperchainERC20 assets across Superchain-compatible networks. +description: Essential best practices for deploying and managing SuperchainERC20 assets across Superchain networks. --- # Best practices for managing SuperchainERC20 tokens @@ -10,19 +10,23 @@ The following best practices are essential for deploying and managing `Superchai Note that the total supply of your tokens never fluctuates across the Superchain. Cross-chain burning and minting only affects the location of a token across the Superchain. -## Consistent addressing across chains +## Consistent addresses across chains -* Use predefined addresses: Assign and verify the same address for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. Otherwise, the SuperchainERC20Bridge would need a way to verify if the tokens they mint on destination correspond to the tokens that were burned on source. Consider using `Create2Deployer` or one of our [predeploys](https://specs.optimism.io/interop/predeploys.html) to ensure this. +Use predefined addresses: Assign and verify the same address for each `SuperchainERC20` instance on every chain. Predefined addresses reduce deployment conflicts and ensure tokens are accurately recognized across chains. Otherwise, the SuperchainERC20Bridge would need a way to verify if the tokens they mint on destination correspond to the tokens that were burned on source. + +Consider using `Create2Deployer` or one of our [predeploys](https://specs.optimism.io/interop/predeploys.html) to ensure this. ## Token metadata consistency -* Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. +Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. + +## Testing before mainnet deployment -## Comprehensive testing before mainnet deployment +Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. -* Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. +We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. -* Validate transfer handling: Test edge cases such as maximum balance transfers and inter-chain latency to ensure asset reliability across different scenarios. +Test edge cases such as maximum balance transfers and inter-chain latency to ensure asset reliability across different scenarios. ## Next steps From 2c5220d5b627cc7fb01bc107c74098285c9ee79a Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:27:22 -0800 Subject: [PATCH 5/9] Apply feedback --- pages/stack/interop/superchainerc20-best-practices.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/superchainerc20-best-practices.mdx index 2fb7f26d0..925a7891b 100644 --- a/pages/stack/interop/superchainerc20-best-practices.mdx +++ b/pages/stack/interop/superchainerc20-best-practices.mdx @@ -16,13 +16,9 @@ Use predefined addresses: Assign and verify the same address for each `Superchai Consider using `Create2Deployer` or one of our [predeploys](https://specs.optimism.io/interop/predeploys.html) to ensure this. -## Token metadata consistency +## Testing before mainnet deployment -Standardize token metadata: Use identical values for `name`, `symbol`, and `decimals` across all chain instances. Inconsistent metadata can lead to display errors and transaction rejections during cross-chain operations. - -## Testing before mainnet deployment - -Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. +Test with production-like conditions: Deploy to staging environments that simulate mainnet conditions, especially for functions like `crosschainBurn` and `crosschainMint`. Test under realistic transaction loads to validate performance. We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. From 5a38888976e0aaece6dbe8e5895092fe66f9d84e Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Thu, 7 Nov 2024 17:03:10 -0800 Subject: [PATCH 6/9] Update pages/stack/interop/superchainerc20-best-practices.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/stack/interop/superchainerc20-best-practices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/superchainerc20-best-practices.mdx index 925a7891b..a483ce43c 100644 --- a/pages/stack/interop/superchainerc20-best-practices.mdx +++ b/pages/stack/interop/superchainerc20-best-practices.mdx @@ -22,7 +22,7 @@ Test with production-like conditions: Deploy to staging environments that simula We recommend using [Supersim](https://supersim.pages.dev/introduction) as an easy way to simulate the Superchain and test your SuperchainERC20 deployment. -Test edge cases such as maximum balance transfers and inter-chain latency to ensure asset reliability across different scenarios. +Test edge cases such as maximum balance transfers and interchain latency to ensure asset reliability across different scenarios. ## Next steps From 456d58f64efbe2732d43ff8fdc60e7d287e543ed Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Thu, 7 Nov 2024 17:06:25 -0800 Subject: [PATCH 7/9] Various linting and nav fixes --- pages/stack/interop/_meta.json | 1 - pages/stack/interop/assets.mdx | 2 ++ pages/stack/interop/assets/_meta.json | 5 +++-- .../interop/{ => assets}/superchainerc20-best-practices.mdx | 0 words.txt | 1 + 5 files changed, 6 insertions(+), 3 deletions(-) rename pages/stack/interop/{ => assets}/superchainerc20-best-practices.mdx (100%) diff --git a/pages/stack/interop/_meta.json b/pages/stack/interop/_meta.json index 008f51298..e81485a1a 100644 --- a/pages/stack/interop/_meta.json +++ b/pages/stack/interop/_meta.json @@ -5,5 +5,4 @@ "message-passing": "Interop message passing", "op-supervisor": "OP Supervisor", "assets": "Assets", - "superchainERC20-best-practices": "SuperchainERC20 best practices" } \ No newline at end of file diff --git a/pages/stack/interop/assets.mdx b/pages/stack/interop/assets.mdx index 7aa352c94..e6aff0bd0 100644 --- a/pages/stack/interop/assets.mdx +++ b/pages/stack/interop/assets.mdx @@ -18,4 +18,6 @@ Documentation covering SuperchainERC20, Superchain WETH, Supersim, and how to tr + + diff --git a/pages/stack/interop/assets/_meta.json b/pages/stack/interop/assets/_meta.json index 9398906a4..fb51b47ae 100644 --- a/pages/stack/interop/assets/_meta.json +++ b/pages/stack/interop/assets/_meta.json @@ -1,6 +1,7 @@ { "superchain-erc20": "SuperchainERC20", - "superchain-weth": "SuperchainWETH (Interoperable ETH)", "transfer-superchainERC20": "How to transfer a SuperchainERC20", - "deploy-superchain-erc20": "Deploy assets using SuperchainERC20" + "deploy-superchain-erc20": "Deploy assets using SuperchainERC20", + "superchainERC20-best-practices": "SuperchainERC20 best practices", + "superchain-weth": "SuperchainWETH (Interoperable ETH)" } \ No newline at end of file diff --git a/pages/stack/interop/superchainerc20-best-practices.mdx b/pages/stack/interop/assets/superchainerc20-best-practices.mdx similarity index 100% rename from pages/stack/interop/superchainerc20-best-practices.mdx rename to pages/stack/interop/assets/superchainerc20-best-practices.mdx diff --git a/words.txt b/words.txt index d61dc00ba..9b508946d 100644 --- a/words.txt +++ b/words.txt @@ -409,3 +409,4 @@ ZKPs ZKVM Zora zora +interchain \ No newline at end of file From d158eb8568bd76fb64ad36af6944970cfa100171 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Thu, 7 Nov 2024 17:14:11 -0800 Subject: [PATCH 8/9] Fix subcategory title --- pages/stack/interop/assets.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/assets.mdx b/pages/stack/interop/assets.mdx index e6aff0bd0..4d287b5f9 100644 --- a/pages/stack/interop/assets.mdx +++ b/pages/stack/interop/assets.mdx @@ -1,5 +1,5 @@ --- -title: Interop +title: Assets description: Documentation covering Cross Chain Message, Explainer, Message Passing, Op Supervisor, Superchain Erc20, Superchain Weth, Supersim, Transfer Superchainerc20 in the Interop section of the OP Stack ecosystem. lang: en-US --- From a8e761b309f4305a74ff0f1e7c6d9d7664523d1e Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Thu, 7 Nov 2024 17:15:28 -0800 Subject: [PATCH 9/9] Remove stray comma --- pages/stack/interop/_meta.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/_meta.json b/pages/stack/interop/_meta.json index e81485a1a..d42e969ce 100644 --- a/pages/stack/interop/_meta.json +++ b/pages/stack/interop/_meta.json @@ -4,5 +4,5 @@ "supersim": "Supersim Multichain Development Environment", "message-passing": "Interop message passing", "op-supervisor": "OP Supervisor", - "assets": "Assets", + "assets": "Assets" } \ No newline at end of file