> For the complete documentation index, see [llms.txt](https://docs.lotrio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lotrio.app/help/faq.md).

# Frequently asked questions

Straight answers about eligibility, WIN POWER, draws, prizes, fees and safety.

## Entry and eligibility

<details>

<summary>Do I buy lottery tickets?</summary>

No. Holding enough `$LOTRIO` creates WIN POWER automatically. One whole WP requires a wallet balance of at least 10,000 `$LOTRIO` before any remaining winner deduction.

</details>

<details>

<summary>Do I stake or deposit tokens?</summary>

No. Eligible tokens remain in your own wallet. There is no lottery staking deposit.

</details>

<details>

<summary>Do I send a transaction when the timer ends?</summary>

No. The keeper handles maintenance transactions. Users enter by holding and do not trigger their own draw entry.

</details>

<details>

<summary>Is 10,000 `$LOTRIO` the purchase amount or final balance?</summary>

Final wallet balance. A buy is subject to the trading fee and market movement, so buying exactly 10,000 tokens of quoted output may leave the wallet below 1 WP.

</details>

## Draw timing and winners

<details>

<summary>Is there always a draw every 15 minutes?</summary>

Not necessarily. Fifteen minutes is the interval, but a draw also needs a pot of at least 0.05 ETH and at least three eligible wallets. Otherwise that round is skipped and the 80% fee share keeps accumulating for the next round.

</details>

<details>

<summary>How many winners are selected?</summary>

Three different wallets. The contract selects without replacement, so one wallet cannot take two places in the same draw.

</details>

<details>

<summary>Can the keeper choose winners?</summary>

No. The keeper submits public transactions and proofs. The contract derives randomness from a previously committed future blockhash and verifies every winner against the saved participant root.

</details>

<details>

<summary>Can someone buy after seeing the random seed?</summary>

They may trade, but the purchase counts only toward a later draw. The current participant snapshot is fixed before the random block exists.

</details>

## Prizes and WIN POWER

<details>

<summary>What happens if my wallet cannot receive ETH?</summary>

The failed payout is reserved in `unclaimedPrizes`. The winning wallet can later call `claim()`.

</details>

<details>

<summary>Does winning remove my tokens?</summary>

No. Winning reduces the separate live WIN POWER value by 30%, 20% or 10%, depending on place. The `$LOTRIO` balance remains in the wallet.

</details>

<details>

<summary>Does deducted WIN POWER recover?</summary>

Yes. Each deduction returns in four equal steps after 24, 48, 72 and 96 subsequently completed prize draws. That is exactly one day at the normal 15-minute cadence. Every win has its own schedule; skipped or reset draws do not count.

Recovery is automatic even if the deduction moved to another wallet with a token transfer. No recipient claim is required; a permissionless claim function exists only as a fallback if keeper processing is delayed.

</details>

<details>

<summary>Can I remove the winner deduction by transferring to a new wallet?</summary>

No. A wallet transfer moves the proportional deduction with the tokens.

</details>

<details>

<summary>What happens if I sell everything and buy again?</summary>

Selling releases the deduction proportionally. Selling the full balance clears its remaining deduction; a later taxed buy earns fresh WP from the new net balance.

</details>

<details>

<summary>Why doesn't my WIN POWER change the instant I trade?</summary>

The Pons token has no hooks, so it cannot notify the lottery directly. The keeper relays each `Transfer` event to the lottery shortly after it happens. The relay cannot set balances: the lottery always rereads your `$LOTRIO` balance from the token. Anyone can also call `syncAccount(wallet)` to refresh a wallet immediately.

</details>

## Fees and the pot

<details>

<summary>Where is `$LOTRIO` traded?</summary>

On the [Pons V2 launchpad](https://www.ponsfamily.com/launchpad). Pons deploys the token and runs its bonding curve. After 4.2 ETH is raised, the token graduates to a Uniswap V4 pool whose liquidity Pons locks permanently. There is no Uniswap V2 pair. The official token page will be linked on [Launch status & official links](/trust-and-verification/launch-status.md) at launch.

</details>

<details>

<summary>What are the trading fees?</summary>

2% on every buy and sell — a 1% Pons trading fee plus a 1% creator tax — on the bonding curve and after graduation. Wallet-to-wallet transfers pay 0%. Pons fixes the creator tax forever at launch.

</details>

<details>

<summary>Where do the trading fees go?</summary>

Pons keeps 0.3% of the trade value. The other ≈1.7% — the creator fees — is paid by Pons to the team's treasury wallet. Every 15 minutes, right before the draw, the keeper moves 80% of the creator fees accrued since the last draw from the treasury into the lottery contract (1.36% of the trade value). The remaining 20% (0.34%) stays with the team for marketing and operations.

</details>

<details>

<summary>Why does the pot on the website grow between draws?</summary>

The website shows the pot live: the ETH already in the lottery plus the 80% share of creator fees accrued since the last deposit. After graduation, Pons sweeps pool fees to the treasury at most once per hour, so the keeper pre-funds the pot from the treasury using each trade's price and reconciles when the sweep lands. The pot freezes at each draw.

</details>

<details>

<summary>Is the 80% guaranteed by a smart contract?</summary>

No, and we want to be clear about it. Pons pays the creator fees to a team wallet, and the 80% transfer into the lottery is sent by the team's keeper from that wallet. It is an operational commitment, not a rule enforced by code.

It is fully verifiable: every deposit is a `TreasuryFunded` event on the lottery contract sent from the published treasury address, and the creator fees that address earns are visible as Pons fee-escrow credits. See [How to verify the deposits](/the-lottery/tokenomics.md#how-to-verify-the-deposits).

</details>

<details>

<summary>Is there a buyback and burn?</summary>

Yes. Every committed pot is split 50% / 30% / 15% between the three winners, and the remaining 5% goes to the buyback burner contract. The burner buys `$LOTRIO` on Pons and sends every token to the dead address, so the circulating supply decreases over time.

Only the keeper can trigger the burn, so it can set a minimum output that protects the purchase against sandwich attacks. If the keeper has not burned for 7 days, anyone can. The burner has no owner and no withdraw function.

Pons also has its own optional buyback feature, which vests bought tokens to the creator over 5 years. That feature is disabled for `$LOTRIO`; the 5% buyback and burn is separate.

</details>

## Safety

<details>

<summary>Can the team withdraw the prize pool or change the odds?</summary>

No. The lottery contract has no owner, no admin and no withdrawal function. Nobody can withdraw the pot or change the odds, the payouts or the 15-minute interval. ETH leaves it only as prizes and as the 5% buyback share sent to the burner, which itself has no owner or withdraw function.

</details>

<details>

<summary>Can the team redirect the fee stream?</summary>

The creator fees are paid to the team's treasury wallet, so the team controls them until the 80% share is deposited into the lottery. As the current recipient, the treasury could also ask Pons to change the recipient; the team commits not to, and any such change is visible on-chain. Pons' own admin (a 2-of-3 Safe multisig) can queue a recipient change for any Pons token, which only takes effect after a 3-day timelock and is visible on-chain as a pending change until then.

Once ETH is inside the lottery, it can only go to winners and the burn.

</details>

<details>

<summary>Can the treasury wallet win?</summary>

No. The treasury wallet, the buyback burner, the lottery, the dead address and all Pons system contracts are permanently excluded from WIN POWER.

</details>

<details>

<summary>Has the protocol been audited?</summary>

The repository includes automated tests, an internal engineering review and a mainnet-fork rehearsal of the lottery and buyback burner against the live Pons contracts. An independent third-party audit has not been completed. Pons' own documentation describes Pons V2 as unaudited.

</details>

<details>

<summary>Where is the official contract address?</summary>

`$LOTRIO` has not launched yet. The official token address and every other production address will be published only on [Launch status & official links](/trust-and-verification/launch-status.md), [lotrio.app](https://lotrio.app) and [@lotrioapp](https://x.com/lotrioapp). Ignore addresses in replies, DMs and unofficial groups.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lotrio.app/help/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
