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

# Abstract

<figure><img src="/files/fK1L3Z7eRIscSp9hpQOB" alt=""><figcaption></figcaption></figure>

Moongate is an attention asset protocol disrupting the $1Tn+ attention economy. The protocol consists of two key layers - a utility layer for any brands to issue smart tokens to drive real-world engagement; and a data layer for users to monetize their engagement data.&#x20;

Moongate protocol aims to disintermediate centralized platforms and maximize brand-consumer value. It also introduces an innovative “engage-to-earn” mechanism that promotes active consumer participation for brand rewards and a share of $MGT emission.

Moongate protocol consists of four key modules: Moongate Campaign, a no-code engine to issue smart tokens with real-world use cases (i.e. NFT tickets, memberships, phygital collectibles); MoonPass, a decentralized ID with rarity stamp and reputation score that accumulates rewards; Moongate Rewards, a marketplace for consumers to selectively and securely share data to brands for rewards; and MoonPad, a brand/memecoin token launchpad.


---

# 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://moongate.gitbook.io/moongate-litepaper/introduction/abstract.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.