pezkuwichain
3139ffa25e
- snowbridge-pezpallet-* → pezsnowbridge-pezpallet-* (201 refs) - pallet/ directories → pezpallet/ (4 locations) - Fixed pezpallet.rs self-include recursion bug - Fixed sc-chain-spec hardcoded crate name in derive macro - Reverted .pezpallet_by_name() to .pallet_by_name() (subxt API) - Added BizinikiwiConfig type alias for zombienet tests - Deleted obsolete session state files Verified: pezsnowbridge-pezpallet-*, pezpallet-staking, pezpallet-staking-async, pezframe-benchmarking-cli all pass cargo check
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 the 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.