Zero-Knowledge Proof's blockchain is built from the ground up to support verifiable compute and privacy-preserving AI — without compromising on developer experience or performance. At its core, the system is modular, EVM-compatible, and optimized for scalability through Substrate’s extensibility and flexibility. ### Scalable ZKP Architecture Our architecture combines WebAssembly and EVM execution layers, layered consensus with Double DPoS, and developer tooling that bridges familiar Ethereum workflows with advanced substrate-native capabilities. Whether you're deploying Solidity contracts, compiling Rust-based runtimes, or interfacing with ZK circuits, the stack is engineered to give builders a versatile, performant foundation. As the project evolves, certain parameters such as fees, block size, and APIs may be fine-tuned to improve stability and throughput. The stack below reflects our current live testnet configuration — LetheZKP — and will continue to expand as we progress toward mainnet. #### Core Network Characteristics - Testnet Name: LetheZKP Testnet based on Polkadot Substrate (L1 testnet). - Chain ID: 500000 (for EVM integration; use in MetaMask and RPC clients). - Network Type: Layer-1 (L1), based on Polkadot Substrate. - Consensus Mechanism: Double Delegated Proof of Stake (Double DPoS). - Compatibility: EVM (Ethereum Virtual Machine) support via pallet addition; natively compatible with mainnet in terms of EVM functionality. #### Smart Contract Languages and Frameworks * Solidity (for EVM), Rust (for Substrate). * Development Frameworks: Truffle, Hardhat, Foundry (for Ethereum-compatible parts). * Virtual Machine: EVM (Ethereum Virtual Machine) and WASM (WebAssembly). #### Infrastructure Nodes * Clients based on Geth (due to EVM compatibility via pallet); for Substrate — standard Polkadot tools. * API: JSON-RPC (standard for EVM), Web3.js support; additional APIs (REST) under development. #### Developer Tools (SDK/CLI) * Remix (as IDE), Web3.py, ethers.js, Dedot, Subxt (for Substrate interaction). * Libraries: ethers.js, Web3.js (for EVM integration); Dedot and Subxt for Substrate-specific tasks. * Test Wallets: MetaMask (EVM compatibility support). #### Standards and Network Parameters Support for any ERC standards (ERC-20, ERC-721, etc.) for the EVM part. Network Parameters: - Block Time: 6 seconds (based on Aura; MILLISECS_PER_BLOCK = 6000, MinimumPeriod = 3000 ms). - Block Size: 5 MiB (MAXIMUM_BLOCK_LENGTH = 5 * 1024 * 1024 bytes; maximumcomputational weight: 2000 ms ref_time per block). - Fees: For extrinsics — based on weight and length via IdentityFee +dynamic multiplier (SlowAdjustingFeeUpdate, OperationalFeeMultiplier = 5);for EVM — base fee of 1 gwei (DefaultBaseFeePerGas = 1_000_000_000),dynamic adjustment (dynamic-fee, divisor = 1024). #### Ongoing Configuration Updates Configuration (fees, API, block time, and other parameters) may change at any time to improve stability and performance during the project's development. See also: * [[ZKP/ZKP Base Layer/ZKP Blockchain/Tech Stack with detailed explanations/Consensus Layer Technologies|Consensus Layer Technologies]] * [[ZKP/ZKP Base Layer/ZKP Blockchain/Tech Stack with detailed explanations/Application Layer Technologies|Application Layer Technologies]] * [[ZKP/ZKP Base Layer/ZKP Blockchain/Tech Stack with detailed explanations/Storage Layer Technologies|Storage Layer Technologies]] * [[ZKP/ZKP Base Layer/ZKP Blockchain/Tech Stack with detailed explanations/Cryptographic Technologies|Cryptographic Technologies]] * [[ZKP/ZKP Base Layer/ZKP Blockchain/Tech Stack with detailed explanations/Implementation Details|Implementation Details]]