-
Notifications
You must be signed in to change notification settings - Fork 0
fix: let MsgRemoveConsumer erase a pre-launch consumer and release its chain id #78
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
giunatale
wants to merge
7
commits into
main
Choose a base branch
from
giunatale/fix/consumer-retirement
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 all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
0102a0b
let a pre-launch consumer be retired and release its chain id
giunatale 0895977
drop a wrong comparison from the retire admission comment
giunatale 206a544
fold retirement into MsgRemoveConsumer
giunatale 415eaf4
name the deletable phases in DeleteConsumerChain
giunatale 99dba75
state whose contract the deletable-phase check is
giunatale b819d85
align the liveness-removal e2e proposal with the remove-consumer sign…
giunatale ac418e0
seed infraction params in the retirement fixture: CreateConsumer vali…
giunatale 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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Unless I am wrong this makes
BeginBlockRemoveConsumersdelete as well the chainID of a previously launched chain.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.
It does, deliberately: releasing at deletion on both routes is half the point of the PR. Without it a consumer removed by the liveness sweep can never re-register its own chain id, since DELETED is terminal. The safety argument is in the comment at this line: by deletion time the client mapping is already removed, so no inbound packet can be attributed to the chain (the provider resolves packets by destination client), evidence, downtime and fee distribution all require LAUNCHED, and on this route a full unbonding period has passed since STOPPED, so nothing is still slashable. Releasing earlier, at STOPPED, would be unsafe precisely because the client mapping still exists there. If you see a concrete path this rationale misses, that is exactly what I want to know.