> For the complete documentation index, see [llms.txt](https://docs.muon.net/muon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.muon.net/muon-protocol/what-is-muon/elevator-pitch.md).
# Elevator Pitch
Since the inception of Ethereum, which enabled dApp development, validating off-chain data has remained a persistent challenge, affecting scalability, interoperability, and security. The main cause of this challenge is a missing component in the general architecture of dApps.
In Web2, projects typically consist of three components: Frontend, backend and database. Frontend is the user interface, the backend processes frontend requests and handles application logic while the database stores data and implements part of the logic through stored procedures.
In the Web3 development stack, smart contracts function as a combination of the database and stored procedures. However, the backend layer β which processes and validates data before pushing it to the blockchain β is missing.
βTo address this architectural challenge, we spent the last few years building Muon, **a request-based, general-purpose validation layer** that serves as a backend for web3 apps, allowing them to pre-process and validate any data before pushing it on-chain. In simple words, Muon takes over processing complex operations that are either not possible or not viable to perform through smart contracts. By doing so, it removes dApp limitations and greatly expands their use-cases.
To ensure security, Muon has designed a [tri-layer security stack](/muon-protocol/muon-protocol/modular-security-stack.md) that includes different validators. See Muon Security Stack for details.
---
# 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://docs.muon.net/muon-protocol/what-is-muon/elevator-pitch.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.