Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

New proxy type for NominationPools #6211

Closed
kianenigma opened this issue Oct 29, 2022 · 5 comments · Fixed by #6846
Closed

New proxy type for NominationPools #6211

kianenigma opened this issue Oct 29, 2022 · 5 comments · Fixed by #6846
Assignees

Comments

@kianenigma
Copy link
Contributor

A new variant that allows NominationPools calls.

Not quite urgent, since most UIs don't support proxy that well yet.

@kianenigma
Copy link
Contributor Author

cc @rossbulat

@kianenigma
Copy link
Contributor Author

@Ank4n this is probably a 5 min job, just being forgotten :D

@xlc
Copy link
Contributor

xlc commented Dec 17, 2022

Should we just have a proxy variant Pallet(PalletIndex) and Call(PalletIndex, CallIndex) and automatically be 80% future proof with new pallets?

@kianenigma
Copy link
Contributor Author

kianenigma commented Dec 20, 2022

I have always been a fan of more flexible proxies that allow for specific call indices instead of matching on specific pallets in the runtime, but there has been push-back that for Polkadot we want to be conservative.

That being said, now with paritytech/substrate#12891, I think we have more reasons to allow this.

@Ank4n
Copy link
Contributor

Ank4n commented Mar 8, 2023

Should we just have a proxy variant Pallet(PalletIndex) and Call(PalletIndex, CallIndex) and automatically be 80% future proof with new pallets?

Created a separate issue for this here
paritytech/polkadot-sdk#700

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants