-
Notifications
You must be signed in to change notification settings - Fork 22
[draft] MIP-73: The SanFran Model #73
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
Open
apenzk
wants to merge
14
commits into
main
Choose a base branch
from
mip/sanfran-model
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 6 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
8fc998c
init
apenzk 1b27553
update mip number
apenzk eb06c8a
update
apenzk 8cc1ea3
overview png
apenzk bb5d296
update rate limiter link
apenzk 3f522d6
fix link
apenzk 81d9356
add motivation
apenzk 09c8794
Fornatting.
franck44 2fa9f97
fix figure errors
apenzk e943bd5
update mip53
apenzk 7649392
adjust format to fit MIP-53 requirement
apenzk eb0a3cc
minor edit
apenzk 0861cb9
add content
apenzk 46ed83e
Merge branch 'main' into mip/sanfran-model
apenzk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,77 @@ | ||
| # MIP-73: The SanFran Model | ||
| - **Description**: Proposes an L2 model that improves the Biarritz model. It transitions to a Lock/Mint-Native Bridge, adds Bridge fees, and proposes changes to existing components. | ||
| - **Authors**: [Andreas Penzkofer](mailto:[email protected]) | ||
|
|
||
| ## Abstract | ||
|
|
||
| The SanFran Model applies the following changes | ||
|
|
||
| - formally adds the Lock/Mint-Native Bridge, see [MIP-58](https://github.com/movementlabsxyz/MIP/pull/58) | ||
| - proposes detailed Bridge fees, see [MD-69](https://github.com/movementlabsxyz/MIP/pull/69) | ||
| - proposes Relayer - Continuous Operation and Bootstrapping algorithm, see [MIP-61](https://github.com/movementlabsxyz/MIP/pull/61) | ||
| - proposes changes to the Informer, see [MIP-71](https://github.com/movementlabsxyz/MIP/pull/71) | ||
| - proposes changes to the Rate Limiter, see [MIP-74](https://github.com/movementlabsxyz/MIP/pull/74) | ||
| - proposes fast-confirmations on L2, see [MIP-65](https://github.com/movementlabsxyz/MIP/pull/65) | ||
|
|
||
| ## Motivation | ||
|
|
||
| This model is the result of the co-location. | ||
|
|
||
| ## Specification | ||
|
|
||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. | ||
|
|
||
| The following Diagram gives an overview of the modified or added components. | ||
|
|
||
|  | ||
| _Modified or added components are shown in orange._ | ||
|
|
||
| ### Lock/Mint-Native Bridge | ||
|
|
||
| Factually the Lock/Mint-Native Bridge has been introduced prior to the co-location. However, to categorize it within a model, the SanFran Model seems suitable. | ||
|
|
||
| We are moving away from the HTLC Native Bridge, see [MIP-39](https://github.com/movementlabsxyz/MIP/tree/main/MIP/mip-39) to the subjectively simpler design of a Lock/Mint Native Bridge, see [MIP-58](https://github.com/movementlabsxyz/MIP/pull/58). For a general overview of bridge designs, see [MIP-60](https://github.com/movementlabsxyz/MIP/pull/60). | ||
|
|
||
| ### Bridge fees | ||
|
|
||
| In order to operate sustainably we require that the bridge fees cover expenditures of the operator sufficiently. We propose an approach for appropriate fee calculation in [MIP-58](https://github.com/movementlabsxyz/MIP/pull/58). | ||
|
|
||
| ### Relayer - Continuous Operation and Bootstrapping | ||
|
|
||
| Introduce an algorithm for continuous operation and bootstrapping for the Relayer, see [MIP-61](https://github.com/movementlabsxyz/MIP/pull/61). | ||
|
|
||
| ### Adjust Informer to the Lock/Mint Native Bridge design | ||
|
|
||
| With the change of the Native Bridge design the requirements, conditions and parameters have changed. [MIP-71](https://github.com/movementlabsxyz/MIP/pull/71) updates the Informer to the new setting. | ||
|
|
||
| ### Adjust the Rate Limiter to the Lock/Mint Native Bridge design | ||
|
|
||
| With the change of the Native Bridge design the requirements, conditions and parameters have changed. [MIP-74](https://github.com/movementlabsxyz/MIP/pull/74) updates the Rate Limiter to the new setting. | ||
|
|
||
| ### Add fastconfirmations | ||
|
|
||
| In order to facility fast confirmations as requested by the Fast-Finality Settlement mechanism, we require confirmations on the L2 in addition to the confirmations on the L1 (postconfirmations, see [MIP-37](https://github.com/movementlabsxyz/MIP/pull/37)). | ||
|
|
||
| We propose such a mechanism called fastconfirmation in [MIP-65](https://github.com/movementlabsxyz/MIP/pull/65). | ||
|
|
||
| ## Reference Implementation | ||
|
|
||
| ## Verification | ||
|
|
||
| Needs discussion. | ||
|
|
||
| --- | ||
|
|
||
| ## Errata | ||
|
|
||
| --- | ||
|
|
||
| ## Appendix | ||
|
|
||
| ### A1 | ||
| Nothing important here. | ||
|
|
||
| --- | ||
| ## Copyright | ||
|
|
||
| Copyright and related rights waived via [CC0](../LICENSE.md). | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Are there any other motivations, such as differences between this and a previous model and how those differences may result in an improved model, that can be mentioned here?
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.
i have added more motivation