# Overall In the field of traditional permissionless blockchain scaling, there has been the Blockchain Trilemma of decentralization, security and scalability that no current blockchain system can simultaneously achieve. LabX believes that the solution lies in the fact that the traditional blockchain has monolithic architecture, which means components are interconnected and interdependent. You couldn’t just take a piece of it and plug it into something else. To solve this problem, LabX adopts a modular architecture which is divided into three layers: Execution Layer, Settlement Layer and Data Availability Layer. • Execution Layer: responsible for the execution of almost all contract-based transactions and supports decentralized applications. It is the combination of ZK Rollup and Collaborative Rollup, where the execution results are submitted to the settlement layer and the settlement layer establishes undeniable security as well as objective finality. • Settlement layer: responsible for verifying and settling the execution results of the execution layer and is also the asset layer, responsible for the management and settlement of the assets on the chain. • Data availability layer: focusing on data storage, it will store permanently high-value data based on data sharding, and with data availability sampling technologies it can support reliable verification for light clients. In addition, relying on our Time Crossing cross-chain protocol, LabX can also implement multi-chain topology to meet the demand for application chains. --- # 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://labxdocs.gitbook.io/labx.protocol.io/labx-introductions/labx-designed/overall.md?ask= ``` 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.