> For the complete documentation index, see [llms.txt](https://doc.auditx.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.auditx.net/auditx-ecosystem/services/dapp-auditing/introduction-to-dapp-security.md).

# Introduction to DApp Security

Decentralized Applications, or **DApps**, are applications that run on a blockchain network rather than a centralized server. They often include smart contracts on the back end and an accessible front end for users. Because DApps interact with valuable assets and user data, **DApp security** is critical to protect both the application and its users from potential risks.

* **Why is DApp Security Critical?**
  * DApps are often open-source, meaning anyone can inspect their code. While this promotes transparency, it also allows attackers to study the code for vulnerabilities.
  * DApps have both a **front end** (the user interface) and a **back end** (often a smart contract on a blockchain). This dual nature introduces unique security challenges that traditional apps don’t face, such as needing to protect both the blockchain-based logic and the user-facing interface.
  * Since DApps handle digital assets, a security breach could lead to financial losses for users and damage to the project’s reputation.


---

# 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.auditx.net/auditx-ecosystem/services/dapp-auditing/introduction-to-dapp-security.md?ask=<question>&goal=<user_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.