> For the complete documentation index, see [llms.txt](https://cascadia.gitbook.io/gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cascadia.gitbook.io/gitbook/developers.md). # Developers Verifying smart contracts is a critical process which ensures the legitimacy, safety, and proper functioning of these digital agreements. By applying verification, you ensure that your contracts are not only well-structured but also secure from potential vulnerabilities. We will outline two prominent methods for this verification: using the [Cascadia Block Explorer](https://explorer.cascadia.foundation/) and the [Hardhat](https://hardhat.org/) development environment. Our Block Explorer is an intuitive online tool that allows for quick and easy verification of smart contracts. It's user-friendly interface and streamlined design ensures accessibility even for those new to smart contracts. In contrast, Hardhat provides a more comprehensive platform for smart contract creation and verification. As an Ethereum-based environment, it offers robust tools and integrations, favoring users seeking a more customizable approach. --- # 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://cascadia.gitbook.io/gitbook/developers.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.