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

# Going to mainnet

Before deploying to mainnet (chain ID `16868`):

* [ ] The same bytecode has been deployed and exercised on testnet.
* [ ] Your contracts do not rely on a [missing precompile](/differences-from-ethereum.md#precompiles).
* [ ] Fee logic reads the gas price from the network instead of assuming Ethereum-level values.
* [ ] The deployer and admin keys are separate from any key used for testing, and are held in a hardware wallet or secure keystore.
* [ ] Upgradeable contracts (UUPS / transparent proxy) have their admin and upgrade authority set to the intended owner, ideally a multisig.
* [ ] The contract has been audited if it will hold real value.

Then deploy exactly as on testnet, using the mainnet RPC:

```bash
forge create src/MyContract.sol:MyContract \
  --rpc-url https://rpc1.nagara.network \
  --account mainnet-deployer \
  --broadcast
```

Keep `https://rpc2.nagara.network` configured as a fallback RPC in your application.


---

# 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.nagara.network/going-to-mainnet.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.