> For the complete documentation index, see [llms.txt](https://docs.solhuger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solhuger.com/products-and-services/staking.md).

# Staking Platforms

Let your community lock or stake tokens to earn rewards.

## Features

| Feature           | Description                                           |
| ----------------- | ----------------------------------------------------- |
| Flexible pools    | Stake and withdraw at any time                        |
| Locked pools      | Fixed lock periods, usually with higher rewards       |
| Reward logic      | Fixed rate, emission-based or custom formulas         |
| Live APY tracking | Dashboard shows current APY and pool stats            |
| Admin controls    | Fund reward pools, adjust parameters per agreed rules |

## Chains

Solana, Ethereum, Base, BSC.

## Design decisions we help you make

* Where rewards come from (pre-funded pool vs emissions) and how long they last
* Lock durations and early-withdrawal rules
* Whether parameters can change after launch and who can change them

{% hint style="info" %}
Sustainable reward design matters more than headline APY. We will model the reward budget with you before development.
{% endhint %}

## Live example

[$TOR Staking](https://docs.solhuger.com/portfolio/portfolio/tor-staking.md) · [staking.solhuger.com](https://staking.solhuger.com)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solhuger.com/products-and-services/staking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
