Kaia’s architecture is structured into three primary networks: the Core Cell Network (CCN), the Endpoint Node Network (ENN), and the Service Chain Network (SCN).
The CCN comprises core cells responsible for executing transactions and generating blocks. Each core cell typically includes a consensus node and multiple proxy nodes. Consensus nodes validate submitted transactions and execute valid ones, ensuring the integrity and consistency of the blockchain. Proxy nodes assist in propagating transactions and blocks across the network, enhancing communication efficiency.
The ENN consists of endpoint nodes that serve as entry points for decentralized applications (dApps) and service chains to interact with the Kaia blockchain. These nodes expose Remote Procedure Call (RPC) APIs, allowing developers and users to read blockchain data and submit transactions directly to the network without intermediaries. Endpoint nodes maintain a full copy of the blockchain ledger, facilitating access to blockchain services.
The SCN includes service chains, which are auxiliary blockchains connected to the Kaia mainnet. Service chains are designed to meet specific application requirements, such as higher transaction throughput or specialized consensus mechanisms. They offer scalability and flexibility, enabling developers to deploy customized solutions while maintaining interoperability with the main Kaia network.
Kaia employs an optimized version of the Istanbul Byzantine Fault Tolerance (IBFT) consensus algorithm to achieve rapid transaction finality and maintain network integrity. IBFT is a consensus mechanism that allows a network to reach agreement on the state of the blockchain, even in the presence of malicious actors, provided that less than one-third of the nodes are faulty or compromised.
In Kaia’s implementation, the consensus process involves a series of steps:
A designated proposer node, selected deterministically, creates a new block containing pending transactions and broadcasts it to the network. Upon receiving the proposed block, validator nodes enter the pre-prepare stage, where they verify the block’s validity, including transaction correctness and adherence to protocol rules.
Validators broadcast their approval of the block to other validators, indicating that they have verified the block and are prepared to add it to the blockchain. Once a supermajority (typically two-thirds) of validators have sent prepared messages, validators proceed to the commit stage, broadcasting commit messages to finalize the block. After receiving a supermajority of commit messages, validators add the block to their local copy of the blockchain, achieving immediate transaction finality.
This optimized IBFT implementation enables Kaia to maintain a one-second block time, ensuring swift transaction processing and high throughput.
Kaia’s architecture and consensus mechanism contribute to its notable performance metrics:
Highlights
Kaia’s architecture is structured into three primary networks: the Core Cell Network (CCN), the Endpoint Node Network (ENN), and the Service Chain Network (SCN).
The CCN comprises core cells responsible for executing transactions and generating blocks. Each core cell typically includes a consensus node and multiple proxy nodes. Consensus nodes validate submitted transactions and execute valid ones, ensuring the integrity and consistency of the blockchain. Proxy nodes assist in propagating transactions and blocks across the network, enhancing communication efficiency.
The ENN consists of endpoint nodes that serve as entry points for decentralized applications (dApps) and service chains to interact with the Kaia blockchain. These nodes expose Remote Procedure Call (RPC) APIs, allowing developers and users to read blockchain data and submit transactions directly to the network without intermediaries. Endpoint nodes maintain a full copy of the blockchain ledger, facilitating access to blockchain services.
The SCN includes service chains, which are auxiliary blockchains connected to the Kaia mainnet. Service chains are designed to meet specific application requirements, such as higher transaction throughput or specialized consensus mechanisms. They offer scalability and flexibility, enabling developers to deploy customized solutions while maintaining interoperability with the main Kaia network.
Kaia employs an optimized version of the Istanbul Byzantine Fault Tolerance (IBFT) consensus algorithm to achieve rapid transaction finality and maintain network integrity. IBFT is a consensus mechanism that allows a network to reach agreement on the state of the blockchain, even in the presence of malicious actors, provided that less than one-third of the nodes are faulty or compromised.
In Kaia’s implementation, the consensus process involves a series of steps:
A designated proposer node, selected deterministically, creates a new block containing pending transactions and broadcasts it to the network. Upon receiving the proposed block, validator nodes enter the pre-prepare stage, where they verify the block’s validity, including transaction correctness and adherence to protocol rules.
Validators broadcast their approval of the block to other validators, indicating that they have verified the block and are prepared to add it to the blockchain. Once a supermajority (typically two-thirds) of validators have sent prepared messages, validators proceed to the commit stage, broadcasting commit messages to finalize the block. After receiving a supermajority of commit messages, validators add the block to their local copy of the blockchain, achieving immediate transaction finality.
This optimized IBFT implementation enables Kaia to maintain a one-second block time, ensuring swift transaction processing and high throughput.
Kaia’s architecture and consensus mechanism contribute to its notable performance metrics:
Highlights