# Staking in TMS

### What is the TMS Staking Portal?

The **Staking Portal** turns your token from “just a balance” into something users can **actively use and earn with**.

With TMS, you can:

* Launch **staking pools** for your token or LP tokens.
* Let users stake through a **branded, white-label portal** on your own domain.
* Distribute rewards automatically, without writing or maintaining your own staking contracts. [decubate.com](https://www.decubate.com/staking?utm_source=chatgpt.com)

The result:

* More **utility** for your token.
* Stronger **loyalty** from your holders.
* Better **liquidity** when you use LP staking.

All while TMS handles the infrastructure, security, and onchain logic under the hood.

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

***

### Why use staking?

Staking is a core building block of a healthy token economy:

* **Incentivize holding**\
  Reward users who commit to your ecosystem instead of selling immediately.
* **Support liquidity**\
  With LP staking, you reward users who provide liquidity to your main trading pairs, helping tighten spreads and improve depth on DEXs.
* **Structure your incentives**\
  Run clear, rules-based programs instead of random giveaways and ad-hoc airdrops.
* **Align behavior with your roadmap**\
  Use lock periods and tailored rewards to encourage long-term participation, not short-term speculation.

Because staking is integrated into TMS, it fits cleanly with your **vesting, locks, and analytics**, rather than serving as yet another separate product.

***

### Supported pool types in TMS

TMS supports two staking pool types (no Dynamic pools in TMS):

#### 1. Compound staking pools (single token)

* Users stake your **token**.
* Rewards are **auto-compounded** into a vault, increasing everyone’s staked balance over time.&#x20;
* A **compound bounty** can incentivize users to trigger harvest events that reinvest rewards for everyone.&#x20;

Use compound pools when:

* You want a **simple “stake & grow” experience**.
* You want to maximize returns through auto-compounding rather than forcing users to restake manually.

***

#### 2. Liquidity pools (LP staking)

* Users stake **LP tokens** from a DEX (e.g. TOKEN/ETH LP).
* Rewards are paid based on:
  * How many LP tokens they stake.
  * How long they stay in the pool.&#x20;
* Lock periods can be used to keep liquidity sticky.

Use LP pools when:

* You want to **bootstrap or deepen liquidity** in specific pairs.
* You want to reward users for taking on LP risk, not just holding the token.

***

### Advanced features (available in TMS)

On top of basic rewards, TMS staking supports several advanced features:

* **NFT boost**\
  Users who hold eligible NFTs in their wallet can receive **multiplied rewards** in supported pools.&#x20;
* **Compound bounty**\
  For compound pools, a small part of the harvested rewards can be given as a **bounty** to whoever triggers the harvest, with the rest automatically reinvested.
* **Management fee**\
  A configurable fee (where enabled) that allows projects or partners to take a share of rewards as protocol or management revenue.

These features are optional and can be configured on a **per-pool** basis. They’re ideal for more sophisticated tokenomics and partner programs.

***

### How staking fits into your token lifecycle

Staking works best as part of a **broader system**, not as an isolated gimmick.

#### Before or around TGE

* Announce upcoming staking programs to create **structured demand**.
* Configure pools (compound and/or LP) aligned with your launch narrative.
* Ensure your **vesting** and **locks** are in place so staking doesn’t conflict with unlocks.

#### After TGE

Use staking to:

* Reward long-term holders while vesting unlocks roll out.
* Stabilize liquidity via LP pools.
* Run seasonal or campaign-based pools around key milestones.

#### Long-term

Over time, staking becomes:

* A permanent **utility layer** for your token.
* A way to **change incentives over time** (by adjusting APRs or creating new pools) without redeploying custom contracts every launch.

***

### Roles & control (Admins vs Managers)

In TMS:

* **Admins**
  * Own the underlying staking infrastructure.
  * Typically control high-privilege actions (like withdrawing leftover rewards, where applicable).
  * Can add/remove Admins and Managers.
* **Managers**
  * Handle **day-to-day pool operations**:
    * Create, edit, and monitor staking pools (within allowed parameters).
    * Configure NFT boosts, management fees, and rewards settings (as permitted by your setup).

The exact UI may show some actions as Admin-only, but conceptually:

* **Admins** = ownership & safety.
* **Managers** = operations & campaigns.

***

### What your users see

From a user’s perspective, staking is simple:

1. They visit your staking portal at a URL like `https://staking.yourproject.com`.
2. They see one or more pools with:
   * Token or LP pair.
   * APR/APY.
   * Lock period and end date.
3. They connect their wallet and choose:
   * How much to stake.
   * Which pool(s) to join.
4. They can:
   * View staked balance and rewards.
   * Claim rewards (and in compound pools, effectively withdraw from an auto-compounding vault).

Your brand, your domain, your token — TMS is just the infrastructure making it work.

***

### Where to go next

If you’re new to staking in TMS, read these next:

* **How staking rewards work**\
  Understand how rewards are calculated for compound and LP pools, and how lock periods & expiration dates behave.

Then:

* **Create a staking pool** – Step-by-step setup for compound and LP pools.
* **Manage staking pools** – How to adjust APR, extend a pool, or close it gracefully.
* **Staking portal customization** – How to make your pools look and feel on-brand.

***


---

# Agent Instructions: 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:

```
GET https://tms-finance.gitbook.io/tms.finance/staking-farms/staking-in-tms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.