> For the complete documentation index, see [llms.txt](https://fabco.gitbook.io/dappy-spec/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fabco.gitbook.io/dappy-spec/glossary/dapp.md). # Dapp ![Dapp](https://dappy.tech/images/dapp.png) Dapps go one step further into decentralization than IP applications. A dapp in the Dappy ecosystem refers to a web application or website that is distributed by the Dappy network. Dapps must therefore have all or part of the assets stored on the blockchain platform the Dappy network is connected to. When a user searches "cooldapp" it is resolved to a blockchain address instead of an IP address, and the same network that was asked to resolve the name, will be queried to load the HTML documents and eventually the other files. **Dapps are not distributed by a unique server connected to the internet, or a centralized web hosting service (like AWS or Digital Ocean), but by a decentralized network of agents that are legally and technically independent one with another.** The availability and accuracy that can be achieved with dapps are higher than that of a centralized website because distinct legal and technical entities are co-responsible for its distribution. A typical implementation of the Dappy protocol would tolerate a small fraction of these agents to go offline or even to be hacked (= serving a fake/malicious version of the code). [Dappy CLI ](https://github.com/fabcotech/dappy-cli)is the npm package use to help you put HTML documents or dapps on the blockchain before loading them in dappy --- # 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://fabco.gitbook.io/dappy-spec/glossary/dapp.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.