# Roadmap

## Q1 2026

* [ ] Liquidity deposit: 1% $STB rule refactor (fixed at 5 $STB per USD)
* [ ] CLMM token account cost improvement release
* [ ] Display pool volume/TVL in pool list and charts
* [ ] Introduction of “stabble community-managed pool” tags
* [ ] Enabling “like” function (heart) for favourite pools and filter function
* [ ] Research: Automatic narrow CLMM range which adjusts with the price, e.g., +-2%; +-5%; +-10%
* [ ] Staking mechanism DAO vote ($STB vs $SOL rewards)

## Q2 2026

* [ ] Money market protocol release (as base for leverage and margin liquidity)
* [ ] Leveraged CLMM positions between 1x to 5x (margin liquidity)
* [ ] CLMM limit orders with optional 1x to 5x leverage
* [ ] Ice block orders (partly sales of a CLMM position, e.g., sell $SOL between $140 and $160 without reverting)
* [ ] Introduction of dynamic (volatility-based) and asymmetric (inventory-based) CLMM fees
* [ ] Enable CLMM fee collection in one token
* [ ] Transparent $STB dashboard (unlock rates, staking rates, volume, price)
* [ ] New staking mechanism (fees will be fully automatically converted to staking assets and distributed)

## Q3 - Q4 2026

* [ ] Money market and CLMM idle capital management (capital efficiency improvements: reallocation, rebalancing, deleveraging, internal matching)
* [ ] Smart liquidity routing (SLR): Protocol-managed liquidity and SLR portfolio management&#x20;

## Q4 2026 - 2027

* [ ] CLMM copy & paste LPing function (similar to copytrading)


---

# 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://docs.stabble.org/appendix/roadmap.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.
