> For the complete documentation index, see [llms.txt](https://wp.gotmlabz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.gotmlabz.io/nft-staking/features/trait-bonuses.md).

# Trait Bonuses

### Reward additonal token based upon specific traits within your collection. Change/add at any time.

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

### **Combo Trait Bonus**

Daily reward if user has a combination of traits on one NFT\
Ability to add generic image and name for UI display front end<br>

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

### **Collective Trait Bonus**

In the below example if the user has 3 nfts each with a different crown, then 10 tokens would be applied to each one per day. ( Set )\
Ability to add generic image and name for UI display front end

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

### New Trait Bonus's

When NFTs are staked a snapshot is taken of the metadata and earnings are based off that. If a user gets a new trait that should be getting a bonus, user can simply claim from that specific NFT which will then take a new snapshot of the NFT and refresh all earnings.


---

# 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://wp.gotmlabz.io/nft-staking/features/trait-bonuses.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.