Validation Layer

The Validation Layer of the Cubane Cubic Consensus Mechanism (CCCM) ensures transaction correctness, consistency, and consensus before finalization. Building on inputs from the ZK Layer, it employs a robust architecture that combines shards, cubes, and advanced algorithms to process zk-proofs securely and efficiently.

This layer implements randomization, cube formation, and a leader-member validation process to validate transactions with high throughput and minimal latency. Through parallel processing and dynamic resource allocation, it achieves scalability while maintaining strict sequencing and consistency via timestamp verification.

Here's a detailed walkthrough of its structure and functionality:

Input: Shards Receive zk-Proofs

• Source: The Validation Layer begins when shards receive zk-proofs with their associated timestamps from the ZK Layer.
• Objective:
  • Organize and manage zk-proofs for efficient validation.
  • Maintain proper sequencing and consistency using timestamps.

Randomization and Cube Formation Algorithm

Randomization Algorithm:

• Purpose:
  • Distribute zk-proofs randomly across shards to prevent overload.
  • Enhance security by making proof distribution unpredictable.
• Implementation:
  • Uses a cryptographically secure random function for dynamic zk-proof allocation to shards.

Cube Formation Algorithm:

• What is a Cube?
  1. A cube is a validation unit containing a Leader Node (LDN) and multiple Member Nodes (MNs).
  2. Each cube independently processes and validates a subset of zk-proofs.
• Formation Process:
  1. Shards group zk-proofs into batches by transaction type or complexity.
  2. Nodes within the shard form cubes using a Cube Formation Algorithm, which considers:
     • Node availability.
     • Computational capacity.
     • Stake.

Leader Node Election

• Election Process:
  • A Randomization Algorithm and Proof-of-Stake (PoS) mechanism select a Leader Node (LDN) for each cube.
  • Selection criteria ensure fairness, randomness, and reliability.
• Responsibilities of the LDN:
  • Organize cube activities.
  • Validate zk-proofs and transaction metadata.
  • Run the Tick Algorithm for timestamp consistency.
  • Share validation results with Member Nodes for consensus.

Batched Validation by the Cube