feat(spec): Fork or Reset Protocol for Starknet #170
Closed
Conversation
This file contains 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
cason
changed the title
| - The validator set for the fork is the last validator set accepted by L1 | ||
| plus all the "stale registrations", i.e., validator set updates produced by | ||
| L1 but not included in Starknet blocks (L2) in due time. | ||
| - This is not enough precise yet, for instance, how the validator set |
There was a problem hiding this comment.
I agree that this point seems a bit unclear.
- If there is a missed deadline, then the deadline was missed (I assume) mostly by the validators that are in this validator set. So why is there trust that the first validator set of the fork is "better" than the last old one. So the question is what scenarios are solved by this?
- Wouldn't it make sense to have a more explicit reset protocol on L1: if a deadline is missed, we mark the L2 as stale -> after that a new validator set needs to be set up -> we commit the new validator set on L1 and start the new L2.
There was a problem hiding this comment.
we commit the new validator set on L1
How would we do that?
There was a problem hiding this comment.
So why is there trust that the first validator set of the fork is "better" than the last old one. So the question is what scenarios are solved by this?
The assumption here is that new validators are more trustworthy than the existing ones. The existing ones are probably maintained in the new validator set, but with lower voting power (they call this "dilution").
I think the assumption here is that most of the existing validator set is good, but the <1/3 assumption was broken by a "small amount" of voting power. In this case, adding new "good" validators would make the <1/3 assumption to hold again.
3 tasks
josef-widder
added a commit
that referenced
this pull request
Apr 25, 2024
|
I have copied the information that was only here to #171. So I close this. |
This was referenced Apr 25, 2024
ancazamfir
added a commit
that referenced
this pull request
Apr 29, 2024
* draft of system overview * more details * fix * a final question for this week * more questions * more questions * the question from slack * last update before meeting * typos * notes from meeting * Update specs/english/overview.md Co-authored-by: Daniel <daniel.cason@informal.systems> * Update specs/english/overview.md Co-authored-by: Daniel <daniel.cason@informal.systems> * re-orged english spec folder to accomodate new spec * cleaned up overview * added missing information from #170 * spell * English spec * ready for review * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * Update specs/english/forced-updates/README.md Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com> * working on Anca's comments * added TODOs so that we can merge --------- Co-authored-by: Daniel <daniel.cason@informal.systems> Co-authored-by: Anca Zamfir <ancazamfir@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #166.
Fork Protocol
Depends on #168. Needs to merged after #168 is merged.
PR author checklist