Run Your Own Node

The Kasplex Layer 2 is composed of four components:

• ​​Client​​：Retrieves L2 transactions from Kaspa L1 and places them into the Executor's mempool for execution. The Client also monitors L1 reorganization events. Upon a reorganization, it notifies the Executor to roll back the state and re-execute affected transactions. In a Light Node, the Client also monitors block generation events from the Full Node and verifies new blocks using Kaspa L1 data.

• Executor​​：Executes transactions in the mempool, completing state transitions.

• Prover​​：Generates proof files at the block-batch level to verify the correctness of state transitions.

• Relayer​​：Forwards transactions from EVM wallets to Kaspa L1, enabling compatibility with the Ethereum toolchain.

Decentralized Participation

Users can operate L2 nodes in various modes, depending on their hardware capabilities:

• Light Node: Receives transactions from EVM wallets and forwards them to L1 via the node’s Relayer. Users can customize the Relayer’s fee strategy to provide RPC service for others. Depends on Regular or Full Nodes for L2 state data.

• Regular Node: Synchronizes historical state from the L2 genesis or the latest Prover-verified L2 state for bootstrapping. Then retrieves L2 transactions from its local Kaspa node, provides full RPC services, and maintains the L2 state locally in a trustless manner.

• Archival Node: Stores complete historical transaction data from the L2 genesis block and provides witness data for zero-knowledge proof generation. Requires more robust hardware than Regular Nodes.