Network
Last updated
Last updated
The dKargo 2.0 network is an Optimistic Rollup-based Layer3 solution developed using the Arbitrum Nitro Stack. Through its Layer3 architecture, dKargo delivers high transaction throughput, fast speeds, and low fees, enabling the effective management and exchange of logistics data. The Layer3 network maintains the security and transparency of Layer1 blockchains while supporting data decentralization and efficient data management. Source code and technical documentation for Arbitrum Nitro can be found at .
1) Layer3 - dKargo
The layer optimized to meet the demands of logistics services, implemented on top of Arbitrum Layer2. This layer provides an environment that supports low network fees and fast processing speeds, facilitating a wide range of transactions.
2) Layer2 - Arbitrum
Designed to address the scalability issues of Layer1, this layer processes and compresses transactions submitted from Layer3, as well as other transactions occurring within Layer2, before submitting them to Layer1. This process significantly enhances speed and cost efficiency.
3) Layer1 - Ethereum
Composed of thousands of nodes worldwide, this layer provides a high level of security. It finalizes and verifies transactions submitted by Arbitrum Layer2, recording the data and state changes. This ensures the integrity and finality of all processed transactions.
The key to the efficiency of the dKargo network lies in the rollup process. The rollup process proceeds as follows:
1) Transaction Sequencing
The Sequencer receives transactions initiated by users, determines the processing order, and groups these transactions into Layer3 blocks, organized by time.
2) State Synchronization
The generated Layer3 blocks are propagated to all nodes within the network. Each node executes the transactions contained in the Layer3 blocks using the State Transition Function (STF), ensuring data synchronization across the entire network. Since the transactions are executed in a predetermined order through the same STF, all nodes maintain a consistent state.
3) Rollup Processing
1) Service Provider
The Service Provider collects transactions generated at Layer3 and transmits them to the Sequencer. Additionally, the Service Provider is responsible for continuous monitoring and management tasks to maintain network stability. Any participant in the dKargo ecosystem can become a Service Provider.
2) Sequencer
The Sequencer is responsible for grouping and compressing transactions generated at Layer3 and recording them onto the Layer2 blockchain. By optimizing the processing order of transactions and bundling them into a single data block, this process enhances efficiency by increasing processing speed and reducing fees. Currently, a single Sequencer is in operation for processing efficiency, but a Sequencer Coordination Manager is also in place to prevent service interruptions.
3) Relayer
The Relayer is a management node that monitors network status and balances loads to maintain an efficient flow of data. It collects transactions generated at Layer3 and forwards them to the Sequencer, while also distributing the generated block information to all nodes to ensure data synchronization across the network. The Relayer also serves as an entry point that facilitates user access and interaction with the blockchain network. The operation of this node is managed by dKargo.
4) Validator
The Validator is a node that monitors the dKargo network's state as recorded on Layer2, verifying the accuracy of the recorded data. If incorrect information is detected, the Validator initiates the dispute and fraud-proof process to determine and correct the error. Currently, Validators operate on a whitelist basis, with only approved users allowed to set up Validator nodes and participate in the validation process.
The Sequencer periodically batches the Layer3 blocks and performs the rollup process, recording these onto Arbitrum-One. This process involves storing the cumulative hash values of the transactions and the structured information of the Layer3 blocks (referred to as Rblocks) on Arbitrum-One.
