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

# autoFLUX

autoFLUX is an **in-wallet DeFi automation tool** designed to **streamline daily and weekly transactions**. It enables users to **automate claiming, reinvesting, and managing yield**, optimizing idle funds by leveraging the **Cosmos authz module** for secure execution.

***

#### **Unlocking Liquidity & Yield Optimization**

A significant portion of funds in the **Fluxtra ecosystem** is locked in **staking rewards, vested tokens, or liquidity incentives**. autoFLUX allows users to **automate transactions** and ensure these assets are **efficiently reinvested, compounded, or converted** to maximize yield.

***

## **Automating DeFi Transactions**

**Yield Sources**

Users can automate transactions from the following sources:

* **Staking Rewards** – Automatically claim and reinvest **staking rewards** from **vested tokens**.
* **Liquidity Incentives** – Claim **LP rewards** from **DEX pools** and reinvest them for compounding.
* **Wallet Balances** – Automate deposits, **DCA (Dollar-Cost Averaging), and transfers** based on customizable thresholds.
  * Example: **Unbond vested tokens** and **auto-deposit them** into a DeFi protocol.
  * Example: **Auto-transfer excess wallet balances** into a savings strategy.
  * Example: **DCA into DeFi investments**, ensuring gradual exposure over time.

Users can suggest additional **yield sources** through the **Fluxtra community**.

***

**Yield Destinations**

Users can define where their **automated yield** is allocated:

* **Amplifier** – Automatically stake rewards into **Fluxtra’s liquid staking derivative (ftOM)**.
* **Compounder** – Auto-deposit yield into **high-yield liquidity pools**, benefiting from **daily compounding**.
* **Token Swaps** – Convert yield into a **specific supported token**, allowing users to **rebalance portfolios** or **cash out profits**.

Additional destinations can be proposed and integrated based on community demand.

***

#### **Scheduling & Execution**

* Users **set an execution interval** (e.g., daily, weekly) for **automated transactions**.
* Execution is **gas-efficient**, meaning **operators will only process transactions** if the reward covers gas fees.
* Users can **manually trigger executions** outside of the scheduled timeframe if needed.

***

## **Example Strategies with autoFLUX**

1. **Token Auto-Staking** – Claim **vesting token rewards** and **auto-stake** them into **ftOM**.
2. **Token Yield Extraction** – Claim **staking rewards** and convert them into **stablecoins**.
3. **Auto-LP Compounding** – Claim **LP incentives** and **auto-compound** them into liquidity pools.
4. **Profit Extraction** – Claim **DEX rewards** and swap them into **stablecoins or other assets**.

***

## **Fee Structure**

Fees are based on the **compounded value** from the automation source:

* **Operator Fee**: **1%**
* **Protocol Fee**:
  * **1% to ftOM holders**
  * **1% to Protocol Treasury**

autoFLUX **removes the need for manual management**, making **staking, compounding, and yield optimization fully automated** while ensuring users remain in control of their assets. 🚀


---

# 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://fluxtra-lsd.gitbook.io/fluxtra-lsd-docs/autoflux.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.