> For the complete documentation index, see [llms.txt](https://thxnet.gitbook.io/thxnet-developers-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thxnet.gitbook.io/thxnet-developers-doc/welcome.md). # Welcome Welcome to the THXNET. Developers' Documentation. This serves as a cornerstone for THXNET. developer users and the dedicated project teams of Layer-1 Leafchain. Our goal is to ensure that you have all the information and resources you need to thrive in our ecosystem. ### Concept Dive deep into the core principles underpinning our platform. Explore the concepts behind Web3-as-a-Service, the design rationale of the THXNET. ecosystem, and the innovations that drive our ID-Wallet. ### Workshop / Tutorials Experience is the best teacher, and hands-on learning often offers the clearest path to understanding. Within this section, we provide a series of tutorials that guide you through constructing demo use cases. These span both web front-end and back-end scope, facilitating the process for developers to create ID-Wallets and utilize the applications in THXNET. ecosystem. ### Reference The API docs and operation details for THXNET. APIs and blockchain networks. --- # 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://thxnet.gitbook.io/thxnet-developers-doc/welcome.md?ask=&goal= ``` `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.