> For the complete documentation index, see [llms.txt](https://whitepaper.dkargo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.dkargo.io/v2.1-eng/introduction/dkargo2.0.md).

# dKargo 2.0

<figure><img src="/files/evXT5CkBbQPquYvWlbaK" alt=""><figcaption></figcaption></figure>

## Transitioning to a New Environment

<figure><img src="/files/GBZM5S3p37h17AwcBM4x" alt=""><figcaption></figcaption></figure>

Since 2019, dKargo has introduced various Web3 logistics services to address inefficiencies in the logistics sector. Leveraging blockchain’s transparency, dKargo has worked to resolve trust challenges within the logistics chain while also integrating Web2 users through intuitive interfaces and a streamlined onboarding process.

However, after gathering feedback and closely observing the network environment over the past  three years, dKargo identified the need for an infrastructure that can support complex and diverse logistics services more efficiently and reliably.

In response, dKargo is transitioning to a Layer3 blockchain platform by building its own network. This newly developed blockchain platform will provide the technical foundation required to deliver smooth services, ensuring a positive on-chain experience. With this transition, dKargo aims to welcome more participants and collaborative partners into the ecosystem, ultimately enhancing logistics industry efficiency.

## dKargo 1.0 vs dKargo 2.0

Due to the nature of blockchain technology, Web3 services often face structural limitations such as slow processing speeds and high network fees in order to maintain decentralization and security. The dKargo network overcomes these limitations by separating execution into Layer3 and consensus into Layer1, thereby providing enhanced usability. The dKargo network offers a faster, more cost-effective, and stable environment, enabling the smooth operation of logistics services.

<figure><img src="/files/sKIPWqz9NG8jcbeKz2zK" alt=""><figcaption></figcaption></figure>

## Suitability for Logistics

Logistics data is generated in real-time and is continuously updated, resulting in high-frequency data occurrences. Unlike batch data, logistics data is sourced from various points, including RFID tags, GPS data, and Warehouse Management Systems (WMS), making the data structure complex and requiring the handling of diverse data formats. The dKargo network, through its Layer 3 architecture, provides the high transaction throughput, fast processing speeds, and low fees necessary to handle large volumes of logistics data. This structure efficiently supports the real-time management and exchange of logistics data. Additionally, the dKargo network is tailored to the logistics industry, optimizing data management and facilitating smooth logistics operations in ways that general-purpose networks cannot.\
\
\&#xNAN;*Last updated on **Apr 2, 2025***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.dkargo.io/v2.1-eng/introduction/dkargo2.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
