Skip to content
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

[Communities] Custom origin #311

Closed
olanod opened this issue Oct 3, 2023 · 1 comment · Fixed by #313
Closed

[Communities] Custom origin #311

olanod opened this issue Oct 3, 2023 · 1 comment · Fixed by #313
Assignees

Comments

@olanod
Copy link
Member

olanod commented Oct 3, 2023

To allow the maximum flexibility for our communities and their members to execute different permissioned actions in other parts of the system(e.g. in the assets pallet) or even across other chains, we should expose a custom origin(#[pallet::origin]) that maps well to the BodyPart of the XCM plurality junction.

BodyPart looks something like this,

pub enum BodyPart {
	Voice,
	Members { count: u32 },
	Fraction { nom: u32, denom: u32 },
	AtLeastProportion { nom: u32, denom: u32 },
	MoreThanProportion { nom: u32, denom: u32 },
}

Our origin type can be a 1:1 mapping or a subset of this

@olanod olanod added this to Virto MVP Oct 3, 2023
@olanod olanod moved this to Ready in Virto MVP Oct 3, 2023
@pandres95 pandres95 changed the title [Communities] Cutom origin [Communities] Custom origin Oct 3, 2023
@pandres95
Copy link
Member

This strategy will be useful for implementing #303. What do you think, @olanod?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants