Practical overview
When it fits
Use it when a Hardhat development workflow needs to verify deployed contracts on Tenderly and make them available for Tenderly debugging, simulation or readable Virtual Environment traces.
Who it is for
- Smart-contract developers working in Hardhat who want to verify contracts on Tenderly.
- Teams that want deployment-time or explicit verification connected to Tenderly debugging and simulation.
Documented uses
- Add Tenderly contract verification to a Hardhat project.
- Verify contracts automatically after deployment or through an explicit method or task.
- Choose public-network or Virtual Environment verification and configure the relevant authentication.
- Set verification visibility to public or project-only for supported configuration.
Requirements & limits
The plugin is installed from npm. Public-network verification authenticates with a Tenderly access key through the Tenderly CLI; Virtual Environment verification authenticates through the environment RPC URL and does not require an access key.
- Public-network verification is public by default; set privateVerification to keep verified contracts visible only inside the project.
- Virtual Environment source visibility follows that environment’s contract-visibility setting.
- Automatic verification is on by default; it can be disabled in favor of explicit calls or the tenderly:verify task.
- Documented automatic proxy verification applies to specified OpenZeppelin Hardhat Upgrades proxies on public networks and uses hardhat-verify configuration.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and configure the Hardhat plugin
Add the Tenderly plugin to a Hardhat project and configure a verification target.
Before you start
- A Hardhat project with a hardhat.config.ts or hardhat.config.js file.
- npm and the Tenderly account/project slugs for the plugin configuration.
- For public-network verification, the Tenderly CLI and an access key; for a Virtual Environment, its RPC URL.
Steps
Install the package with npm install --save-dev @tenderly/hardhat-tenderly.
Import @tenderly/hardhat-tenderly in the Hardhat config after the other plugin imports.
Add the tenderly configuration with the account username or organization slug and project slug.
Configure a public-network RPC and authenticate with the Tenderly CLI access key, or configure a Virtual Environment network with its RPC URL.
Expected outcome
The Hardhat project has the plugin and a configured Tenderly verification target.
Guide limitations
- This guide covers setup only; it does not run a deployment or verify a contract.
- Public-network verification requires Tenderly CLI access-key authentication; Virtual Environment verification uses the RPC URL instead.
Verify a deployed contract with the Hardhat task
Request Tenderly verification for a named contract address using the plugin task.
Before you start
- The plugin installed and configured in a Hardhat project.
- A contract name, deployed contract address and configured network.
- Tenderly authentication appropriate to the target: an access key for a public network or the Virtual Environment RPC URL.
Steps
Run npx hardhat tenderly:verify Greeter=0x... --network {network_name}, replacing the example name, address and network with the project values.
Use npx hardhat help tenderly:verify for task-specific details.
Expected outcome
The task requests verification of the specified contract on the selected network.
Guide limitations
- The task requires an existing deployed contract address.
- The source describes the command and authentication requirements but does not provide a verification result.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- Tenderly/hardhat-tenderly · Official homepage title · retained in its source language