Architecture Overview

Nezo Sydra Architecture

Nezo Sydra leverages zkEVM and Data Availability technology to process transactions in batches, to ensure validity and compress data. The transaction flow involves several components working together:

  1. User Transactions: Users initiate transactions within the Nezo Sydra network.

  2. Sequencer Nodes (Elected): These nodes validate, order, and batch transactions, preparing them for zk-proof generation.

  3. Prover Nodes: Generate zk-proofs for the transaction batches, ensuring data validity and compression.

  4. zkEVM Processing: The zero-knowledge proofs generated by the Prover Nodes are processed here.

  5. Submission to Ethereum: The zk-rollup proofs and compressed data are submitted to the Ethereum mainnet for finality and security.

Detailed Role of Validators and Nodes

Validators (Sequencer Nodes)

Validators (sequencers) are essential for maintaining the integrity and efficiency of the NezoHub network. They are responsible for:

  • Transaction Validation: Ensuring that transactions are valid and compliant with network rules.

  • Batch Formation: Grouping validated transactions into batches to be processed by the zkEVM.

  • Staking and Delegation: Staking a minimum of 5,000 Nezo tokens to participate as a Sequencer Node Validator. Community members can delegate their tokens to these validator nodes, increasing their stake and potential rewards.

Nodes

NezoHub leverages two distinct node types within Nezo Sydra:

  • Sequencer Nodes (Elected): As described earlier, these nodes are elected through a DPoS mechanism. They are responsible for validating transactions, ordering them into batches, and submitting them for zk-proof generation. Maintaining high performance is crucial for sequencer nodes to be selected.

  • Prover Nodes: These nodes are responsible for generating zk-proofs for the transaction batches submitted by sequencers. Prover nodes can be permissionless, allowing anyone with sufficient computational resources to participate. The selection process for assigning transaction batches to prover nodes is an area of ongoing development. Potential approaches include:

    • Load Balancing: Distributing batches based on prover node capacity.

    • Market-Based System: Prover nodes could compete for batches based on factors like cost and proof generation speed. Sequencers could choose the most efficient option.

Security Measures

NezoHub employs several robust security measures to ensure the integrity and safety of the network:

  • Cryptographic Techniques: Utilize state-of-the-art cryptographic primitives to secure communication channels and protect user data.

  • Regular Smart Contract Audits: Regular security audits conducted by independent firms identify and address potential vulnerabilities in smart contracts.

  • Decentralized Sequencers: Distributing sequencer responsibilities mitigates risks associated with single points of failure and malicious actors controlling a majority of sequencers.

  • Slashing Mechanism: A slashing mechanism penalizes validators who act maliciously or fail to perform their duties effectively. This mechanism discourages bad actors and incentivizes honest participation.

Nezo Core Architecture

We are in the advanced stages of designing the core infrastructure for Nezo Core, a next-generation Layer 1 blockchain. NezoCore is engineered to support over 10,000 transactions per second (TPS), offering full EVM compatibility while also integrating AI-driven smart contracts. This platform enables the creation of sovereign app-chains, each with its own independent consensus mechanism, allowing them to operate autonomously. Additionally, NezoCore supports custom tokens for gas fees, providing businesses with the flexibility to tailor transaction costs to their economic models.

This architecture aligns seamlessly with the broader NezoHub ecosystem, leveraging our preferred technology stack while maintaining the sovereignty and scalability required by businesses seeking advanced blockchain solutions. As we continue to refine our research and design, we will provide further details that align with our objectives of faster deployment times, enhanced performance, and robust support for AI tools. More comprehensive updates will be shared as our development progresses.

Stay tuned for further updates and insights from our ongoing work. Follow us

Last updated