Synchronizer

a synchronizer is a component responsible for ensuring consistent state updates between the L2 network and its underlying Layer 1 (L1) blockchain. This involves periodically communicating and verifying the state of the L2 network with the L1, often through mechanisms like state roots or cross-chain protocols. This synchronization is crucial for security, interoperability, and the overall functionality of the L2 solution.

State synchronization with the Kaia chain

Snakee features a mechanism to relay specific events from the Kaia chain to Snakee. This involves:

• Contracts on Kaia triggering the StateSynced event via StateSender.sol.

• Heimdall monitoring these events and proposing state changes through StateReceiver.sol.

• Snakee committing these state changes at the start of every sprint, ensuring synchronization with the Kaia chain’s state.

This state sync process is a crucial aspect of maintaining consistency between the Kaia and SNakee chains, ensuring that relevant state changes on Kaia are reflected in Snakee’s state.

Running your own Kaia Endpoint Node (EN) is not simple, it requires technical expertise, monitoring and computing resources. It comes with a cost of maintaining storage, network bandwidth as well as having to divert engineering time and resources; nodes must be kept up to date and health checked regularly.

Hence, the main benefit of using an existing Public EN is that it allows you to solely focus on building and testing your blockchain product without the distraction of maintaining infrastructure to connect and interact with the Kaia network.

Things to Consider

The node providers are not responsible for any damage or losses caused in relation to traffic or interaction with the nodes.

If traffic is concentrated on certain nodes, you may experience service delay.

To prevent too many requests, rate limits may apply on a per-node basis, which are subject to change without prior notification.