Add Context #223
Merged
Add Context #223
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
meaghanfitzgerald
requested review from
martineckardt and
a team
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ashucoder9
approved these changes
Dec 11, 2024
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.
Q: After expiration of the current Subnet validation, can the Subnet validators continue/restake their validation without switching to L1 validation? If not, how do Subnet validators switch to L1 validation now they have expired?
A: In short: No, once a Subnet has been converted to an L1, Subnet validators can no longer be added. A validator would be able to rejoin the network as an L1 validator by interacting with the Validator Manager contract just as all other validators in the network would if they want to join.