> For the complete documentation index, see [llms.txt](https://docs.roguetrading.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roguetrading.io/tokenomics-unabridged/reward-floors-and-stability.md).

# 📘 Reward Floors & Stability

*The system that ensures predictable minimum rewards for nodes and stakers — without compromising long-term token sustainability.*

Rogue AI uses several mechanisms to stabilize rewards during low-revenue periods:

* **Node ROI Floors**
* **Staking APR Floors**
* **Micro-Emission Engine (capped)**
* **Automatic Floor Shutdown Logic**

These systems prevent rewards from collapsing and protect participants through all market conditions.

***

## **11.1 The Purpose of Reward Floors**

Reward floors ensure:

#### ✔ Minimum guaranteed yield

#### ✔ Stable, predictable ROI

#### ✔ Strong network participation

#### ✔ No collapse during bad months

#### ✔ No panic sells or mass unstaking

#### ✔ Long-term ecosystem health

Node operators and stakers receive protection even during revenue dips.

***

## **11.2 Node ROI Floor (Minimum Guaranteed Node Reward)**

Nodes earn a minimum reward even when monthly revenue is low.

#### **Node ROI Floor Formula**

```
NODE_ROI_FLOOR (monthly) = max(NodeRevenuePayout, NodeValue × 0.008)
```

This guarantees:

* 0.8% monthly minimum ROI
* \~9.6% annual minimum ROI

Nodes always receive premium yield.

#### Why this matters:

* Node infrastructure is mission-critical
* High capital cost requires stable returns
* Encourages long-term participation

***

### **Node ROI Floor Diagram**

```
Revenue Check
     │
     ▼
┌─────────────────────┐
│ Node Payout ≥ Floor│───► Yes → Use Revenue
└──────────┬──────────┘
           │ No
           ▼
┌───────────────────────┐
│ Issue Micro-Emission  │
│ Within Monthly Cap    │
└───────────────────────┘
```

***

## **11.3 Staking APR Floor (Minimum Guaranteed Staking Yield)**

Staking also receives a minimum APR to ensure holders always receive meaningful yield.

#### **Staking APR Floor Formula**

```
STAKING_APR_FLOOR (monthly)
 = max(StakingRevenuePayout, StakedValue × 0.005)
```

This guarantees:

* 0.5% minimum monthly APR
* \~6% minimum yearly APR

Staking remains attractive even in bear markets.

***

### **Staking APR Floor Diagram**

```
Revenue Check
     │
     ▼
┌────────────────────────┐
│ Staking APR ≥ Floor?  │──► Yes → Use Revenue
└──────────┬─────────────┘
           │ No
           ▼
┌──────────────────────────┐
│ Micro-Emission (Capped)  │
└──────────────────────────┘
```

***

## **11.4 Micro-Emission Stabilization Engine (Emergency-Only)**

If revenue cannot meet the Node or Staking floor, the system may mint **tiny, capped emergency emissions**.

#### It activates ONLY when:

* Floors cannot be met using revenue
* And emission caps have not been reached

#### It is capped at:

```
MAX_EMISSION_PER_MONTH = 0.05% of total supply
MAX_EMISSION_PER_YEAR  = 0.5% of total supply
```

This ensures emissions never threaten token value or cause dilution.

***

### **Micro-Emission Cap System Diagram**

```
        Revenue Low?
             │
             ▼
     ┌───────────────────┐
     │ Activate Floors    │
     │ Node + Staking     │
     └─────────┬──────────┘
               │ Generates
               ▼
     ┌──────────────────────────┐
     │  Micro-Emission Engine   │
     └─────────┬────────────────┘
               │
               ▼
      ┌───────────────────┐
      │ Apply Emission    │
      │ Within Monthly Cap│
      └─────────┬─────────┘
                │
                ▼
   ┌────────────────────────────┐
   │ Cap Check (0.05% Monthly)  │
   └──────────────┬────────────┘
                  │ Exceeds Cap?
            ┌─────┴──────┐
            │             │
          Yes            No
            │             │
            ▼             ▼
  ┌────────────────┐   ┌────────────────┐
  │ Halt Emission  │   │ Continue Floor │
  │ Immediately     │   │ Support       │
  └────────────────┘   └────────────────┘
```

***

## **11.5 Automatic Floor Shutdown Logic**

To prevent runaway emissions, floors **turn off automatically** when:

```
Revenue > (Node Floor + Staking Floor)
AND
APR and ROI exceed floor minimums
```

Or when:

```
Emission caps reached (monthly or annual)
```

This guarantees emissions are used *only when absolutely necessary*.

***

## **11.6 Why Floors + Safeguards Are Essential**

#### ✔ Protects node operators

Nodes require strong reward guarantees due to high capital requirements.

#### ✔ Prevents staking collapse

Consistent yield encourages holders to keep tokens locked.

#### ✔ Keeps supply dilution microscopic

Micro-emissions are hard-capped and rare.

#### ✔ Ensures ecosystem health across markets

Rewards remain stable even during volatility.

#### ✔ Controls inflation

The cap system ensures emissions can NEVER become a threat.

***

## **11.7 Summary**

Rogue AI’s reward floor system ensures:

* Predictable yields
* Network stability
* Ecosystem health
* Protection during downturns
* Minimal and controlled emissions
* Long-term sustainability

Nodes and stakers always earn reliably — without damaging token value.


---

# 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://docs.roguetrading.io/tokenomics-unabridged/reward-floors-and-stability.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.