> 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/contract-controls.md).

# Contract controls

This page separates actual owner powers from functions that do not exist.

## What the owner can do

Before ownership is renounced, the owner can:

* open trading once;
* permanently remove anti-whale wallet and transaction limits;
* set the draw interval between 1 minute and 1 day;
* set the reveal delay between 1 and 200 Robinhood L2 blocks;
* renounce ownership.

## What the owner cannot do

The reviewed contract has no owner function to:

* mint more supply;
* change buy, sell or transfer fees;
* close trading after it opens;
* blacklist wallets;
* pause wallet-to-wallet trading;
* raise or restore removed limits;
* replace the marketing recipient;
* change the 0.05 ETH minimum treasury;
* withdraw the lottery treasury;
* choose or replace winners;
* replace the committed participant snapshot;
* provide a custom random number.

## Fixed privileged addresses

The deployer, contract itself, marketing recipient, Uniswap router and registered pair have fixed system treatment for fees, limits or lottery eligibility. The contract does not expose a general-purpose function for adding arbitrary wallets to those exclusions.

## Operational dependencies

| Dependency        | If unavailable                                                         |
| ----------------- | ---------------------------------------------------------------------- |
| Keeper            | Draws are delayed until a valid public transaction advances them       |
| RPC provider      | Website data or keeper transactions may be delayed                     |
| Uniswap liquidity | Trading and buyback execution may suffer or fail                       |
| Frontend hosting  | Contract remains on-chain, but the normal interface may be unavailable |

## Main risks

* Smart-contract testing cannot prove that no defect exists.
* Future-blockhash randomness is weaker than dedicated VRF.
* Thin liquidity can produce severe price impact.
* Internal fee swaps and buybacks may experience slippage or MEV.
* The token may become illiquid or lose all value.
* Timing controls remain with the owner until ownership is renounced.

{% hint style="warning" %}
The repository contains an internal engineering review and automated tests. This is not an independent third-party audit or formal verification.
{% endhint %}


---

# 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/contract-controls.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.