> For the complete documentation index, see [llms.txt](https://docs.megalottery.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megalottery.fun/trust-and-verification/launch-status.md).

# Launch status & official links

{% hint style="danger" %}
**Pre-launch scam warning:** `0x77705c026e60df3217258F7EADf4232503640777` is the only planned production `$MEGA` address. It is not deployed and has no code. Deployment is pending. The Uniswap pair and swap link do not exist. Do not trade until the official launch.
{% endhint %}

## Deployment status

| Item                      | Status                                                                    |
| ------------------------- | ------------------------------------------------------------------------- |
| `$MEGA` token and lottery | Planned: `0x77705c026e60df3217258F7EADf4232503640777`; deployment pending |
| MEGA/WETH Uniswap pair    | Does not exist yet                                                        |
| Official swap link        | Does not exist yet                                                        |
| Verified source code      | TBD                                                                       |
| Ownership status          | TBD                                                                       |
| Keeper status             | Test deployment completed; production TBD                                 |
| Independent audit         | Not completed                                                             |

## Official channels

| Resource                   | Link                                                                                                                                     |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Website                    | [megalottery.fun](https://megalottery.fun)                                                                                               |
| X                          | [@megalotteryfun](https://x.com/megalotteryfun)                                                                                          |
| Telegram                   | [t.me/megalotteryfun](https://t.me/megalotteryfun)                                                                                       |
| Explorer                   | [Robinhood Chain Blockscout](https://robinhoodchain.blockscout.com)                                                                      |
| Planned production address | [`0x77705c026e60df3217258F7EADf4232503640777`](https://robinhoodchain.blockscout.com/address/0x77705c026e60df3217258F7EADf4232503640777) |

## Address verification checklist

Before buying:

1. Copy the token address from this page or the official website.
2. Open that exact address in Robinhood Chain Blockscout.
3. Confirm the source is verified.
4. Confirm the Uniswap pair points to the same token and WETH.
5. Confirm the constructor values match the published launch configuration.
6. Check whether ownership has been renounced or which controls remain.

Never share a seed phrase or private key. The team, keeper and contract 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 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.megalottery.fun/trust-and-verification/launch-status.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.