> 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/pt-br/desenvolver/basico/verificar-smart-contract/verificar-com-hardhat.md).

# Verificar com Hardhat

Verifique smart contracts da Chiliz Chain pela linha de comando usando o plugin hardhat-verify com chaves de API do Chiliscan ou Chiliz Block Explorer.

Como a Chiliz Chain é uma rede compatível com EVM, você pode verificar seu contrato usando o plugin padrão [hardhat-verify](https://hardhat.org/docs/guides/smart-contract-verification), usando uma API de block explorer para conectar seu ambiente de desenvolvimento com o próprio blockchain.

Tanto o Chiliscan quanto o Chiliz Block Explorer fornecem documentação sobre verificação com 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>" %}

A própria documentação do Hardhat tem uma página completa sobre verificação de contratos:

{% 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/pt-br/desenvolver/basico/verificar-smart-contract/verificar-com-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.