III. System Architecture Overview

mova builds a high performance and highly available payment infrastructure through a layered architecture that covers the full on chain transaction lifecycle — from request access and consensus validation to event generation, ledger storage, and data synchronization 3 1 system logical structure the mova network consists of key modules, each responsible for specific tasks management platform provides visual management functions including chain administration, block data queries, and node runtime monitoring smart contract ide an integrated online environment for contract development, compilation, and debugging supports both evm and wasm contracts command line tools (cli) supports certificate generation, chain configuration, deployment, and fast node setup for local development sdk toolkit (sdk) multi language rpc interfaces enabling contract deployment, invocation, and query gateway nodes act as protocol converters between off chain services and on chain protocols also collect transactions, pre execute them, and broadcast batches to consensus nodes verification nodes verify transaction and block signatures, and vote on verkletree state sets produced by block execution consensus nodes core accounting role responsible for transaction ordering, event generation, validation, and consensus voting sync nodes (witness nodes) synchronize blocks, execute transactions, and store full ledger copies, but do not participate in consensus voting light nodes synchronize state sets from consensus nodes and allow users to verify ledger correctness using only block headers and verkletree state sets without storing full blocks or executing transactions storage nodes provide distributed file system capability for on chain fragmented storage of large files (video, audio, images) for compliant payment proofs, invoices, etc storage services standard apis to bind file type data to transactions, enabling synchronized on chain storage of data and payment behavior note during deployment, the number of consensus nodes must meet consensus algorithm requirements sync node count can be adjusted based on persistence and read needs 3 2 core processing flow mova’s event driven model is dag based and supports high concurrency consensus the core flow is transaction reception transactions come from clients/dapps via rpc or from p2p broadcasts verification nodes pre process and validate signatures event proposal proposal nodes select qualified transactions, simulate them in batches, generate events, and submit them to consensus event broadcast the consensus module uses p2p to broadcast events to all consensus nodes event reception & consensus confirmation nodes run the witness algorithm if events in round r+2 strongly see an absolute majority of witness events in round r+1, the event is confirmed consensus is reached and the event becomes immutable block generation & dag update the dag is asynchronously analyzed new transaction blocks are generated and verified in parallel, then written into global state db and historical ledger