> For the complete documentation index, see [llms.txt](https://docs.florence.finance/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.florence.finance/docs/duke-dash/duke-dash-incentives.md).
# Duke Dash Incentives
Florence Finance, a pioneer in the RWA sector, is excited to launch Duke Dash, a creative campaign that combines Duke NFTs with a tiered reward system, reflecting a user's engagement and dedication within our community.
Earn Points & Level Up 🆙
Duke Dash invites every user to begin their noble journey by minting a Duke NFT, marking their entry into a realm of engagement, achievement, and rewards. As participants delve into various platform activities, they ascend up the leaderboard proving their level of nobility.
Starting as a Squire, your journey in the Duke Dash will be filled with opportunities to earn points and rise through the ranks:
* **Squire:** Every participant’s beginning rank.
* **Count**: Progress to this rank by being in the bottom 50% of point earners.
* **Earl**: Reach higher by breaking into the top 50%-20% on the leaderboard.
* **Knight**: Earn this prestigious rank by collecting 10 badges through active community participation.
* **Archduke**: The pinnacle of Duke Dash, reserved for the top echelon of point earners.
---
# 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.florence.finance/docs/duke-dash/duke-dash-incentives.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.