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

Document safety constraints of pallet-scheduler #14715

@kianenigma

Description

@kianenigma

There is a lot of insider information, spread mostly in forum posts like https://forum.polkadot.network/t/pallet-idea-safe-scheduler/1009 that the existing scheduler pallet is unsafe, and should only be used internally by the runtime. In other words, scheduling operations should not be allowed by arbitrary external users.

I am worried that, similar to offchain workers, this pallet it as first glance a silver bullet that might lead to someone designing an application with the wrong assumption, thinking that this pallet is going magically schedule things for them across blocks, while it won't, and it can easily lead a parachain to stall.

This information is vital and should be in the source docs of the pallet, not the heads of a few.

Additionally, a warning about the change of decoding for stored calls is also a good point to be mentioned.

Update https://paritytech.github.io/substrate/master/pallet_scheduler/index.html to be aligned with the house pallet documentation guidelines, and make sure this point is also covered.

Metadata

Metadata

Assignees

No one assigned

    Labels

    I6-documentationDocumentation needs fixing, improving or augmenting.Z6-mentorAn easy task where a mentor is available. Please indicate in the issue who the mentor could be.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions