hardhat.org valid

Hardhat 3

Hardhat is a development environment for Ethereum and EVM-compatible blockchains.

For agents: Hardhat 3 development environment docs for writing, testing, deploying and verifying smart contracts on Ethereum and EVM chains.

ethereumsmart contractsevmsolidity testingblockchain deployment

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T04:33:37.576Z. Cached copy · Source on hardhat.org

# Hardhat 3

> Hardhat is a development environment for Ethereum and EVM-compatible blockchains.
> It helps developers compile, deploy, test, and debug Solidity smart contracts.
> Solidity is the primary programming language for writing smart contracts on Ethereum.
>
> This documentation covers Hardhat 3, the latest major version.
> The docs are organized into sections: core Hardhat usage, Hardhat Ignition
> (a declarative deployment system), migration guides from Hardhat 2,
> and a plugin development guide.


## Hardhat 3
- [Getting started with Hardhat 3](https://hardhat.org/docs/getting-started.md): Get started using Hardhat 3
- [Hardhat 2's documentation](https://hardhat.org/hardhat2.md): Documentation for Hardhat 2, the previous version of Hardhat

### Hardhat 3

- [What's new in Hardhat 3](https://hardhat.org/docs/hardhat3/whats-new.md): What's new in Hardhat 3
- [Migrate to Hardhat 3](https://hardhat.org/docs/hardhat3/migration.md): How to migrate to Hardhat 3

### Tutorial

- [Hardhat 3 Tutorial](https://hardhat.org/docs/tutorial.md): Hardhat 3 Tutorial - Introduction
- [Setting up a Hardhat project](https://hardhat.org/docs/tutorial/setup.md): Hardhat 3 Tutorial - Setting up a project
- [Writing and testing a Solidity contract](https://hardhat.org/docs/tutorial/writing-and-testing.md): Hardhat 3 Tutorial - Writing and testing a Solidity contract
- [Using an assertions library](https://hardhat.org/docs/tutorial/assertions-library.md): Hardhat 3 Tutorial - Using an assertions library
- [Writing fuzz tests in Solidity](https://hardhat.org/docs/tutorial/fuzz-tests.md): Hardhat 3 Tutorial - Writing fuzz tests in Solidity
- [Using a Hardhat plugin](https://hardhat.org/docs/tutorial/plugins.md): Hardhat 3 Tutorial - Using a Hardhat plugin
- [Writing TypeScript tests](https://hardhat.org/docs/tutorial/typescript-tests.md): Hardhat 3 Tutorial - Writing TypeScript tests
- [Measuring test coverage](https://hardhat.org/docs/tutorial/coverage.md): Hardhat 3 Tutorial - Measuring test coverage
- [Deploying a contract](https://hardhat.org/docs/tutorial/deploying.md): Hardhat 3 Tutorial - Deploying a contract with Hardhat Ignition
- [Using Configuration Variables](https://hardhat.org/docs/tutorial/configuration-variables.md): Hardhat 3 Tutorial - Using Configuration Variables
- [Verifying a contract](https://hardhat.org/docs/tutorial/verifying.md): Hardhat 3 Tutorial - Verifying a contract on Etherscan
- [Learn more](https://hardhat.org/docs/tutorial/learn-more.md): Hardhat 3 Tutorial - Learn more about Hardhat

### Guides

- [Verifying smart contracts](https://hardhat.org/docs/guides/smart-contract-verification.md): How to verify a smart contract
- [Managing config values and secrets safely](https://hardhat.org/docs/guides/configuration-variables.md): How to manage config variables and secrets safely
- [Writing Hardhat tasks](https://hardhat.org/docs/guides/writing-tasks.md): How to write custom Hardhat tasks with Hardhat 3
- [Writing scripts with Hardh
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=hardhat.org · GET /v1/domain/hardhat.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for hardhat.org:
1. POST https://agentwebmap.com/v1/sites/hardhat.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://hardhat.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/hardhat.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/hardhat.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.