# Big Pay Days (BPD)

#### Big Pay Days (BPDs)

Big Pay Days are special refund events funded entirely by the auction phase. Their purpose is simple but powerful: to return USDT back to committed participants in a transparent, rule-based, and random way.

During a Big Pay Day, selected eligible addresses receive **100% of their total auction USDT contribution back**. This is a refund, not a reward, and it does not affect the participant’s <mark style="color:blue;">**FLEX**</mark> stake, rewards, or future eligibility.

To be eligible for Big Pay Days, an address must meet three conditions.\
**First**, it must have participated in the auction by contributing USDT.\
**Second**, it must have claimed its auction <mark style="color:blue;">**FLEX**</mark> **as a stake**.\
**Third**, it must **never** have claimed auction <mark style="color:blue;">**FLEX**</mark> as liquid tokens.

{% hint style="info" %}
If an address ever claims liquid FLEX from the auction, even once, it becomes permanently ineligible for all Big Pay Days. This rule is irreversible and enforced automatically by the protocol.
{% endhint %}

***

#### How Big Pay Days Work

All addresses that meet the eligibility rules are stored in a historical list. This list grows over time as more users participate in the auction and claim their <mark style="color:blue;">**FLEX**</mark> as stakes.

When a Big Pay Day is executed, the protocol requests a random number from **Chainlink VRF v2.5**, a verifiable on-chain randomness provider. This random number determines a starting position in the eligibility list.

From that starting point, the protocol begins issuing refunds sequentially through the list. Each selected address receives a refund equal to **100% of the total USDT it has ever contributed during the auction phase**.

For example, if an address contributed:

* 100 USDT on Day 5
* 200 USDT on Day 20

its total auction contribution is 300 USDT.\
When that address is selected in a Big Pay Day, it receives **300 USDT back in full**.

***

#### Limits, Fairness, and Repeated Wins

Each Big Pay Day execution processes **at least 50 refunds**. Because of this minimum, no single address can receive more than **2% of the available Big Pay Day pool** in a single execution. This prevents concentration and ensures that refunds are spread across many participants.

A single execution can process **up to 222 refunds**. If, after one execution, there is still sufficient USDT left in the Big Pay Day pool, **anyone** may trigger another execution. This process can repeat multiple times until the pool is effectively drained.

{% hint style="info" %}
Importantly, **winning a Big Pay Day does not remove eligibility**. An address remains eligible as long as the auction phase is active and the eligibility rules are still satisfied. This means the same address can receive multiple Big Pay Day refunds across different days.
{% endhint %}

In practice, an address that consistently participates in the auction and claims <mark style="color:blue;">**FLEX**</mark> as a stake may receive several full refunds over the 150-day auction period.

***

#### What Big Pay Days Are — and Are Not

Big Pay Days do not mint <mark style="color:blue;">**FLEX**</mark>, do not modify stakes, and do not affect staking rewards or share calculations. They are purely a USDT refund mechanism layered on top of the auction and staking systems.

They exist to reward commitment, discourage short-term extraction, and create a probabilistic upside for users who choose to stake their auction <mark style="color:blue;">**FLEX**</mark> instead of claiming it as liquid tokens.


---

# 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/daily-auctions/big-pay-days-bpd.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.