-
Notifications
You must be signed in to change notification settings - Fork 17
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
MD/MIP describing the bridge architecture. #68
Labels
Draft MD/MIP
A new/draft MD/MIP
Comments
Yes this would be great, thanks Franck. |
franck44
added a commit
that referenced
this issue
Jan 9, 2025
franck44
added a commit
that referenced
this issue
Jan 9, 2025
apenzk
added a commit
that referenced
this issue
Feb 3, 2025
* feat: parent-child MIPs and PMIPs * fix: file structure * fix: detail about PR number * fix: remove references to PMIPs * Update README.md * fix: add author as codeowner * minor changes * Minor typo #68 --------- Co-authored-by: apenzk <[email protected]> Co-authored-by: franck44 <[email protected]>
apenzk
added a commit
that referenced
this issue
Feb 6, 2025
* feat: parent-child MIPs and PMIPs * fix: file structure * fix: detail about PR number * fix: remove references to PMIPs * Update README.md * fix: add author as codeowner * minor changes * Minor typo #68 --------- Co-authored-by: apenzk <[email protected]> Co-authored-by: franck44 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MIP-58 proposes a bridge design of type lock/mint.
The overall bridge mechanism relies on a few components, contracts (L1, L2), relayer etc.
As @0xmovses suggested, it may useful to have a high-level description of the bridge architecture that spells out the components and the assumptions for each of them.
We could also add some arguments for correctness, e.g. that eventually each L1-initiated transfer is completed on L2 (and under what assumptions).
This is similar in spirit to MIP-39 which was for the old HTLC bridge design.
The text was updated successfully, but these errors were encountered: