# 1. LMTLS Network

The LMTLS network consists of a public blockchain network, an automated node network that autonomously executes scenarios for earning through actions, and an API gateway connecting these networks to external blockchain networks and internet services.

**Hierarchical Blockchain Network**

In the continuously evolving environment of public blockchains and emerging technologies, there are inherent limitations to implementing the vision of LMTLS's Web2 and Web3 digital marketing platform solely with public blockchains. To address this challenge, the LMTLS blockchain network adopts a layered approach. 

The Layer 1 blockchain serves as the hub for the LMTLS token economy, handling crucial transactions that significantly influence the LMTLS platform, such as DAPPs and sizable LMTLS token transactions. On the other hand, the limited performance and high gas costs of Layer 1 made it challenging to process a large volume of transactions in a short timeframe. To overcome this, LMTLS introduces the Layer 2 blockchain network. Layer 2 efficiently processes rewards for LMTLS user activities, events with a large volume of transactions involving many LMTLS users in a short period, and high-volume transactions originating from digital marketing campaigns.

Through this hierarchical approach, the LMTLS platform overcomes the constraints of public blockchains, ensuring optimal performance, scalability, and cost efficiency for its Web2 and Web3 digital marketing ecosystem.<br>


---

# Agent Instructions: 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:

```
GET https://docs.lmtls.io/lmtls-project/lmtls-platform/1.-lmtls-network.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.