Block Request Judgement Calls on Polkadot #338
Merged
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
acatangiu
approved these changes
May 31, 2024
muharem
approved these changes
May 31, 2024
seadanda
approved these changes
May 31, 2024
|
/merge |
fellowship-merge-bot
bot
merged commit 04c69bf
into
polkadot-fellows:main
40 checks passed
|
Enabled Available commands
For more information see the documentation |
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.
This change blocks
request_judgementcalls on the Relay Chain. This is because requesting judgement reserves some funds to be sent to the registrar. This complicates migration to the People Chain and requires either breaking changes to the Identity pallet or phantom reserved funds. Blocking new requests (but allowing judgements and cancellations) prior to the migration will be simpler and lower risk.