# ZKP Blockchain The [[ZKP/ZKP Base Layer/In-depth Introduction|Zero-Knowledge Proof (ZKP) base layer]] forms the backbone of the [[ZKP/Introduction/ZKP Ecosystem/Architecture|ZKP ecosystem]], optimized for distributed AI compute, prioritizing security, scalability, and privacy. This section offers a comprehensive technical analysis of its architecture—spanning the [[ZKP/ZKP Base Layer/ZKP Blockchain/Technical Build Consensus Layer/Consensus Model|Consensus Layer]], [[ZKP/ZKP Base Layer/ZKP Blockchain/Technical Build Application Layer/Overview of Components|Application Layer]], [[ZKP/ZKP Base Layer/ZKP Blockchain/Performance/Storage Layer|Storage Layer]], [[ZKP/ZKP Base Layer/ZKP Blockchain/Exploring zk-Rollup for Future EVM Compatibility A Technical Analysis/Performance Metrics|network dynamics,]] and security features—followed by an in-depth examination of attack vectors and mitigations, and a discussion on future scalability enhancements via [[ZKP/ZKP Base Layer/ZKP Blockchain/Exploring zk-Rollup for Future EVM Compatibility A Technical Analysis/zk-Rollups for Future EVM Compatibility|zk-rollups.]] ## Overview of the ZKP Blockchain Layers The ZKP blockchain employs a multi-layered architecture to optimize functionality and scalability: - **Consensus Layer:** Achieves ledger agreement via a hybrid Proof of Intelligence (PoI) and Proof of Space (PoSp) model, integrated with Substrate's BABE+GRANDPA consensus framework through custom pallets. - **Application Layer:** Executes AI-driven logic through Ethereum Virtual Machine (EVM) and WebAssembly (WASM) runtimes via Substrate's EVM pallet and native WASM execution, secured by ZKPs. - **Storage Layer:** Combines on-chain metadata storage using Patricia Tries with off-chain systems like IPFS and Filecoin for efficient data management. These layers coordinate through Substrate's runtime interface, enabling seamless communication between pallets via the Executive pallet, with state updates committed through Substrate's block authoring process [107, 108]. Smart contracts facilitate Application-Storage interactions; for instance, a dataset's CID and ZKP proof are stored on-chain via custom pallets, while the data resides on IPFS, retrieved with Filecoin ensuring availability [12, 13]. Event-driven protocols (e.g., DatasetStored events) trigger pallet interactions, ensuring real-time alignment across the runtime. ![[Diagram2 1.png]] See also: [[ZKP/ZKP Base Layer/ZKP Blockchain/Layer Interactions|Layer Interactions]]