16 major breaking releases
19.0.0 | Sep 26, 2024 |
---|---|
18.0.0 | Jul 18, 2024 |
17.0.0 | Jul 12, 2024 |
16.0.0 | Jun 24, 2024 |
0.0.0 | Aug 31, 2023 |
#49 in #exit
10,750 downloads per month
Used in 8 crates
(via polkadot-sdk)
2.5MB
44K
SLoC
Release
Polkadot SDK stable2409
lib.rs
:
Safe Mode
Trigger for stopping all extrinsics outside of a specific whitelist.
Pallet API
See the pallet
module for more information about the interfaces this pallet exposes,
including its configuration trait, dispatchables, storage items, events, and errors.
Overview
Safe mode is entered via two paths (deposit or forced) until a set block number.
The mode is exited when the block number is reached or a call to one of the exit extrinsics is
made. A WhitelistedCalls
configuration item contains all calls that can be executed while in
safe mode.
Primary Features
- Entering safe mode can be via privileged origin or anyone who places a deposit.
- Origin configuration items are separated for privileged entering and exiting safe mode.
- A configurable duration sets the number of blocks after which the system will exit safe mode.
- Safe mode may be extended beyond the configured exit by additional calls.
Example
Configuration of call filters:
impl frame_system::Config for Runtime {
// …
type BaseCallFilter = InsideBoth<DefaultFilter, SafeMode>;
// …
}
Entering safe mode with deposit:
Entering safe mode via privileged origin:
Exiting safe mode via privileged origin:
Low Level / Implementation Details
Use Cost
A storage value (EnteredUntil
) is used to store the block safe mode will be exited on.
Using the call filter will require a db read of that storage on the first extrinsic.
The storage will be added to the overlay and incur low cost for all additional calls.
Dependencies
~17–33MB
~529K SLoC