3.7. Block Validation and Consensus

The standard NAXION block validity test verifies whether the global status information of all contracts is included in the block header and if it matches the global status hash value.

This cryptographic system validates all nodes on the network and maintains a status database with verifiable duplicates. NAXION's status databases are categorized into private status and public status, both stored separately in memory using Patricia-Merkle trees.

The NAXION block validity test applies only to public status (i.e., verifiable status from connected nodes or on-chain data). Private (state) consensus is managed at the application layer and supported through the new storage root RPC API.

If a contract party requests password status consensus, the application searches for the contract status hash on the appropriate block. This hash can then be shared with other contract participants through either off-chain or on-chain transactions. The block validity test includes global transaction hash consensus, public consensus, and additional verification checks.

The Ethereum Virtual Machine (EVM) executes operations decisively, ensuring that the same inputs always produce the same outputs, thereby confirming consensus on the transaction list.