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

# Mecanismo de oferta

<div data-full-width="false"><figure><img src="/files/dfb4891756792fa2ec1af5ca21673b7872ea86d7" alt=""><figcaption></figcaption></figure></div>

Cada propietario de NFT, una vez al día, al presionar el botón “daily sign”, determina en cuántas partes se dividirán las recompensas acumuladas en el fondo ese día. De este modo, el sistema funciona con la aprobación diaria de los participantes.

Cada NFT solo puede recibir una recompensa por día.

Si una cuenta posee más de un NFT, no puede realizar la operación daily sign; solo las cuentas con un único NFT pueden firmar.

La razón principal de esto es incentivar la distribución de los NFT en diferentes carteras. Así aumenta la proporción de unique owner (propiedad única) y se reduce el riesgo de centralización del sistema.


---

# 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://vrnouns.gitbook.io/flooor/documentation/documentation-es/comenzando/whatsflooordotfun.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.
