Add Deregister ParaId component and integrate into Actions #11499
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
10 tasks
10 tasks
|
Based on the implications of this action and the fact that once the button is clicked the UI is the same as any other transaction signing action, I’d advise adding some kind of extra confirmation before sending. Something like: |
Added a warning message here to clearly explain what deregistering a paraID does and its consequences. |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
📝 Description
This PR aims to add the component for deregister a reserved parachain ID (paraID).
Screen.Recording.2025-04-22.at.10.14.55.mov
✨ What's New
registrar.reserve) are now visible in the UI.🎯 Why
Users previously had no clear way to cancel a reserved paraID, leading to confusion and frustration over "locked" DOT/KSM deposits. This improves visibility and control during the parathread onboarding process.