# FAQ This FAQ covers the most common questions about staking in TMS — both from your team’s point of view and from what your community will ask. *** ### 1. What’s the difference between Compound and Liquidity pools? **Compound pools (single token)** * Users stake your **token**. * Rewards are auto-compounded into a vault. * Users’ share grows over time; they withdraw more tokens than they deposited (if they stay long enough). **Liquidity pools (LP staking)** * Users stake **LP tokens** from a DEX pair (e.g. TOKEN/USDT LP). * Rewards are paid for providing liquidity, not just holding the token. Use **Compound** to reward long-term holders.\ Use **Liquidity** to reward liquidity providers and deepen trading pairs. *** ### 2. Who can create and manage staking pools? * **Admins** * Own the contracts and have ultimate control. * Can perform high-privilege actions (like withdrawing leftover rewards if the design allows). * **Managers** * Handle day-to-day operations: * Create pools (within allowed parameters). * Adjust APR/APY, end dates, caps (when editable). * Monitor TVL and rewards. Admins should be high-security wallets (ideally multisig).\ Managers are for operational work. *** ### 3. Do users give up custody of their tokens when staking? Users **keep control of their tokens**, but: * When they stake, tokens are locked in the staking contract until: * The **lock period** ends, and * They actively withdraw. TMS never has access to private keys.\ Users always sign staking and withdrawal transactions from their own wallet. *** ### 4. How are rewards calculated? At a high level: * You configure **APR/APY** and pool duration. * The contract calculates a **reward rate** over time. * Each user’s rewards are based on: * Their share of total staked value (TVL). * How long they stay in the pool. * Any boosts (e.g. NFT boost). In compound pools, rewards are periodically **reinvested** into the pool, increasing everyone’s share.\ In LP pools, rewards are paid based on LP stake and time. For a deeper explanation, see:\ **How staking rewards work** *** ### 5. Can we change APR/APY after launch? Usually yes, but with care: * **Increasing APR/APY** * Can attract more TVL. * Increases how quickly rewards are distributed (you may need more rewards). * **Decreasing APR/APY** * Slows down reward distribution. * Should be communicated clearly to avoid surprise. Changing APR/APY affects **future accrual**, not past rewards already earned. *** ### 6. What happens when a pool expires? When a pool reaches its **end/expiration date**: * No new stakes are accepted. * Users can still **withdraw** their stake (subject to lock period). * Reward accrual usually stops at the configured end time. From your side: * The pool shows as **Ended/Expired** in the admin. * You can keep it visible so users who haven’t withdrawn can still do so. * If you want to continue, you typically create a **new pool** (“Season 2”) with new parameters. *** ### 7. Can users withdraw before the lock period ends? In standard TMS pools: **no**. * The **lock period** is a hard rule. * Users must wait until the lock finishes before withdrawing their stake. If you set a 0 lock period (where allowed), you effectively give users flexible staking — but that’s a design choice you should make explicitly. *** ### 8. Why can’t users see a particular pool? Check: 1. **Status** * Is the pool **Active** or **Upcoming**? * If the start date is in the future, it may not show as open yet. 2. **Visibility (if available)** * Make sure the pool isn’t hidden in your admin settings. 3. **Network** * Users must be connected to the correct EVM network in their wallet. 4. **Domain/URL** * Confirm they’re using your official staking URL (not a testnet/staging link). If all that is fine and the pool still doesn’t show, verify that it was **successfully deployed** (and not just saved as a draft in the admin). *** ### 9. Why are users getting failed transactions or errors? Most common causes: * **Rewards underfunded / depleted** * The pool doesn’t have enough reward tokens. * Claim or reward-related operations may revert. * **Pool expired** * New stakes are blocked; users may only be able to withdraw. * **Lock period not over** * Users trying to withdraw before lock ends will fail. * **Wrong network / token** * Users must be on the right chain and have the right asset (token or LP) in their wallet. Check the pool’s **reward status**, **dates**, and **lock settings** in the admin panel. *** ### 10. What fees do users pay when they stake or claim? Users pay two things on each onchain action (stake, claim, withdraw): 1. **Network gas fee** * Paid to the blockchain (e.g. ETH, BNB). * Standard Web3 behavior. 2. **TMS protocol fee** * A small fee in the same native token, included in the transaction. * Goes to Decubate/TMS to fund the infrastructure. * Applied on claim and relevant staking interactions. You as a project typically **do not** pay a platform % fee on flows.\ For more details, see **Pricing**. *** ### 11. How does staking interact with vesting? Simple rule: * **Vesting** controls **when users receive tokens**. * **Staking** controls **what they can earn with those tokens** once they have them. Typical flow: 1. User gets tokens via **vesting claim**. 2. They decide to **stake** some or all of those tokens in your staking portal. 3. They earn additional rewards over time. Staking doesn’t change vesting schedules.\ Vesting doesn’t automatically stake tokens — users must opt-in. *** ### 12. Should we test staking on testnet first? Yes, strongly recommended — especially for: * Your first staking pool. * Any pool with advanced features (NFT boosts, management fee, compound bounty). On testnet, you can: * Create a pool mirroring your planned mainnet config. * Stake test tokens / LP. * Check rewards, lock behavior, and UI. * Practice withdrawing and ending pools. Once everything behaves as expected, you can safely reproduce the setup on mainnet. *** ### 13. How many pools should we run at once? You *can* run many pools at once, but: * Too many pools can fragment TVL and confuse users. * A good starting point is: * 1–2 **compound** pools (e.g. short lock, long lock). * 1–2 **LP** pools for your main trading pairs. As you see what your community likes, you can iterate.\ Always keep pool names and descriptions clear so users understand the differences quickly. --- # 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/faq.md?ask= ``` 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.