> For the complete documentation index, see [llms.txt](https://docs.onyx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyx.org/developer-guide/deploying-contracts.md).

# Deploying Contracts

Deploy and verify Solidity contracts on Onyx Mainnet.

Use ordinary Solidity tooling with Chain ID `327`. Estimate gas and read the current gas price instead of pinning values copied from another network.

```javascript
import "dotenv/config";
import { JsonRpcProvider, Wallet, ContractFactory } from "ethers";
import artifact from "./artifacts/Example.json" with { type: "json" };

const provider = new JsonRpcProvider("https://rpc.onyx.org", 327);
const signer = new Wallet(process.env.DEPLOYER_PRIVATE_KEY, provider);
const factory = new ContractFactory(artifact.abi, artifact.bytecode, signer);
const contract = await factory.deploy();
await contract.waitForDeployment();
console.log(await contract.getAddress());
```

Keep private keys out of source code and shell history. After deployment, confirm `eth_getCode` is non-empty and verify the source through [Onyx Scan](https://onyxscan.org).

Onyx follows EVM execution semantics but is not required to expose every Ethereum client-specific debug or tracing extension. Test the exact RPC methods your deployment and verification pipeline needs before Mainnet use.


---

# 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.onyx.org/developer-guide/deploying-contracts.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.
