> For the complete documentation index, see [llms.txt](https://whitepaper.zbyte.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.zbyte.io/zbyte-dapp-store.md).

# zbyte dApp Store

The zbyte dApp store is a decentralized, one stop shop for developers to create, publish and monetize their dApps. While decentralized, the dApp store furnishes a clean and modern user interface akin to traditional app stores to ensure a good user experience. Accessed dApps can be operated by paying in $DPLAT, regardless of the blockchain protocol they are built on. Developers will have the ability to set usage fees, earning $DPLAT per transaction to support ongoing development and maintenance of applications.

Developers also have the ability to earn $DPLAT by encouraging their users to stake their tokens against their dApps. Staking rewards associated with a dApp will be divided between the staking user and the developer, ensuring that developers who garner the most support from their users are rewarded appropriately.&#x20;


---

# 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://whitepaper.zbyte.io/zbyte-dapp-store.md?ask=<question>&goal=<endgoal>
```

`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.
