> 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/trust-and-verification/launch-status.md).

# Launch status & official links

The only page to trust for production addresses, verification and official links.

{% hint style="warning" %}
**Launch pending.** `$LOTRIO` has not launched on Pons V2 yet. Every production address below will be published here, on [lotrio.app](https://lotrio.app) and on [@lotrioapp](https://x.com/lotrioapp) at launch. Until then, any token or contract using LOTRIO name is not ours.
{% endhint %}

## Production addresses

Network: **Robinhood Chain mainnet** (chainId 4663). Explorer: [RobinScan (Etherscan)](https://robin.etherscan.io).

| Component                                    | Address                             |
| -------------------------------------------- | ----------------------------------- |
| `$LOTRIO` token (created by Pons)            | Not deployed — published at launch  |
| Pons bonding curve                           | Not deployed — published at launch  |
| Treasury wallet (Pons creator-fee recipient) | Not published — published at launch |
| Lottery contract                             | Not deployed — published at launch  |
| Buyback burner                               | Not deployed — published at launch  |
| Keeper / transfer relay                      | Not published — published at launch |
| Uniswap V4 pool                              | Created by Pons at graduation       |

The token will be named **LOTRIO** (symbol `LOTRIO`) with a fixed supply of 1,000,000,000, created by Pons together with its bonding curve in the launch transaction.

The treasury wallet is named as Pons' creator-fee recipient in the launch transaction. Before every draw, the keeper moves 80% of the creator fees accrued since the last draw from this wallet into the lottery contract; every such deposit is a `TreasuryFunded` event on the lottery whose `from` is the treasury address published here.

## Deployment status

| Item                                               | Status                                       |
| -------------------------------------------------- | -------------------------------------------- |
| `$LOTRIO` token on Pons                            | Pending                                      |
| Treasury wallet                                    | Published at launch                          |
| Lottery contract                                   | Pending                                      |
| Buyback burner                                     | Pending                                      |
| Keeper                                             | Pending                                      |
| Official trade link                                | Published at launch                          |
| Uniswap V4 pool                                    | Created by Pons at graduation                |
| Mainnet-fork rehearsal against live Pons contracts | Completed for the lottery and buyback burner |
| RobinScan source verification                      | Pending                                      |
| Independent audit                                  | Not completed                                |
| Pons V2 audit                                      | Pons describes V2 as unaudited               |

## Launch verification

The lottery contract and the buyback burner will be source-verified on RobinScan; until then their verification status above stays **pending**.

A read-only verification script is run against the production deployment. It fails unless:

* Pons names the published treasury wallet as the token's creator-fee recipient;
* no creator-fee-recipient change is pending on Pons;
* Pons' own optional buyback (which would vest tokens to the creator) is disabled and the creator tax is the published 1%;
* the lottery's token, transfer relay, 0.05 ETH minimum pot and 5% buyback share match the published values;
* the buyback burner is wired to the published token, curve, Pons pool and keeper operator;
* every Pons system address, the treasury wallet, the buyback burner, the lottery and the dead address are excluded from WIN POWER.

## Official channels

| Resource  | Link                                                                                                |
| --------- | --------------------------------------------------------------------------------------------------- |
| Website   | [lotrio.app](https://lotrio.app)                                                                    |
| X         | [@lotrioapp](https://x.com/lotrioapp)                                                               |
| Launchpad | [Pons V2](https://www.ponsfamily.com/launchpad) — the `$LOTRIO` token page is linked here at launch |
| Explorer  | [RobinScan (Etherscan)](https://robin.etherscan.io)                                                 |

## Address verification checklist

Before buying:

1. Copy the token address from this page or the official website.
2. Open that exact address on RobinScan (robin.etherscan.io).
3. Confirm Pons lists the same token on its launchpad.
4. Confirm Pons names the published treasury wallet as the token's creator-fee recipient, with no recipient change pending.
5. Confirm the lottery's `token()` is the same token, its `minTreasury()` is 0.05 ETH and its `buybackBurner()` is the published buyback burner.
6. Confirm `excludedFromLottery(treasury)` returns `true` on the lottery.
7. Confirm the lottery and burner sources match the published build.
8. After the first draws, confirm the lottery's `TreasuryFunded` deposits come from the published treasury wallet.

Never share a seed phrase or private key. The team, keeper and contracts never need them.


---

# 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/trust-and-verification/launch-status.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.
