> For the complete documentation index, see [llms.txt](https://securedapp.gitbook.io/securedapp-launchpad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://securedapp.gitbook.io/securedapp-launchpad/secure-token-staking.md).

# Secure Token Staking

Use SecureDApp staking to reward your holders or for governance of your DAO.

**STEP BY STEP GUIDE TO SET UP STAKING**

1\. Click on “Stake” and then “Create Stake” or go to this link: ---

2\. Enter in the address of the token you want people to stake (this is usually your token) and enter in the address of the token you want to reward people with (This can be your token or any token but you need to supply this token for the rewards)

3\. Enter in the name of the Staked tokens (Check below to learn more about this) and the Staked symbol

4\. Choose the reward type, there are four options:

·         Percent Reward

·         Fixed Reward

·         No Reward

5\. If you chose Percent or Fixed Reward you then must choose your Reward Ratio

6\. Make sure the switch is green if you want your stakers to be able to claim anytime or if not select the date you want your stakers to be able to claim by.

7\. Next you must set the hard cap; this is the amount you want to cap the total staked at. If you want no cap set the total to more than the total supply.

8\. The min limit to stake is the minimum you require of your holders to stake, if you do not want a minimum, you can set it to 0.

9\. You next must choose if you want the Staking Token to be transferrable or not and if there is min period to stake before they are allowed to be transferred to another wallet.

10\. Pick the start and the end date for your pool.

11\. Fill out your staking pool information, including socials and the description.

12\. Check your pool and then hit complete

**STAKED TOKENS**: This is the token held by the wallets that are staking the token, SecureDApp uses it so it doesn’t matter if you’re staking or not to be eligible for tiers. You may also use this token to get make it so only those who stake are eligible for tiers or whatever suits your project.

**PERCENT REWARD**: This reward depends on the amount you stake. E.g If the reward ratio is set to 10 and your holder stakes 100 tokens, they will earn 1,000 of the reward tokens per year.

**FIXED REWARD**: This means the reward amount is fixed. E.g If the reward ratio is set to 10,000, the total amount staked is 1,000 and your holder stakes 100 tokens, they will earn 4,000 of the reward tokens per year.

**NO REWARD**: There is no reward for staking, instead it can be used as a GOV token for a DAO once staked

**COST OF STAKING**: **1BNB/0.2ETH/3500ALVEY/300MATIC listing and 2%** of deposited staking rewards


---

# 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://securedapp.gitbook.io/securedapp-launchpad/secure-token-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.
