> For the complete documentation index, see [llms.txt](https://doc.layerswallet.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.layerswallet.fun/overview/introduction.md). # Introduction To introduce Layers, explain what it does, and set the tone for the project documentation. Layers is an innovative wallet-generation platform built on the Solana blockchain. It allows users to create custom wallet addresses with personalized prefixes and suffixes — giving users the ability to make their wallets recognizable, brandable, and expressive. Most blockchain wallets today are long, impersonal strings of random characters. Layers addresses this issue by bringing personalization and identity to wallet addresses without compromising security. With Layers, users can create addresses that reflect their personal or community brand, making transactions easier to identify, share, and remember. This documentation serves as a guide for understanding how Layers works, how to use it, and how to integrate it into applications. It is designed for developers, users, and partners interested in building or engaging with on-chain identity tools within the Solana ecosystem. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://doc.layerswallet.fun/overview/introduction.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 `build a script that syncs our docs to a CMS` 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.