pezkuwichain
1c0e57d984
This commit systematically rebrands various references from Parity Technologies' Polkadot/Substrate ecosystem to PezkuwiChain within the kurdistan-sdk. Key changes include: - Updated external repository URLs (zombienet-sdk, parity-db, parity-scale-codec, wasm-instrument) to point to pezkuwichain forks. - Modified internal documentation and code comments to reflect PezkuwiChain naming and structure. - Replaced direct references to with or specific paths within the for XCM, Pezkuwi, and other modules. - Cleaned up deprecated issue and PR references in various and files, particularly in and modules. - Adjusted image and logo URLs in documentation to point to PezkuwiChain assets. - Removed or rephrased comments related to external Polkadot/Substrate PRs and issues. This is a significant step towards fully customizing the SDK for the PezkuwiChain ecosystem.
18 lines
914 B
Markdown
18 lines
914 B
Markdown
Provides types and traits for creating and checking inherents.
|
|
|
|
Each inherent is added to a produced block. Each runtime decides on which inherents it
|
|
wants to attach to its blocks. All data that is required for the runtime to create the inherents
|
|
is stored in the `InherentData`. This `InherentData` is constructed by the node and given to
|
|
the runtime.
|
|
|
|
Types that provide data for inherents, should implement `InherentDataProvider` and need to be
|
|
registered at `InherentDataProviders`.
|
|
|
|
In the runtime, modules need to implement `ProvideInherent` when they can create and/or check
|
|
inherents. By implementing `ProvideInherent`, a module is not enforced to create an inherent.
|
|
A module can also just check given inherents. For using a module as inherent provider, it needs
|
|
to be registered by the `construct_runtime!` macro. The macro documentation gives more
|
|
information on how that is done.
|
|
|
|
License: Apache-2.0
|