> 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-en/getting-started/light-staking.md).

# Light Staking

In the classic staking method, when an NFT is staked, the relevant NFT is transferred directly from its owner to the contract. This method prevents the same NFT from being reused repeatedly with different accounts and prevents manipulation.

In light staking, users do not have to put their NFTs directly at risk. Instead, they only report ownership information about the NFT they own to the contract. With this notification, the relevant NFT becomes un-signable by other accounts for 24 hours. When the period expires, if the user is still the owner of that NFT, they can claim their entitled rights.

For accounts that own multiple NFTs, listing the ownership information of all NFTs in the contract and checking them with loops can cause problems in terms of both security and gas costs. For this reason, the system was deliberately kept simple in the first version and designed to operate only on a single NFT.


---

# 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-en/getting-started/light-staking.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.