difftreelog
Reworked
in: master
1 file changed
pallets/scheduler/src/lib.rsdiffbeforeafterboth43//!43//!44//! This Pallet exposes capabilities for scheduling dispatches to occur at a44//! This Pallet exposes capabilities for scheduling dispatches to occur at a45//! specified block number or at a specified period. These scheduled dispatches45//! specified block number or at a specified period. These scheduled dispatches46//! may be named or anonymous and may be canceled.46//! should be named and may be canceled.47//!48//! **NOTE:** The scheduled calls will be dispatched with the default filter49//! for the origin: namely `frame_system::Config::BaseCallFilter` for all origin50//! except root which will get no filter. And not the filter contained in origin51//! use to call `fn schedule`.52//!53//! If a call is scheduled using proxy or whatever mecanism which adds filter,54//! then those filter will not be used when dispatching the schedule call.55//!47//!56//! **NOTE:** The unique scheduler is designed for deferred transaction calls by block number.48//! **NOTE:** The unique scheduler is designed for deferred transaction calls by block number.57//! Any user can book a call of a certain transaction to a specific block number.49//! Any user can book a call of a certain transaction to a specific block number.58//! Also possible to book a call with a certain frequency.50//! Also possible to book a call with a certain frequency.59//!51//!60//! Key differences from original pallet:52//! Key differences from the original pallet:61//! https://crates.io/crates/pallet-scheduler53//! https://crates.io/crates/pallet-scheduler62//! Schedule Id restricted by 16 bytes54//! Schedule Id restricted by 16 bytes. Identificator for booked call.63//! Priority limited by HARD DEADLINE (<= 63). Calls over maximum weight don't include to block55//! Priority limited by HARD DEADLINE (<= 63). Calls over maximum weight don't include to block.56//! The maximum weight that may be scheduled per block for any dispatchables of less priority than `schedule::HARD_DEADLINE`.64//! Maybe_periodic limit is 100 calls57//! Maybe_periodic limit is 100 calls. Reserved for future sponsored transaction support.58//! At 100 calls reserved amount is not so much and this is avoid potential problems with balance locks.65//! Any account allowed to schedule any calls. Account withdraw implemented through default transaction logic.59//! Any account allowed to schedule any calls. Account withdraw implemented through default transaction logic.66//!60//!67//! ## Interface61//! ## Interface68//!62//!69//! ### Dispatchable Functions63//! ### Dispatchable Functions70//!64//!71//! * `schedule` - schedule a dispatch, which may be periodic, to occur at a specified block and72//! with a specified priority.73//! * `cancel` - cancel a scheduled dispatch, specified by block number and index.74//! * `schedule_named` - augments the `schedule` interface with an additional `Vec<u8>` parameter65//! * `schedule_named` - augments the `schedule` interface with an additional `Vec<u8>` parameter75//! that can be used for identification.66//! that can be used for identification.76//! * `cancel_named` - the named complement to the cancel function.67//! * `cancel_named` - the named complement to the cancel function.