Call- published functions that may be called with a set of arguments
Error- used to inform users why a function invocation (
Event- pallets can emit events to make users aware of some state changes
Log- an extensible header item
Metadata- information that allows inspection of the above
Origin- specifies the source of a function invocation (
nis the number of nodes (participants) in the system.
subkey, allow users to implicitly specify the dev phrase by only specifying a derivation path such as
Callby convention) and interpreting it in order to call a published function in a runtime module ("pallet") with some arguments. Such published functions take one additional parameter, known as
origin, that allows the function to securely determine the provenance of its execution.
p, that a proposed block, denoted by
B, will remain in the canonical chain; as more blocks are produced on top of
decl_module!and compose pallets (e.g.
construct_runtime!into a working runtime that can easily be used to power a Substrate-based blockchain. The convention used in the Substrate codebase is to preface FRAME's core modules with
frame_and the optional pallets with
pallet_*. For instance, the macros mentioned above are all defined in the
frame_supportmodule and all FRAME-based runtimes must include the
frame_systemmodule. Once the
frame_support::construct_runtimemacro has been used to create a runtime that includes the
frame_systemmodule, optional pallets such as the Balances pallet may be used to extend the runtimes core capabilities.