Practical overview
When it fits
Use it when a Hardhat-based EVM project needs named deployment records shared between deployment scripts, tests and application configuration.
Who it is for
- Developers building EVM smart contracts in Hardhat projects.
- Teams that need consistent deployment records across networks and testing environments.
- Developers who want contract addresses and ABIs available for application configuration.
Documented uses
- Manage repeatable contract deployments across networks.
- Refer to deployed contracts by name in scripts and tests.
- Reuse deployments as test fixtures, with caching support.
- Export deployed contract addresses and ABIs for web applications.
- Save contract metadata for later verification submissions.
Requirements & limits
The repository identifies the project as MIT-licensed. The v2 documentation is for Hardhat 3; v1 documentation is maintained separately.
- Version 2 is documented for Hardhat 3, while v1 has separate documentation.
- The plugin uses rocketh for deployment storage and is split into modules for deployment, proxies, diamonds, transaction helpers and viem integration.
- The project README says active development and issue tracking have moved to the rocketh monorepo; the hardhat-deploy repository remains for brand and history.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Explore the browser-based deployment walkthrough
Observe four deployment-script stages for an upgradeable contract in a local EVM running in a browser tab.
Before you start
- A browser that can open the official rocketh documentation page.
Steps
Open the official rocketh documentation page.
Select **Start** in the interactive walkthrough.
Follow its four deployment steps, including proxy deployment, writing a greeting, upgrading the implementation, and writing another greeting.
Expected outcome
The walkthrough shows an EVM running in the browser, with deployed contract addresses and how an upgrade changes the implementation while preserving proxy storage.
Guide limitations
- The walkthrough runs in the browser's local EVM; it does not deploy to a network, and its state disappears when the page is reloaded.
- The example notes that upgrade implementations should append storage variables rather than reorder or insert them above existing variables.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- wighawag/hardhat-deploy · Official homepage title · retained in its source language