> 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/fr/developper/notions-de-base/verifier-un-smart-contract/verifier-avec-hardhat.md).

# Vérifier avec Hardhat

Vérifiez des smart contracts Chiliz Chain en ligne de commande en utilisant le plugin hardhat-verify avec les clés API de Chiliscan ou de Chiliz Block Explorer.

Puisque Chiliz Chain est une chaîne compatible EVM, vous pouvez vérifier votre contrat en utilisant le plugin standard [hardhat-verify](https://hardhat.org/docs/guides/smart-contract-verification), en vous appuyant sur une API d'explorateur de blocs pour faire le lien entre votre environnement de développement et la blockchain elle-même.

Chiliscan et Chiliz Block Explorer proposent tous deux une documentation sur la vérification avec Hardhat :

{% embed url="<https://info.routescan.io/en/articles/11991333-deploying-and-verifying-contracts-hardhat>" %}

{% embed url="<https://docs.blockscout.com/devs/verification/hardhat-verification-plugin>" %}

La propre documentation de Hardhat contient une page complète sur la vérification de contrats :

{% embed url="<https://hardhat.org/docs/tutorial/verifying>" %}


---

# 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/fr/developper/notions-de-base/verifier-un-smart-contract/verifier-avec-hardhat.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.