pezkuwichain
cf463fe8ee
- Fixed is_using_frame_crate() macro to check for pezframe/pezkuwi_sdk - Removed disable_pezframe_system_supertrait_check temporary bypasses - Feature-gated storage-benchmark and teyrchain-benchmarks code - Fixed dead_code warnings with underscore prefix (_Header) - Removed unused imports and shadowing use statements - Version bumps: procedural-tools 10.0.1, benchmarking-cli 32.0.1, docs 0.0.2, minimal-runtime 0.0.1, yet-another-teyrchain 0.6.1, umbrella 0.1.2 - Updated MAINNET_ROADMAP.md with FAZ 1 completion status
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 the Wasm meta protocol documentation.
👇 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.