> For the complete documentation index, see [llms.txt](https://docs.filecoin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filecoin.io/build-on-filecoin/verification.md). # Contract verification Verify smart contracts on Filecoin using development frameworks or block explorer interfaces. Contract verification lets users inspect the source code of deployed contracts and confirm they work as intended. This section covers how to verify contracts through both development tools and web interfaces. ## Table of contents * [Verify using Hardhat](/build-on-filecoin/verification/hardhat.md) — automate verification from your Hardhat development environment * [Verify using Foundry](/build-on-filecoin/verification/foundry.md) — automate verification from your Foundry development environment * [Verify using Blockscout](/build-on-filecoin/verification/blockscout.md) — verify contracts through the Blockscout web interface * [Verify using Filfox](/build-on-filecoin/verification/filfox.md) — verify contracts through the Filfox web interface --- # 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.filecoin.io/build-on-filecoin/verification.md?ask=&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.