> For the complete documentation index, see [llms.txt](https://docs.nemus.earth/nemus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nemus.earth/nemus-docs/nemus-litepaper/the-nemus-nft/sponsor-nft.md).

# Sponsor NFT

For each drop, the single largest NFT is reserved for the sponsor of the drop. In the [Genesis Drop](/nemus-docs/nemus-drops/drop-one-the-genesis-drop.md), this NFT is 324 hectares (800 acres) in size. In order to secure the sponsor NFT, a sponsor is required to seed the rewards pool with NEA tokens that are then distributed to Guardians over time.

Below are three important motivations for a sponsor to participate in a drop.

#### Exposure

The sponsor’s purchase of NEA signals to thousands of Guardians their desire to make Nemus a success. Each Guardian will be reminded of their motive each time they receive their rewards. Brand exposure will also be integrated into the app experience.

**Alignment**

Sponsorship makes a strong statement on the organization’s environmental stance, by empowering a community aligned with securing and conserving forest lands.

#### **Carbon Offsetting**

While it is not the main focus, the sponsor may be able claim a carbon offset for their sponsor area, directly benefiting from the value of carbon sequestration on the land.


---

# 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.nemus.earth/nemus-docs/nemus-litepaper/the-nemus-nft/sponsor-nft.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.