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

Allow to specify origin for scheduled calls #6372

Closed
xlc opened this issue Jun 17, 2020 · 0 comments · Fixed by #6387
Closed

Allow to specify origin for scheduled calls #6372

xlc opened this issue Jun 17, 2020 · 0 comments · Fixed by #6387
Assignees
Labels
J0-enhancement An additional feature request.

Comments

@xlc
Copy link
Contributor

xlc commented Jun 17, 2020

We would like to allow calls to be dispatched at given block with a given origin.

Use case:

Acala implements multiple protocols and each protocols have its own council, which have the permission to modify the parameters of its protocol. But protocol council are not suppose to dispatch calls to modify parameters for other protocols.

We need the ability to schedule a parameter modification to be dispatched at later block, but currently the calls are dispatched with ROOT origin, which means any code that are able to schedule task have ROOT access.

We have developed our scheduler with half working dispatch origin feature but there are too many things needs to be considered for a scheduler (mostly weight related) so we will want to avoid to maintain a scheduler ourself given that now there is pallet-scheduler.

@xlc xlc added the J0-enhancement An additional feature request. label Jun 17, 2020
@xlc xlc self-assigned this Jun 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
J0-enhancement An additional feature request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant