This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Kusama origins as xcm multi_location #6273
Merged
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
a3197ec
Kusamsa origins as xcm multilocation
muharem 6919d89
Fellows origin index
muharem 3e0cf79
origins to xcm plurality body
muharem 96a223b
cleanup
muharem 96ddd4b
fix cargo spellcheck
muharem e386bdb
Merge remote-tracking branch 'origin/master' into muharem-kusama-xcm-…
muharem d64fa67
Merge remote-tracking branch 'origin/master' into muharem-kusama-xcm-…
muharem 5c26797
Apply suggestions from code review
muharem ffb5eb6
include Fellows into scope
muharem 78474c1
include Fellows into scope
muharem f8e3432
Merge branch 'master' into muharem-kusama-xcm-origins
gavofyork 5a7a49e
include common bodies into xcm
muharem 11fd946
whitelist "defence" for spellchecker
muharem 83848b9
Merge remote-tracking branch 'origin/master' into muharem-kusama-xcm-…
muharem cbd0dd6
rename to more frequent "defense"
muharem 4ff9d36
improve docs
muharem 1d78d62
rustfmt
muharem 6100f1a
Merge remote-tracking branch 'origin/master' into muharem-kusama-xcm-…
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 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 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 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 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 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 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
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.
Would we want a new body ID for the Fellowship, or use Technical for the Technical Committee and Fellowship (for the time that they co-exist)?
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.
I think it's better to use Technical. XCM is a higher level protocol, we make less changes to it, and it does not have to be one to one mapping.
I did not touched the docs of Technical, since its only for Kusama now.
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.
Double checked, Technical not used/mapped right now in kusama or polkadot (only docs tells as its supposed to be used as Tech Comm), it's correct to start using it as Fellows.