> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/develop/basics/verify-a-smart-contract.md).

# Verify a Smart Contract

Verify deployed Chiliz Chain contracts via Chiliscan (Routescan) or Chiliz Block Explorer (Blockscout), with Hardhat CLI and flattening options.

{% hint style="success" %}
After creating a smart contract, it is **necessary** to verify it.\
Only **you** can do it, and you should do it as soon as the contract is deployed.
{% endhint %}

Verifying a smart contract allows you to confirm that the contract's source code corresponds to a specific contract address on the blockchain. This is crucial for transparency and trust, especially in the decentralized world of blockchain.

Once you have deployed your smart contract on Chiliz Chain, you can verify it by using a block explorer, such as [Chiliscan](https://chiliscan.com/) (by [Routescan](https://routescan.io/)) or [Chiliz Block Explorer](https://scan.chiliz.com/) (by [Blockscout](https://www.blockscout.com/)).

{% content-ref url="/pages/QmhlZEvcZGdhu1QvIR0p" %}
[Verify with Chiliscan](/develop/basics/verify-a-smart-contract/verify-with-chiliscan.md)
{% endcontent-ref %}

{% content-ref url="/pages/uYTtcHioYwh7WkNtwSzW" %}
[Verify with Chiliz Block Explorer](/develop/basics/verify-a-smart-contract/verify-with-chiliz-block-explorer.md)
{% endcontent-ref %}

You can also verify your contract through the command line:

{% content-ref url="/pages/Utz4llTOvh55F6bXKBcP" %}
[Verify with Hardhat](/develop/basics/verify-a-smart-contract/verify-with-hardhat.md)
{% endcontent-ref %}

Note that it might be easier for you to validate your deployed smart contract using a flattened version of it. Here is how:

{% content-ref url="/pages/ECjnpYfhcIQjbbGFIK6a" %}
[Flatten a Smart Contract](/develop/basics/verify-a-smart-contract/flatten-a-smart-contract.md)
{% endcontent-ref %}

In any case, always follow the best practices!

{% content-ref url="/pages/45qDeGBAYOmk49ac0xbH" %}
[Verification Best Practices](/develop/basics/verify-a-smart-contract/verification-best-practices.md)
{% endcontent-ref %}


---

# 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.chiliz.com/develop/basics/verify-a-smart-contract.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.