feat(lazer): add governance sources info to state #2927
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
danimhr
approved these changes
Aug 6, 2025
keyvankhademi
approved these changes
Aug 6, 2025
Riateche
force-pushed
the
lazer-governance-sources-state
branch
from
08285f0 to
2f08833
Compare
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.
Summary
governance_instruction.prototostate.proto.RemoveGovernanceSource. Governance sources cannot be safely removed because governance sequence no has to be retained in the state to protect against replay attacks. It can be fully depermissioned instead.Rationale
This is part of the Lazer governance implementation.
How has this been tested?