> For the complete documentation index, see [llms.txt](https://docs.cronos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cronos.com/for-dapp-developers/cronos-smart-contract/contract-verification.md). # Contract Deployment and Verification ## Block Explorer The Cronos blockchain network is now using the new [Cronos Explorer](https://explorer.cronos.com). The Cronos Explorer URLs are as follows: * Mainnet: * Testnet: The documentation of the Cronos Explorer APIs are available at the following URLs: * Mainnet: * Testnet: ## Contract Deployment To interact with Cronos mainnet, you can use the public endpoint `https:.//evm.cronos.com` or an endpoint provided by a commercial vendor. You will need CRO in your self-custodial wallet in order to pay for transaction fees. In [this Github repository](https://github.com/kentimsit/cronos-hardhat-boilerplate), you will find a convenient example of Hardhat configuration for smart contract development on Cronos Testnet and Mainnet. Please refer to [the README.md file](https://github.com/kentimsit/cronos-hardhat-boilerplate/blob/main/README.md) for a list of frequently used commands, and to the [Hardhat documentation](https://hardhat.org) for more details. In the `hardhat.config.js` file, you will notice that we currently recommend to set the gas price at 10100000000000 wei, but please [check the Average Gas Price](https://explorer.cronos.com/charts) for a more up to date value. ## Contract Verification In order to enable users and fellow developers to do their own research, it is imperative that you publish your smart contract code on Cronos Explorer. This is called verifying your contracts. The new Cronos Explorer supports smart contract verification either through the web interface or programmatically via Hardhat (we recommend to use Hardhat). **Contract Verification Via Explorer Hardhat:** For verification via Hardhat, refer to the example provided in [this boilerplate repository](https://github.com/kentimsit/cronos-hardhat-boilerplate/blob/main/README.md). Cronos is supported by Hardhat out of the box, you just need to configure the network parameters in `hardhat.config.js` . You will need an API key. To find out how to obtain an API key, refer to the [Cronos Explorer API documentation](https://docs.cronos.com/block-explorers/block-explorer-and-api-keys#creating-account-and-getting-api-key-cronso-explorer). After the contract verification is complete, the Cronos Explorer will display details about your smart contract code like shown below.

Cronos Explorer screenshot

**Contract Verification Via Explorer interface:** For verification via the web interface, visit the following URLs: * Mainnet: * Testnet: **Contract Verification Via Remix and Explorer:** For contracts developed in Remix, developers can follow the steps below to verify them on the Explorer: 1. Compile the contract. 2. Download the JSON file under `artifacts/build-info/` , and please ensure the file follows this [format](https://docs.soliditylang.org/en/latest/using-the-compiler.html#input-description). 3. Go to the Explorer Contract Verifier introduced in the previous section, fill in the required information, upload the JSON file and verify it on Cronos Explorer. --- # 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.cronos.com/for-dapp-developers/cronos-smart-contract/contract-verification.md?ask=&goal= ``` `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.