> For the complete documentation index, see [llms.txt](https://docs.takara.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.takara.gg/rewards-and-fees/usdtakara.md).

# $TAKARA

## What it is

A reward token. Not required to play, not a claim on revenue but a tax token whose transfer tax routes back into the machine. Details (supply, launch venue, exact tax rate) are decided at launch.

## What the tax does

A small tax on transfers accumulates in a tax wallet. It does not sit in a treasury but a keeper sweeps it back into the protocol:

{% stepper %}
{% step %}

## Read the accumulated ETH

Leave a gas reserve.
{% endstep %}

{% step %}

## Swap it to USDG

Swap it in one hop.
{% endstep %}

{% step %}

## Split the USDG actually received

* One part calls `fundJackpot()` on the Machine — growing the top prize.
* The rest calls `deposit()` on the [Bankroll Vault](broken://pages/474e83af3b874ff4c779b415e05d121083f1fc04) — deepening the house.
  {% endstep %}
  {% endstepper %}

**The jackpot leg is irreversible.** `fundJackpot` only ever adds; there is no pot withdrawal. So that money can only ever leave to a winner.

**The vault leg mints LP shares to the tax wallet.** The protocol becomes its own bankroll provider. A deeper vault is what lets the larger packs turn on and more spins run at once. There is no donate-to-LPs shortcut — the vault only counts assets that arrive through `deposit()`.

So trading volume makes the game bigger: a larger jackpot and a deeper bankroll, not a richer team.

## What $TAKARA does *not* do

Being explicit, because this is where most token projects overpromise:

* **It is not required to play.** Spins are paid in ETH. You never need to hold or buy $TAKARA.
* **It gates nothing.** No tiers, no multipliers, no holder-only packs.
* **It does not change your odds.** The table is the table, for everyone.
* **It is not a claim on revenue.** Holding it does not entitle you to protocol fees.

What it aligns is one honest thing: the more it trades, the deeper the bankroll and the bigger the jackpot and every player benefits from volume they had nothing to do with.

## Verifying it, once it's live

Every sweep is visible on chain: `JackpotFunded` on the Machine and `Deposited` on the vault. You can check the tax is doing what this page says without trusting the page.

## Addresses

|                   |                                                                                |
| ----------------- | ------------------------------------------------------------------------------ |
| $TAKARA           | — (not deployed)                                                               |
| Tax wallet        | — (pending)                                                                    |
| Bankroll Vault    | *see* [*Deployments*](broken://pages/c488ae4b2aa1173564e49fae025fe2aa821bce11) |
| Machine (jackpot) | *see* [*Deployments*](broken://pages/c488ae4b2aa1173564e49fae025fe2aa821bce11) |


---

# 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.takara.gg/rewards-and-fees/usdtakara.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.