General council and technical committee #104
Merged
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.
The governance structure on the RegionX parachain combines elements of gov1 and gov2.
We delegate the root privilege to the relay chain token holders, allowing them to modify the code of the RegionX parachain.
However, the RegionX parachain also has a general council and a technical committee with the authority to cancel proposals suggested by relay chain token holders. This is because the RegionX parachain has its own native token that provides some benefits. We want to protect RegionX native token holders by ensuring that Root cannot remove these benefits.
We also have a whitelisted caller origin that can expedite calls with root privileges. If the technical committee authorizes the whitelisting proposal, it can be processed through the whitelisting track, which is faster than the root track.
This PR also introduces spending origins for allocating funds from the RegionX treasury. It will be up to the RegionX token holders to vote on spending proposals. This will be achieved by introducing another instance of the referenda pallet, where the currency will be set to the parachain's native currency. (This will be added in a separate PR)