# Summary

#### Important Note – Overview vs. Protocol Constitution

This GitBook is intended to provide a **high-level, user-friendly overview** of how the <mark style="color:blue;">**FLEX**</mark> Protocol works. Its purpose is to help readers quickly understand the core ideas, mechanics, and participant flows without requiring technical background.

This documentation **does not attempt to describe every edge case, formula, or internal accounting rule** of the protocol.

For **precise definitions, exact parameters, mathematical formulas, and full technical behaviour**, readers must refer to the official <mark style="color:blue;">**FLEX**</mark>**&#x20;Protocol Technical Paper (Protocol Constitution)**.

The technical paper is the **single authoritative source of truth** for how the protocol operates on-chain. In the event of any difference between this GitBook and the technical paper, **the smart contracts and the technical paper take precedence**.

{% hint style="info" %}
The full technical specification is available at:\
👉 [**https://flexdefi.io/docs**](https://flexdefi.io/docs)
{% endhint %}

Participation in the FLEX Protocol implies acceptance of the rules as enforced by the deployed smart contracts, regardless of how they are summarised in this overview.

## **Overview**

<mark style="color:blue;">**FLEX**</mark> is a crypto protocol built around one simple idea: **long-term commitment should be rewarded more than short-term behaviour**.

Instead of encouraging fast trading, <mark style="color:blue;">**FLEX**</mark> rewards users who lock their tokens for time, stay committed, and avoid gaming the system. Everything runs automatically through smart contracts. There is no company, no admin, no governance, and no ability to change the rules after launch.

Users can participate through an initial auction phase, stake <mark style="color:blue;">**FLEX**</mark> to earn rewards, receive USDT rewards from protocol activity, and potentially get refunded through special events called Big Pay Days.


---

# 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://flexdefi.gitbook.io/flex/summary.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.