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.
Node
ℹ️ A node - in PezkuwiChain - is a binary executable, whose primary purpose is to execute the runtime.
🔗 It communicates with other nodes in the network, and aims for consensus among them.
⚙️ It acts as a remote procedure call (RPC) server, allowing interaction with the blockchain.
👉 Learn more about the architecture, and a difference between a node and a runtime here.
👇 Here are the most important files in this node template:
chain_spec.rs: A chain specification is a source code file that defines the chain's initial (genesis) state.service.rs: This file defines the node implementation. It's a place to configure consensus-related topics. In favor of minimalism, this template has no consensus configured.