mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-30 01:27:56 +00:00
8b9455465b
* CI: Add feature sorting check Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Sort all features Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Add some mistakes Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Revert "Add some mistakes" This reverts commit b2b1099f979f6decb22d09b46689c1554bb72e81. * CI job naming Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Add oneliner formatting Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Explain tool Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Use latest version Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Better erorr message Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Format after master merge Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Use --check option Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Messed up the merge commit... Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> --------- Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Client backend that is backed by a database.
Canonicality vs. Finality
Finality indicates that a block will not be reverted, according to the consensus algorithm, while canonicality indicates that the block may be reverted, but we will be unable to do so, having discarded heavy state that will allow a chain reorganization.
Finality implies canonicality but not vice-versa.
License: GPL-3.0-or-later WITH Classpath-exception-2.0