Cubane uses a custom built consensus named Cubane Cubic Consensus Mechanism[CCCM], where it focuses on privacy, scalability and consistency. Making this to live, cubane distributes the architecture in a way to modularize Privacy, Transaction validation, Data compression and on-chain consistency.

ZK-Layer:

Understanding flow within ZK-Layer.

ZK layer receives transaction requests from various nodes and is responsible for generating zkProofs, to get them timestamped and batching of these proofs for transaction validation.

CCCM aims for providing scalability and consistency at this layer, to achieve this the zkProofs that are generated should be interactive and generation time should be scalable over large volumes.

Comparative study on zkSTARKs vs zkSNARKs:

ZK-LayerZero-Knowledge Proofs (ZKPs) are cryptographic techniques that enable one party to show knowledge of specific information without disclosing it. Two major varieties, zkSNARKs (Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge) and zkSTARKs (Zero-Knowledge Scalable Transparent Arguments of Knowledge) differ in design, scalability, and cryptographic assumptions.

zkSTARKs [Zero-Knowledge Scalable Transparent Arguments of Knowledge]:

Structure:

• Uses hash functions instead of elliptic curve cryptography.
• Transparent proof generation without a trusted setup.

Key Features:

• Setup: No trusted setup, ensuring transparency and better security.
• Proof Size: Larger than zkSNARKs but more scalable.
• Verification: Relatively fast, though slightly less efficient than zkSNARKs for small proofs.

Advantages:

• Resistance to quantum attacks due to hash-based cryptography.