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

# Tickets

Tickets are your weight in the weekly draw. They come from two things, how much you hold and how long you hold it.

Every dollar you keep in an Ample vault for a full week earns 100 tickets for that week's draw. Deposit mid-week and the week counts partially; from the next cycle onward it counts in full. Withdraw, and your weight falls from that moment. Tickets cost nothing, expire nothing, and re-accrue every cycle on their own.

### Time

If tickets were a simple snapshot of balances at draw time, the winning strategy would be to deposit five minutes before every draw and leave right after, contributing no yield to the pool everyone shares. Ample weights tickets with time instead. Your count reflects your **average balance across the whole cycle**, so the deposits that generated the week's yield are the deposits with weight in its draw.

### How tickets are calculated

Your time-weighted average balance over a cycle, and the tickets it earns.

$$\mathrm{TWAB} = \frac{1}{T}\sum\_{i} B\_i \cdot \Delta t\_i \qquad\qquad \text{tickets} = \lfloor 100 \times \mathrm{TWAB} \rfloor$$

where T is the cycle length and each balance B is weighted by the time Δt it was held, sampled at every deposit, withdrawal, and transfer, in USD terms.

As a worked example, deposit $1,000 exactly halfway through a cycle.

```
TWAB    = (0 × 3.5 days + 1,000 × 3.5 days) / 7 days = $500
tickets = 100 × 500 = 50,000 this cycle
        = 100,000 every full cycle after
```

Three rules apply on top.

* **Eligibility** requires at least 1 hour of continuous holding within the cycle.
* **Aggregation** sums balances across all your vaults in USD. One ticket count per draw, not one per vault.

### From base tickets to final tickets

The base count is then adjusted by multipliers you earn and bonuses you collect.

$$\text{final} = \lfloor \mathrm{TWAB} \times (m\_{\text{loyalty}} \cdot m\_{\text{luck}} \cdot m\_{\text{streak}} + b\_{\text{boost}}) \rfloor \times 100 + \text{bonus tickets}$$

| Input                                 | Range                                      | Explained in                                             |
| ------------------------------------- | ------------------------------------------ | -------------------------------------------------------- |
| Loyalty, luck, and streak multipliers | 1.00 to 1.91 combined                      | [Your Odds, Over Time](/docs/how-payouts-work/odds.md)   |
| Boost (best single one applies)       | campaign-defined, typically +0.10 to +0.25 | [Boosts](/docs/how-payouts-work/boosts.md)               |
| Bonus tickets                         | flat additions                             | [Bonus Tickets](/docs/how-payouts-work/bonus-tickets.md) |

Your dashboard always shows the final number, the same one the draw uses.


---

# 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:

```
GET https://ample-2.gitbook.io/docs/how-payouts-work/tickets.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.