Architecture

Nigo Protocol separates consensus data, state-transition execution, consensus and networking, persistent storage, and external APIs behind distinct module boundaries.

Start with the architecture overview to understand data and control flow, then continue to the area relevant to your work.

• StateCell: the smallest unit of consensus state and its lifecycle
• Transaction model: canonical transaction kinds and execution results
• EVM compatibility layer: execution, transaction ingress, RPC, and policy differences
• Native Program: protocol programs that validate StateCell transitions
• Permissioned QBFT consensus: static validator profile, finality, and recovery boundaries

The documentation focuses on maintained contracts and data flow, rather than exposing internal task history or implementation order.