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

# NeoStake

\
NeoStake is a decentralized staking platform designed to reward users for locking up Neotech tokens in flexible, independent staking pools. Each pool offers a unique staking duration, token cap, and reward allocation, providing a dynamic and engaging staking experience. The platform incentivizes long-term participation by redistributing rewards among remaining stakers when others withdraw early, potentially amplifying returns for committed users.Core MechanicsBase APY Structure\
NeoStake uses a dynamic APY model, where each staking pool has its own reward rate based on the allocated reward tokens and duration. For our initial deployment:

* Duration: 90 days (3 months).
* Base APY: 50% over 90 days (equivalent to 12.5% quarterly yield).
* Token Cap: 2,500,000 Neotech tokens.
* Reward Pool: 312,500 Neotech tokens, distributed to stakers at the end of the period.\
  Future pools may vary in APY, duration, and cap, offering diverse opportunities (e.g., 1-month pools at 10% APY or 12-month pools at higher rates).

Modular Pool System

* Independent Pools: Each pool operates as a separate smart contract with configurable parameters:
  * Duration: Options like 1, 3, 6, or 12 months.
  * Token Cap: Maximum tokens allowed (e.g., 2.5M for the current pool).
  * Reward Allocation: Fixed reward tokens (e.g., 312,500 for the current 90-day pool).
* Scalability: Multiple pools can run simultaneously (e.g., 3-month and 6-month pools), with no limit on the number of active pools. Special event pools may offer unique APYs or caps.

Capped Pools

* Each pool has a maximum staking cap (e.g., 2,500,000 tokens for the current pool).
* Entry Window: Users have 7 days to stake before the pool locks. If the cap isn’t reached (e.g., only 2,000,000 tokens staked), the pool closes at that amount and begins the staking period.
* Example: If 1,800,000 tokens are staked in 7 days, the pool locks at 1,800,000, and the 90-day countdown starts.

Dynamic Reward Distribution

* Fixed Reward Pool: A predetermined number of tokens is allocated per pool (e.g., 312,500 tokens for the current 2.5M-token pool).
* Withdrawal Impact: Users can unstake penalty-free before the period ends but forfeit rewards. The fixed reward pool is then split among remaining stakers, increasing their effective APY.
* Example:
  * Pool cap: 2,500,000 tokens.
  * Reward: 312,500 tokens (12.5% over 90 days).
  * If 500,000 tokens are unstaked, the remaining 2,000,000 tokens split the 312,500, raising the effective APY to \~15.625% for those stakers.
* Extreme Case: If only 1 token remains staked, that user claims the entire 312,500-token reward!
* Incentive: This design rewards “diamond hands” who stay committed, creating a FOMO effect for early withdrawers.

Entry Window

* Pools have a 7-day window for staking.
* If the cap isn’t reached, the pool locks with the staked amount and starts. No further deposits are allowed, but withdrawals remain possible until the period ends.

Single Participation Rule

* Users can stake in only one instance of a pool type at a time (e.g., one 90-day pool).
* If you unstake, you can’t re-enter that pool but can join a new pool when it launches.
* Example: Unstake from “90-Day Pool #1,” then join “90-Day Pool #2” later.

Deployment Plan

* Initial Pool:
  * Duration: 90 days.
  * Token Cap: 2,500,000 Neotech tokens.
  * Reward Pool: 312,500 Neotech tokens (50% APY over 90 days).
* Future Pools: Additional pools with varying durations, caps, and APYs will be deployed based on community demand and platform growth.


---

# 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://neotechai.gitbook.io/neotechai/neostake.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.