-
Notifications
You must be signed in to change notification settings - Fork 262
Tutorial: custom bridges (also how do have SuperchainERC20 equivalence without using the same addresses) #1574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for docs-optimism ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -0,0 +1,326 @@ | |||
--- | |||
title: Custom interoperability bridge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Building a custom bridge
<Callout> | ||
The SuperchainERC20 standard is ready for production deployments. | ||
Please note that the OP Stack interoperability upgrade, required for crosschain messaging, is currently still in active development. | ||
</Callout> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this call out is not relevant
## Overview | ||
|
||
Sometimes the address of an ERC20 contract is not available on a different chain. | ||
This means that the [standard bridge](/interop/superchain-erc20) is not an option. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SupercahinTokenBridge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SuperchainTokenBridge***
Description
How to make a custom bridge, and how to use that when you can upgrade your ERC-20 but you can't create ERC-20 in the same address elsewhere.
Tests
N/A
Additional context
N/A
Metadata
This should be merged after #1525