> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/about-xyo/xyo-101/xyo-layer-one.md). # XYO Layer One Welcome to the next step in your journey through the XYO ecosystem. This section dives deeper into how XYO works under the hood — why the system was designed the way it is, and what makes it sustainable, scalable, and ready for real-world data. ### Why Did We Make XYOL1? In this page, you'll learn about the biggest issue facing large data-driven companies today: Blockchain Bloat. This problem affects industries like artificial intelligence (AI), real-world assets (RWA), and DePINs, like ourselves. The short version? Most blockchains slow down as they grow. Here, you’ll get to see why that happens and how XYO Layer One takes a data-focused approach to avoid it. ### How XYO Layer One Tackles Blockchain Bloat Instead of requiring every node to store the entire blockchain, XYO Layer One uses innovations like Lookback Windows and sovereign chains. You’ll explore how its “Chain of Chains” architecture enables fast syncing, minimal bloat, and real scalability. ### How XYO Layer One Impacts Big Industries XYO Layer One gives industries a blockchain that can actually handle their data. From AI models that need trusted inputs to DePINs like XYO that connect millions of nodes, XYO Layer One makes large-scale data usable without slowing down. XYO solves blockchain bloat by adding features like roll-ups, sovereign chains, and permanent storage. With these, it creates a foundation for logistics, healthcare, insurance, gaming, and more to build systems that stay fast and reliable as they grow. ### Two Tokens, One Ecosystem The XYO Token supports the broader DePIN economy, while the XL1 Token powers on-chain activity within XYO Layer One. You’ll see how this dual-token model separates concerns, increases performance, and creates value for both users and developers. Let’s dig in! --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xyo.network/about-xyo/xyo-101/xyo-layer-one.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.